Date: Fri, 01 Sep 2000 15:22:59 +0700 From: Roger Merritt <mcrogerm@stjohn.ac.th> To: Dave Uhring <duhring@charter.net> Cc: freebsd-stable@freebsd.org Subject: Re: ata0-slave doesn't show up! Message-ID: <3.0.6.32.20000901152259.008dd2f0@stjohn.stjohn.ac.th> In-Reply-To: <00083123523300.00265@dave.uhring.com> References: <3.0.6.32.20000901105303.008c39d0@stjohn.stjohn.ac.th> <3.0.6.32.20000901105303.008c39d0@stjohn.stjohn.ac.th>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:52 PM 8/31/00 -0500, you wrote: >On Thu, 31 Aug 2000, Roger Merritt wrote: >> Has anybody found a solution to this yet? My workaround was to go back >> to the wdc device rather than the ata device, but it might be better >> for me to back down from 4.1-STABLE to 4.1-RELEASE and use the newer >> device. My CD-ROM is at ata0-slave and also wasn't being detected at >> bootup. Exactly the same symptoms as below. >> >-----------snip of dmesg and conf file ------------------ > >See dmesg from my system: > >Dave > >Attachment Converted: "c:\program files\eudora\attach\dmesg1" > OK, so from your dmesg I see: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 12427MB <Maxtor 91303D6> [25249/16/63] at ata0-master using UDMA33 ad1: 1220MB <Maxtor 81275 A3> [2480/16/63] at ata0-slave using WDMA2 acd0: CDROM <IDE/ATAPI CD-ROM 44XS> at ata1-master using UDMA33 which means the ata driver is detecting the hard drive at ata0-slave, while for some reason it does *not* detect the cd-rom at ata0-slave on my machine. Hmmm. Well, let me try a new compile with the ata device. -- Roger 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?3.0.6.32.20000901152259.008dd2f0>