Basil Chupin wrote:
hdparm /dev/hdx
IO_support = 1 (32-bit) unmasking = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 1024 (on) HDIO_GETGEO failed: Inappropriate ioctl for device
So DMA is now enabled for that drive. That means hdparm is doing what's supposed to. If the setting does not survive a reboot, your BIOS is resetting it. But you also said FORCE_DMA is not working - which is probably worth reporting as hdparm is ok.
BUT, I also just noticed that even though the DMA is now set for all the devices (hda, hdb, hdc and hdd) there is still one anomaly in what is shown in Control Centre/Hardware/DMA.
Devices hda and hdc are identical Maxtor drives, from the same batch as far as I am concerned, only separated by small number of digits in the serial numbers. However, Control Centre reports that hda has Ultra set to 100 and hdd is set to 133! So I now have:
hda UDMA100 (WRONG) hdb DMA33 (Correct) hdc UDMA133 (Correct) hdd DMA66 (Correct)
I don't use the YaST control centre much - but maybe it just displays the current setting - what are you comparing to when you say UDMA100 for hda is wrong? What does "hdparm -i /dev/hdx" say? /Per