From owner-freebsd-current@FreeBSD.ORG Thu Jul 2 20:36:17 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDFF91065678; Thu, 2 Jul 2009 20:36:17 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id ADD878FC0C; Thu, 2 Jul 2009 20:36:17 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from feathers.peganest.com (feathers.peganest.com [78.33.110.3]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n62Ka8AH021977 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 2 Jul 2009 20:36:11 GMT (envelope-from ken@mthelicon.com) From: Pegasus Mc Cleaft Organization: Feathers To: freebsd-current@freebsd.org Date: Thu, 2 Jul 2009 21:36:03 +0100 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; amd64; ; ) References: <895D2AA2E9964CEE970A64C74D2FF622@PegaPegII> <95B6A153-B61A-474B-B3D6-66D80DA53D50@exscape.org> <4A4CC937.5050008@fletchermoorland.co.uk> In-Reply-To: <4A4CC937.5050008@fletchermoorland.co.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907022136.04164.ken@mthelicon.com> Cc: Thomas Backman , current@freebsd.org, Paul Wootton Subject: Re: Has anyone been able to actually boot the AMD64 kernel after r194958? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2009 20:36:18 -0000 On Thursday 02 July 2009 15:50:31 Paul Wootton wrote: > > With you saying this, I decided to try GENERIC kernel configuration and > that builds and runs just fine. I suspect that Peg and myself have > something in our kernel conf files that is causing an issue. I'll have a > go later on and see if I can narrow it down a little bit more > > Paul > Hi Paul, I think I may have tracked down the trigger, although I dont know how to pin- point the cause. It looks like compiling in the radeondrm driver into the kernel is the culprit. if I omit that line from my kernel config, the latest kernels will compile and boot properly on my machine. I'm using a R7xx (but it load the R6xx code) radeon HD card. From talking to you, I know you are using a proper R6xx card. Strangely I can kldload the driver after the machine has booted and all is well, it just seems to hate being compiled into the kernel. Can you see if this is the same on your machine? Peg