System doesn't boot

[Dmitriy Kropivnitskiy]

Binary package hint: linux-image-2.6.17-7-generic

When I attempt to boot my system using linux-image-2.6.17-7-generic and usplash, the boot stops when the usplash screen is displayed (no messages are shown and progress bar doesn't move). When I try to boot this without splash and quitet settings it gets to the USB part and stops without any apparent error messages.
My System: HP xw4100 PIV 2.4Ghz 1.5GB RAM
attached are output of dmidecode and lspci -v

[Dmitriy Kropivnitskiy (nigde)]

The last known working kernel is linux-image-2.6.17-6-686 2.6.17-6.18
The version this was tried on is linux-image-2.6.17-7-generic 2.6.17-7.20
I am about to try and boot
linux-image-2.6.17-7-386 2.6.17-7.20

[Dennis Kaarsemaker (dennis)]

Emiliano: don't play with the bugtracker please.

[Ben Collins (ben-collins)]

There is no 2.6.17 in dapper.

[Ben Collins (ben-collins)]

This is an installer bug which is already fixed.

At the grub menu, change the line root=/dev/sda1 to root=/dev/hda1.

After booting, edit /boot/grub/menu.lst, remove the line with kopt_2_6, and run "sudo update-grub"

[Dmitriy Kropivnitskiy (nigde)]

I don't know how this ended up in dapper. I was reasonably sure, that when I was filing it I was filing under edgy. This bug is for edgy. It also says that it was initially uploaded to Edgy. WTF? And I don't know why someone marked it related to firefox. I have to say that launchpad interface is extremely confusing. In any case, on my relatively standard system, latest Edgy kernel doesn't boot. If you don't want bug reports, just say so.

[Dmitriy Kropivnitskiy (nigde)]

Oh, linux-image-2.6.17-7-386 didn't work in the same fashion.

[Matthew Garrett (mjg59)]

Dmitry,

See Ben's comment. If that doesn't rectify things for you, let us know and we'll reopen the bug.

[Dmitriy Kropivnitskiy (nigde)]

I will try, but I don't think this will help much, since my root device actually IS /dev/sda1.

[Ben Collins (ben-collins)]

It actually was sda1, but the new kernel is likely seeing hda1 now, which would be the problem.

Please try the above fix.

[Dmitriy Kropivnitskiy (nigde)]

Wow, it actually worked. Did they change kernel naming scheme? Also I noticed, that my /etc/fstab mounts partitions by UUID, which is probably why it still works despite the change in naming. Is that one of the Edgy's improvements?