From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 8 04:33:41 2008 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E13716A41A for ; Tue, 8 Jan 2008 04:33:41 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 44D2313C43E for ; Tue, 8 Jan 2008 04:33:34 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id PAA00508; Tue, 8 Jan 2008 15:33:26 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 8 Jan 2008 15:33:25 +1100 (EST) From: Ian Smith To: Xn Nooby In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-mobile@freebsd.org Subject: Re: Two minute pause at acpi.ko message on old HP laptop with 7.0-RC1 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2008 04:33:41 -0000 On Mon, 7 Jan 2008, Xn Nooby wrote: > I have an old zv5445us HP Pavillion laptop, essentially the zv5000 > model, which pauses at the /boot/kernel/acpi.ko message during boot. > It hangs there, with a non-spinning ASCII character, for about 2 > minutes - then it boots. I tried entering the following commands in > to the loader.conf to no avail: > > set hint.atkbd.0.disabled="1" > set hint.acpi.0.disabled="1" > > I'm currently using FreeBSD 7.0-RC1, but it has the same behavior with > FreeBSD 6.3-RC2. > > The machine seems to work okay after that, though I am having other > problems with the screen going blank when I try to configure X. For > now, I was just trying to eliminate the 2 minute pause on acpi.ko. > > Any suggestions? Could you post the actual last couple of lines you see while it's pausing? And the next line or so seen after the pause? If you select to boot verbosely then the section either side of and including this pause in your /var/run/dmesg.boot could be helpful. Just that it's not clear whether the 'acpi.ko message' you're seeing is printed before, during or after loading acpi, ie perhaps that's finished and the pause is before the next thing you see, in which case it could be hanging on something network related, or something else altogether .. cheers, Ian