Date: Thu, 16 Feb 2006 18:15:50 -0600 From: Andrew <andrew.chace@gmail.com> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: freebsd-questions@freebsd.org Subject: Re: newly built kernel fails to boot Message-ID: <1140135350.602.21.camel@netvista.network> In-Reply-To: <20060216204535.3c4e7d9c@localhost> References: <1140117830.602.19.camel@netvista.network> <20060216204535.3c4e7d9c@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2006-02-16 at 20:45 +0100, Fabian Keil wrote: > Andrew <andrew.chace@gmail.com> wrote: > > > I've just had a go at configuring and rebuilding a kernel for my > > desktop machine. I read the section in handbook, and skimmed over > > NOTES and the GENERIC config. I then copied GENERIC to NETVISTA and > > commented out drivers/devices that I didn't think were relevant to my > > hardware. config(8) is happy with my file, and 'make buildkernel' and > > 'make installkernel' proceed without any errors. So, I ran > > nextboot(8) and rebooted, but the new kernel hangs right after the > > first line printed to the console; the first portion of which is > > 'acpi.ko'. > > > # NETVISTA Kernel Config > > # ACPI Video Extensions (LCD backlight/brightness, video output, etc.) > > > device acpi_video > > Just guessing, but man acpi says: > > |BUGS > | If the acpi driver is loaded as a module when it is already linked as > | part of the kernel, odd things may happen. > > Maybe having acpi_video in the kernel and then loading acpi as > module triggers "odd things" as well. > > Fabian Thank you; I'll remove that device and see what happens... -Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1140135350.602.21.camel>