Any suggestions of things I could try to help pinpoint the problem and
let you know the results? Everything was fine before 2.4.1.
I've been using the pcmcia-cs without kernel pcmcia support up until it
didn't work with 2.4.1, then I tried using the kernel pcmcia and no deal
there either.
As
> I have a Dell Inspiron 8000. Trying to use pcmcia with kernel
> (yenta_socket) or pcmcia-cs only causes pcmcia card to take irq 11,
> which my eth device is on also. This didn't happen with 2.2 or 2.4.0
> kernels.
Sharing a PCI irq is legal, so that isnt the cause. It could be that the
irq
Upgrading from 2.2.18 and 2.4.0 to 2.4.1-ac15 broke pcmcia.
I have a Dell Inspiron 8000. Trying to use pcmcia with kernel
(yenta_socket) or pcmcia-cs only causes pcmcia card to take irq 11,
which my eth device is on also. This didn't happen with 2.2 or 2.4.0
kernels.
What param would I pass
Upgrading from 2.2.18 and 2.4.0 to 2.4.1-ac15 broke pcmcia.
I have a Dell Inspiron 8000. Trying to use pcmcia with kernel
(yenta_socket) or pcmcia-cs only causes pcmcia card to take irq 11,
which my eth device is on also. This didn't happen with 2.2 or 2.4.0
kernels.
What param would I pass
I have a Dell Inspiron 8000. Trying to use pcmcia with kernel
(yenta_socket) or pcmcia-cs only causes pcmcia card to take irq 11,
which my eth device is on also. This didn't happen with 2.2 or 2.4.0
kernels.
Sharing a PCI irq is legal, so that isnt the cause. It could be that the
irq routing
Any suggestions of things I could try to help pinpoint the problem and
let you know the results? Everything was fine before 2.4.1.
I've been using the pcmcia-cs without kernel pcmcia support up until it
didn't work with 2.4.1, then I tried using the kernel pcmcia and no deal
there either.
As
6 matches
Mail list logo