Per Jessen wrote:
Basil Chupin wrote:
I am using the hdparm which comes with 10.1: 6.3-11
I suspect you can ignore the error with HDIO_GETGEO - it is odd for hdparm to try lok up the geometry of a CDROM-drive, but it doesn't really cause a problem, does it?
Doing hdparm -dx /dev/hdx does not produce the error but it also does not give me the same results- I only get-
using_dma = 0 (off) busstate = 1 (1)
and that's all.
I would not expect the same results as for the display command, just the change in the DMA setting.
What happens when you do the following:
hdparm -d0 /dev/hdx
I get: setting using_dma to 0 (off)
hdparm /dev/hdx
the same blurb with the HDIO_GETGEO failed error I mentioned in my original post.
hdparm -d1 /dev/hdx
setting using_dma to 1 (on) using_dma = 1 (on)
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
If DMA is not enabled now, something isn't working. Which I believe is what you reported initially?
The DMA is now set by looking in Control Centre (which, BTW is spelt a Control CENTER even though I have selected British English to use and NOT <shudder> that unknown pretend-language, 'US English'). 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) Cheers. -- All answers questioned here.