From owner-freebsd-bugs Mon Jul 5 2:40: 6 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F1C1514E55 for ; Mon, 5 Jul 1999 02:40:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA94989; Mon, 5 Jul 1999 02:40:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 5 Jul 1999 02:40:04 -0700 (PDT) Message-Id: <199907050940.CAA94989@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Kenneth D. Merry" Subject: Re: kern/12495: 3.1 install fails to detect Toshiba CDROM on AHA1740 adapter Reply-To: "Kenneth D. Merry" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/12495; it has been noted by GNATS. From: "Kenneth D. Merry" To: wilko@FreeBSD.ORG (Wilko Bulte) Cc: freebsd-bugs@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/12495: 3.1 install fails to detect Toshiba CDROM on AHA1740 adapter Date: Mon, 5 Jul 1999 03:33:58 -0600 (MDT) [ If you don't CC messages to me, it'll take a lot longer to get a reply. ] Wilko Bulte wrote... > The following reply was made to PR kern/12495; it has been noted by GNATS. > > From: Wilko Bulte > To: freebsd-gnats-submit@freebsd.org, wilko@freebsd.org > Cc: > Subject: Re: kern/12495: 3.1 install fails to detect Toshiba CDROM on AHA1740 > adapter > Date: Sun, 04 Jul 1999 12:08:50 +0200 > > Hi Ken, > > Thanks for your reply. > > On your question: yes, there was a 3.1 release CD in the drive during > the boot. Okay, that rules out that problem. > And you are right, the Toshiba drive is not exactly an ancient device. > Not new either, it is a 4x > cdrom. > > What puzzles me is the fact that 2.2.x has always worked just fine, > I have multiple of the > same Toshiba model in both my Intel and Alpha machines. It's not as puzzling as you might think. We don't wait for the CDROM drive to finish probing before we start booting. So if sysinstall probes right away, it might not see the cdrom drive. The old SCSI layer probed things sequentially, so you would finish probing everything, no matter how long it took, before any booting took place. > I'll probably give 3.2-release a try next Saturday. Good idea, it's possible that'll fix the problem, although I'm not so sure it will. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message