From owner-freebsd-questions Sun May 23 18: 2:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mta1-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.1]) by hub.freebsd.org (Postfix) with ESMTP id 21B4E14DA3 for ; Sun, 23 May 1999 18:02:10 -0700 (PDT) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.152.128]) by mta1-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990524010434.KFRM7869945.mta1-rme@wocker>; Mon, 24 May 1999 13:04:34 +1200 From: "Dan Langille" Organization: The FreeBSD Diary To: "Michael A. Smith" Date: Mon, 24 May 1999 13:02:09 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: install problem follow-up Reply-To: junkmale@xtra.co.nz Cc: freebsd-questions@FreeBSD.ORG In-reply-to: <4.1.19990523203944.00a077b0@pop3.vais.net> X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990524010434.KFRM7869945.mta1-rme@wocker> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 May 99, at 20:43, Michael A. Smith wrote: > [RECAP: 3.1-STABLE install on 486 hangs at boot on "ep0 not found at > 0x300"] > > The 3.1 Errata tells me: > > o Kernel change information is not saved in the new kernel, even > though this is claimed to work in the docs. > > Fix: The change information is being written out, in fact, but to the > wrong location. move /kernel.config to /boot/kernel.conf (if it > exists, otherwise there were no changes to save) and add the > following lines to /boot/loader.rc: > > load /kernel > load -t userconfig_script /boot/kernel.conf > autoboot 5 > > This will cause the kernel change information to be read in and > used properly (and you just learned a little about the new 3-stage > loader in the process, so the exercise wasn't a total loss). > > > This certainly may be what's wrong with my system, but if I can't boot it > up, how do I make these changes?? I've tried the fixit shell & CD-ROM live > filesystem, but am runing into difficulties. There are two ways that I would try. I know the first will work. I've never tried the second. 1 - boot from floppies so you can do the visual configuration again. That will get you running and you can do the above changes. 2 - boot into single user mode, issue a "mount /" and make the changes, then reboot again. -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message