From owner-freebsd-questions Mon Feb 16 23:03:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17158 for freebsd-questions-outgoing; Mon, 16 Feb 1998 23:03:16 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17151 for ; Mon, 16 Feb 1998 23:03:13 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id WAA11297; Mon, 16 Feb 1998 22:34:06 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 16 Feb 1998 22:34:06 -0800 (PST) From: Doug White Reply-To: Doug White To: Zoltan Sebestyen cc: FreeBSD questions mailinglist Subject: Re: FBSD2.2.2-REL. does not boot! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Feb 1998, Zoltan Sebestyen wrote: > Last Friday, a friend of mine got sick of using an NT4.0 as a fileserver > for a bunch of Macs and wanted me to install a FreeBSD and setup a > netatalk. The only problem was that FBSD did not boot neither from the > cdrom nor from the boot floppy. It panicked after changing the root device > to fd0c.(It tried to do that even if booting from cdrom, but I think that > can't be a problem, because FBSD did the same on other machinesd without > any problem.) The machine has some old PCI (perhaps ASUS) mainboard, a PCI > NE2000 compatible card(it was recognized well) two 2.5 GIG and two 6 GIG > HDs; a 2.5 was replaced with the cdrom for the install. What was the panic output? How much memory does this machine have? Details, details, details.... Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message