From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 25 02:25:42 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34A201065670 for ; Fri, 25 Apr 2008 02:25:42 +0000 (UTC) (envelope-from nate@root.org) Received: from nlpi101.prodigy.net (nlpi101.prodigy.net [207.115.36.117]) by mx1.freebsd.org (Postfix) with ESMTP id DF2748FC13 for ; Fri, 25 Apr 2008 02:25:41 +0000 (UTC) (envelope-from nate@root.org) X-ORBL: [71.139.17.63] Received: from [10.0.5.18] (ppp-71-139-17-63.dsl.snfc21.pacbell.net [71.139.17.63]) by nlpi101.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id m3P2Pd0H007403; Thu, 24 Apr 2008 21:25:40 -0500 Message-ID: <48114123.3000708@root.org> Date: Thu, 24 Apr 2008 19:25:39 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Zbigniew Baniewski References: <20080420134236.GA6019@sarge.my.own.domain.no-net> <480C0DEF.2030707@root.org> <20080421095156.GA5263@sarge.my.own.domain.no-net> <58AFE814-343F-4F83-94DA-A2979180C512@FreeBSD.org> <20080424171712.GA5180@sarge.my.own.domain.no-net> <20080424234921.GR92261@server.vk2pj.dyndns.org> In-Reply-To: <20080424234921.GR92261@server.vk2pj.dyndns.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Problem with ACPI using Abit BE6-II V2.0 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2008 02:25:42 -0000 Peter Jeremy wrote: > On Sun, Apr 20, 2008 at 03:42:36PM +0200, Zbigniew Baniewski wrote: >> I suppose, if it can work on Linux, it can (and should) work on FreeBSD too. >> Why not, actually? On the same motherboard I tried NetBSD in versions 2.0 >> and 3.0 - there weren't ACPI-related problems. > > Different OSs will have different work-arounds for ACPI bugs and/or > will rely on different ACPI features. It seems most likely that > FreeBSD is relying on ACPI features that are not working in your ACPI. Since the problems are specific to this system, which was manufactured in 1999, you're going to find it hard to get others to fix things for you. So the best bet is to try to track down what Linux is doing differently. This is a great opportunity for you to join in! Thanks, -- Nate