From owner-freebsd-bugs Mon Jul 31 07:08:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id HAA22777 for bugs-outgoing; Mon, 31 Jul 1995 07:08:31 -0700 Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.129.34]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id HAA22768 for ; Mon, 31 Jul 1995 07:07:53 -0700 Received: (from robin@localhost) by rucus.ru.ac.za (8.6.11/8.6.9) id QAA15399; Mon, 31 Jul 1995 16:00:52 +0200 From: Robin Lunn Message-Id: <199507311400.QAA15399@rucus.ru.ac.za> Subject: Re: Suggestion. To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 31 Jul 1995 16:00:52 +0200 (SAT) Cc: roberto@blaise.ibp.fr, freebsd-bugs@FreeBSD.org In-Reply-To: <199507310522.HAA02131@uriah.heep.sax.de> from "J Wunsch" at Jul 31, 95 07:22:18 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2267 Sender: bugs-owner@FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Ollivier Robert wrote: > > > > > I think most of you will only be using SCSI devices and so not have come > > > accross this problem much. Suggestion: in the install program if the > > > installer tries to boot from the SCSI while IDE controller was detected, > > > warn them that this is impossible on the IBM PC platform. > > > > It is not that impossible with our boot blocks. You can ask to boot from > > hd() instead of sd()/wd(). It will then boot from the SCSI drive. The boot > > blocks are to be on the IDE drive of course. Broken PC arch. again... > > I don't think it's a question of the boot blocks. It's a matter of > the BIOS chosing the IDE(s) as drives 0x80 and 0x81, and trying to > boot only off drives 0 and 0x80. > > However, you could disable the IDE(s) in the BIOS and should get the > SCSI adapter hook its drives with SCSI ID(s) 0 and 1 in place for the > BIOS drives 0x80 and 0x81. You won't be able to use the IDE(s) from > DOS then, but it should be possible to use them from FreeBSD. We did try that. I dont know if its just that our AMI BIOS was being a sod, but we did undefine "Hard Disk 1". The SCSI said not to define anything for it and so "Hard Disk 2" was not defined either. The SCSI did then show up as "C:" instead of "D:" but the boot prompt did not show and the machine just hung. We scrounged through the Adaptec host config program that one can get before boot and the only likely option was to enable booting under certain circumstances (it was about 2 screens from the initial screen, the context escapes me and I dont feel like rebooting to check it ;) but sadly that didnt help either. Perhaps you could make another boot block that would boot off the scsi while the boot block sits on the IDE should the installer have SCSI and IDE and wish to boot from the SCSI. (If this is possible with the current boot blocks ignore me. I tend not to fiddle with boot blocks regularly) -- _ __ ' ) ) / /--' ____/___o __ / \_(_) /_) (__/) )_ (BeamJack@IRC) "The soundest fact may fail or prevail in the style of its telling" (Ursula LeGuin) Standard Disclaimer: Only my ideas are expressed here unless it is expressly noted that they are other peoples ideas.