Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You can try adding the flags -m16 and -c3 to the hdparm command. Just man hdparm to see what these options actually do. It's a bit long-winded to explain fully, but it basically enables multiple sector mode and 32-bit I/O support.
The option -c3 enables 32 bit I/O with sync. You may want to turn on unmaskirq. What it will do is make the computer do other jobs while the hard drive is finding the file. Though not all drives work well with multicount and read-ahead, so you have to experiment.
Are you sure you enabled specific support for your ide-chipset at kernel compilation?
This is what I can think of, when you mentioned the difference between previous- and your custom kernel.
Segate is the master of the first channel and the WD is the slave. GCE is the master of the second channel.
The kernel that i compiled worked well. The reading speed was in a normal state, and it is about 27M/s.
This problem was suddenly happened.
I found that if I close the 'ACPI aware OS' in the BIOS, the reading speed under kernel 2.6 is good. But after I set this, the other system on my computer, Windows, couldn't boot up, it just reboot again and again.