On Tuesday 21 Jan 2003 3:39 pm, John Richard Smith wrote:
> I definately have DMA enabled in bios.
>
> But how do I get hdparm to check and enable DMA.
>
> my hard drive is /dev/hda
Attached is my notes on hdparm, mostly supplied by Technoslick.
Anne
--
Registered Linux User No.293302
{\rtf1\ansi\deff1\adeflang1025
{\fonttbl{\f0\froman\fprq2\fcharset0 Times New Roman{\*\falt Thorndale};}{\f1\fnil\fprq0\fcharset0 Garamond;}{\f2\fnil\fprq0\fcharset0 Garamond;}{\f3\froman\fprq2\fcharset0 Arial;}{\f4\fswiss\fprq2\fcharset0 helvetica;}{\f5\fnil\fprq2\fcharset0 HG Mincho Light J;}{\f6\fnil\fprq2\fcharset0 Arial Unicode MS;}}
{\colortbl;\red0\green0\blue0;\red0\green0\blue128;\red128\green128\blue128;}
{\stylesheet{\s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\snext1 Default;}
{\s2\sa120{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\sbasedon1\snext2 Text body;}
{\s3\sa120{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\fs24\lang1033\sbasedon2\snext3 List;}
{\s4\sb120\sa120{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs20\lang255\ai\ltrch\dbch\af5\afs20\langfe255\ai\loch\fs20\lang1033\i\sbasedon1\snext4 Caption;}
{\s5{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\fs24\lang1033\sbasedon1\snext5 Index;}
}
{\info{\comment StarWriter}{\vern6410}}\deftab720
{\*\pgdsctbl
{\pgdsc0\pgdscuse195\pgwsxn11905\pghsxn16837\marglsxn1134\margrsxn1134\margtsxn1134\margbsxn1134\pgdscnxt0 Default;}}
\paperh16837\paperw11905\margl1134\margr1134\margt1134\margb1134\sectd\sbknone\pgwsxn11905\pghsxn16837\marglsxn1134\margrsxn1134\margtsxn1134\margbsxn1134\ftnbj\ftnstart1\ftnrstcont\ftnnar\aenddoc\aftnrstcont\aftnstart1\aftnnrlc
\pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033{\ltrch\loch\f1 knowledge about the {\b params} for your drives, you can almost safely assume that you can push things a bit...}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 On customers' computers, as well as my own, I start with /hda (or whatever) and try hdparm -X66 /dev/hda - then work my way up - using 67,68.69 and 70. 70 is for UDMA6...69 for 5, 68 for 4 (you get the picture)...}
\par {\ltrch\loch\f3 Enabling DMA is simple - hdparm -d1 /dev/hda}
\par {\ltrch\loch\f3 You CAN get a bit more elaborate as well - attached is my HDPARM doco...}
\par {\ltrch\loch\f3 Overall, it's a matter of tweaking per drive, per system. When you find the right mix, mate, it's a beaut to have all the drives justa hummin!}
\par {\ltrch\loch\f3 --}
\par {\ltrch\loch\f3 NAME}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033{\ltrch\loch\f1 {\b hdparm} - get/set hard disk parameters}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 SYNOPSIS}
\par {\ltrch\loch\f3 hdparm [ flags ] [device] ..}
\par {\ltrch\loch\f3 DESCRIPTION}
\par {\ltrch\loch\f3 hdparm provides\tab a command line interface to various hard}
\par {\ltrch\loch\f3 disk ioctls supported by the stock Linux ATA/IDE device}
\par {\ltrch\loch\f3 driver subsystem. Some options may work correctly only}
\par {\ltrch\loch\f3 with the latest kernels.\tab For best results, compile hdparm}
\par {\ltrch\loch\f3 with the include files from the latest kernel source code.}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 OPTIONS}
\par {\ltrch\loch\f3 When no flags are given, -acdgkmnru is assumed.}
\par {\ltrch\loch\f3 -a Get/set sector count for filesystem read-ahead. \tab This is\tab used to improve performance in sequential reads of large files, by prefetching additional blocks in anticipation of them being needed by the running task In the curren
t\tab kernel version (2.0.10)\tab this has a default setting of 8 sectors (4KB). This value seems good for most purposes, but in a system where most file accesses are random seeks, a smaller setting might provide better per\-formance.\tab Also, many IDE drives al
so have a separate built-in read-ahead function, which alleviates the need for a filesystem read-ahead in many situa\-tions.}
\par {\ltrch\loch\f3 -A Disable/enable the IDE drive's read-lookahead fea\-ture (usually ON by default).}
\par {\ltrch\loch\f3 -b Get/set bus state.}
\par {\ltrch\loch\f3 -B Get setting of Advanced Power Management feature, if the drive supports it.}
\par {\ltrch\loch\f3 -c Query/enable (E)IDE 32-bit I/O support. A numeric parameter\tab can be used to enable/disable 32-bit I/O support: Currently supported values include 0 to disable 32-bit I/O support, 1 to enable 32-bit data transfers, and 3 to enable 32-bit
data\tab transfers with a special\tab sync sequence\tab required by many chipsets.\tab The value 3 works with nearly all 32-bit IDE chipsets, but incurs slightly more overhead. Note that "32-bit" refers to data transfers across a PCI or VLB bus to the
interface card only; all (E)IDE drives still have only a 16-bit connection over the ribbon cable from the interface card.}
\par {\ltrch\loch\f3 -C Check the current IDE power mode status, which will always be one of unknown (drive does not support this command), active/idle (normal operation), standby (low power mode, drive has spun down), or sleeping (lowest power mode, drive
is completely shut down). The -S, -y, -Y, and -Z flags can be used to manipulate the IDE power modes.}
\par {\ltrch\loch\f3 -d Disable/enable the "using_dma" flag for this drive. This option now works with most combinations of drives and PCI interfaces which support DMA and which are known to the IDE driver. It is also\tab a good idea to use the appropriate
-X option in combination with -d1 to ensure that the drive itself is programmed for the correct DMA mode, although most BIOSs should do this for you at boot time. Using DMA nearly always gives the best performance, with fast I/O throughput a
nd low\tab CPU usage. But there are at least a few configurations of chipsets and drives for which DMA does not make much of a difference, or may even slow things down (on really messed up hardware!). Your mileage may vary. }
\par {\ltrch\loch\f3 -D Enable/disable the on-drive defect management feature, whereby the drive firmware tries to automatcally manage defective sectors by relocating them to "spare" sectors reserved by the factory for such.}
\par {\ltrch\loch\f3 -E Set cdrom speed.\tab This is NOT necessary for regular operation, as the drive will automatically switch speeds on its own. But if you want to play with it, just supply a speed number after the option, usually a number like 2 or 4.}
\par {\ltrch\loch\f3 -f Sync and flush the buffer cache for the device on exit. This operation is also performed as part of the -t and -T timings.}
\par {\ltrch\loch\f3 -g Display the drive geometry (cylinders, heads, sectors), the size (in sectors) of the device, and the starting offset (in sectors) of the device from the beginning of the drive.}
\par {\ltrch\loch\f3 -h Display terse usage information (help).}
\par {\ltrch\loch\f3 -i Display the identification info that was obtained from the drive at boot time, if available. This is a feature of modern IDE drives, and may not be supported by older devices.\tab The data returned may or may not be current, depending on act
ivity since booting the system. However, the current multiple sector mode count is always shown. For a more detailed interpretation of the identification info, refer to AT Attachment Interface for Disk Drives \tab (ANSI ASC X3T9.2 working draft
, revision 4a, April 19/93).}
\par {\ltrch\loch\f3 -I Request identification info directly from the drive, which is displayed in a new expanded format with considerably more detail than with the older -i flag.}
\par {\ltrch\loch\f3 -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).\tab This flag defaults to off, to prevent drive res
et loops which could be caused by combinations of -dmu settings. The -k flag should therefore only be set after one has achieved confidence in correct system operation with a chosen set of configuration settings. In practice, all that is typically
necessary 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).}
\par {\ltrch\loch\f3 -K Set the\tab 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.}
\par {\ltrch\loch\f3 -L Set the drive's doorlock flag. Setting this to will lock the door mechanism of\tab some removeable hard drives (eg. Syquest, ZIP, Jazz..), and setting it to maintains the door locking mechanism automatically, depending on drive usage (lo
cked whenever a filesystem is mounted). But on\tab system\tab shutdown,this can be a nuisance if the root partition is on a removeable disk, since the root partition is left mounted (read-only) after shutdown. So, by using this command to unlock the door the
root filesystem is remounted read-only, one can then remove the cartridge from the drive after shutdown.}
\par {\ltrch\loch\f3 -m Get/set sector count for multiple sector I/O on the drive. A setting of 0 disables this feature. Multiple sector mode (aka IDE Block Mode), is a feature of most modern IDE hard drives, permitting the transfer of multiple sectors per I/
O interrupt, rather than the usual one sector per interrupt. When this feature is enabled, it typically reduces operating system verhead for disk I/O by 30-50%. On many systems, it also provides increased data throughput of anywhere from 5% to
50%. Some drives, however (most notably the WD Caviar series), seem to run slower with multiple mode enabled. Your mileage may vary.Most drives support the minimum settings of 2, 4, 8, or 16 (sectors). Larger settings may also be possible,
depending\tab on the drive. A setting of 16 or 32 seems optimal on\tab many systems.\tab Western Digital recommends lower settings of 4 to 8 on many of their drives, due tiny (32kB) drive buffers and non-optimized buffering algorithms. The -i flag c
an be used to find the maximum setting supported by an installed drive (look for MaxMultSect in the output).\tab Some drives claim to\tab support\tab multiple mode, but lose data at some settings. Under rare circumstances, such failures can result in mas
sive filesystem corruption.}
\par {\ltrch\loch\f3 -n Get or set the "ignore write errors" flag in the driver. Do NOT play with this without grokking the driver source code first.}
\par {\ltrch\loch\f3 -p Attempt to reprogram the IDE interface chipset for the specified PIO mode, or attempt to auto-tune for the "best" PIO mode supported by the drive. This feature is supported in the kernel for only a few "known" chipsets, and even then th
e support is iffy at best.\tab Some IDE chipsets are unable to alter the PIO mode for a single drive, in which case this flag may cause the PIO mode for both drives to be set. Many IDE chipsets support either fewer or more than the standard six (0 to
5) PIO modes, so the exact speed setting that is actually implemented will vary by chipset/driver sophistication. Use with extreme caution! This feature includes zero protection for the unwary, and an unsuccessful outcome may result in se
vere filesystem corruption!}
\par {\ltrch\loch\f3 -P Set the maximum sector count for the drive's internal prefetch mechanism.\tab Not all drives support this feature.}
\par {\ltrch\loch\f3 -q Handle the next flag quietly, supressing normal output. This is useful for reducing screen clutter when running from /etc/rc.c/rc.local. Not applicable to the -i or -v or -t or -T flags.}
\par {\ltrch\loch\f3 -r Get/set read-only flag for device. When set, write operations are not permitted on the device.}
\par {\ltrch\loch\f3 -R Register an IDE interface. Dangerous. See the -U option for more information.}
\par {\ltrch\loch\f3 -S Set the\tab standby (spindown) timeout for the drive. This value is used by the drive to determine how long to wait (with no disk activity) before turning off the spindle motor to save power. Under such circumstances, the drive may t
ake as long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker. The encoding of the timeout value is somewhat peculiar. A value of zero means "off". Values from 1 to 240 specify multiples of 5 seconds, for timeo
uts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, for timeouts\tab from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes, 253 sets a vendor-defined timeout, and 255 is inter
preted as 21 minutes plus 15 seconds.}
\par {\ltrch\loch\f3 -T Perform timings of cache reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an otherwise inactive system (no other active processes) with at least a couple of megabytes
of free memory. This displays the speed of reading directly from the Linux buffer cache without disk access. This measurement is essentially an indication of the throughput of the processor, cache, and memory of the system under test.
If the -t flag is also specified, then a correction factor based on the outcome of -T will be incorporated into the result reported for the -t operation.}
\par {\ltrch\loch\f3 -t Perform timings of device reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an otherwise inactive system (no other active processes) with at least a couple of megabytes
of free memory. This displays the speed of reading through the buffer cache to the disk without any prior caching of data. This measurement is an indication of how fast the drive can sustain sequential data reads under Linux, without a
ny filesystem overhead. To ensure accurate measurments, the buffer cache is flushed during the processing of -t using the BLK\-FLSBUF ioctl. If the -T flag is also specified, then a correction factor based on the outcome of -T will be incorporated in
to the result reported for the -t operation.}
\par {\ltrch\loch\f3 -u Get/set interrupt-unmask flag for the drive.\tab A setting of 1 permits the\tab driver\tab to unmask other interrupts during processing of a disk interrupt, which greatly improves Linux's responsiveness and eliminates "serial port overrun" erro
rs.\tab Use this feature with caution: some drive/controller combinations do not tolerate the increased I/O latencies possible when this feature is enabled, resulting in massive filesystem corruption. In particular, CMD-640B and RZ1000 (E)IDE in
terfaces can be unreliable (due to a hardware flaw) when this option is used with kernel versions earlier than 2.0.13. Disabling the IDE prefetch feature of these interfaces (usually a BIOS/CMOS setting) provides a safe fix for the problem for use
with earlier kernels.}
\par {\ltrch\loch\f3 -U Un-register an IDE interface. Dangerous.\tab The companion for the -R option. Intended for use with hardware\tab made specifically for hot-swapping (very rare!). Use with knowledge and extreme caution as this can easily hang or damage your
system. The \tab hdparm source distribution includes a\tab 'contrib' directory with some user-donated scripts for hot-swapping on the UltraBay of a ThinkPad 600E. Use at your own risk.}
\par {\ltrch\loch\f3 -v Display all settings, except -i (same as -acdgkmnru for IDE, -gr for SCSI or -adgr for XT).\tab This is also the default behaviour when no flags are specfied. -TP -w Perform a device reset (DANGEROUS). Do NOT use this option. It exist
s for unlikely situations where a reboot might otherwise be required to get a confused drive back into a useable state.}
\par {\ltrch\loch\f3 -W Disable/enable the IDE drive's write-caching feature (default state is\tab undeterminable; manufacturer/model specific).}
\par {\ltrch\loch\f3 -X Set the IDE transfer mode for newer (E)IDE/ATA2 drives. This is typically used in combination with -d1 when enabling DMA to/from a drive on a supported interface chipset, where -X34 is used to select multiword DMA mode2 transfers.
With systems which support UltraDMA burst timings, -X66 is used to select UltraDMA mode2 transfers (you'll need to prepare\tab the chipset for UltraDMA beforehand). Apart from that, use of this flag is seldom necessary since most/all modern I
DE 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\tab to prevent loss and/or corruption of data. Use this with extreme caution! For the\tab PIO (Programmed Input/Output) transfer modes used b
y Linux, this value is simply the desired PIO mode number plus 8. Thus, a value of 09 sets\tab PIO mode1, 10 enables PIO mode2, and 11 selects PIO mode3. Setting 00 restores the drive's "default"\tab PIO mode, and 01 disables IORDY. For multiword DM
A, the value used is\tab the desired DMA mode number plus 32. for UltraDMA, the value is the desired UltraDMA mode number plus 64.}
\par {\ltrch\loch\f3 -y Force an IDE drive to immediately enter the low power consumption standby mode, usually causing it to spin down. The current power mode status can be checked using the -C flag.}
\par {\ltrch\loch\f3 -Y Force an IDE drive to immediately enter the lowest power consumption sleep mode, causing it to shut down completely.\tab A hard or soft reset is required before the drive can be accessed again (the Linux IDE driver will automatically h
andle issuing a reset if/when needed). The current power mode status can be checked using the -C flag.}
\par {\ltrch\loch\f3 -Z Disable the automatic power-saving function of certain Seagate drives (ST3xxx models?), to prevent them from idling/spinning-down\tab at inconvenient times.}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 BUGS}
\par {\ltrch\loch\f3 As noted above, the -m sectcount and -u 1 options should be used with caution at first, preferably on a read-only filesystem. Most drives work well with\tab these\tab features, but a few drive/controller combinations are not 100% compatible.\tab Filesy
stem corruption may result. Backup everything before experimenting!}
\par {\ltrch\loch\f3 Some options (eg. -r for SCSI) may not work with old kernels as necessary ioctl()'s were not supported.}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 Although this utility is intended primarily for\tab use with (E)IDE hard disk devices, several of the options are also valid (and permitted) for use with SCSI hard disk devices and MFM/RLL hard disks with XT interfaces.}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 AUTHOR}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033{\ltrch\loch\f3{\fs20\f3 hdparm has been written by Mark Lord <}{\ul\f4\cf2 [EMAIL PROTECTED]}{\fs20\f3 >, the primary developer and maintainer of the (E)IDE driver for Linux, with suggestions from many netfolk.}}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 The disable Seagate auto-powersaving code is courtesy of Tomi Leppikangas([EMAIL PROTECTED]).}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 SEE ALSO}
\par {\ltrch\loch\f3 AT Attachment Interface for Disk Drives, ANSI ASC X3T9.2 working draft, revision 4a, April 19, 1993.}
\par {\ltrch\loch\f3 AT Attachment Interface with Extensions (ATA-2), ANSI ASC}
\par {\ltrch\loch\f3 X3T9.2 working draft, revision 2f, July 26, 1994.}
\par {\ltrch\loch\f3 AT Attachment with Packet Interface -\tab 5 (ATA/ATAPI-5),}
\par {\ltrch\loch\f3 T13-1321D working draft, revision 3, February 29, 2000.}
\par {\ltrch\loch\f3 Western\tab Digital\tab Enhanced IDE\tab Implementation\tab Guide, by}
\par {\ltrch\loch\f3 Western Digital Corporation, revision 5.0, November 10,}
\par {\ltrch\loch\f3 1993.}
\par {\ltrch\loch\f3 Enhanced Disk Drive Specification, by Phoenix Technologies}
\par {\ltrch\loch\f3 Ltd., version 1.0, January 25, 1994.}
\par {\ltrch\loch\f3 Version 4.6\tab \tab December 2001\tab \tab \tab HDPARM(8)}
\par {\ltrch\loch\f3 ----}
\par {\ltrch\loch\f3 By testing your drives (the HD's and the CD's) and having a bit of knowledge about the params for your drives, you can almost safely assume that you can push things a bit...}
\par {\ltrch\loch\f3 On customers' computers, as well as my own, I start with /hda (or whatever) and try}
\par {\ltrch\loch\f3 hdparm -X66 /dev/hda - then work my way up - using 67,68.69 and 70. 70 is for UDMA6...69 for 5, 68 for 4 (you get the picture)...}
\par {\ltrch\loch\f3 Enabling DMA is simple - hdparm -d1 /dev/hda}
\par {\ltrch\loch\f3 You CAN get a bit more elaborate as well - above is my HDPARM doco...}
\par {\ltrch\loch\f3 Overall, it's a matter of tweaking per drive, per system. When you find the right mix, mate, it's a beaut to have all the drives justa hummin!}
\par {\ltrch\loch\f3 --}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ai\ltrch\dbch\af3\afs20\ai\loch\f3\fs20\i {\ltrch\loch\f3 'hdparm -d1 -X69 /dev/hdX (but it will change per drive and system)'}
\par {\ltrch\loch\f3 What does this line do?}
\par \pard\plain \s1{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\rtlch\afs24\lang255\ltrch\dbch\af5\afs24\langfe255\loch\f1\fs24\lang1033\rtlch\af3\afs20\ltrch\dbch\af3\afs20\loch\f3\fs20 {\ltrch\loch\f3 this line tells /dev/hd(whatever) to use DMA (-d1) and to run in UDMA5 mode (-X69)}
\par {\ltrch\loch\f3 ----}
\par }
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
