Thomas, I did similar tests with hardy. I had the same results. But a fresh installation is working just fine. This happened only when I upgraded to Hardy. I wonder if it is related to libata bug 195221 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195221) You can see Ravindran's comment (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/131094/comments/760) It show udma2 being selected instead of udma4. Can others confirm this ?
Thomas, I did similar tests with hardy. I had the same results. But a fresh installation is working just fine. This happened only when I upgraded to Hardy. I wonder if it is related to libata bug 195221 (https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/195221) /bugs.launchpad .net/ubuntu/ +source/ linux-source- 2.6.22/ +bug/131094/ comments/ 760) It show udma2 being selected instead of udma4.
You can see Ravindran's comment (https:/
Can others confirm this ?