Joe Morris (NTM) wrote:
Ed McCanless wrote:
Joe Morris (NTM) wrote:
Carl Hartung wrote:
One more thing: Before attempting this procedure, you might want to first boot the system using your installation media (DVD/CD) and select 'Boot installed system' to ensure the appropriate environment has been established for installing the updates.
If that would work then I believe it indicates a grub problem and not a kernel problem.
Thanks for the input, Joe; Booting as Carl suggested did work. I had lucked into that solution before contacting the list. But how would that apply to all the missing modules (I got a message saying there might be some missing) and the "FATAL:"messages in the message log?
There are many possibilities. You could try running as root depmod -a and see if there is any errors. This is normally checked and run if needed in the boot scripts. Maybe it modified your modprobe.conf or associated config files to start some bogus hardware. What does uname -r give you? That would tell you which kernel you are booting with. Maybe it did not replace the old kernel, or maybe it goofed up on installing the delta and only part of the kernel was installed. I would need more info to nail it down to something more specific.
Ran depmod -a WARNING: Couldn't open directory /lib/modules/2.6.16.13-4-default: No such file or directory FATAL: Could not open /lib/modules/2.6.16.13-4-default/modules.dep.temp for writing: No such file or directory Ran uname -r 2.6.16.13-4-default Will wait for more input, before trying "repair installed system" --ED--