From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 00:07:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C49516A41F; Fri, 4 Nov 2005 00:07:21 +0000 (GMT) (envelope-from mauritz.sundell@telia.com) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0219843D46; Fri, 4 Nov 2005 00:07:20 +0000 (GMT) (envelope-from mauritz.sundell@telia.com) Received: from pne-ps2-sn1 (81.228.11.132) by pne-smtpout1-sn2.hy.skanova.net (7.2.060.1) id 436A3A5300016CC3; Fri, 4 Nov 2005 01:07:18 +0100 Message-ID: <14401715.1131062838696.JavaMail.tomcat@pne-ps2-sn1> Date: Fri, 4 Nov 2005 01:07:18 +0100 (MET) From: Mauritz Sundell To: bzeeb-lists@lists.zabbadoz.net Mime-Version: 1.0 Content-Type: text/plain;charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: CP Presentation Server X-clientstamp: [217.211.26.85] X-Mailman-Approved-At: Fri, 04 Nov 2005 13:08:16 +0000 Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Re: CURRENT Safemode does not boot but ACPI-mode does [SOLVED] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mauritz Sundell List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 00:07:21 -0000 On Thu, 3 Nov 2005, Bjoern A. Zeeb wrote: >On Thu, 3 Nov 2005, Mauritz Sundell wrote: > >> 27 october I cvsuped and build kernel and world >> since then I cant boot without ACPI >> when I boot without there looks to be problems with resource- >> allocations >> drivers cannot attach, cannot map interrupt, and finally Mount root >> fail >> due to no harddisk found. >> >> My previous kernel was from the 26th october. >> >> Im running CURRENT on an HP Pavilion zv5000 (laptop) with amd64. >> >> Do someone have any tips where I should look? > >There had been more changes in that timeframe. > >Try re-adding > device atpic >to your kernel config file if it's missing. Thanks Bjoern adding atpic solved the problem Mauritz Sundell