Subject: Re: VIA chipset problems - what is recommended solution / workaround?
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: Kent Polk <kent@tiamat.goathill.org>
List: port-i386
Date: 05/14/2001 16:24:53
Manuel Bouyer wrote:
> On Sun, May 13, 2001 at 07:26:55PM +0000, Kent Polk wrote:
> > I thought I'd contribute a little bit of possibly interesting information.
> > 
> > I just picked up a :
> > wd1 at pciide0 channel 1 drive 0: <FUJITSU MPF3102AH>
> > wd1: drive supports 16-sector PIO transfers, LBA addressing
> > wd1: 9773 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 20016348 sectors
> > wd1: 32-bit data port
> > wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
> > 
> > in addition to my :
> > wd0 at pciide0 channel 0 drive 0: <Maxtor 83201A6>
> > wd0: drive supports 16-sector PIO transfers, LBA addressing
> > wd0: 3060 MB, 6218 cyl, 16 head, 63 sec, 512 bytes/sect x 6267744 sectors
> > wd0: 32-bit data port
> > wd0: drive supports PIO mode 4, DMA mode 2
> > 
> > 
> > When I run the MPF3102AH as wd0, it experiences all of the
> 
> With the Maxtor 83201A6 as wd1 on pciide0 channel 1 drive 0 ?

Correct.

> > "pciide0:0:0: lost interrupt" behaviours that have been mentioned.
> > Basically it can't run as wd0.
> > 
> > However, it runs just fine as wd1... Right now I'm booting off of
> > wd1 and it's working great.
> 
> Is it defined in the bios (probably as D or E) ?

AFAIK, both drives show up *correctly* in the bios, regardless of
which channel I have them connected to. I can't remember which
drive designation they correspond to, but they show up in the
correct order. I'll check on that tonight and get back with you.

The Fuj (ATA66) can also *boot* NetBSD from either channel.  Note
that I haven't tried booting the Maxtor (ATA33) from channel 1,
but I don't think there would be a problem.

> Also, is it connected to same cable when as wd1 and wd0 (i.e. do you swap
> cables on motherboard instead of drives) ?

Yes, I am swapping the cables at the motherboard and no other
changes.

With the Fujitsu (ATA66) in channel 0 drive 0, netbsd boots off
the drive fine, but as soon as it tries to set up mount points, it
fails and after a few tries, drops to the boot debugger. I can't
even get the partition it's complaining about to sync before I try
to reboot.  When I reboot with the drive as channel 1 drive 0 after
this, none of the filesystems are corrupted though, so it appears
as though the partitions are never modified.

Another data point (consistent) is that I could only install NetBSD
on the Fuj when it was connected to channel 1 (wd1). It wouldn't
install as wd0 (channel 0), but I can't remember the error message
that was provided when I tried.

As to stability of the Fuj on channel 1(wd0), I did a dump/restore
from the Maxstor straight to the Fuj and completely rebuilt kde2
from that drive yesterday, with no problems whatsoever.