* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:35 Enrico Bartky
0 siblings, 0 replies; 8+ messages in thread
From: Enrico Bartky @ 2004-11-12 15:35 UTC (permalink / raw)
To: linux-kernel
The dmesg after hdparm command is
--snip--
hde: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }ide: failed opcode was 100
hde: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: CHECK for good STATUS
--snap--
What does that mean?
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
^ permalink raw reply [flat|nested] 8+ messages in thread* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:51 Enrico Bartky
0 siblings, 0 replies; 8+ messages in thread
From: Enrico Bartky @ 2004-11-12 15:51 UTC (permalink / raw)
To: linux-kernel
In the catalog there is described that the drive can use UDMA66 Mode
http://www.fujitsu.com/global/support/computing/storage/hdd/eol/dhdd/mpd3xxat-catalog.html
"Piszcz, Justin Michael" <justin.piszcz@mitretek.org> schrieb am 12.11.04 16:46:08:
Maybe someone can step in if I am wrong, but I believe the drive cannot
use that mode.
There could also be multi-mode/issues.
Try hdparm -c3 -d1 -u1 -X68 /dev/hde
If that does not work, I am not sure if the drive will support that
mode.
For reference, I have a 61.4GB (MAXTOR) on a promise card, and it uses
the following mode in use:
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 57 Queue depth: 1
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = 0
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 192, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
And a 40GB:
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 40 Queue depth: 32
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
My guess is either:
1) The drive does not support it.
2) There is a multi-mode issue with DMA/the disk.
See the following kernel option:
Device Drivers --->
ATA/ATAPI/MFM/RLL support --->
<*> Include IDE/ATA-2 DISK support
[*] Use multi-mode by default
The help states:
Use multi-mode by default
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
I normally say Y here.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Enrico Bartky
Sent: Friday, November 12, 2004 10:35 AM
To: linux-kernel@vger.kernel.org
Subject: RE: PROMISE Ultra133 TX2 (PDC20269)
The dmesg after hdparm command is
--snip--
hde: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
DataRequest }ide: failed opcode was 100
hde: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: CHECK for good STATUS
--snap--
What does that mean?
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201
^ permalink raw reply [flat|nested] 8+ messages in thread* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:49 Piszcz, Justin Michael
0 siblings, 0 replies; 8+ messages in thread
From: Piszcz, Justin Michael @ 2004-11-12 15:49 UTC (permalink / raw)
To: Enrico Bartky, linux-kernel
Odd, what speed did you get with UDMA2? UDMA3?
Any errors in dmesg other then the ones you pasted?
Also, when benchmarking with hdparm (as it states in the man page, it is
good to run it 3 times for each run and take the average) as it can vary
sometimes.
I have also noticed if you are running hdparm -t /dev/hde when running
X, window manager, etc, I get 8-10MB/s less vs. when I run it in single
user mode.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Enrico Bartky
Sent: Friday, November 12, 2004 10:44 AM
To: linux-kernel@vger.kernel.org
Subject: RE: PROMISE Ultra133 TX2 (PDC20269)
mysterios, .. now it says udma4 but with 7 MB/s
schrottkiste:~# hdparm -I /dev/hde
/dev/hde:
ATA device, with non-removable media
Model Number: FUJITSU MPD3084AT
Serial Number: 01064533
Firmware Revision: DD-03-44
Standards:
Supported: 4 3 2 1
Likely used: 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 16514064
device size with M = 1024*1024: 8063 MBytes
device size with M = 1000*1000: 8455 MBytes (8 GB)
Capabilities:
LBA, IORDY(cannot be disabled)
Buffer size: 512.0kB bytes avail on r/w long: 4 Queue
depth: 1
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 16 Current = ?
Advanced power management level: unknown setting (0x0000)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
READ BUFFER cmd
WRITE BUFFER cmd
Host Protected Area feature set
* Look-ahead
* Write cache
Power Management feature set
Security Mode feature set
SMART feature set
Advanced Power Management feature set
Security:
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
24min for SECURITY ERASE UNIT.
schrottkiste:~# hdparm -t /dev/hde
/dev/hde:
Timing buffered disk reads: 26 MB in 3.45 seconds = 7.53 MB/sec
schrottkiste:~#
__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 8+ messages in thread* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:43 Enrico Bartky
0 siblings, 0 replies; 8+ messages in thread
From: Enrico Bartky @ 2004-11-12 15:43 UTC (permalink / raw)
To: linux-kernel
mysterios, .. now it says udma4 but with 7 MB/s
schrottkiste:~# hdparm -I /dev/hde
/dev/hde:
ATA device, with non-removable media
Model Number: FUJITSU MPD3084AT
Serial Number: 01064533
Firmware Revision: DD-03-44
Standards:
Supported: 4 3 2 1
Likely used: 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 16514064
device size with M = 1024*1024: 8063 MBytes
device size with M = 1000*1000: 8455 MBytes (8 GB)
Capabilities:
LBA, IORDY(cannot be disabled)
Buffer size: 512.0kB bytes avail on r/w long: 4 Queue depth: 1
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 16 Current = ?
Advanced power management level: unknown setting (0x0000)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
READ BUFFER cmd
WRITE BUFFER cmd
Host Protected Area feature set
* Look-ahead
* Write cache
Power Management feature set
Security Mode feature set
SMART feature set
Advanced Power Management feature set
Security:
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
24min for SECURITY ERASE UNIT.
schrottkiste:~# hdparm -t /dev/hde
/dev/hde:
Timing buffered disk reads: 26 MB in 3.45 seconds = 7.53 MB/sec
schrottkiste:~#
__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201
^ permalink raw reply [flat|nested] 8+ messages in thread* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:41 Piszcz, Justin Michael
0 siblings, 0 replies; 8+ messages in thread
From: Piszcz, Justin Michael @ 2004-11-12 15:41 UTC (permalink / raw)
To: Enrico Bartky, linux-kernel
Maybe someone can step in if I am wrong, but I believe the drive cannot
use that mode.
There could also be multi-mode/issues.
Try hdparm -c3 -d1 -u1 -X68 /dev/hde
If that does not work, I am not sure if the drive will support that
mode.
For reference, I have a 61.4GB (MAXTOR) on a promise card, and it uses
the following mode in use:
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 57 Queue depth: 1
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = 0
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 192, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
And a 40GB:
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 40 Queue depth: 32
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
My guess is either:
1) The drive does not support it.
2) There is a multi-mode issue with DMA/the disk.
See the following kernel option:
Device Drivers --->
ATA/ATAPI/MFM/RLL support --->
<*> Include IDE/ATA-2 DISK support
[*] Use multi-mode by default
The help states:
Use multi-mode by default
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
I normally say Y here.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Enrico Bartky
Sent: Friday, November 12, 2004 10:35 AM
To: linux-kernel@vger.kernel.org
Subject: RE: PROMISE Ultra133 TX2 (PDC20269)
The dmesg after hdparm command is
--snip--
hde: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
DataRequest }ide: failed opcode was 100
hde: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: CHECK for good STATUS
--snap--
What does that mean?
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 8+ messages in thread* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:29 Piszcz, Justin Michael
0 siblings, 0 replies; 8+ messages in thread
From: Piszcz, Justin Michael @ 2004-11-12 15:29 UTC (permalink / raw)
To: Enrico Bartky, linux-kernel
After you try to set it with -X68 (udma4) check the udma setting, if it
has not changed, type 'dmesg' and check for any error messages and post
them back to the list.
I also use the same card and have not had these problems; however, the
smallest drive I use is 40GB.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Enrico Bartky
Sent: Friday, November 12, 2004 10:14 AM
To: linux-kernel@vger.kernel.org
Subject: PROMISE Ultra133 TX2 (PDC20269)
Hello,
I have the following problem with my controller:
I have attached a 8 GB UDMA4 Harddisk, but it works only with UDMA2. The
controller BIOS displays the right mode (4), but in the kernel dmesg it
comes with pio. after i execute hdparm -I /dev/hde it says:
... udma2* udma3 udma4
If I try to force the UDMA4 mode with hdparm -Xudma4 /dev/hde , ...
theres no difference. The harddisk leaves at udma2.
What can I do?
I have tried 2.4.26, 2.6.9, 2.6.10-rc1...
Can you help me?
Thanx, EnricoB
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:26 Piszcz, Justin Michael
0 siblings, 0 replies; 8+ messages in thread
From: Piszcz, Justin Michael @ 2004-11-12 15:26 UTC (permalink / raw)
To: Enrico Bartky, linux-kernel
Hrmm, I have never seen that syntax, have you tried
hdparm -X68 /dev/hde (udma 4)
Or
hdparm -X69 /dev/hde (udma 5)
What type of disk are you using?
root@p500:~# hdparm -X69 /dev/hde
/dev/hde:
setting xfermode to 69 (UltraDMA mode5)
root@p500:~# hdparm -X68 /dev/hde
/dev/hde:
setting xfermode to 68 (UltraDMA mode4)
root@p500:~# hdparm -X67 /dev/hde
/dev/hde:
setting xfermode to 67 (UltraDMA mode3)
root@p500:~# hdparm -X69 /dev/hde
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Enrico Bartky
Sent: Friday, November 12, 2004 10:14 AM
To: linux-kernel@vger.kernel.org
Subject: PROMISE Ultra133 TX2 (PDC20269)
Hello,
I have the following problem with my controller:
I have attached a 8 GB UDMA4 Harddisk, but it works only with UDMA2. The
controller BIOS displays the right mode (4), but in the kernel dmesg it
comes with pio. after i execute hdparm -I /dev/hde it says:
... udma2* udma3 udma4
If I try to force the UDMA4 mode with hdparm -Xudma4 /dev/hde , ...
theres no difference. The harddisk leaves at udma2.
What can I do?
I have tried 2.4.26, 2.6.9, 2.6.10-rc1...
Can you help me?
Thanx, EnricoB
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 8+ messages in thread
* PROMISE Ultra133 TX2 (PDC20269)
@ 2004-11-12 15:14 Enrico Bartky
0 siblings, 0 replies; 8+ messages in thread
From: Enrico Bartky @ 2004-11-12 15:14 UTC (permalink / raw)
To: linux-kernel
Hello,
I have the following problem with my controller:
I have attached a 8 GB UDMA4 Harddisk, but it works only with UDMA2. The controller BIOS displays the right mode (4), but in the kernel dmesg it comes with pio. after i execute hdparm -I /dev/hde it says:
... udma2* udma3 udma4
If I try to force the UDMA4 mode with hdparm -Xudma4 /dev/hde , ... theres no difference. The harddisk leaves at udma2.
What can I do?
I have tried 2.4.26, 2.6.9, 2.6.10-rc1...
Can you help me?
Thanx, EnricoB
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2004-11-12 15:52 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-12 15:35 PROMISE Ultra133 TX2 (PDC20269) Enrico Bartky
-- strict thread matches above, loose matches on Subject: below --
2004-11-12 15:51 Enrico Bartky
2004-11-12 15:49 Piszcz, Justin Michael
2004-11-12 15:43 Enrico Bartky
2004-11-12 15:41 Piszcz, Justin Michael
2004-11-12 15:29 Piszcz, Justin Michael
2004-11-12 15:26 Piszcz, Justin Michael
2004-11-12 15:14 Enrico Bartky
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox