* Roger Haxton [03-13-06 23:31]:

I must've missed in YasT where I can set hdparms other than dma. I'd love to know where in YasT this is.

YasT2 Control Center -> Hardware -> IDE DMA MODE -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

On Mon, 13 Mar 2006, Roger Haxton wrote:-

On Monday March 13 2006 21:57, Patrick Shanahan wrote:

...

You can do that in YasT or a line in /etc/init.d/boot.local I must've missed in YasT where I can set hdparms other than dma. I'd love to know where in YasT this is.

YaST -> System -> /etc/syconfig Editor -> Hardware -> IDE -> DEVICES_FORCE_IDE_DMA enter: /dev/hda:-c1 /dev/hdc:-c1 exit YaST. This will ensure that 32bit mode is set every reboot. To enable it without rebooting, enter: /etc/rc.d/boot.idedma restart Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | RPC600 129Mb RISCOS 3.6 | Falcon 14Mb TOS 4.02 AMD2600(64) 512Mb SUSE 10.0 | A4000 4Mb RISCOS 3.11 | STE 4Mb TOS 1.62

On Tue, 14 Mar 2006 17:32:08 +0000, you wrote:

On Tue, 14 Mar 2006, in a serious and blatant case of a self-followup did forget to include some stuff when he wrote:-

...

YaST -> System -> /etc/syconfig Editor -> Hardware -> IDE -> DEVICES_FORCE_IDE_DMA

enter:

/dev/hda:-c1 /dev/hdc:-c1

You can also include other options for hdparm here by using the format:

<device>:<option>:<option>:<option>

Why do people insist on using a screwdriver to hammer nails? If you know enough to fool around with hdparm, you should be able to master bash and an editor. Put this in boot.local (adjust for your local hardware): hdparm -A1 -c1 -d1 -m16 -u1 /dev/hda hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdb hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdc hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdd hdparm -A1 -c1 -d1 -m16 -u1 /dev/hde hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdf hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdg hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdh hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdi hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdj Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,

On Wed, 15 Mar 2006, Michael Behrens wrote:- <snip>

Why do people insist on inventing any single type of wheel again and again?

Because it's a fun thing to do?

The distribution already has means to configure DMA.

And that was the method that I showed. That doesn't mean that showing other ways isn't useful. Adding stuff to boot.local is another way of achieving the same results and it's quite useful to know about especially if you're (possibly going to be) using other distributions.

...

Put this in boot.local (adjust for your local hardware): hdparm -A1 -c1 -d1 -m16 -u1 /dev/hda hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdb hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdc hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdd hdparm -A1 -c1 -d1 -m16 -u1 /dev/hde hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdf hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdg hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdh hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdi hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdj

printf "%s\n%s\n%s\n%s\n" "hdparm -A1 -c1 -d1 -m16 -u1 "/dev/hd{a,b,c,d} >>/etc/init.d/boot.local Or echo -e "hdparm -A1 -c1 -d1 -m16 -u1 "/dev/hd{a,b,c,d}"\n" >>/etc/init.d/boot.local Both add multiple lines to boot.local, and neither even need an editor. Using "echo" is slightly shorter, since you don't need to remember a "%s\n" for each line, but using "echo" adds a space at the beginning of the line like so: hdparm -A1 -c1 -d1 -m16 -u1 /dev/hda hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdb hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdc hdparm -A1 -c1 -d1 -m16 -u1 /dev/hdd not that having the space there matters. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | RPC600 129Mb RISCOS 3.6 | Falcon 14Mb TOS 4.02 AMD2600(64) 512Mb SUSE 10.0 | A4000 4Mb RISCOS 3.11 | STE 4Mb TOS 1.62

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-03-14 at 17:32 -0000, David Bolt wrote:

...

YaST -> System -> /etc/syconfig Editor -> Hardware -> IDE -> DEVICES_FORCE_IDE_DMA

enter:

/dev/hda:-c1 /dev/hdc:-c1

You can also include other options for hdparm here by using the format:

<device>:<option>:<option>:<option>

¿Are you sure? My 9.3 doesn't mention that syntax, it only talks about DMA: # Force DMA mode for selected device. Use pairs <device>: separated # by space - dma_mode can be "on" (enable default DMA mode), "off" (disable DMA # mode) or any mode supported by hdparm (e.g. "mdma2", "udma5", ...) # Example: "/dev/hdc:off /dev/hdd:udma2" # DEVICES_FORCE_IDE_DMA="/dev/hda:on /dev/hdb:on /dev/hdc:on /dev/hdd:on " - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEGBOTtTMYHG2NR9URAt4hAJ43icbiKzeiYKChRb6rC4B6b+wQXACgkrCG 5P4Ov0EovFmTxuhqNufYmOo= =6YWX -----END PGP SIGNATURE-----

