From owner-freebsd-hackers Fri Jun 12 21:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24325 for freebsd-hackers-outgoing; Fri, 12 Jun 1998 21:22:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gdi.uoregon.edu (metriclient-1.uoregon.edu [128.223.172.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24319 for ; Fri, 12 Jun 1998 21:22:33 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id CAA00314 for ; Thu, 11 Jun 1998 02:39:58 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Thu, 11 Jun 1998 02:39:58 -0700 (PDT) From: Doug White Reply-To: Doug White To: hackers@FreeBSD.ORG Subject: Re: ATAPI CD ROM Installation Failure on BSD 2.2.6 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To: Doug White 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, ERROR=d8 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? Thanks Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message