From owner-freebsd-questions Tue Aug 29 20:05:46 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id UAA05286 for questions-outgoing; Tue, 29 Aug 1995 20:05:46 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id UAA05276 for ; Tue, 29 Aug 1995 20:05:35 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id MAA27565; Wed, 30 Aug 1995 12:37:32 +0930 From: Michael Smith Message-Id: <199508300307.MAA27565@genesis.atrad.adelaide.edu.au> Subject: Re: pilot error on my part or feedback on the 2.1 snap To: kaleb@x.org (Kaleb S. KEITHLEY) Date: Wed, 30 Aug 1995 12:37:31 +0930 (CST) Cc: questions@freebsd.org In-Reply-To: <199508300138.VAA04525@exalt.x.org> from "Kaleb S. KEITHLEY" at Aug 29, 95 09:38:40 pm Content-Type: text Content-Length: 2126 Sender: questions-owner@freebsd.org Precedence: bulk Kaleb S. KEITHLEY stands accused of saying: > On the advice of Richard Wackerbarth I decided to install the 2.1 snap > instead of the 2.0.5 RELEASE. This after years of running FreeBSD 1.x > and 386BSD before that. While I applaud the new improved installation > there needs to be a way to see what went wrong with something, a terse > "It didn't work" isn't very satisfying. Howzabout a "Press F3 to see > the log" or something similar? It could stand an "expert only" escape > to a command shell too. How about reading the docco, setting the 'extra debugging' flag in the options menu, and hitting alt-F2 to watch the output? > But even more confounding is, when it finally seems willing to write > the label, to have the kernel panic with the message "biodone: buffer > not busy", sync the disk and reboot. So far this has happened several > times and I have been otherwise unsuccessful in installing. I'd suggest that pilot error is manifesting here. Go down the menu, one entry at a time. Start with the slice editor, then the labeller, and so on. > and an old Logitech busmouse controller. The boot probe says that wdc0 > is an AC31200F. The disk itself is, as I recall, a Seagate Barracuda, > 1222 meg drive, actual geometry reported during the boot probe is 2484 > Cyl, 16 H, 63 Sec, CMOS geometry is 621 Cyl, 64 H, 64 Sec. This machine > has been running OS/2 3.0 quite happily for many moons with no problems. > > Thoughts? Well, the Barracuda is a SCSI disk, so you're not running one of them. What you have is a Western Digital AC31200F. Prodiving you're within the 1024-cylinder mark, you should be fine. This is an installation question, and not even vaguely suitable for the -hackers list. > Kaleb KEITHLEY -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[