Re: UDMA and VIA APOLLO CHIPSET

Matthias Andree (mandree@sx1.HRZ.Uni-Dortmund.DE)
Wed, 7 Jul 1999 13:31:01 +0200

* Sid Boyce (szb50@amdahl.com) [1999-07-03 15:04]:
> I have some problems seen below, when I installed the new Maxstor drive
> and tried installing Caldera 2.2 on it, I got a repeated hang with the
> HD and CDROM (EIDE both) having their access lights solidly on.

Maxtor drives are _extremely_ picky about cabling and clocks.

> I had to take the Maxstor drive to a friend's house and install Caldera
> on it using his machine.
> Soon after I read somewhere in this mailing list that there are known
> problems with UDMA HD's and CDROM's associated with the Via Apollo
> chipset.

I'm not.

lspci (stripped VGA, Multimedia and Net stuff)
00:00.0 Host bridge: VIA Technologies, Inc. VT82C597 [Apollo VP3] (rev 04)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8598
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586 ISA [Apollo VP] (rev 41)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
00:08.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875 (rev 03)
00:0b.0 SCSI storage controller: Advanced Micro Devices 53c974 [PCscsi] (rev 10)

(Heck, I need to upgrade my pci stuff, it does not contain the chips I
sent to Martin quite some time ago)

emma1:~ # hdparm -iv /dev/hda | grep -v '(off)' # stripped serialno

/dev/hda:
multcount = 8 (on)
I/O support = 3 (32-bit w/sync)
unmaskirq = 1 (on)
using_dma = 1 (on)
readahead = 8 (on)
geometry = 2482/255/63, sectors = 39876480, start = 0

Model=WDC AC420400D, FwRev=J58OA30K, SerialNo=
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=39560/16/63, TrkSize=0, SectSize=0, ECCbytes=34
BuffType=3(DualPortCache), BuffSize=1966kB, MaxMultSect=16, MultSect=8
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
CurCHS=2482/255/63, CurSects=39876480, LBA=yes, LBAsects=39876480
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4

> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

Try shorter cables or some SLOW PIO mode until you have better (shorter
cables). Nothing about the chip set.

-- 
Matthias Andree


            Give a man a fish and you feed him for a day;
     teach him to use the Net and he won't bother you for weeks.


-
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/