I have the same problem. I upgraded my potato machine yesterday. I had a bunch of unresolved symbols. I did a update-modules. Now my machine is complaining about /etc/modules.conf being older than /lib/modules/2.2.5/modules.dep. Somehow, the depmod -a from init.d script seems to be not writing the modules.dep. When I run depmod -a manually, the modules.dep gets created. Next time, I boot, there is a old modules.dep in my /lib/modules.
Any clues. Regards, Vaidhy On Mon, Oct 25, 1999 at 01:36:18AM -0700, George Bonser wrote: > > Well, I THINK it is modutils that is causing the problem. Two machines, > both upgraded yesterday. Now neither one can properly depmod. All modules > report unresolved symbols and refuse to load. > > NOTE this only affects kernel compiled after the upgrade so it could be a > libc or ldso issue, not sure what changed in the past few days. > > Old kernels that were working before the upgrade still work. Kernels built > after the upgrade are broken. > > > George Bonser > > "When someone annoys you, it takes 32 muscles to frown, but it only > takes 4 muscles to extend your arm and smack them in the head." > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
