Date: Wed, 5 Apr 2000 19:56:51 -0400 From: Coleman Kane <cokane@one.net> To: Matt Heckaman <matt@ARPA.MAIL.NET> Cc: Coleman Kane <cokane@one.net>, John Baldwin <jhb@FreeBSD.org>, Warner Losh <imp@village.org>, FreeBSD-STABLE <freebsd-stable@FreeBSD.org>, lioux@uol.com.br Subject: Re: How stable is the ATA code? Message-ID: <20000405195651.A7702@evil.2y.net> In-Reply-To: <Pine.BSF.4.21.0004051453290.50365-100000@epsilon.lucida.qc.ca>; from matt@ARPA.MAIL.NET on Wed, Apr 05, 2000 at 02:56:46PM -0400 References: <20000405145559.A6856@evil.2y.net> <Pine.BSF.4.21.0004051453290.50365-100000@epsilon.lucida.qc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
I have heard of trouble trying to get a non-UDMA drive working connected to a UDMA drive. Try Linking the ad1 to your CDROM's channel and disable the UDMA for Master+Slave 2nd controller in BIOS. Also, WDMA wasn't properly implemented on some drives (I have an old maxtor to testify to that, and many nights of wasted time). This problem is just in the nature of how IDE works, if the two drives being linked together is the problem. Also, your UDMA options in BIOS tell the controller what mode to set the drive in on POST. It may help if there is some problem in the driver to have it turned off in BIOS. I do know that an ATA66 drive should never share the channel with another drive. --cokane Matt Heckaman had the audacity to say: > > And to add one of those annoying "me too" posts, I absolutely cannot get > my setup to work. It's as follows: > > 4.0-STABLE as of April 3 2000 > > atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 > on pci0 > > ad0: 8063MB <WDC AC38400L> [16383/16/63] at ata0-master using UDMA33 > ad1: 1549MB <WDC AC21600H> [3148/16/63] at ata0-slave using WDMA2 > acd0: CDROM <MATSHITA CR-589> at ata1-master using WDMA2 > > ad0 and acd0 work fine, ad1 does not. It bombs with the following error: > > ad1: HARD READ ERROR blk# 0ata0-slave: WARNING: WAIT_READY > active=ATA_ACTIVE_ATA > ad1: HARD READ ERROR blk# 0 status=59 error=04 > ad1: DMA problem fallback to PIO mode > ad1: reading primary partition table: error reading fsbn 0 > > sysctl settings: hw.atamodes: dma,pio,dma,---, > > I know the drive is fine, it works under the wd? drivers but that's a less > than ideal situation. My original posting about this got a reply from > Jordon saying that it was the rollover reason for 4.0-RELEASE, but the bug > is still there and I'm at a loss and quite frustrated. > > Regards, > Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000405195651.A7702>