linux-image-2.6.24-16-generic not booting on my Dell Inspiron 530

[Bryan Siegfried]

Binary package hint: linux-image-2.6.24-16-generic

I have a Dell 530n, one of the ubuntu Dells that Dell was selling last summer. I had a fresh install of Kubuntu Gutsy on it, which I upgraded about a month ago through the update-manager -d process. The problem I instantly had was that the computer would refuse to boot with the 2.6.24-16-generic kernel. However, I could still boot into the old 2.6.22 gutsy kernel and everything seems to be working OK. When the beta came out, I thought I would simply do a fresh install, but the beta cd refused to boot my computer, even despite the CD's own check process being fine.

I think there must me something wrong between my computer's hardware and the 2.6.24 kernel. I have looked through /var/log, int eh dmesg, messages, kern.log, syslog, and others and cannot find the specific error message I am seeing.

On bootup, I go through grub just fine, but then the bootsplash screen just does the Cylon thing for sevral minutes before dropping into an endless error message. I do have a screenshot of this on photobucket: http://i253.photobucket.com/albums/hh60/martalli/img_4651.jpg

This was the error with 2.6.24-15, but the same thing is happening with the newer kernel. Does anyone have suggestions, or need me to get further information from the machine?

[Michael Rooney (mrooney)]

Hi martalli, this sounds like a duplicate of #216575, check it out and let me know if you agree, and I can mark it as such and increase the awareness that way.

[Bryan Siegfried (martalli)]

I think the errors that I am getting at different. I have put several screenshots on flickr at:
http://flickr.com/photos/martalli/sets/72157600530741685/

I *think* this looks like a different error from #216575

[Bryan Siegfried (martalli)]

I added a few comments to the screenshots as to what was going on at the time.

[Saivann Carignan (oxmosys)]

Does changing your Sata mode from IDE to RAID in the "Integrated peripherals" menu inside your BIOS fixes this issue? If yes, please set this bug as a duplicate of bug #153702. Thanks for your bug report!