From owner-freebsd-stable Sat Dec 18 0:56:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id EF33E14A19 for ; Sat, 18 Dec 1999 00:56:31 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id DAA88723; Sat, 18 Dec 1999 03:56:30 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id DAA02633; Sat, 18 Dec 1999 03:56:30 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912180856.DAA02633@rtfm.newton> Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: from Tom at "Dec 17, 1999 10:35:01 pm" To: Tom Date: Sat, 18 Dec 1999 03:56:30 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" => => A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) => => => would not boot from 3.3 CD if the SCSI disks are online. It => => => would say: "Read Error" on the upper left of the screen -- => => => where you'd normally see the spinning dash. I suspect, this is => => => a loader's bug :(, which may make it to 3.4 ... => => = => => = Don't see a problem with that here. I just booted the 3.3-R CD => => =on an ATAPI CD ROM with no other IDE devices, and everything was => => =fine. [...] => Lucky you... Are the SCSI disks otherwise bootable? Is the CD on the => primary or the secondary IDE channel? = = The SCSI disk is bootable in that set in the BIOS to boot (I used "A: =CD C:" boot order), but I don't think it has an OS on it. = = You could just have a boot order issue. Maybe the SCSI disk has a =screwed up boot sector, and SCSI disk is earlier in the boot order ("A: =C: CD"), so it never gets to the CD. Nope. If I take the CD out of the drive, the machine will nicely boot from the SCSI disk... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message