Date: Sat, 13 Jun 1998 11:45:54 -0700 From: Mike Smith <mike@smith.net.au> To: Doug White <dwhite@resnet.uoregon.edu> Cc: hackers@FreeBSD.ORG Subject: Re: ATAPI CD ROM Installation Failure on BSD 2.2.6 (fwd) Message-ID: <199806131845.LAA00629@antipodes.cdrom.com> In-Reply-To: Your message of "Thu, 11 Jun 1998 02:39:58 PDT." <Pine.BSF.3.96.980611023912.305C-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Somebody want to try to decode the ATAPI error message that this guy is > getting? We've checked cabling and it all checks out. I forget the model > of drive tho. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > NOTICE: Make sure your mailer replies to dwhite@resnet or I won't get it! > > ---------- Forwarded message ---------- > Date: Tue, 9 Jun 1998 21:15:09 -0400 > From: Hartong <hartong@erols.com> > To: Doug White <dwhite@resnet.uoregon.edu> > Subject: Re: ATAPI CD ROM Installation Failure on BSD 2.2.6 > > Hello Doug... > > Sorry about not getting back to you sooner, I had to go into the hospital > again.. ye olde kidneys went into failure mode .... > > > >Hm.... verify that your master/slave jumpers are correct and you cable is > >okay. That's about all I can figure is going on. > > > I've tried all the combinations of the CD-ROM as master and slave both on > the primary and secondary ide controller with the same results. > > ATAPI1.O: INVALID COMMAND PHASE, > IREASON=0xd8,STATUS=d8<BUSY,READY,OPDONE,IRQ>, ERROR=d8<mchg> > > > Any other ideas? > > Do you know anyone on the core team who spent some time writing the > interface driver could read the error message? Maybe they could put the > error message in context and that will provide some clues as to what is > going wrong? Sure; the driver is saying "the drive is not in the phase I expected it to be in". Sort of "what the hell does it think it's doing?" More interestingly, note that the 'ireason', 'status' and 'error' values are *all* 0xd8. This implies that there's a really basic problem talking to the drive. My suspicions would tend to suggest timing problems of some sort; either we are not giving the drive enough time to behave, or perhaps the user is overclocking and their IDE controller isn't playing the game. Seeing the full set of wd* probe messages would be useful, especially if there are other devices involved. Also, knowing the set of actions leading to the fault would help. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806131845.LAA00629>