From owner-freebsd-mobile@FreeBSD.ORG Tue May 27 08:29:39 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FE5737B401 for ; Tue, 27 May 2003 08:29:39 -0700 (PDT) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E9E43F85 for ; Tue, 27 May 2003 08:29:38 -0700 (PDT) (envelope-from rsidd@online.fr) Received: from user-0ccejuk.cable.mindspring.com ([24.199.79.212] helo=greenrondo.a.la.turk) by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19KgOP-00068h-00 for mobile@freebsd.org; Tue, 27 May 2003 08:29:37 -0700 Received: (qmail 32413 invoked by uid 1002); 27 May 2003 15:24:41 -0000 Date: Tue, 27 May 2003 11:24:40 -0400 From: Rahul Siddharthan To: mobile@freebsd.org Message-ID: <20030527152440.GA32335@online.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: Linux 2.4.20 i686 User-Agent: Mutt/1.5.4i Subject: psm0 and acpi X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 15:29:39 -0000 As I reported on -current a few days back, my laptop doesn't recognize psm0 (it fails to show up in dmesg) if acpi is enabled. If acpi is disabled, psm0 shows up, but the boot process doesn't complete -- it hangs while mounting the disks. This is with 5.1-BETA2. I don't think this is because of broken ACPI implementation because Linux works fine on that machine, with or without acpi -- acpi isn't totally functional, standby/suspend don't work but battery, AC status, lid etc work fine. I understand the linux people use the same ACPI code as FreeBSD, from Intel. I'll send dmesg etc if it's helpful, but it looks like many people have had this problem with FreeBSD since at least 2001 and there's also a PR or two (eg, i386/49116), I tried some of the suggestions I heard (fiddling with /boot/device.hints in various ways), but it's no use so far. Any ideas? Otherwise I'm forced to stick with linux, which I guess isn't so bad, but I've grown used to freebsd over the last 3-4 years. (The laptop has no APM bios, and at least I get *some* ACPI support with linux, so I think won't bother with FreeBSD 4.) Thanks Rahul