Date: Sun, 13 Jun 1999 18:27:35 +1000 From: Greg Black <gjb-freebsd@gba.oz.au> To: John Reynolds~ <jreynold@sedona.ch.intel.com> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, "Kenneth D. Merry" <ken@plutotech.com>, freebsd-stable@FreeBSD.ORG Subject: Re: Is the CD driver supposed to attach() now regardless of media? Message-ID: <19990613082735.9292.qmail@alice.gba.oz.au> In-Reply-To: <14177.22897.138261.369110@hip186.ch.intel.com> of Fri, 11 Jun 1999 11:46:09 MST References: <14177.13953.82252.18827@hip186.ch.intel.com> <75485.929125556@zippy.cdrom.com> <14177.22897.138261.369110@hip186.ch.intel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> If you have media in the drives at probe time, then sysinstall is happy. If > you don't have media at probe time (but DO have the media in the drive well > ahead of chosing the "media" option within sysinstall), Kenneth was saying > that the drivers still attach() but then sysinstall is confused. There is some weird breakage in the 3.1 sysinstall even when the media is in the drive at boot time. I was going to report it, but got sidetracked after I finally tricked sysinstall into completing. Then I started using the box for some of my own development and have now forgotten the details. Since my 3.2 CDs should arrive soon, I'm holding off doing anything unless the problem persists in 3.2. Here's what I can remember. Simple box, with three devices on one SCSI controller (disk, tape and CD). It and its four sister machines have all installed 2.2.6, 2.2.7 and 2.2.8 from the CDs several times with no problems of any kind. Went through the basic standard process I use with 3.1 (pretty much full install of everything with sources) and it refused to load any software when I told it to go ahead, because it could not find the CD -- but I didn't write down the message at the time as I planned to do a full re-run for documentation purposes and never did it. The irritating thing was that it had booted from the CD and got sysinstall and anything else it was using up to that point from the CD. I went back and forwards through several menus in different ways, rebooted dozens of times, and eventually discovered a way that I could repeat by which I could get it to not produce this error and to perform the install. I'm sorry this is a useless report (which is why I've held off making it), but I simply did not have time to do the right thing at the time. However, if it happens with 3.2 when the CDs arrive, I will most definitely document it and make a proper report. -- Greg Black -- <gjb@acm.org> or <gjb@computer.org> Fight censorship in Australia: <http://www.efa.org.au>; 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?19990613082735.9292.qmail>