Messages in this thread | | | From | Andrej Todosic <> | Subject | RE: Abit BP6 UDMA issues. | Date | Fri, 13 Aug 1999 09:03:15 -0400 |
| |
i have a quantum fireballst udma 33 drive. Its not that fast but anyways. i cant run udma33 either i get the exact same thing if i switch to udma 33 ,
i did turn dma on , and i did turn 32bit transfers on ... but thats it. that made me go up to 7.5 from 4-5 mb/sec ... since this is my boot dirve i had to reboot about 7 times (every time i turned udma on ) and i finally gave up...
here is a listing from my hdparm :
[root@beast widow]# hdparm /dev/hda
/dev/hda: multcount = 0 (off) I/O support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 782/128/63, sectors = 6306048, start = 0
here are the settings i use : grep hdparm * grep: init.d: Is a directory rc.local:hdparm -X12 /dev/hda rc.local:hdparm -c1 /dev/hda rc.local:hdparm -d1 /dev/hda rc.local:hdparm -u1 /dev/hda
-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 (such as the Intel 430FX Triton), where -X34 is used to select multiword DMA mode2 trans- fers. 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 need- less 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.
> -----Original Message----- > From: Bart Kus [mailto:kernel@ERTW.ca] > Sent: Friday, August 13, 1999 12:12 AM > To: linux-kernel@vger.rutgers.edu > Subject: Abit BP6 UDMA issues. > > > Hi, I hope you find this informative. > > I recently bought an Abit BP6 and am trying to get my drives > working with it at UDMA(33) speeds. I keep on getting these errors: > > hdb: timeout waiting for DMA > hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest } > hda: DMA disabled > hdb: DMA disabled > ide0: reset: success > > whenever I try to write large amounts of data to /dev/hdb. > > Here are some "interesting" clippings of boot sequences and > other things. > > (from dmesg) > hda: ST36450A, 6149MB w/448kB Cache, CHS=784/255/63, DMA > hdb: Maxtor 92048D8, 19531MB w/512kB Cache, CHS=39683/16/63, UDMA(33) > hdc: IBM-DJAA-31700, 1628MB w/96kB Cache, CHS=3308/16/63, DMA > hdd: ATAPI 24X CD-ROM drive, 128kB Cache, DMA > > (from dmesg) > Partition check: > hda: hda1 > hdb: hdb1 > hdc:hdc: timeout waiting for DMA > hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest } > hdc: timeout waiting for DMA > hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest } > hdc: timeout waiting for DMA > hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest } > hdc: timeout waiting for DMA > hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest } > hdc: DMA disabled > hdd: DMA disabled > ide1: reset: success > [PTBL] [827/64/63] hdc1 > > (from hdparm -t /dev/hda) > /dev/hda: > Timing buffered disk reads: 32 MB in 3.73 seconds = 8.58 MB/sec > > (from hdparm -t /dev/hdb) > /dev/hdb: > Timing buffered disk reads: 32 MB in 1.67 seconds =19.16 MB/sec > > As you can tell, I bought /dev/hdb for SPEED :) It'd be nice > to be able to > capture video to it. Make It Go(tm) ? :) > > --Bart > > > - > To unsubscribe from this list: send the line "unsubscribe > linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > 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.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |