It works for me (2.6.19-rc4-git7). The pre-required steps now to make the modem
function of my pcmcia card usable are :
- prevents the network driver from being loaded (install 3c589_cs /bin/true in
modprobe.conf), else there's irq conflict between network and modem function
(see following log, "pcmcia: request for exclusive IRQ could not be fulfilled")
- manually load the CIS file via sysfs (cat /lib/firmware/3CXEM556.cis >
/sys/class/pcmcia_socket/pcmcia_socket0/cis), altough the CIS has already been
loaded by the network driver from another code path (see following log too, "ds:
trying to load firmware 3CXEM556.cis").
I'm wondering if the setup process could be somewhat automatized via the generic
udev rules (does it make sense to blacklist this card in pcmcia-check-broken-cis
for example ?)
It works for me (2.6.19-rc4-git7). The pre-required steps now to make the modem
function of my pcmcia card usable are :
- prevents the network driver from being loaded (install 3c589_cs /bin/true in
modprobe.conf), else there's irq conflict between network and modem function
(see following log, "pcmcia: request for exclusive IRQ could not be fulfilled")
- manually load the CIS file via sysfs (cat /lib/firmware/ 3CXEM556. cis > pcmcia_ socket/ pcmcia_ socket0/ cis), altough the CIS has already been
/sys/class/
loaded by the network driver from another code path (see following log too, "ds:
trying to load firmware 3CXEM556.cis").
I'm wondering if the setup process could be somewhat automatized via the generic check-broken- cis
udev rules (does it make sense to blacklist this card in pcmcia-
for example ?)