Re: hdparm for lib_pata

[Stephen Clark <Stephen.Clark@seclark.us>]

Robert Hancock wrote:

>>Hi guys,
>>
>>Me again, sorry.
>>
>>Is it possible to make hdparm work with libata?
>>I have some drives that for some reason fall back to lower UDMA
>>settings (like UDMA/44) while the drive is UDMA/100. I blame the way I
>>set-up my raid arrays for this and the bus not being able to handle
>>all the data that goes trough it but that isnt really the case now.
>>
>>Anyway, I used to be able to force the drive back with using hdparm
>>-X68 -d 1 /dev/sdk
>>But with the new lib_pata drivers I get "Inappropriate iotcl for
>>device" and HD_IO_DRIVE_CMD Input/Output errors.
>>
>>Or! Is there some other way to force the drive not to failback to
>>lower UDMA settings? (Yep, I know, if this is answer, it's my risk, I
>>cant and wont blame you for destructing my pr0n or severe trauma I
>>suffer from losing data)
>>    
>>
>
>Only some of the hdparm functionality is supported in libata, which is 
>partially by design. Presently there's no way to override the DMA 
>settings in libata, it starts out at the fastest supported settings and 
>falls back if it gets too many errors of certain types.
>
>You shouldn't be seeing errors like this unless you have bad IDE cables 
>or are using 40-wire cables with high UDMA modes. Can you post the 
>output you're seeing?
>
>  
>
Ok,

But why are we taking away the users capability to control his/her own 
hardware. Sounds like windows.

My $.02
Steve Clark

-- 

"They that give up essential liberty to obtain temporary safety, 
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty 
decreases."  (Thomas Jefferson)