modprobe: FATAL: could not load /lib/modules/2.6.28-11-generic/modules.dep: No such file or directory (LIES!) then ubuntu boots fine

[khamil8686]

When i boot i get these errors
[1.572014] ata1: Softreset failed (device not ready)
[2.792017] ata3: Softreset failed (device not ready)
modprobe: FATAL: Could not load /lib/modules/2.6.28-11-generic/modules.dep: No such file or directory

and then ubuntu boots fine! the file modules.dep also exists! weird. anyways i think this is related to a problem i have where i can suspend fine just once but then when i resume gnome-power-manager puts a plug icon in my tray that says "Unable to get data..." and then wont allow me to suspend again! another weird side effect is if i log out and log back in, it freezes and says unable to initialize HAL! ive tried killall gnome-power-manager, gets rid of the icon, not the problem :P and ive tried sudo service hal restart and it gets rid of the icon but then when i try to suspend again it attempts to suspend but freezes showing a screen full of text and never shuts off the fans or power or anything, anyways any help would be apprecited to get rid of the error on boot, or the problem with gnome-power-manager :)

oh, im using ubuntu jaunty jackalope 9.04 64-bit, i have another partition as my main os right now which is ubuntu 8.10. this problem persists after a clean install of jaunty

thank you for any help! :)

[dk75 (amidk75)]

possible workaround http://ubuntuforums.org/showpost.php?p=7312473&postcount=5

[Kevin Ingolfsland (kevin-ingolfsland)]

I get this same error message (although w/ ata1 and ata5) on a fresh install of Jaunty 32-bit. I have 3 external USB drive enclosures with 5 drives in them that are not being recognized. The drives are not recognized. Once Ubuntu boots, if I unplug the usb cable and reconnect the drives will be detected and mounted.

[khamil8686 (khamil8686)]

i randomly stumbled upon a way to get rid of that modprobe error

http://ubuntuforums.org/showthread.php?t=1162619

Kevin ->
Those 3 external drives might not show up because you have a setting in your bios which doesnt let the bios scan for usb drives and boot off usb drives. i have an option in my bios which enables or disables recognization of usb devices so the bios can attempt to boot off of them. im not a linux expert, been using ubuntu for several months, close to half a year but this is my guess as to what happens :) if you can take the usb plugs out and then reinsert them that says ubuntu is recognizing usb drives and probably something more hardware related isnt recognizing the usb devices at startup, which points to bios :P hopefully this helps you out :) send me a message if you have any questions! i sent you an email with my email because i dont know if launchpad allows sending of messages between users, i just got your email off a notification that someone posted on this thread

modprobe error ->
not really sure why it happens, but i assume its something to do with the initramfs (initial ram filesystem?)
your filesystem hasnt been mounted before this file is searched for so it searches the initramfs instead of the filesystem for the file. i unno if thats a normal thing or what, its odd that everything boots up fine afterwards. maybe it just searches for the file, issues a error, the filesystem is mounted, then its searched for again and finds it
not sure hot to solve the modprobe errors, im saving up for a new motherboard and such so i can install jaunty, ive been using 8.10 for a long time and its worked perfectly, i dont goto jaunty because the switch to using pmutils instead of ususwp i believe isnt compatible with my motherboard so i cant suspend, i usually turn my comp on in the morning and suspend it all day because i come back to search for stuff randomly or girlfriend needs to use the computer or whatever. i dont wanna leave it on all day, i like to be as green as possible :)

[khamil8686 (khamil8686)]

typo: not sure how to get rid of modprobe errors should read not sure how to get rid of softreset failed errors :P

[Kevin Ingolfsland (kevin-ingolfsland)]

After the last package updates I no longer get these errors and my drives are recognized automatically on boot.

[Colin Watson (cjwatson)]

I don't quite understand. You've filed this against an installer component; are you getting this error on installation? But then you talk about booting and it sounds as though you already have an installed system ...

[khamil8686 (khamil8686)]

this bug was fixed with some kernel upgrades, i did have it installed
already but wasnt sure what to file it under :)

Please consider the environment before printing this email!

Colin Watson wrote:
> I don't quite understand. You've filed this against an installer
> component; are you getting this error on installation? But then you talk
> about booting and it sounds as though you already have an installed
> system ...
>
>