Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
seems that you have the same problem as I have in my laptop. The problem is - this is what I found out up to know - that you only have udma2 instead of udma5 (100) used by the system. this is related to the piix module which is not implemented in the kernel but loaded separately during boot. And it looks like that this is exact the problem: would your idemodule piix be integrated into the kernel then you would be able to use hdparm to change to udma5, but loaded during boot it seems to be not possible. your numbers for the disk writes are the same as mine, and I have udma2. you can check this with hdparm -iI /dev/hda (if hda is your disk). the actual udma-mode is characterized by a star(*). I have not found any solution to the problem up to now. the only one would be probably to compile your own kernel, but for me this was no option. anyone here with another suggestion?
I use the same. But did you check with hdparm -iI if udma5 is really set?
Try hdparm -iI, the actual used udma is marked with a star (*).
In my case, I set dma to udma5 with the line you told me also. After that checking with hdparm -iI tells me udma2* is the actual mode. So nothing changed. How it is in your case?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.