From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 22:01:41 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E3BA106566C for ; Wed, 21 Dec 2011 22:01:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 41D178FC1F for ; Wed, 21 Dec 2011 22:01:41 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id EDA3D46B0D; Wed, 21 Dec 2011 17:01:40 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 83C6DB941; Wed, 21 Dec 2011 17:01:40 -0500 (EST) From: John Baldwin To: freebsd-amd64@freebsd.org, tomdean@speakeasy.org Date: Wed, 21 Dec 2011 17:01:39 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <201112190730.pBJ7UESQ097170@freefall.freebsd.org> <4EF1D472.5000708@FreeBSD.org> <1324490127.6799.12.camel@asus> In-Reply-To: <1324490127.6799.12.camel@asus> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201112211701.39995.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 21 Dec 2011 17:01:40 -0500 (EST) Cc: Subject: Re: amd64/163442: boot/loader.conf not processed at boot time X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 22:01:41 -0000 On Wednesday, December 21, 2011 12:55:27 pm Thomas D. Dean wrote: > On Wed, 2011-12-21 at 07:43 -0500, John Baldwin wrote: > > On 12/20/11 1:06 PM, Thomas D. Dean wrote: > > > 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. > > > > Sorry, I was not clear. > > I installed grub in my original configuration of the new machine, built > from components, no OS. I created gpt partitions on two disks with > linux. > > I installed windows 7 on the first disk, then, linux with grub on the > second disk, fixing grub to boot windows. Then, I installed FreeBSD on > the second disk. Again, I edited grub (in linux) to boot all three. > > At this point, I had grub configured to directly load the FreeBSD > kernel, not using the loader. So, any loader configurations were not > effective because the loader was never executed. The beastie never > appeared. Until the discussion on this list, I never noticed the > absence. This was a mistake on my part. I wanted to use the FreeBSD > loader and get the benefits of configuring modules, etc., at boot time. > > Going back to linux and configuring grub properly to use the FreeBSD > loader fixed the problem. > > I can try to gather information, but, I will have to go back to the > improper (broken?) grub configuration to do it. Oh, nevermind, I understand now. No need for further information. -- John Baldwin