Quote:
Originally posted by egag
can you try " modprobe " instead of " insmod " ?
egag
|
Do you mean "insmod" instead of "modprobe"? I used modprobe...
I did a bit of reading about modprobe and found its basically a wrapper around insmod. I tried to use insmod instead (so I could see the default operation, and also to try and 'force' it to work with a -f flag), and I got the exact same error, except it was only the first two lines instead of all 4 from the failed output above.
I tried it by default, and also with the -f flag, like so:
Code:
$ insmod 3c59x
errors output here...
$ insmod -f 3c59x
errors output here...
I also tried removing the module with rmmod in case it was loaded in some sort of failed state, but this was not the case. It seems like an error occurs in my /var/log/syslog when the server tries to load this module (probably for my processor...):
Code:
Jul 23 ...: insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: init_module: Device or resource busy
Jul 23 ...: insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: Hint: insmod errors can be caused by incorrenct module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jul 23 ...: insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: insmod amd768_rng failed
Jul 23 ...: kernel: amd768_rng: cannot register misc device
I pointed this out, because it appears in my log file just before the insmod call to load my NIC driver happens. Looking more at the syslog file, these 3 things happen when my system boots:
Code:
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/net/3c59x.o: insmod 3c59x failed
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/usb/usbcore.o: insmod usb-ohci failed
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: init_module: Device or resource busy
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: init_module: Device or resource busy
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: Hint: insmod errors can be caused by incorrenct module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/char/amd768_rng.o: insmod amd768_rng failed
Jul 23 15:59:56 hostname kernel: amd768_rng: cannot register misc device
Jul 23 15:59:56 hostname insmod: /lib/modules/2.4.29/kernel/drivers/net/3c59x.o: insmod 3c59x failed
The weirder thing is, this data keeps repeating in the logfile (at the same timestamp), like 6-8 times with nothing but those error messages looping until the output from that timestamp stops and it looks like a new reboot happens, where it starts all over again.
I actually just talked to my boss and he told me if I get him something to work on over the next few hours, he'll give me alot more free time to get the server working. I think I _need_ to recompile my kernel to at least load support for USB, _MY PROCESSOR(S)_ and native support for this 3c59x driver.
I appreciate any extra help in this thread, but odds are I'll need to recompile the kernel over the next day or 2, so keep on the lookout for my "kernel recompile errors" thread