Fresh Slack 10 install::Can't modprobe...insmod failing.

kersten78 · 11-04-2004, 04:44 PM

Hey everybody, I started a thread about this a while ago and didn't get any response...I'm trying again, as I can't figure out the problem and it's driving me batty.

I just did a fresh install of slack 10 on an old sony vaio laptop. I have ndiswrapper "working" with (read recognizing) a D-Link pcmcia card, but I can't get it to modprobe. Actually, I can't really get anything to modprobe--I get errors about insmod failing, no such device with sonypi.0.gz, etc. Here's the errors:

Code:

/lib/modules/2.4.26/kernel/drivers/char/sonypi.o.gz: init_module: No such device
/lib/modules/2.4.26/kernel/drivers/char/sonypi.o.gz: 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
/lib/modules/2.4.26/kernel/drivers/char/sonypi.o.gz: insmod /lib/modules/2.4.26/kernel/drivers/char/sonypi.o.gz failed
/lib/modules/2.4.26/kernel/drivers/char/sonypi.o.gz: insmod ndiswrapper failed

I don't think this is an IO or IRQ issue as lspci shows the card, and ndiswrapper -l shows that the hardware is present. Also, pcmcia seems to be configured correctly, as wired pcmcia ethernet works fine, and the D-Link card's power led is lit.
I've tried googling sonypi.o.gz. I'm thinking the init_module error there may be the root of my problem--but I haven't figured anything out yet.
Why would modprobe ndiswrapper attempt to load the sonypi.o.gz module before loading ndiswrapper?
If anyone has any ideas, I'd really appreciate the help...I'm stumped.

carboncopy · 11-06-2004, 11:01 PM

Why not compile the drive into the kernel instead of using modules?

ViN86 · 11-07-2004, 12:07 PM

i use modprobe instead of insmod. i just find it easier for slack to load all the necessary modules with the one i want to load.

if youre gettin errors, then these are probably the following problems:

1. IRQ conflicts
2. the module does not exist
3. the component the module supports is not recognized by the OS

i would just try compiling a new kernel and adding module support for whatever you need. then the modules will be loaded on startup, and you know they are included. if you have problems still, its probably a problem with the hardware.

scottman · 11-07-2004, 12:16 PM

If you get those messages at boot time, they may be happening when
your init scripts load /etc/rc.d/rc.modules. As far as the sonypi.o.gz
kernel modules that is failing to load, documentation for my 2.4.26 Slack 10
system can be found in /usr/src/linux-2.4.26/Documentation/sonypi.txt.
It seems like it's a driver specific to your system. If it's not in the path
shown in the errors, you might want to recompile your kernel to add it as
a module, or at least check that it's compiled statically. To see if that drivers working the following could check for the device it's supposed to create.
#ls /dev/sonypi

That's about all I can come up with, I also have a related question. Carboncopy, you touched on it. How would I compile an external module
statically into a kernel? Like ndiswrapper for instance, how would add that
into a kernel at compile time, rather than use it as a module?