On Thu, Nov 11, 1999 at 02:58:41PM +0100, Mesman, Ben wrote:
> > I have the same card, upgrade your kernel to >= 2.2.13.
> > It fixed my problem.
>
> Ok, I upgraded, but the problem persists. Also the xircom driver development
> list at
>
> http://hyper.stanford.edu/HyperNews/get/pcmcia/xircom.ht
On Thu, Nov 11, 1999 at 02:58:41PM +0100, Mesman, Ben wrote:
> > I have the same card, upgrade your kernel to >= 2.2.13.
> > It fixed my problem.
>
> Ok, I upgraded, but the problem persists. Also the xircom driver development
> list at
>
> http://hyper.stanford.edu/HyperNews/get/pcmcia/xircom.ht
I also have a Xircom card, it's a CE3B. Initially it dindn't work with
kernel 2.0.36. Then I added a patch to the driver source file and it
worked. When I upgraded to kernel 2.2.10, it didn't work with the new
PCMCIA package. What I did was to use the old patched source file in the
new PCMCIA packa
I also have a Xircom card, it's a CE3B. Initially it dindn't work with
kernel 2.0.36. Then I added a patch to the driver source file and it
worked. When I upgraded to kernel 2.2.10, it didn't work with the new
PCMCIA package. What I did was to use the old patched source file in the
new PCMCIA packa
> I have the same card, upgrade your kernel to >= 2.2.13.
> It fixed my problem.
Ok, I upgraded, but the problem persists. Also the xircom driver development
list at
http://hyper.stanford.edu/HyperNews/get/pcmcia/xircom.html
did not contain a solution. Anyone else have a suggestion? Maybe just a
> I have the same card, upgrade your kernel to >= 2.2.13.
> It fixed my problem.
Ok, I upgraded, but the problem persists. Also the xircom driver development
list at
http://hyper.stanford.edu/HyperNews/get/pcmcia/xircom.html
did not contain a solution. Anyone else have a suggestion? Maybe just a
6 matches
Mail list logo
