** Description changed: Binary package hint: linux-source-2.6.20 From my forum post; 2.6.20-15.25 still does not fix: I've had problems for about a week, and I'm unsure of how to proceed. Installed Feisty beta, and had a rockin' system until upgrade from kernel 2.6.20-13 to 2.6.20-14. Starting with .14, could not boot; system would freeze early in the boot process, and would eventually exit into busybox shell. Investigated all week, and I think the hang-up is related to the switch to PATA; my (ide) drives are no longer hda, hdb, etc, but now sda, sdb. The specific error message at the hang is "ata2.00: qc timeout (cmd oxfer)" then "ata2.00:failed to set xfermode (err_mask=0x4)." This has been consistent any time I've tried to boot the .14 kernel. By the way 2.6.20-13 still booted fine at first. Had a problem when I - upgraded (actually downgraded) vvidia-glx, because of a kernel mismatch, + upgraded (actually downgraded) nvidia-glx, because of a kernel mismatch, and eventually had to start using the nv driver instead. I'm using 2.6.20-13 with that driver now. In busybox, looking at /dev, The drives are listed, but not the partitions - sda, sdb, but not sda1, sdb1. This is confirmed by downloading a daily build that uses 2.6.20-14, booting to it, and installing gparted. It can see the drives, but the partitions have <!> and are unreachable. Been waiting for the 2.6.20-15 update all day, hoping that would fix this problem; it does not - same errors. This has been very confusing as I've combed through the forums and - launchpad bug reports looking for these specific issues, and I've many - found similar or related bugs (usually related to SATA drives, however, + launchpad bug reports looking for these specific issues, and I've found + many similar or related bugs (usually related to SATA drives, however, or external drives, etc - I have good old ide) but little help. Don't know if I should start a new bug on launchpad or keep monitoring the ones I already am, waiting for fixes... Any advice, or similar experiences to convince me this is more widespread, would be much appreciated.
-- 2.6.20-15 still won't boot https://bugs.launchpad.net/bugs/106418 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
