© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Lot of misleading stuff in this report. I see several people showing they cannot enable DMA. Some are shown on hda and some are on sda. So this complicates the "needs PATA driver, not IDE driver". Also, some reports show that udma is actually enabled.
Also, to explain the problem a bit better for feisty (my mistake for not being verbose). Switching drivers sounds easy, but it's actually quite complicated when you have to factor in regression testing. The reason for using the current driver set is because they proved to be stable, and in some cases (like for controllers mentioned here) the alternate driver was actually very unstable, not allowing people to boot. So I consider it very prudent to use a driver that may degrade CD-ROM support for some people as opposed to using a driver that makes the system unbootable for others.
So we will not be working to fix this in feisty. It's unfortunate, but it's a decision we have to make, and it's been made. However, we definitely want to get this fixed in gutsy. There's still three months left of development, so plenty of time.
What I need is a concise description and set of logs for one person (original submitter?) showing the problem under latest gutsy 2.6.22-8-generic kernel. Logs include dmesg, lspci -vvn and hdparm outputs.
Thanks