I'm not a reporter but I can confirm that bug persist in gutsy. I have no ability to test it against hardy alpha as this is production machine and i do not want to couse more harm than good.
Anyway the current solution for this problem is (I've tried this once): blacklist ata_piix run update-initramfs -k all -u (this seems to update initramfs with values from /etc/modprobe.d/blacklist) then initramfs is ok, so all you do is unblacklist ata_piix in real filesystem as this allow cd to work correctly. Main reason for the bug is fact that when ata_piix gets loaded before ahci then it will take controll of hdd but this module is somehow broken and is not able to to this correctly. This is also the reason that sometimes ubuntu starts correctly, some kind of race condition in kernel and the modules gets loaded in proper way (ahci first, then ata_piix) (chance of this event are about 5% for feisty, more in gutsy, 95% in custom compiled kernel what what i can tell - i really do not understand that part of booting) Also this bug seems like upstream kernel reggression. It was already solved on launchad for edgy or dapper, i dont remember. Perhaps newest kernel will solve the issue. (kernel 2.6.23 did not - I've tried compiling manualy from master kernel thread on ubuntuforums) I'm not linux expert so what I've laid out perhaps have some mistakes or anything. -- gutsy tribe 5 ok with live cd but doesnt boot when installed (ata_piix problem ?) https://bugs.launchpad.net/bugs/139790 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
