hoffman:/root# modprobe ds
/lib/modules/2.4.12-scv/kernel/drivers/pcmcia/ds.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.12-scv/kernel/drivers/pcmcia/ds.o: insmod /lib/modules/2.4.12-scv/kernel/drivers/pcmcia/ds.o failed
/lib/modules/2.4.12-scv/kernel/drivers/pcmcia/ds.o: insmod ds failed
hoffman:/root# dmesg | tail -1
ds: no socket drivers loaded!
This is on a Dell Inspiron 4000 FWIW. I'm using 2.4.12-ac3, but had
exactly the same problem with plain 2.4.9 and every other 2.4 kernel I've
tried.
I've put my .config, and output from a few other commands at:
http://sam.vilain.net/no-socket/
Any ideas?
Sam.
"Jesse W. Asher" <[email protected]> wrote:
> Sam, did you ever figure out what was causing this? I'm having the
> exact same problem and ran across your post from October. Any
> information you gathered would be appreciated!! Thanks!!
Yep. I said "Y" rather than "M" to the questions under "general
setup"..."PCMCIA/CardBus support" that applied to me. The "sockets" it
refers to would be provided by either the cardbus support, or one of the
PCMCIA bridges.
I probably could have got away with the appropriate modprobe command, but
it seems to be out of fashion these days to include the name of the module
a kernel configuration option compiles to in the help text for that
option.
Sam.
cc:ed to the list for the benefit of people searching the net for this
problem ;)