From owner-freebsd-questions Sat Jun 19 18:46:11 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (Postfix) with SMTP id CD4DB14BE5 for ; Sat, 19 Jun 1999 18:46:09 -0700 (PDT) (envelope-from mike@hyperreal.org) Received: (qmail 24247 invoked by uid 12); 20 Jun 1999 01:45:58 -0000 Message-ID: <19990620014558.24244.qmail@hyperreal.org> From: mike@hyperreal.org Subject: Re: kernel errors in dmesg In-Reply-To: <199906191022.GAA90423@lakes.dignus.com> from Thomas David Rivers at "Jun 19, 1999 06:22:58 am" To: rivers@dignus.com (Thomas David Rivers) Date: Sat, 19 Jun 1999 18:45:58 -0700 (PDT) Cc: freebsd-questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL51 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > I believe the problem would be that you've got an old boot > configuration file. Did you previously disable those > devices at boot time? That's it.. someone else pointed it out, as well. /boot/kernel.conf is not mentioned at all in the FreeBSD Handbook's kernel config section. Apparently /boot/kernel.conf is parsed if a userconfig_script_load variable in /boot/loader.conf is "YES". I had originally installed FreeBSD 3.2-RELEASE, which uses the GENERIC kernel, of course, and I chose through the installer to disable a bunch fo devices, then promptly forgot all about having done this. Several kernel compiles later, I'd trimmed those drivers out of the kernel but the /boot/kernel.conf file was still saying to disable them, assuming they were loaded. Hence "syntax error" (not the best choice of error messages, IMHO). Thanks!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message