[SOLVED] DMA2 instead of DMA3 despite BIOS recognizing DMA3
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
DMA2 instead of DMA3 despite BIOS recognizing DMA3
Hello,
I have on my old PC 2 HDDs.
Both are recognized as ATA66 (DMA3) in the BIOS.
During booting with TinyCoreLinux, one HDD is recognized with DMA3. But the other one (in this case the slave, which is on the same IDE flat harness for both HDDs, 80wires 40pins) is recognized as DMA2 (ATA33).
Somebody know what should be done in order to have both with DMA3?
Thanks
If your hard disk are '/dev/hda' & '/dev/hdb' then use that as the replacement for '/dev/your_device'. Plus note the case of' 'I' and the difference between using 'i' or 'I' in the below excerpt.
Quote:
excerpt from 'man hdparm';
-i Display the identification info which the kernel drivers (IDE, libata) have stored from boot/configuration time. This may
differ from the current information obtainable directly from the drive itself with the -I flag. The data returned may or
may not be current, depending on activity since booting the system. For a more detailed interpretation of the identifica-
tion info, refer to AT Attachment Interface for Disk Drives, ANSI ASC X3T9.2 working draft, revision 4a, April 19/93, and
later editions.
-I Request identification info directly from the drive, which is displayed in a new expanded format with considerably more
detail than with the older -i flag.
Notice the asterisk beside the DMA assignment? You should be able to set the DMA on that drive below the current setting. If you attempt anything beyond that then you will have trouble with that drive. The asterisk denotes the DMA state that can be handled by the drive. Check your manufacture specifications for the drive in question to be sure of the DMA capabilities for the drive. You possibly could have an errant report for the HDD.
FYI: You should learn to use the vbcode tags # or Quote. By placing long lists of data within the vbcode tags the post will be cleaner therefore easier to read.
Hi,
Check your manufacture specifications for the drive in question to be sure of the DMA capabilities for the drive. You possibly could have an errant report for the HDD.
for the Quantum Fireball 6.4CR: ATA/66
for the WD 10GB: UDMA66
Not quite what you want to hear, and not quite the same motherboard, but I know the K6BV3+/66 had a warning in the manual along the lines of "drives from different manufacturers may not work properly together. The problem is the drives, not the motherboard".
Since the K6XV3+/66 is the same chipset, I wouldnt be supirised if the same is true for it as well (that is saying that its a chipset issue though).
Last edited by cascade9; 03-08-2011 at 12:40 PM.
Reason: typo
Thanks for the recommendation.
I discovered (complementary to all recommendations here) in the manual for the linux kernel code "IDE"
- harness > 40 wires for udma > 2
- drivers of the same HDD type can be on the same harness (different HDDs on different harness)
- if only 1 HDD on the harness, it should be on the master
- separate the devices on 2 harness
I will try
- force the HDD with hdparm -X"udma4" -d 1 /dev/hdb at boot and see the errors in dmesg
- if not ok, put the slow HDD as master (alone) and see if it goes faster
- put my OS on the quickest HDD
- separate the quickest HDD from the slowest (on 2 different cables)
And adapt the structure:
- the quickest HDD: boot + home (alone on 1 harness)
- the slowest HDD as backup + second OS. On this harness I will put the IDE-adapter + CF
And post the results. In any case, I understood a bit more what happens in hardware.
so, even as master HDD (alone on 1 udma5 harness), the 6GB HDD was not recognized as UDMA4 (despite the HDD spec indicate ATA66). So I stop here: I will put my main OS on the quickest 10GB HDD.
Hello,
I found an advice in the internet.
The computer (HW or SW) has issue in checking the 80wires.. then goes to UDMA33 (despite the HDD spec show UDMA66 and the MoBo Via chips show UDMA66 as spec), so this 80 wire check has to be disabled.
As boot code "ide_core.ignore.cable=1" (for my cable on ide"1"), the HDD is now recognized as UDMA66 ! (double speed).
This topic is SOLVED.
Last edited by floppy_stuttgart; 04-23-2011 at 06:05 PM.
Reason: error in the post
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
