On Sunday 10 August 2003 04:24 pm, Stephen Kuhn wrote: > On Mon, 2003-08-11 at 03:54, David E. Fox wrote: > > > hdparm -X69 -d1 -u1 -c3 -m16 -A1 -W1 /dev/hdX > > > > Stephen - want to run down briefly those settings and what they mean? > > And doesn't -m16 set 16-bit? Wouldn't 32 bit be better? > > Ok... > > hdparm - program to set/change/configure IDE drive interface settings > > -X69 - TRANSFER_MODE - this is a relatively generic setting that I've > been using - you can use 68, 67, 69 or 70 - but I've found that 69 is > best (not a joke, y'all) - here is from the man page: > > Set the IDE transfer mode for newer (E)IDE/ATA drives. This is > typically used in combination with -d1 when enabling DMA to/from > a drive on a supported interface chipset, where -X mdma2 is used > to select multiword DMA mode2 transfers and -X sdma1 is used to > select simple mode 1 DMA transfers. With systems which support > UltraDMA burst timings, -X udma2 is used to select UltraDMA > mode2 transfers (you'll need to prepare the chipset for UltraDMA > beforehand). Apart from that, use of this flag is seldom neces- > sary since most/all modern IDE drives default to their fastest > PIO transfer mode at power-on. Fiddling with this can be both > needless and risky. On drives which support alternate transfer > modes, -X can be used to switch the mode of the drive only. > Prior to changing the transfer mode, the IDE interface should be > jumpered or programmed (see -p flag) for the new mode setting to > prevent loss and/or corruption of data. > For the PIO (Programmed Input/Output) transfer modes > used by Linux, this value is simply the desired PIO mode number > plus 8. Thus, a value of 09 sets PIO mode1, 10 enables PIO > mode2, and 11 selects PIO mode3. Setting 00 restores the > drive's "default" PIO mode, and 01 disables IORDY. For multi- > word DMA, the value used is the desired DMA mode number plus 32. > for UltraDMA, the value is the desired UltraDMA mode number plus > 64. > > -d1 - USE DMA > -u1 - UNMASK IRQ > -c3 - ENABLE 32-BIT TRANSFERS WITH SPECIAL SYNC > -m16 - set sector count for multiple sector count > -A1 - ENABLE DRIVE LOOK-AHEAD (forced) > -W1 - ENABLE WRITE CACHING > > I've experimented with heaps of drives and this seems to always be the > one that works the best - so much so that I created a script that I run > when I slap a customers (or a friends) drive into the MDK boxen... Stephen, do you not need to put the parameters in /etc/rc.d/rc.local or somewhere like that to get the hd set on each boot up? Long time back I seem to recall having to do that on one of my older machines but forgot about it till this thread popped up. -- Dennis M. linux user #180842
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
