Check your lilo.conf and make sure you are booting the 2.2.17 kernel. If you need to modify it, you need to run /sbin/lilo again to make the changes to your MBR. > -----Original Message----- > From: Brady Hegberg [mailto:bradyh at bitstream.net] > Sent: Friday, April 06, 2001 5:08 PM > To: tclug-list at mn-linux.org > Subject: Re: [TCLUG] modprobe eth0 fails after kernel upgrade > > > I installed the newest version of modutils but now when I do > a "depmod -a" > I get > > depmod: *** Unresolved symbols in > /lib/modules/2.2.17-14/block/DAC960.o > ... > and so on for every module in every directory. > > Hmmm...I just checked dmesg and it says "Linux version > 2.2.5-15..." but all > the files in my /boot directory say 2.2.17-14. This is very > confusing. > > >The dependencies have to be up to date. The usual symptom > for the wrong > >version of modutils tends to be "unresolved symbols". Try > the depmod -a > >instruction and then load your modules and see what happens. > > > >Tom Veldhouse > >veldy at veldy.net > > > >----- Original Message ----- > >From: "Austad, Jay" <austad at marketwatch.com> > >To: <tclug-list at mn-linux.org> > >Sent: Friday, April 06, 2001 2:11 PM > >Subject: RE: [TCLUG] modprobe eth0 fails after kernel upgrade > > > > > > > He's probably using an old version of modutils. Upgrade > your modutils > > > package to be sure that it looks at modules.conf (conf.modules is > > > depricated), and that it parses the file correctly. > > > > > > Jay > > > > > > > -----Original Message----- > > > > From: Troy Johnson [mailto:Troy.A.Johnson at state.mn.us] > > > > Sent: Friday, April 06, 2001 12:00 PM > > > > To: tclug-list at mn-linux.org > > > > Subject: Re: [TCLUG] modprobe eth0 fails after kernel upgrade > > > > > > > > > > > > Just a few more details: > > > > > > > > Which RPMs were installed for the kernel upgrade (list 'em)? > > > > Where was 3c59x.o found? > > > > > > > > If I am not mistaken, "3c59x" is the name of the module, and > > > > "3c59x.o" is the object file that contains this module. I > > > > think the modules.conf syntax is correct, and if modprobe > > > > could find the "3c59x.o" file it would load it (if it is > > > > compiled for this kernel, but I think it would give you a > > > > different message if that were the problem here). > > > > > > > > >>> bradyh at bitstream.net 04/06/01 11:37AM >>> > > > > I'm using Redhat 6.0 and I upgraded my kernel to 2.2.17 using > > > > Redhat's RPMs > > > > but now I get a message in my log that says: > > > > > > > > modprobe: can't locate module eth0 > > > > > > > > My modules.conf file has this line: > > > > > > > > alias eth0 3c59x > > > > > > > > I searched for the 3c59x file with no luck - though I did > > > > find the 3c59x.o > > > > file. > > > > What should I do? > > > > > > > > Thanks, > > > > Brady > > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list >