Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Jun 2007 16:43:56 -0700
From:      Garrett Cooper <youshi10@u.washington.edu>
To:        Greg Rivers <gcr+freebsd-current@tharned.org>
Cc:        freebsd-current@freebsd.org, Chris Lee <clee@kde.org>
Subject:   Re: AMD64 panic on boot
Message-ID:  <466C8CBC.7030903@u.washington.edu>
In-Reply-To: <20070610122840.T71148@nc8000.tharned.org>
References:  <db69205d0706100924h595a9d1dwac3cf42c3935546b@mail.gmail.com> <20070610122840.T71148@nc8000.tharned.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Greg Rivers wrote:
> On Sun, 10 Jun 2007, Chris Lee wrote:
>
>> I built a custom kernel and it says that it can't map interrupts for
>> certain devices (like my ATA controller), which prevents it from being
>> able to find my disks and mount my root fs.
>>
>> I *think* my kernel configuration is fairly standard. It's available
>> at http://c133.org/freebsd-7.conf if anybody would mind taking a look
>> and offering some pointers. I cvsup'd yesterday around midnight, and
>> my hardware is a pretty standard nforce4 mobo with a dual-core Opteron
>> for the main CPU.
>>
>
> Your config lacks a "machine" directive.  I think you want "machine 
> amd64"
> above "cpu HAMMER".
>
Not necessary. Look at the GENERIC config under the amd64/conf dir.
-Garrett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?466C8CBC.7030903>