Date: Wed, 21 Dec 2011 07:43:30 -0500 From: John Baldwin <jhb@FreeBSD.org> To: tomdean@speakeasy.org Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/163442: boot/loader.conf not processed at boot time Message-ID: <4EF1D472.5000708@FreeBSD.org> In-Reply-To: <1324404366.2107.23.camel@asus> References: <201112190730.pBJ7UESQ097170@freefall.freebsd.org> <1324319166.3799.144.camel@asus> <201112200801.00926.jhb@freebsd.org> <1324404056.2107.21.camel@asus> <1324404366.2107.23.camel@asus>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/20/11 1:06 PM, Thomas D. Dean wrote: > On Tue, 2011-12-20 at 10:00 -0800, Thomas D. Dean wrote: > >> insmod part_gpt >> insmod ufs_2 >> set root='(hd1.gpt4)' >> kfreebsd /boot/kernel/kernel >> kfreebsd_loadenv /boot/device.hints >> set kFreeBSD.vfs.root.mountfrom=ufs:/dev/ada1p4 >> set kFreeBSD.vfs.root.mountfrom.options=rw > > Changing to the loader fixed things. > > kfreebsd /boot/loader > > Thanks for the help, discussing this lead me to looking for the beastie > and the fix. Uh, so using grub to load the loader was the fix? That isn't a real fix. Can you disable the beastie (beastie_disable="YES") and the automatic boot (autoboot_delay="NO") in loader.conf and then either use a serial console or a camera to capture the messages on the screen when it loads the modules. Then do a boot -v from the prompt and save the output of 'dmesg' to a file after it boots. Put that file up somewhere where I can look at it to see if there were errors parsing the modules loaded from the loader. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF1D472.5000708>