I have just upgraded from Edgy to Feisty on my laptops and workstation. The laptops seem to have gone fine, the workstation has not. When I try and boot with the 2.6.20-15 kernel, it hangs for a while and then drops out to Busybox with prompt (initramfs) and the message:
ata2: port failed to respond
Clearly this is a blocker! I am not sure how to get dmesg type information since it won't actually boot so I don't get a record.
If I boot the old 2.6.17-11 kernel then everything works fine. The "uname -a" information is:
Linux balin 2.6.17-11-generic #2 SMP Tue Mar 13 23:32:38 UTC 2007 i686 GNU/Linux
I could attach the dmesg etc. record is that is helpful.
If I try the 2.6.20-15 recover boot then I see messages looking a little like the above which is why I have attached to this bug report rather than create a new one. If this was the wrong thing to do, I can always start a new entry.
I am at a total loss to know how to proceed on this one. 2.6.17-11 is fine 2.6.20-15 is totally broken on this one machine although fine on others :-(
I have just upgraded from Edgy to Feisty on my laptops and workstation. The laptops seem to have gone fine, the workstation has not. When I try and boot with the 2.6.20-15 kernel, it hangs for a while and then drops out to Busybox with prompt (initramfs) and the message:
ata2: port failed to respond
Clearly this is a blocker! I am not sure how to get dmesg type information since it won't actually boot so I don't get a record.
If I boot the old 2.6.17-11 kernel then everything works fine. The "uname -a" information is:
Linux balin 2.6.17-11-generic #2 SMP Tue Mar 13 23:32:38 UTC 2007 i686 GNU/Linux
I could attach the dmesg etc. record is that is helpful.
If I try the 2.6.20-15 recover boot then I see messages looking a little like the above which is why I have attached to this bug report rather than create a new one. If this was the wrong thing to do, I can always start a new entry.
I am at a total loss to know how to proceed on this one. 2.6.17-11 is fine 2.6.20-15 is totally broken on this one machine although fine on others :-(
Thanks.