From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:38:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27BAE16A400 for ; Thu, 6 Apr 2006 12:38:36 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A850F43D48 for ; Thu, 6 Apr 2006 12:38:35 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id h27so95467wxd for ; Thu, 06 Apr 2006 05:38:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hyxoZ0ebtMuVCGBHa3QijYwwS3IvdDXIfYwZ14Qx8Yu/zLb+c/o9EFU4N+m59P7VLEMaFczktPPCrs9NwH6XI14FqIc3/j+pkzrSdoyNK3RRrKuwyWXcnHO2so1hAgeR+5eprAANmpSTwDhoBSvy6EO4TLskX3wjD4ShIakq9ds= Received: by 10.70.116.12 with SMTP id o12mr1069714wxc; Thu, 06 Apr 2006 05:38:34 -0700 (PDT) Received: by 10.70.54.2 with HTTP; Thu, 6 Apr 2006 05:38:34 -0700 (PDT) Message-ID: <790a9fff0604060538m1dc0e253pd33988a78b650ac0@mail.gmail.com> Date: Thu, 6 Apr 2006 07:38:34 -0500 From: "Scot Hetzel" To: "David Gilbert" In-Reply-To: <17460.22467.330090.949775@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17460.22467.330090.949775@canoe.dclg.ca> Cc: freebsd-stable@freebsd.org Subject: Re: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 12:38:36 -0000 On 4/5/06, David Gilbert wrote: > At this point, I've been through 4 AMD64 motherboards. Commonly, > AE_BAD_CHARACTER stops ACPI (or apic?) from figuring out the system > --- this has happened on 3 out of four boards. On this latest board, > it can turn off APIC. If I do that, FreeBSD hangs after detecting the > disks. The only "wrong" thing on the screen is > > module_register_init: MOD_LOAD (amr_linux, 0xffffffff805ebcc0, 0) > error 6 > > I have tested boot CDs for amd64 from 6.0-RELEASE, 6.1-BETA1 and > 6.1-BETA4. None have successfully booted on these boards. > I had a strange problem booting amd64 on my HP Pavilion dv8xxx laptop with the 6.1 BETA4 CDs. If I didn't touch the keyboard, the boot process would crash when loading the kernel (my best guess). As the last thing I saw was the boot loader reading /boot/loader.conf (screen was unreadable after the crash). I tried to break into the boot loader, but instead of getting the boot loader prompt, the boot loader loaded the kernel and I was able to install FreeBSD/amd64. After it was installed, I haven't had any futher problems booting FreeBSD/a= md64. > Strangely enough, i386 boots fine, APIC and all. I'm not sue if this will work: 1. install FreeBSD/i386 2. Copy the FreeBSD/amd64 kernel to /boot/kernel_amd64 3. reboot the system 4. break into the boot loader, and tell it to 'boot /boot/kernel_amd64' lf this boots the amd64 kernel, then it looks like the boot loader on the FreeBSD/amd64 CD's are bad. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.