Dave, I would have thought that re-running the "depmod -a" command would have fixed this. Oh well...
Mark Post -----Original Message----- From: Dave Myers [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 2002 5:23 PM To: [EMAIL PROTECTED] Subject: Re: Couple of problems with RedHat LOADER install After I got the "instoco dasda1" to run ok... I did not have an "eth0" device activated when I booted the new system. I did an lsmod command and saw that the lcs.o mod was not loaded. So..I did an insmod /lib/modules/2.4.9-17tape/kernel/drivers/s390/net/lcs.o and it loaded the driver, but it gave me a msg saying that I was "tainting" the kernel?? Then I issued an "ifup eth0" and I had my eth0 device!! After next boot, I was back to no eth0 device, so I added the lcs.o mod to /lib/modules/2.4.9-17tape/kernel/net/ directory Rebooted and ....I had my eth0 device!! I read the man page on "modules.conf" and looked for the default path it searches for modules it says path[boot]=/lib/modules/boot path[toplevel]=/lib/modules/`uname -r` path[toplevel]=/lib/modules/`kernelversion` path[toplevel]=/lib/modules/default path[toplevel]=/lib/modules ...but I still don't under stand why it's looking in /lib/modules/2.4.9-17tape/kernel/net for the lcs.o mod and not in /lib/modules/2.4.9-17tape/kernel/drivers/s390/net ????? Ah...learning linux is fun...but....tedious at times... Dave
