Date: Sun, 31 May 1998 16:09:41 -0400 From: "Hartong" <hartong@erols.com> To: <freebsd-questions@FreeBSD.ORG> Cc: <freebsd-newbies@FreeBSD.ORG>, <freebsd-hardware@FreeBSD.ORG> Subject: ATAPI CD ROM Installation Failure on BSD 2.2.6 Message-ID: <01bd8cd0$0c06cb60$7229accf@mhartong.man.fs.lmco.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BD8CAE.84F52B60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable HELP!!!!! While installing FreeBSD 2.2.6 I I obtain the following: The system locks up with the dreaded blue screen of death on virtual = console 1 with "Probing devices, Please wait..." Diagnostic message on virtual console 2 ATAPI.IO: INVALID COMMAND PHASE, = IREASON=3D0xd8,STATUS=3Dd8<BUSY,READY,OPDONE,IRQ>, ERROR=3Dd8<mchg> Hardware Configuration: NEC CD-Rom Drive 273, running as master on = secondary IDE controller 1GB HD running as master on primary IDE = controller. System is a Dell Dimension P133. <All in all a relatively = "standard" equipment and configuration, I think> Additional Diagnostic Information: 1 System will do intial boot from CD Rom player with CD Rom selected as = intial boot medium. Configuration is accomplished, all conflicts are = resolved. System starts reboot recognizes wcd0 and wcd1 controllers, = then freezes. 2. System will do intial boot from floopy selected as intial boot = medium. Configuration is accomplished, all conflicts are resolved. = System starts reboot recognizes wcd0 and wcd1 controllers, then freezes 3. CD-ROM player placed as slave on primary IDE controller. System = will do intial boot from CD Rom with CD Rom selected as intial boot = medium. Configuration is accomplished, all conflicts are resolved. = System starts reboot recognizes wcd0 and wcd1 controllers, then = freezes. 4. CD-ROM player placed as slave on primary IDE controller. System = will do intial boot from flloppy selected as intial boot medium. = Configuration is accomplished, all conflicts are resolved. System = starts reboot recognizes wcd0 and wcd1 controllers, then freezes. Help, what do I do next! I've gone through the FAQ's, searched the = Mailing List archives, and tried deciphering the ATAPIA source code with = no luck. I've run out of ideas. I'm sure that someone must have = encountered this problem somewhere. As a last resort I could try a DOS = installation, but that still leaves the problem of an unrecognized CD = ROM player to fix. I really DON"T want to go back to Linux :( Regds =20 Mark Hartong =20 hartong@erols.com mark.hartong@lmco.com ------=_NextPart_000_0008_01BD8CAE.84F52B60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3Dtext/html;charset=3Diso-8859-1 = http-equiv=3DContent-Type> <META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT color=3D#000000 size=3D2>HELP!!!!!</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>While installing FreeBSD 2.2.6 I I = obtain the=20 following:</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT size=3D2>The system locks up with the dreaded blue screen of=20 death on virtual console 1 with "Probing devices, Please=20 wait..."</FONT></DIV> <DIV><FONT size=3D2></FONT><FONT color=3D#000000 size=3D2><FONT = color=3D#000000=20 size=3D2></FONT></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2><FONT color=3D#000000 = size=3D2>Diagnostic message on=20 virtual console 2</FONT></FONT></DIV> <DIV><FONT color=3D#000000 size=3D2><FONT color=3D#000000 = size=3D2></FONT> </DIV> <DIV>ATAPI.IO: INVALID COMMAND PHASE,=20 IREASON=3D0xd8,STATUS=3Dd8<BUSY,READY,OPDONE,IRQ>,=20 ERROR=3Dd8<mchg></FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>Hardware Configuration: = </FONT><FONT=20 color=3D#000000 size=3D2>NEC CD-Rom Drive 273, running as master on = secondary IDE=20 controller 1GB HD running as master on primary IDE = controller. =20 System is a Dell Dimension P133. <All in all a relatively=20 "standard" equipment and configuration, I = think></FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>Additional Diagnostic = Information:</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>1 System will do intial boot = from CD Rom=20 player with CD Rom selected as intial boot medium. Configuration = is=20 accomplished, all conflicts are resolved. System starts = reboot =20 recognizes wcd0 and wcd1 controllers, then freezes.</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>2. System will do intial boot = from floopy=20 selected as intial boot medium. Configuration is accomplished, all = conflicts are resolved. System starts reboot recognizes wcd0 = and=20 wcd1 controllers, then freezes</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>3. CD-ROM player placed as = slave on=20 primary IDE controller. System will do intial boot from CD Rom = with CD Rom=20 selected as intial boot medium. Configuration is accomplished, all = conflicts are resolved. System starts reboot recognizes wcd0 = and=20 wcd1 controllers, then freezes.</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>4. CD-ROM player placed = as slave on=20 primary IDE controller. System will do intial boot from flloppy = selected=20 as intial boot medium. Configuration is accomplished, all = conflicts are=20 resolved. System starts reboot recognizes wcd0 and wcd1 = controllers,=20 then freezes.</FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV> <DIV><FONT color=3D#000000 size=3D2>Help, what do I do next! I've = gone through=20 the FAQ's, searched the Mailing List archives, and tried deciphering the = ATAPIA=20 source code with no luck. I've run out of ideas. I'm sure = that=20 someone must have encountered this problem somewhere. As a last = resort I=20 could try a DOS installation, but that still leaves the problem of an=20 unrecognized CD ROM player to fix. </FONT><FONT size=3D2>I really = DON"T=20 want to go back to Linux :(</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV></DIV> <DIV><FONT color=3D#000000 size=3D2> <DIV><FONT size=3D2>Regds</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>Mark Hartong</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2><A=20 href=3D"mailto:hartong@erols.com">hartong@erols.com</A></FONT></DIV> <DIV><FONT size=3D2></FONT><FONT color=3D#000000 size=3D2><A=20 href=3D"mailto:mark.hartong@lmco.com">mark.hartong@lmco.com</A></FONT></D= IV></FONT></DIV></BODY></HTML> ------=_NextPart_000_0008_01BD8CAE.84F52B60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01bd8cd0$0c06cb60$7229accf>