Boot errors upgraded Ubuntu 10.10, mod probe: FATAL: could not load /lib/modules/2.6.35-22-generic/modules.dep

Asked by James B. Murphy

Hello,

I have been running 10.04 for about 5 months without any problems.

Yesterday I upgraded to 10.10 without a hitch, except:
When the install process re-booted my machine I noticed the following errors (both identical)
----------------------------------------------------------------------------------------------------------------------------------
mod probe: FATAL: could not load /lib/modules/2.6.35-22-generic/modules.dep
no such file or directory

mod probe: FATAL: could not load /lib/modules/2.6.35-22-generic/modules.dep
no such file or directory
-----------------------------------------------------------------------------------------------------------------------------------
After approx 10 seconds the screen clears and the system boots okay and as far as I can tell (I have not checked everything)
10.10 is working.....

Follow-up

One person suggested:
Booting to Recovery Mode.........., but I am unable to accomplish this task ?????
I only see the grub prompt occassionally and the esc buttom doesn't allow me to login or issue the command

However, I looked at the suspect file and noticed the following:

Other .dep files in the same directory have a header/descriptor record beginning with a "#"

the modules.dep file, referred to in the error message does not have a header record????

I tried issuing the "$ sudo depmod -a" command in the terminal mode. I appears to complete without error,
however, on reboot none of the original symptoms/errors have changed?

I tried to run the modprobe command and got the same error message.............

I still see some (~5) messages which appear on shutdown, but each time they are different?????

HELP.....
& Thanks,

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Boot to root recovery mode and run:

sudo depmod -a

Should fix it

Can you help with this problem?

Provide an answer of your own, or ask James B. Murphy for more information if necessary.

To post a message you must log in.