From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263662AbTHWVy3 (ORCPT ); Sat, 23 Aug 2003 17:54:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263733AbTHWVy3 (ORCPT ); Sat, 23 Aug 2003 17:54:29 -0400 Received: from mx1.redhat.com ([66.187.233.31]:62982 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S263662AbTHWVx1 (ORCPT ); Sat, 23 Aug 2003 17:53:27 -0400 Date: Sat, 23 Aug 2003 14:55:45 -0700 From: Andrew Morton To: Tomasz Torcz Cc: linux-kernel@vger.redhat.com Subject: Re: 2.6.0-test4 - lost ACPI Message-Id: <20030823145545.2b7d6ec9.akpm@osdl.org> In-Reply-To: <20030823105243.GA1245@irc.pl> References: <20030823105243.GA1245@irc.pl> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Tomasz Torcz wrote: > > I am using ACPI for few years now. As far as I can see, on my > machine it is only usfeul for binding events to Power button (like > running fbdump) and for powering off. I'm also experimenting > with swsusp, which I run by /proc/acpi/sleep. > > 2.6.0-test4 has a surprise for me: me too. > ACPI disabled because your bios is from 00 and too old > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ One of my trusty-but-old testboxes does exactly the same thing. It's just the ACPI guys running away from broken BIOSes I think ;) Add "acpi=force" to your kernel boot command line and everything should work as before.