On Sun, Feb 06, 2000 at 06:14:24PM +1300, Juha Saarinen wrote:
> %-> > > Just got a new IBM 7200 RPM 13G HDD, and I am finding it
> %-> impossible to
> %-> > > turn on DMA with hdparm. Kernel version is 2.2.15pre5. It
> %-> immediately
> %-> > > resets and disables DMA. Using '-d1 -X34' causes an immediate, hard
> %-> > > lockup. What's really disappointing is that my el-cheapo WD
> %-> HDDs with
> %-> > > DMA on show 2-3 times the throughput of the IBM with 'hdparm -tT'
>
> Why do you use -X34? The drive is supposed to default to the fastest
> transfer mode at power on. Does -A1c1d1m16u1 work for you? If you use the -X
> parameter, I believe you should try -X66 (UDMA mode 2).
All those options work, except the 'd1'. Causes an immediate reset.
Have tried them individually and as a group.
Well, I usually don't use 'X34', but when all fails I check the man page:
-d Disable/enable the "using_dma" flag for this drive. This option only
works with a few combinations of drives and interfaces which support
DMA and which are known to the IDE driver. In particular, the Intel
Triton chipset is supported for bus-mastered DMA operation with many
drives (experimental). It is also a good idea to use the -X34 option
in combination with -d1 to ensure that the drive itself is programmed
for multiword DMA mode2. Using DMA does not necessarily provide any
improvement in throughput or system performance, but many folks swear
by it. Your mileage may vary.
Just tried it once though, locked up hard.
> That drive is a UDMA-66 one as well... might have something do with your
> problems. What chip set do you have?
This one is an Intel TX (?), supports UDMA33, but not 66. The drive
works fine otherwise.
I rebuilt kernel with Andre Hedrick's latest patch on top of
2.2.15pre5, to no avail. Went back through the config and found
something new there that sounds like it might fit the bill:
Use multi-mode by default
CONFIG_IDEDISK_MULTI_MODE
If you get this error, try to enable this option.
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
I don't see this in 2.2.14 final config. This is not the exact error I get,
but close:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
So I am building again.
--
Hal B
[EMAIL PROTECTED]
--
Linux helps those who help themselves
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
