Hi,
On Monday 25 April 2005 15:53, James wrote:
> Hello,
>
> Upon rebooting my portable I get these settings:
> /dev/hda:
>  multcount    = 16 (on)
>  IO_support   =  0 (default 16-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    = 256 (on)
>  geometry     = 16383/255/63, sectors = 60011642880, start = 0
>
> I then issue: hdparm -d 1 -A 1 -m 16 -u 1 -c1 -a 256 /dev/hda

 -d1 -u1 -c1 /dev/hda would have been enough.

-A/-a 256, m16 is already set, no need to set it again.
But you should check with -i if your drive likes the multicount of 16...

> Last, when I issue:
> hdparm -k1 /dev/hda I get:
> /dev/hda:
>  setting keep_settings to 1 (on)
>  keepsettings =  1 (on)
>
> But upon reboot, I'm back to:
> multcount    = 16 (on)
>  IO_support   =  0 (default 16-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    = 256 (on)
>

-k does not work across reboots. It only works across drive resets, and it is 
something you SHALL NOT use. Because if your drive resets, it has usually 
some problems, forcing DMA over a flaky cable could kill your data in that 
moment. If the problems disappeared, you can always issue hdpam -d1 again ...

I guess, you have not read man hdparm:

-A     Disable/enable the IDE drive's read-lookahead feature (usually ON by 
default).

 -k     Get/set the keep_settings_over_reset flag for the drive.  When this 
flag is set, the driver will preserve  the  -dmu  options
              over  a  soft  reset,  (as done during the error recovery 
sequence).  This flag defaults to off, to prevent drive reset loops
              which could be caused by combinations of -dmu settings.  The -k 
flag should therefore only be set after one has achieved con-
              fidence  in  correct system operation with a chosen set of 
configuration settings.  In practice, all that is typically neces-
              sary to test a configuration (prior to using -k) is to verify 
that the drive can be read/written,  and  that  no  error  logs
              (kernel messages) are generated in the process (look 
in /var/adm/messages on most systems).

       -K     Set the drive's keep_features_over_reset flag.  Setting this 
enables the drive to retain the settings for -APSWXZ over a soft
              reset (as done during the error recovery sequence).  Not all 
drives support this feature.


and there is a lot more interesting stuff in it.

Glück Auf
Volker


-- 
gentoo-user@gentoo.org mailing list

Reply via email to