From owner-freebsd-questions Tue Apr 6 12: 8:42 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 6BA5414E21 for ; Tue, 6 Apr 1999 12:08:34 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA04351; Tue, 6 Apr 1999 12:06:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 6 Apr 1999 12:06:34 -0700 (PDT) From: Doug White To: Gregory Carvalho Cc: questions@freebsd.org Subject: Re: FreeBSD 3.1 boot anomaly In-Reply-To: <199904051748.KAA24611@proxy4.ba.best.com> 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, 5 Apr 1999, Gregory Carvalho wrote: > I have installed FreeBSD 3.1 (fresh system) off the CD-ROMs (including all > sources and all encryption technology included). When the system is shutdown > gracefully, it will not boot back up. I have a true NE2000 (IRQ 10, I/O 300) > which FreeBSD balks at when probing other devices with that I/O address. > FreeBSD just stops booting. You can get to the boot-time configuration without using the CD. When the system is booting, hit a key to get the prompt, then type 'boot -c'. From there you can disable the devices. Unfortunately these changes aren't saved between boots. > I have discovered a method to boot by first booting off the live filesystem > CD and altering the configuration with the visual configuration option just > after the bootable CD boots (which was done when FreeBSD was originally > installed off Disk 1). The sysinstall program interface appears, then I > select "Exit Install", the systems reboots and properly detects devices and > provides a login prompt. I will not reconfigure the GENERIC file and make > the system, as I am nearby and can drop off the computer for your inspection > (in case this is some kind of bug). It appears that one of the device probes is destructive enough to crash the system in your configuration. I would suggest the following solutions: 1) Rebuild your kernel, commenting out the devices you don't have. 2) Create the file '/kernel.config' and list commands to process in the boot-time configuration's command line. For example: irq ed0 10 port ed0 0x200 disable le0 disable cs0 [ and so on ] Then create '/boot/boot.conf' and put this in it: load /kernel load -t userconfig_script /kernel.config autoboot 5 I heartily suggest Solution 1; you can tune other system parameters while you're at it. The kernel building process is fully documented in the FreeBSD Handbook (http://www.freebsd.org/handbook). Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message