inti
2003-11-13, 12:38 PM CST
Hi. Anyone else have this problem? Running FC1 on a Sony Vaio laptop and pcmcia support seems to be broken.
pcmcia works with RH9 kernel 2.4.20-20.9, by the way. If I reboot with that kernel the yenta_socket module loads fine, even though I get the same IRQ error message.
Below is the output from insmod and the relevant info from dmesg.
Any ideas?
Matt
--------------------------
[inti@gobi] sudo insmod yenta_socket
Using /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/pcmcia/yenta_socket.o
/lib/modules/2.4.22-1.2115.nptl/kernel/drivers/pcmcia/yenta_socket.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
------------------------
[inti@gobi] sudo dmesg
<snip>
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: No IRQ known for interrupt pin A of device 01:02.0.
PCI: No IRQ known for interrupt pin B of device 01:02.1.
ds: no socket drivers loaded!
<snip>
pcmcia works with RH9 kernel 2.4.20-20.9, by the way. If I reboot with that kernel the yenta_socket module loads fine, even though I get the same IRQ error message.
Below is the output from insmod and the relevant info from dmesg.
Any ideas?
Matt
--------------------------
[inti@gobi] sudo insmod yenta_socket
Using /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/pcmcia/yenta_socket.o
/lib/modules/2.4.22-1.2115.nptl/kernel/drivers/pcmcia/yenta_socket.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
------------------------
[inti@gobi] sudo dmesg
<snip>
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: No IRQ known for interrupt pin A of device 01:02.0.
PCI: No IRQ known for interrupt pin B of device 01:02.1.
ds: no socket drivers loaded!
<snip>