DMA and RedHat 7.3 PLEASE HELP

mavness · 08-18-2002, 11:04 PM

I have a western digital special edition hard drive with an 8 meg buffer. these are the results i get when i -t -T it....

/dev/hda:
Timing buffer-cache reads: 128 MB in 0.23 seconds =556.52 MB/sec
Timing buffered disk reads: 64 MB in 12.64 seconds = 5.06 MB/sec

when i try to turn dma on...

/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

I am also using redhat 7.3. I looked in my kernel and it seems that all the dma related stuff is turned on. Can somone please tell me what to do. and if its not a problem with my kernel, could it just be an incompatable drive? BTW, i looked in windows and my HD is using DMA5. Thanks in advance.

neo77777 · 08-18-2002, 11:10 PM

What hdparm -i /dev/hda reports compare it to
hdparm -I /dev/hda
Anything different?

mavness · 08-18-2002, 11:20 PM

/sbin/hdparm -i /dev/hda

/dev/hda:

Model=WDC WD1000JB-32CWE0, FwRev=22.04A22, SerialNo=WD-WMA9P1733836
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=195371568
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 *udma5
AdvancedPM=no WriteCache=enabled
Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4 ATA-5

/sbin/hdparm -I /dev/hda

/dev/hda:

non-removable ATA device, with non-removable media
Model Number: WDC WD1000JB-32CWE0
Serial Number: WD-WMA9P1733836
Firmware Revision: 22.04A22
Standards:
Supported: 1 2 3 4 5
Likely used: 5
Configuration:
Logical max current
cylinders 16383 4047
heads 16 16
sectors/track 63 255
bytes/track: 57600 (obsolete)
bytes/sector: 600 (obsolete)
current sector capacity: 16511760
LBA user addressable sectors = 195371568
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 8192.0kB ECC bytes: 40 Queue depth: 1
Standby timer values: spec'd by standard, with device specific minimum
r/w multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
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
SET MAX security extension
* DOWNLOAD MICROCODE cmd
Security:
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 0 determined by CSEL
Checksum: correct

finegan · 08-19-2002, 01:49 AM

See that little '*' infront of the udma5, that's what the drive is running at... but that's weird that the parm is so slow, what's the rpm and size of this monster? Also, is it hooked up to a normal IDE controller or an ata100 controller? Also, do you have it hooked up with an ata 80wire cable or just the normal 48?

Its reading off of that cache at a ridiculous fast speed, but that seek read needs work... even still, if the drive is huge, say 80Gb+, its just hard to get around that.

Cheers,

Finegan

mavness · 08-19-2002, 09:20 AM

7200rpm 8.9 ms seek time and its a 100 gig. But the linux partition is only og 50 gigs of it. This drive IS insanely fast. Thats why i got it. I has an 8 meg buffer as i said. I dont think its on a bad cable because im using the ones that came with the board. Also, i dont know if i said this, windows picks it up as UDMA5. Also, it may have the * because i used -X69 just to see what the drive would do, but i still cant enable dma...anyone have any ideas?

just so you know what its doing...

if i go to UNRAR something or burn a cd, or transfer files over a network, it will go for like 5 seconds, then freeze for 5 seconds, mouse and music stop...then it will go for 5, freeze for 5, etc. This is obviously beyond annoying.

neo77777 · 08-19-2002, 11:51 AM

Hmm, what's the version of hdparm you are currently using? the current is 5.2 available from http://www.ibiblio.org/pub/Linux/system/hardware/ or RPM http://rpmfind.net/linux/rpm2html/se...p?query=hdparm

mavness · 08-19-2002, 12:00 PM

neo, i had 4.6

I installed 5.2.2 and it is still giving me the same error. =(

but thanks, i had no idea redhat 7.3 would put such an outdated program with their distro, lol

mavness · 08-19-2002, 10:22 PM

anyone? =(

N_A_J_M · 08-20-2002, 05:27 AM

Hey Mav how have you gotten on with that DMA error?

I have the same Operation not permitted error

please reply if you have any ideas?

I dont have as good a drive as you but Im sure i should be getting more than 6.7Mb/sec ???
I have a Maxtor 40Gb 7200rpm drive
running Redhat 7.2

mavness · 08-20-2002, 08:19 AM

no...no one can seem to figure this out

neo77777 · 08-20-2002, 08:50 AM

Maybe a stupid question but it is here -
Are you root? /sbin/hdparm -d1 /dev/hda also you might want to use -X flag but before doing so read the man hdparm

Quote:

-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 multi-
word DMA mode2 transfers. With systems which support UltraDMA 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
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
to prevent loss and/or corruption of data. Use this with extreme caution! For the PIO (Programmed
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. Setting 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.

mavness · 08-20-2002, 09:12 AM

yes i am root, and yes i sent the X already. Beleive me, i did read the manual and i have had many people who are much more knoweldgeabe than i try it. I did state somewhere in this thread that i tried the -X69 and it set something to UDMA5 however, i still cant enable dma. Also, i set the IO mode from 16 to 32, that helped a little. I can change anything else except for the -d1. I am on root, and i did do the -X69....im at a loss...no one can seem to figure this one out...Also, i went into the kernel config and all the geenric dma stuff was on...I dont know what else to do.