On Wed, 15 Mar 2006, Carlos E. R. wrote:-

¿Are you sure? My 9.3 doesn't mention that syntax, it only talks about DMA:

Yes, I'm quite sure.

# Force DMA mode for selected device. Use pairs <device>: separated # by space - dma_mode can be "on" (enable default DMA mode), "off" (disable DMA # mode) or any mode supported by hdparm (e.g. "mdma2", "udma5", ...) # Example: "/dev/hdc:off /dev/hdd:udma2" #

DEVICES_FORCE_IDE_DMA="/dev/hda:on /dev/hdb:on /dev/hdc:on /dev/hdd:on "

If you have a look at /etc/init.d/boot.idedma, which is the script that sets the DMA modes, you'll see these lines inside the function idedma_main(): # The setting e.g. "/dev/hda:69:-c1:-m16:-u1:-W1:-A1" should be # expanded as "hdparm -d 1 -X 69 -c1 -m16 -u1 -W1 -A1 /dev/hda" which shows the exact format to use. A few lines further down, there's this part where the DMA modes are actually set: # Set DMA mode by hdparm utility if [ -z "$MODE" ] ; then echo "Missing DMA mode for device $DEVICE" rc_failed elif [ $MODE = "off" ] ; then $HDPARM -d 0 "$DEVICE" || rc_failed elif [ $MODE = "on" ] ; then $HDPARM -d 1 "$DEVICE" || rc_failed else $HDPARM -d 1 -X "$MODE" ${OPTIONS:+$OPTIONS} "$DEVICE" || rc_failed fi So, from this, you get to choose either a case-sensitive "on" "off", which will turn on or off the DMA, or you can pass specific options to hdparm. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | RPC600 129Mb RISCOS 3.6 | Falcon 14Mb TOS 4.02 AMD2600(64) 512Mb SUSE 10.0 | A4000 4Mb RISCOS 3.11 | STE 4Mb TOS 1.62

On Wed, 15 Mar 2006, Carlos E. R. wrote:- <snip>

Umm! What if I don't want to set -X (xfermode) to anything at all? The -X parameter is implicit. I tried

DEVICES_FORCE_IDE_DMA="/dev/hdd:-c1:-m16:-u1 "

and it says:

/dev/hdd: setting 32-bit IO_support flag to 1 setting multcount to 16 setting unmaskirq to 1 (on) setting using_dma to 1 (on) setting xfermode to 0 (default PIO mode) <=== multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on)

Looking at the script, it assumes that the first option will be a numerical mode number, but doesn't actually check this is true. I think that there should be a minor change to the script just to counter this. Something like this should do: # Set DMA mode by hdparm utility if [ -z "$MODE" ] ; then echo "Missing DMA mode for device $DEVICE" rc_failed elif [ $MODE = "off" ] ; then $HDPARM -d 0 "$DEVICE" || rc_failed elif [ $MODE = "on" ] ; then $HDPARM -d 1 "$DEVICE" || rc_failed else # if $MODE is non-numeric, $(($MODE+0)) will be return "0" which means # the test is returns true and the first command is executed, otherwise # the second command is executed. if [ $(($MODE+0)) -eq 0 ] ; then $HDPARM -d 1 "$MODE" ${OPTIONS:+$OPTIONS} "$DEVICE" || rc_failed else $HDPARM -d 1 -X "$MODE" ${OPTIONS:+$OPTIONS} "$DEVICE" || rc_failed fi fi Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | RPC600 129Mb RISCOS 3.6 | Falcon 14Mb TOS 4.02 AMD2600(64) 512Mb SUSE 10.0 | A4000 4Mb RISCOS 3.11 | STE 4Mb TOS 1.62

Check your system BIOS - you'll often find a switch for running your disks in 32bit mode. I'm surprised they don't do it by default. I looked. I'm running on a Dell Inspiron 9100 and the BIOS is very limited as to the changes I can make. I can set that on the Sony Vaio that I have that I'm running Kubuntu on. I'll just add the commands to

On Tuesday March 14 2006 01:28, Per Jessen wrote: the /etc/init.d/boot.local file and roll on. -- ~R~ ---------------------------------------------------------- The more things change, the more they stay insane.