Re: [Cooker] U66 solved
Hi, Nooo! For UltraDMA2 on your fisrst ide drive, it would be something like this (for an explanation of the number after the -X, see the man page of hdparm): I noticed Webmin in 7.1 has a nice section for setting and testing hdparm, it's under Hardware Partitions on Local Disks Edit IDE Parameters. It even has pop-up help screens for each option. Cheers, -- Phil Lavigna [EMAIL PROTECTED] http://www.linux-mandrake.com/en/demos/
Re: [Cooker] U66 solved
"bobby dowling" [EMAIL PROTECTED] writes: What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? nope, froze anyway here :(
Re: [Cooker] U66 solved
Hello Pixel, On 19 Jun 2000 11:12:38 +0200 GMT your local time, which was Monday, June 19, 2000, 4:12:38 PM (GMT+0700) my local time, Pixel wrote: "bobby dowling" [EMAIL PROTECTED] writes: What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? nope, froze anyway here :( Now a more intriguing question is, has anyone tried to replace these drives under waranty as being out of spec??? They claim to be UDMA66 and they donot run properly so what about getting ones money back... -- Best regards, tracer Using theBAT 1.44 mail to : [EMAIL PROTECTED] using FireTalk: 321338 LOCAL phone: 271194
RE: [Cooker] U66 solved
I have reported the same problem even with the -X option. I've tried various settings on the X flag and when I turned on DMA Transfer, it would crash also. B. K. Barley -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, June 19, 2000 5:13 AM To: [EMAIL PROTECTED] Subject: Re: [Cooker] U66 solved "bobby dowling" [EMAIL PROTECTED] writes: What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? nope, froze anyway here :(
Re: [Cooker] U66 solved
What if you see this at boot-up: HPT366: onboard version of chipset, pin1=1 pin2=2 PCI: HPT366: Fixing interrupt 11 pin 2 to ZERO HPT366: IDE controller on PCI bus 00 dev 98 HPT366: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:DMA, hdf:pio HPT366: IDE controller on PCI bus 00 dev 99 HPT366: not 100% native mode: will probe irqs later ide3: BM-DMA at 0xc400-0xc407, BIOS settings: hdg:DMA, hdh:pio hda: CD-ROM 45X, ATAPI CDROM drive hdc: YAMAHA CRW8424E, ATAPI CDROM drive hde: Maxtor 51536U3, ATA DISK drive hdg: WDC WD136BA, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 ide2 at 0xb000-0xb007,0xb402 on irq 11 ide3 at 0xbc00-0xbc07,0xc002 on irq 11 hde: Maxtor 51536U3, 14655MB w/2048kB Cache, CHS=29777/16/63, UDMA(66) hdg: WDC WD136BA, 13042MB w/1961kB Cache, CHS=26500/16/63, UDMA(66) Doesn't this mean that Dma is already turned on? From: Eugenio Diaz [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Cooker] U66 solved Date: Sun, 18 Jun 2000 22:47:53 -0700 (PDT) MIME-Version: 1.0 Received: from [216.71.84.35] by hotmail.com (3.2) with ESMTP id MHotMailBB16FF6F0062D820F3C8D84754234A0B0; Sun Jun 18 22:49:35 2000 Received: (from sympa@localhost)by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) id AAA00834for [EMAIL PROTECTED]; Mon, 19 Jun 2000 00:48:51 -0500 Received: from web121.yahoomail.com (web121.yahoomail.com [205.180.60.129]) by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) with SMTP id AAA00302 for [EMAIL PROTECTED]; Mon, 19 Jun 2000 00:47:13 -0500 Received: (qmail 14189 invoked by uid 60001); 19 Jun 2000 05:47:53 - Received: from [207.36.26.197] by web121.yahoomail.com; Sun,18 Jun 2000 22:47:53 PDT From [EMAIL PROTECTED] Sun Jun 18 22:51:13 2000 Message-Id: [EMAIL PROTECTED] X-Loop: [EMAIL PROTECTED] X-Sequence: 1232 Precedence: list --- bobby dowling [EMAIL PROTECTED] wrote: What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? Nooo! For UltraDMA2 on your fisrst ide drive, it would be something like this (for an explanation of the number after the -X, see the man page of hdparm): hdparm -d1 -X66 /dev/hda or for an older EIDE drive: hdparm -d1 -X34 /dev/hda **Please note this is dangerous stuff; if you punch in a mode that does not corresponds to what your drive/controller is capable, under some circumstances it could lead to a corrupted file systems. = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: [Cooker] U66 solved
Nope, this are just MFG. ID strings being read by the kernel from the devices. --- bobby dowling [EMAIL PROTECTED] wrote: What if you see this at boot-up: HPT366: onboard version of chipset, pin1=1 pin2=2 PCI: HPT366: Fixing interrupt 11 pin 2 to ZERO HPT366: IDE controller on PCI bus 00 dev 98 HPT366: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:DMA, hdf:pio HPT366: IDE controller on PCI bus 00 dev 99 HPT366: not 100% native mode: will probe irqs later ide3: BM-DMA at 0xc400-0xc407, BIOS settings: hdg:DMA, hdh:pio hda: CD-ROM 45X, ATAPI CDROM drive hdc: YAMAHA CRW8424E, ATAPI CDROM drive hde: Maxtor 51536U3, ATA DISK drive hdg: WDC WD136BA, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 ide2 at 0xb000-0xb007,0xb402 on irq 11 ide3 at 0xbc00-0xbc07,0xc002 on irq 11 hde: Maxtor 51536U3, 14655MB w/2048kB Cache, CHS=29777/16/63, UDMA(66) hdg: WDC WD136BA, 13042MB w/1961kB Cache, CHS=26500/16/63, UDMA(66) Doesn't this mean that Dma is already turned on? = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/
Re: [Cooker] U66 solved
I tried hdparm -d1 -X66 /dev/hdX and I got a significant reduction in performance: Maxtor: 28mb/sec to 15 mb/sec WD: 22mb/sec to 20 mb/sec So, I guess I will just leave the dma setting off (???). From: Eugenio Diaz [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Cooker] U66 solved Date: Sun, 18 Jun 2000 22:47:53 -0700 (PDT) MIME-Version: 1.0 Received: from [216.71.84.35] by hotmail.com (3.2) with ESMTP id MHotMailBB16FF6F0062D820F3C8D84754234A0B0; Sun Jun 18 22:49:35 2000 Received: (from sympa@localhost)by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) id AAA00834for [EMAIL PROTECTED]; Mon, 19 Jun 2000 00:48:51 -0500 Received: from web121.yahoomail.com (web121.yahoomail.com [205.180.60.129]) by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) with SMTP id AAA00302 for [EMAIL PROTECTED]; Mon, 19 Jun 2000 00:47:13 -0500 Received: (qmail 14189 invoked by uid 60001); 19 Jun 2000 05:47:53 - Received: from [207.36.26.197] by web121.yahoomail.com; Sun,18 Jun 2000 22:47:53 PDT From [EMAIL PROTECTED] Sun Jun 18 22:51:13 2000 Message-Id: [EMAIL PROTECTED] X-Loop: [EMAIL PROTECTED] X-Sequence: 1232 Precedence: list --- bobby dowling [EMAIL PROTECTED] wrote: What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? Nooo! For UltraDMA2 on your fisrst ide drive, it would be something like this (for an explanation of the number after the -X, see the man page of hdparm): hdparm -d1 -X66 /dev/hda or for an older EIDE drive: hdparm -d1 -X34 /dev/hda **Please note this is dangerous stuff; if you punch in a mode that does not corresponds to what your drive/controller is capable, under some circumstances it could lead to a corrupted file systems. = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: [Cooker] U66 solved
Ok Ok but how do you test the speeds of your drives?
My drive supports
Model=Maxtor 92720U8, FwRev=MA540RR0, SerialNo=C803RN7C
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=53177040
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4
so.. UDMA 4 is the fastest... I dont know what I am running
at right now.. is this told in the above information?
I mainly want to know if there is a way to benchmark your
throughput...
Thanks.
Chrisopher Campbell
On Mon, 19 Jun 2000, you wrote:
Did you do it specifiying both flags at the same time?
What -Xxx value did you use?
First query your drive with "hdparm -i /dev/hda" to
see what modes your drive support.
From the hdparm man page:
...
-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 supAD
ported interface chipset (such as the
Intel 430FX
Triton), where -X34 is used to select
multiword DMA
mode2 transfers. With systems which
support UltraAD
DMA burst timings, -X66 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 necessary 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 alterAD
nate 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 setAD
ting to prevent loss and/or
corruption of data.
Use this with extreme caution! For the
PIO (ProAD
grammed 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. SetAD
ting 00 restores the drive's
"default" PIO mode,
and 01 disables IORDY. For multiword
DMA, the
value used is the desired DMA mode
number plus 32.
for UltraDMA, the value is the
desired UltraDMA
mode number plus 64.
...
It says that most modern drives default to the fastest
mode; he, he, he, I had always have to use hdparm to
get an average of only *twice* the default performance
with all the drives I have ever had. ;-)
--- Pixel [EMAIL PROTECTED] wrote:
"bobby dowling" [EMAIL PROTECTED] writes:
What do you mean the -d flag without the -X flags?
So, you can say -dX and those WD drives that froze
the system before would
work?
nope, froze anyway here :(
=
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__
Do You Yahoo!?
Send instant messages with Yahoo! Messenger.
http://im.yahoo.com/
Re: [Cooker] U66 solved
--- bobby dowling [EMAIL PROTECTED] wrote: Both drives say that they are capable of the following: DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 I am supposing the star means that the drive is set to udma4, correct? If you used "hdparm -I" then you get the info unformatted directly from the drive, and yes the asterisk indicates the mode the drive is currently set to. These are my hdparm settings: hdparm -q -c3 -q -A1 -q -m16 I guess you could use something like this: hdparm -q -c3 -q -A1 -q -m16 -q -d1 -q -X68 = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/
Re: [Cooker] U66 solved
On Mon, 19 Jun 2000, bobby dowling wrote: I tried hdparm -d1 -X66 /dev/hdX and I got a significant reduction in performance: Maxtor: 28mb/sec to 15 mb/sec WD: 22mb/sec to 20 mb/sec So, I guess I will just leave the dma setting off (???). With 28MB/s dma is definitly turned on. Probably by the kernel. I get 14MB/s on a U33 drive which isn't to old. seb
Re: [Cooker] U66 solved
Just comment out the optimization code in the file "/etc/rc.d/init.d/mandrake_everytime", and put in your own optimization string, so that part of the file looks like this (*note, I have posted here before that the some Western Digital drives hang the machine if you use the -d without the -X flags): -- # Optimisation of Hard drive. #if grep -qi opti /proc/cmdline || [ -n "$HDPARM" ]; then #if [ -x /sbin/hdparm ];then # LIST_HD=$(grep '^hd.:' /var/log/dmesg|\ # grep -ivE '(CD.*ROM|DVD.*ROM|FLOPPY|TAPE|STATUS)'|cut -d: -f1|sort|uniq) # # if grep -i nohdparm /proc/cmdline /dev/null ; then # action "Hard Drive optimisations disabled" \ # echo "" # else # for i in $LIST_HD;do # action "Starting Hard Drive optimisations for $i" \ # hdparm -q -c1 -q -A1 -q -m16 -q -d1 /dev/$i # done # fi #fi #fi hdparm -q -c1 -q -A1 -q -u1 -q -m16 -q -d1 -q -X66 /dev/hda # WDC AC310100B 10.1GB DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 hdparm -q -c1 -q -A1 -q -u1 -q -m16 -q -d1 -q -X66 /dev/hdb # WDC WD307AA 30.7 GB DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 hdparm -q -c1 -q -A1 -q -u1 -q -m16 -q -d1 -q -X66 /dev/hdc # WDC AC310200R 10.2 GB DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 hdparm -q -c1 -q -A1 -q -u1 -q -m16 -q -d1 -q -X34 /dev/hdd # Maxtor 85120A8 DMA modes: mdma0 mdma1 mdma2 Also note that Linux only support up to UDMA2, UDMA3 and UDMA4 are not yet supported. As a matter of fact I don't know what these modes are, since I always though ATA66 == UDMA2! Anyone know what UDMA3 and UDMA4 are? May be ATA100? Remember that if you activate dma without indicating a proper -x flag, it will hang! At least the WD drives I got. --- Stratos Laspas [EMAIL PROTECTED] wrote: ML7.1 installes and runs ok, on a system with a Promise U66, provided that no disk optimization is employed. = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/
Re: [Cooker] U66 solved
Eugenio Diaz [EMAIL PROTECTED] writes: Just comment out the optimization code in the file "/etc/rc.d/init.d/mandrake_everytime", and put in your own optimization string, so that part of the file looks like this (*note, I have posted here before that the some Western Digital drives hang the machine if you use the -d without the -X flags): nice hint. Testing it on my box :) (which effectively froze with -d without -X) thanks, cu Pixel.
Re: [Cooker] U66 solved
What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? From: Pixel [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Cooker] U66 solved Date: 18 Jun 2000 12:11:56 +0200 Received: from [216.71.84.35] by hotmail.com (3.2) with ESMTP id MHotMailBB15EBA4002BD820F3A7D8475423353D0; Sun Jun 18 03:12:52 2000 Received: (from sympa@localhost)by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) id FAA20636for [EMAIL PROTECTED]; Sun, 18 Jun 2000 05:13:15 -0500 Received: from leia.mandrakesoft.com (office [195.68.114.34]) by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) with ESMTP id FAA19797 for [EMAIL PROTECTED]; Sun, 18 Jun 2000 05:10:50 -0500 Received: by leia.mandrakesoft.com (Postfix, from userid 505) id 44E3357A9; Sun, 18 Jun 2000 12:11:56 +0200 (CEST) From [EMAIL PROTECTED] Sun Jun 18 03:17:03 2000 Sender: [EMAIL PROTECTED] References: [EMAIL PROTECTED] In-Reply-To: Eugenio Diaz's message of "Sun, 18 Jun 2000 02:42:43 -0700 (PDT)" Message-Id: [EMAIL PROTECTED] Lines: 14 X-Mailer: Gnus v5.7/Emacs 20.7 X-Loop: [EMAIL PROTECTED] X-Sequence: 1184 Precedence: list Eugenio Diaz [EMAIL PROTECTED] writes: Just comment out the optimization code in the file "/etc/rc.d/init.d/mandrake_everytime", and put in your own optimization string, so that part of the file looks like this (*note, I have posted here before that the some Western Digital drives hang the machine if you use the -d without the -X flags): nice hint. Testing it on my box :) (which effectively froze with -d without -X) thanks, cu Pixel. Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: [Cooker] U66 solved
--- bobby dowling [EMAIL PROTECTED] wrote: What do you mean the -d flag without the -X flags? So, you can say -dX and those WD drives that froze the system before would work? Nooo! For UltraDMA2 on your fisrst ide drive, it would be something like this (for an explanation of the number after the -X, see the man page of hdparm): hdparm -d1 -X66 /dev/hda or for an older EIDE drive: hdparm -d1 -X34 /dev/hda **Please note this is dangerous stuff; if you punch in a mode that does not corresponds to what your drive/controller is capable, under some circumstances it could lead to a corrupted file systems. = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/
