This happens when you tick "Install updates" during installation of the
system. The installer first places the bootloader for current kernel at
BIOS; but if the "Install updates" was ticked, the system installs the
newer version of kernel and, apparently, does not the old one.

For example, the module on my Live CD was "generic-module-2.6.35".
During installation I ticked for automatic updates, which resulted in
the installer downloading a newer version. The bootloader, however was
not updated. Hence its showing the "No such file or directory" message.

The error message is not fatal, but inconvenient as it cripples the
aesthetics. To fix this I had to go an extra mile and reinstall the
system, but this time with automatic updating switched off.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/642421

Title:
  Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to