From owner-freebsd-questions Sun Jan 9 11:24: 1 2000 Delivered-To: freebsd-questions@freebsd.org Received: from camelot.bitart.com (camelot.BITart.com [206.103.221.33]) by hub.freebsd.org (Postfix) with SMTP id 364A714E4B for ; Sun, 9 Jan 2000 11:23:59 -0800 (PST) (envelope-from gerti@bitart.com) Received: (qmail 2787 invoked by uid 101); 9 Jan 2000 19:24:00 -0000 Message-ID: <20000109192400.2786.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <3878DCC8.7C40FB57@azstarnet.com> X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Sun, 9 Jan 2000 13:24:00 -0600 To: Scott Corey Subject: Re: Dmesg giving erroneous messages (Long Message) Cc: FreeBSD Questions Reply-To: gerti@BITart.com References: <3878DCC8.7C40FB57@azstarnet.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Corey wrote: > I am having a heck of a time trying to figure out where I am getting > these kernel "No such device" config calls from. Here is my dmesg: > > [...] > When you first installed FreeBSD and configured the generic kernel, the configuration was stored in /boot/kernel.conf'. This file is applied on each reboot. My guess is you have since build a lean customized kernel, which does not contain devices anymore you don't have. So you can now use a mostly empty kernel.conf. I don't know what the proper procedure is, but this worked for me: cd /boot mv kernel.conf kernel.conf.orig echo "q" >kernel.conf Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message