The fix is to run "depmod -a". I forget which FM that was in, becauseQuote:>Ok I'm an extream nubbie. I get "/lib/modules/2.2.14/modules.dep is
>older than modules.conf.
>This has happened after alot of changes when I was trying to install a
>I would like to just be pointed to the right info. I don't mind the
>rtfm, I just don't know which one to read. Please help.
BTW, it's not a good idea to be running as root unless it's really
necessary. The rule is, "If you can do it as a normal user, then do so."
Posting to Usenet is certainly a normal-user thing....
Matt G / Dances With Crows \###| Programmers are playwrights
There is no Darkness in Eternity \##| Computers are lousy actors
But only Light too dim for us to see \#| Lusers are vicious drama critics
(Unless, of course, you're working with NT)\| BOFHen burn down theatres.
Just upgraded my RH6.2 box to kernel 2.2.18 (in conjunction with
applying vpn masq patch). Now I notice that it complains about
conf.modules, so I renamed this to conf.modules.old and made a copy as
modules.conf. Now it complains that modules.conf is newer than
modules.dep. And, in any case, it doesn't seem to load my modules
(specifically 3c509.o for ethernet).
My present workaround is just to manually invoke this module (modprobe
3c509) and restart /etc/rc.d/init.d/network (as well as dhcpd and
named), but I know there's gotta be a "Right Way" of doing this.
What's different between 2.2.18 and my old kernel (2.2.14-5.0) in
terms of handling these files? And, more importantly, how do I
correct this situation? Many thanks, in advance.