From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 23 10:46:47 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id A732616A4E0
for <freebsd-acpi@freebsd.org>; Sun, 23 Jul 2006 10:46:47 +0000 (UTC)
(envelope-from floran@minorisa.es)
Received: from minorisa.es (athedsl-62470.otenet.gr [87.203.221.84])
by mx1.FreeBSD.org (Postfix) with SMTP id DEA8843D46
for <freebsd-acpi@freebsd.org>; Sun, 23 Jul 2006 10:46:44 +0000 (GMT)
(envelope-from floran@minorisa.es)
Message-ID: <92428CD6.7C9008A@minorisa.es>
Date: Sun, 23 Jul 2006 02:25:23 -0800
From: "Anna Melide" <floran@minorisa.es>
User-Agent: Mozilla 3.04 (Macintosh; I; 68K)
X-Accept-Language: en-us
To: <freebsd-acpi@freebsd.org>
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Content-Type: text/plain; charset="unicode"
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: We are struggling for the future of our planet, please help us.
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Anna Melide <floran@minorisa.es>
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jul 2006 10:46:47 -0000
We are struggling for the future of our planet, please help us.
Only together we can stand for our nature!
[1]Send a message to the "Environmental Protection Agency and Food and
Drug Administration" to improve mercury testing so we can keep tuna
safe for our families and for dolphins.
Some of the tuna producers -- particularly in Ecuador and Mexico --
use practices that can hurt or kill dolphins and catch tuna with
increased mercury levels.
Since the late 1950s, approximately seven million dolphins have died
from this practice.
[2]Sign for it - help yourself and thousands of other lives.
One another way you can help us is to send this letter or the link to
our website: http://www.against-cruelty.com/register.htm- to all
people you know.
2006 [3]Help Dolphins
References
1. http://www.animal-petitions.com/
2. http://protectinnocent.org/register.htm
3. {http://www.against-cruelty.com/
From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 24 11:02:44 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id E732416A4DF
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 11:02:44 +0000 (UTC)
(envelope-from owner-bugmaster@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP id F080743DA8
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 11:02:37 +0000 (GMT)
(envelope-from owner-bugmaster@freebsd.org)
Received: from freefall.freebsd.org (peter@localhost [127.0.0.1])
by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k6OB2Slm013531
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 11:02:28 GMT
(envelope-from owner-bugmaster@freebsd.org)
Received: (from peter@localhost)
by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k6OB2RS1013527
for freebsd-acpi@freebsd.org; Mon, 24 Jul 2006 11:02:27 GMT
(envelope-from owner-bugmaster@freebsd.org)
Date: Mon, 24 Jul 2006 11:02:27 GMT
Message-Id: <200607241102.k6OB2RS1013527@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: peter set sender to
owner-bugmaster@freebsd.org using -f
From: FreeBSD bugmaster <bugmaster@freebsd.org>
To: freebsd-acpi@FreeBSD.org
Cc:
Subject: Current problem reports assigned to you
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2006 11:02:45 -0000
Current FreeBSD problem reports
Critical problems
Serious problems
S Submitted Tracker Resp. Description
-------------------------------------------------------------------------------
o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt
o [2003/08/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70
o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel
o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3
o [2004/03/09] i386/64002 acpi acpi problem
o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree
o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma
o [2005/03/21] i386/79080 acpi acpi thermal changes freezes HP nx6110
o [2005/03/21] i386/79081 acpi ACPI suspend/resume not working on HP nx6
o [2005/04/28] i386/80426 acpi [APIC] [panic] 5.4-RC3 still panic when b
o [2005/10/17] i386/87568 acpi [ACPI] [REGRESSION] 6.0-STABLE needs ACPI
11 problems total.
Non-critical problems
S Submitted Tracker Resp. Description
-------------------------------------------------------------------------------
o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3)
o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5
o [2004/11/11] i386/73822 acpi [request] add thermal support to ACPI
o [2004/11/11] kern/73823 acpi [feature request] acpi / power-on by time
f [2004/11/17] kern/74030 acpi Unplugging AC causes battery % to stay lo
f [2005/12/24] kern/90871 acpi ACPI problems with ASUS A8N-VM-CSM
o [2006/05/30] kern/98171 acpi [acpi] ACPI 1304 / 0501 errors on Acer 50
7 problems total.
From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 24 21:52:07 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id EC78116A55E
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 21:52:07 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id 8CF0843D78
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 21:51:57 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6OLoEdo089532
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 14:50:14 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6OLoEHO089531
for freebsd-acpi@freebsd.org; Mon, 24 Jul 2006 14:50:14 -0700 (PDT)
(envelope-from sgk)
Date: Mon, 24 Jul 2006 14:50:14 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: freebsd-acpi@freebsd.org
Message-ID: <20060724215014.GA89464@troutmask.apl.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2006 21:52:08 -0000
ACPI gurus,
My colleague has installed FreeBSD 6.1-table onto his
Alienware MJ-12 laptop. During the boot process, we
see
acpi0: [MPSAFE]
ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace, AE_NOT_FOUND
SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace, AE_NOT_FOUND
SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace, AE_NOT_FOUND
SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace, AE_NOT_FOUND
SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
The system boots and appears to function (although cardbus seems broken).
I've roamed Alienware's web site and used google to search for an BIOS
update without success.
Are these messages something to worry about? Anyone know how to fix
the problem.
I've put a verbose boot meesage at
http://troutmask.apl.washington.edu/~kargl/alienware.dmesg
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 24 22:23:35 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id DD74A16A4DD
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 22:23:35 +0000 (UTC)
(envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
[66.23.211.162])
by mx1.FreeBSD.org (Postfix) with ESMTP id 57A4D43D45
for <freebsd-acpi@freebsd.org>; Mon, 24 Jul 2006 22:23:35 +0000 (GMT)
(envelope-from jhb@freebsd.org)
Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1])
(authenticated bits=0)
by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6OMNY6Y029250;
Mon, 24 Jul 2006 18:23:34 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-acpi@freebsd.org
Date: Mon, 24 Jul 2006 18:23:24 -0400
User-Agent: KMail/1.9.1
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
In-Reply-To: <20060724215014.GA89464@troutmask.apl.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200607241823.24477.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
Mon, 24 Jul 2006 18:23:34 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.87.1/1616/Mon Jul 24 13:49:29 2006 on
server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2006 22:23:35 -0000
On Monday 24 July 2006 17:50, Steve Kargl wrote:
> ACPI gurus,
>
> My colleague has installed FreeBSD 6.1-table onto his
> Alienware MJ-12 laptop. During the boot process, we
> see
>
> acpi0: [MPSAFE]
> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace,
AE_NOT_FOUND
> SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
AE_NOT_FOUND
> SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
AE_NOT_FOUND
> SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
AE_NOT_FOUND
> SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
Well, that's probably why cardbus is broken. Can you get the output of
acpidump? Specifically I'd be interested in the parts that mention LNKH (as
well as where it actually lives in the device tree).
--
John Baldwin
From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 24 22:59:18 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 2B0F316A4DD;
Mon, 24 Jul 2006 22:59:18 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id D9C9043D49;
Mon, 24 Jul 2006 22:59:17 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6OMvYvm090031; Mon, 24 Jul 2006 15:57:34 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6OMvSt5090030; Mon, 24 Jul 2006 15:57:28 -0700 (PDT)
(envelope-from sgk)
Date: Mon, 24 Jul 2006 15:57:28 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20060724225728.GA89987@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200607241823.24477.jhb@freebsd.org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2006 22:59:18 -0000
On Mon, Jul 24, 2006 at 06:23:24PM -0400, John Baldwin wrote:
> On Monday 24 July 2006 17:50, Steve Kargl wrote:
> > ACPI gurus,
> >
> > My colleague has installed FreeBSD 6.1-table onto his
> > Alienware MJ-12 laptop. During the boot process, we
> > see
> >
> > acpi0: [MPSAFE]
(acpi errors purged)
> Well, that's probably why cardbus is broken. Can you get the output of
> acpidump? Specifically I'd be interested in the parts that mention LNKH (as
> well as where it actually lives in the device tree).
Thanks for the quick response. I'll get you the requested
info tomorrow morning (need to leave in 5 minutes to go
stand on a little league field in 95 degrees temperatures).
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 25 05:37:11 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id EC35A16A4DD;
Tue, 25 Jul 2006 05:37:11 +0000 (UTC) (envelope-from nate@root.org)
Received: from pimout5-ext.prodigy.net (pimout5-ext.prodigy.net
[207.115.63.73])
by mx1.FreeBSD.org (Postfix) with ESMTP id 8F2F843D45;
Tue, 25 Jul 2006 05:37:11 +0000 (GMT) (envelope-from nate@root.org)
X-ORBL: [71.139.3.149]
Received: from [10.0.5.51] (ppp-71-139-3-149.dsl.snfc21.pacbell.net
[71.139.3.149])
by pimout5-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id
k6P5b9Fw045472; Tue, 25 Jul 2006 01:37:09 -0400
Message-ID: <44C5ADFF.2090705@root.org>
Date: Mon, 24 Jul 2006 22:37:03 -0700
From: Nate Lawson <nate@root.org>
User-Agent: Thunderbird 1.5.0.2 (X11/20060501)
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
In-Reply-To: <200607241823.24477.jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-acpi@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2006 05:37:12 -0000
John Baldwin wrote:
> On Monday 24 July 2006 17:50, Steve Kargl wrote:
>> ACPI gurus,
>>
>> My colleague has installed FreeBSD 6.1-table onto his
>> Alienware MJ-12 laptop. During the boot process, we
>> see
>>
>> acpi0: [MPSAFE]
>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace,
> AE_NOT_FOUND
>> SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
>> SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
>> SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
>> SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
>
> Well, that's probably why cardbus is broken. Can you get the output of
> acpidump? Specifically I'd be interested in the parts that mention LNKH (as
> well as where it actually lives in the device tree).
>
Just for the record, the usage is:
acpidump -d -t | gzip -c > alien.asl.gz
--
Nate
From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 25 14:02:17 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 4D49216A4DD
for <freebsd-acpi@freebsd.org>; Tue, 25 Jul 2006 14:02:17 +0000 (UTC)
(envelope-from eischen@vigrid.com)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
by mx1.FreeBSD.org (Postfix) with ESMTP id F2E5143D45
for <freebsd-acpi@freebsd.org>; Tue, 25 Jul 2006 14:02:16 +0000 (GMT)
(envelope-from eischen@vigrid.com)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6PE2Fkv022675
for <freebsd-acpi@freebsd.org>; Tue, 25 Jul 2006 10:02:15 -0400 (EDT)
Date: Tue, 25 Jul 2006 10:02:15 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-X-Sender: eischen@sea.ntplx.net
To: freebsd-acpi@freebsd.org
Message-ID: <Pine.GSO.4.64.0607250953000.19799@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
Subject: Fn keys on Dell E1405
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: deischen@freebsd.org
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2006 14:02:17 -0000
Greetings and salutations,
Is there anything I can do to get Fn key functionality on
my Dell E1405 notebook? I've seen the patches for video
switching and will try them at some point, but it's not
as important to me as getting suspend/resume and wireless
radio on/off. Also getting the CD/DVD drive to eject would
be nice.
I'm using the latest and greatest BIOS on this system, and
the output of 'acpidump -dt' is at:
http://people.freebsd.org/~deischen/e1405.acpi.dump
FYI, I can get the system to suspend by hitting the power
button or by Fn+Esc (standby), but it will not wakeup
no matter what I do. Also, the wireless radio (Fn+F2)
will turn the radio off, but will not toggle it back
on. Fn+F8 (CRT/LCD) does not work (will try those
patches) and Fn+F10 (eject CD/DVD), Fn+PageUp (vol
up), Fn+PageDown (vol down), Fn+End (mute), also
do not work.
Thanks,
--
DE
From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 25 20:17:48 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 8D6DE16A4DE;
Tue, 25 Jul 2006 20:17:48 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id 47F4643D45;
Tue, 25 Jul 2006 20:17:48 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6PKFu28097466; Tue, 25 Jul 2006 13:15:56 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6PKFupD097465; Tue, 25 Jul 2006 13:15:56 -0700 (PDT)
(envelope-from sgk)
Date: Tue, 25 Jul 2006 13:15:56 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20060725201556.GA97140@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200607241823.24477.jhb@freebsd.org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2006 20:17:48 -0000
On Mon, Jul 24, 2006 at 06:23:24PM -0400, John Baldwin wrote:
> On Monday 24 July 2006 17:50, Steve Kargl wrote:
> > ACPI gurus,
> >
> > My colleague has installed FreeBSD 6.1-table onto his
> > Alienware MJ-12 laptop. During the boot process, we
> > see
> >
> > acpi0: [MPSAFE]
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
>
> Well, that's probably why cardbus is broken. Can you get the output of
> acpidump? Specifically I'd be interested in the parts that mention LNKH (as
> well as where it actually lives in the device tree).
>
John,
The pattern LNKH appears in multiple places throughout the asl file.
Instead of sending seemly random chucks to the list, the entire asl
can be found at (uncompressed and gzipped)
http://troutmask.apl.washington.edu/~kargl/alienware.asl
http://troutmask.apl.washington.edu/~kargl/alienware.asl.gz
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 25 21:12:52 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 52DDE16A4DD
for <freebsd-acpi@freebsd.org>; Tue, 25 Jul 2006 21:12:52 +0000 (UTC)
(envelope-from dana.myers@gmail.com)
Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.198])
by mx1.FreeBSD.org (Postfix) with ESMTP id 1748A43D93
for <freebsd-acpi@freebsd.org>; Tue, 25 Jul 2006 21:12:36 +0000 (GMT)
(envelope-from dana.myers@gmail.com)
Received: by wx-out-0102.google.com with SMTP id i31so1027701wxd
for <freebsd-acpi@freebsd.org>; Tue, 25 Jul 2006 14:12:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
b=QlON99qENmSsNsmUHmd9//TiKf+DN+jvSm7WPzEos/5g/NM7Cnv82iHkc6MrGVPiZtnxdjo4nSwjPz6D8IJTENHzjt6KJUUretQ3fSYsl9jWHxb6Tg4ZLRegGUtmSta/0h90eLr6dMQlp6R1yFj15rYqWKQYAsqoqENvHOg8bIw=
Received: by 10.70.99.11 with SMTP id w11mr1527712wxb;
Tue, 25 Jul 2006 14:12:36 -0700 (PDT)
Received: from ?192.168.0.2? ( [67.180.22.170])
by mx.gmail.com with ESMTP id i37sm11017605wxd.2006.07.25.14.12.35;
Tue, 25 Jul 2006 14:12:36 -0700 (PDT)
Message-ID: <44C6894E.1010606@gmail.com>
Date: Tue, 25 Jul 2006 14:12:46 -0700
From: "Dana H. Myers" <dana.myers@gmail.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu> <200607241823.24477.jhb@freebsd.org>
<20060725201556.GA97140@troutmask.apl.washington.edu>
In-Reply-To: <20060725201556.GA97140@troutmask.apl.washington.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2006 21:12:52 -0000
Steve Kargl wrote:
> On Mon, Jul 24, 2006 at 06:23:24PM -0400, John Baldwin wrote:
>> On Monday 24 July 2006 17:50, Steve Kargl wrote:
>>> ACPI gurus,
>>>
>>> My colleague has installed FreeBSD 6.1-table onto his
>>> Alienware MJ-12 laptop. During the boot process, we
>>> see
>>>
>>> acpi0: [MPSAFE]
>>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace,
>> AE_NOT_FOUND
>>> SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
>>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
>> AE_NOT_FOUND
>>> SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
>>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
>> AE_NOT_FOUND
>>> SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
>>> ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
>> AE_NOT_FOUND
>>> SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
>> Well, that's probably why cardbus is broken. Can you get the output of
>> acpidump? Specifically I'd be interested in the parts that mention LNKH (as
>> well as where it actually lives in the device tree).
>>
>
> John,
>
> The pattern LNKH appears in multiple places throughout the asl file.
> Instead of sending seemly random chucks to the list, the entire asl
> can be found at (uncompressed and gzipped)
>
> http://troutmask.apl.washington.edu/~kargl/alienware.asl
I guess it's not a huge surprise, but I can't find a link device
named LINKH. Might this be a broken DSDT? Have you checked for an
updated BIOS and/or had a second-look at your BIOS setup?
Dana
From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 25 21:30:10 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 779B716A4DA;
Tue, 25 Jul 2006 21:30:10 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id D8A5443D55;
Tue, 25 Jul 2006 21:30:09 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6PLSHhm097953; Tue, 25 Jul 2006 14:28:17 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6PLSH60097952; Tue, 25 Jul 2006 14:28:17 -0700 (PDT)
(envelope-from sgk)
Date: Tue, 25 Jul 2006 14:28:17 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "Dana H. Myers" <dana.myers@gmail.com>
Message-ID: <20060725212817.GA97789@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
<20060725201556.GA97140@troutmask.apl.washington.edu>
<44C6894E.1010606@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44C6894E.1010606@gmail.com>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2006 21:30:10 -0000
On Tue, Jul 25, 2006 at 02:12:46PM -0700, Dana H. Myers wrote:
> Steve Kargl wrote:
> >
> > The pattern LNKH appears in multiple places throughout the asl file.
> > Instead of sending seemly random chucks to the list, the entire asl
> > can be found at (uncompressed and gzipped)
> >
> > http://troutmask.apl.washington.edu/~kargl/alienware.asl
>
> I guess it's not a huge surprise, but I can't find a link device
> named LINKH. Might this be a broken DSDT? Have you checked for an
> updated BIOS and/or had a second-look at your BIOS setup?
>
Yes, I checked the Alienware website for an updated BIOS.
It's a Phoenix BIOS, which has very few knobs in the BIOS
setup. My next step I guess is to try to contact the Alienware
tech support to see if a BIOS is available through a
specific request.
I'll have to locate a live cd of 6.1 Release because I'm
fairly certain that I had the wireless nic working.
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 08:15:06 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 87FA216A4DF;
Wed, 26 Jul 2006 08:15:06 +0000 (UTC)
(envelope-from ducrot@poupinou.org)
Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96])
by mx1.FreeBSD.org (Postfix) with ESMTP id 9E4D443D5F;
Wed, 26 Jul 2006 08:15:05 +0000 (GMT)
(envelope-from ducrot@poupinou.org)
Received: from ducrot by poup.poupinou.org with local (Exim)
id 1G5eXo-0004Pt-00; Wed, 26 Jul 2006 10:15:04 +0200
Date: Wed, 26 Jul 2006 10:15:04 +0200
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20060726081504.GV17014@poupinou.org>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200607241823.24477.jhb@freebsd.org>
User-Agent: Mutt/1.5.9i
From: Bruno Ducrot <ducrot@poupinou.org>
Cc: freebsd-acpi@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 08:15:06 -0000
Hi,
On Mon, Jul 24, 2006 at 06:23:24PM -0400, John Baldwin wrote:
> On Monday 24 July 2006 17:50, Steve Kargl wrote:
> > ACPI gurus,
> >
> > My colleague has installed FreeBSD 6.1-table onto his
> > Alienware MJ-12 laptop. During the boot process, we
> > see
> >
> > acpi0: [MPSAFE]
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
> > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> AE_NOT_FOUND
> > SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
>
> Well, that's probably why cardbus is broken. Can you get the output of
> acpidump? Specifically I'd be interested in the parts that mention LNKH (as
> well as where it actually lives in the device tree).
>
>From the dmesg:
pccard0: <16-bit PCCard bus> on cbb0
pcib0: matched entry for 0.5.INTA
pcib0: slot 5 INTA hardwired to IRQ 18
ioapic0: routing intpin 18 (PCI IRQ 18) to vector 49
Note the INTA which, I think, isn't related to
a Device (LNKH) but maybe a Device (LNKA) from the ASL
pointed from another mail.
I'm not sure at all, though.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 18:07:46 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 683D116A4FD;
Wed, 26 Jul 2006 18:07:46 +0000 (UTC) (envelope-from john@utzweb.net)
Received: from marley.grokthis.net (marley.grokthis.net [69.93.78.26])
by mx1.FreeBSD.org (Postfix) with ESMTP id ED66A43D4C;
Wed, 26 Jul 2006 18:07:45 +0000 (GMT) (envelope-from john@utzweb.net)
Received: from utzweb.net (marley.grokthis.net [127.0.0.1])
by marley.grokthis.net (Postfix) with ESMTP id 577C4F1445;
Wed, 26 Jul 2006 14:07:47 -0400 (EDT)
Received: from 69.93.78.27 (proxying for 216.254.62.194)
(SquirrelMail authenticated user john-utzweb-net);
by utzweb.net with HTTP; Wed, 26 Jul 2006 14:07:48 -0400 (EDT)
Message-ID: <47098.69.93.78.27.1153937268.squirrel@69.93.78.27>
In-Reply-To: <Pine.GSO.4.64.0607250953000.19799@sea.ntplx.net>
References: <Pine.GSO.4.64.0607250953000.19799@sea.ntplx.net>
Date: Wed, 26 Jul 2006 14:07:48 -0400 (EDT)
From: john@utzweb.net
To: deischen@freebsd.org
User-Agent: SquirrelMail/1.4.3a
X-Mailer: SquirrelMail/1.4.3a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: freebsd-acpi@freebsd.org
Subject: Re: Fn keys on Dell E1405
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 18:07:46 -0000
> Greetings and salutations,
>
> Is there anything I can do to get Fn key functionality on
> my Dell E1405 notebook?
port the nice linux i8ktools to freebsd before i do :-)
i started last weekend (i only have hxring time on the weekends) and i am
sure that i will eventually finish it successfully if somebody else doesnt
do it first.
i dont know if it will look much like the linux version when i am
finished, it makes use of the proc filesystem.
we do have a proc filesystem that we can kldload, but i am not sure how
robust it is and i dont want to be requiring an additional kld if my code
would be the only one using it.
it also uses a kernel timer to manage checking the keystrokes, i am not
sure if i wanna do that, i'd rather limit the kernel part to be limited to
the creation of /dev/smm and let the rest of the stuff happen in a daemon,
but i havent gotten far enuf along to have a coherent opinion ( i just
finally got the assembly code working to the point where i can get the
bios version back - banal, but critical :-) )
> I've seen the patches for video
> switching and will try them at some point, but it's not
> as important to me as getting suspend/resume and wireless
> radio on/off. Also getting the CD/DVD drive to eject would
> be nice.
>
> I'm using the latest and greatest BIOS on this system, and
> the output of 'acpidump -dt' is at:
>
> http://people.freebsd.org/~deischen/e1405.acpi.dump
>
> FYI, I can get the system to suspend by hitting the power
> button or by Fn+Esc (standby), but it will not wakeup
> no matter what I do.
not wake up or not restore the display? can you ping it?
> Also, the wireless radio (Fn+F2)
> will turn the radio off, but will not toggle it back
> on.
that's odd, i would have expected it to not work period.
> Fn+F8 (CRT/LCD) does not work (will try those
> patches) and Fn+F10 (eject CD/DVD), Fn+PageUp (vol
> up), Fn+PageDown (vol down), Fn+End (mute), also
> do not work.
i8k !
> Thanks,
>
> --
> DE
> _______________________________________________
> freebsd-acpi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org"
>
>
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 18:20:29 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id DE56D16A4DA
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 18:20:29 +0000 (UTC)
(envelope-from deischen@freebsd.org)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
by mx1.FreeBSD.org (Postfix) with ESMTP id B180643D77
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 18:20:25 +0000 (GMT)
(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6QIKOc5014855;
Wed, 26 Jul 2006 14:20:24 -0400 (EDT)
Date: Wed, 26 Jul 2006 14:20:24 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: john@utzweb.net
In-Reply-To: <47098.69.93.78.27.1153937268.squirrel@69.93.78.27>
Message-ID: <Pine.GSO.4.64.0607261415410.26919@sea.ntplx.net>
References: <Pine.GSO.4.64.0607250953000.19799@sea.ntplx.net>
<47098.69.93.78.27.1153937268.squirrel@69.93.78.27>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
Cc: freebsd-acpi@freebsd.org
Subject: Re: Fn keys on Dell E1405
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 18:20:29 -0000
On Wed, 26 Jul 2006, john@utzweb.net wrote:
>> Greetings and salutations,
>>
>> Is there anything I can do to get Fn key functionality on
>> my Dell E1405 notebook?
>
> port the nice linux i8ktools to freebsd before i do :-)
I do not know what they are. I would expect my keys to work
without using a port (assuming you turned i8ktools into a port)
;-)
> i started last weekend (i only have hxring time on the weekends) and i am
> sure that i will eventually finish it successfully if somebody else doesnt
> do it first.
>
> i dont know if it will look much like the linux version when i am
> finished, it makes use of the proc filesystem.
>
> we do have a proc filesystem that we can kldload, but i am not sure how
> robust it is and i dont want to be requiring an additional kld if my code
> would be the only one using it.
>
> it also uses a kernel timer to manage checking the keystrokes, i am not
> sure if i wanna do that, i'd rather limit the kernel part to be limited to
> the creation of /dev/smm and let the rest of the stuff happen in a daemon,
> but i havent gotten far enuf along to have a coherent opinion ( i just
> finally got the assembly code working to the point where i can get the
> bios version back - banal, but critical :-) )
>
>> I've seen the patches for video
>> switching and will try them at some point, but it's not
>> as important to me as getting suspend/resume and wireless
>> radio on/off. Also getting the CD/DVD drive to eject would
>> be nice.
>>
>> I'm using the latest and greatest BIOS on this system, and
>> the output of 'acpidump -dt' is at:
>>
>> http://people.freebsd.org/~deischen/e1405.acpi.dump
>>
>> FYI, I can get the system to suspend by hitting the power
>> button or by Fn+Esc (standby), but it will not wakeup
>> no matter what I do.
>
> not wake up or not restore the display? can you ping it?
I'm not that dense! The system is suspended -- no pingy,
no fanny, no disky, no LEDy, no nothing.
>> Also, the wireless radio (Fn+F2)
>> will turn the radio off, but will not toggle it back
>> on.
>
> that's odd, i would have expected it to not work period.
Yeah, me too.
>> Fn+F8 (CRT/LCD) does not work (will try those
>> patches) and Fn+F10 (eject CD/DVD), Fn+PageUp (vol
>> up), Fn+PageDown (vol down), Fn+End (mute), also
>> do not work.
>
> i8k !
Knock yourself out ;-)
--
DE
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 19:05:47 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 3DE5B16A4DA
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 19:05:47 +0000 (UTC)
(envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
[66.23.211.162])
by mx1.FreeBSD.org (Postfix) with ESMTP id 7841643D66
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 19:05:46 +0000 (GMT)
(envelope-from jhb@freebsd.org)
Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1])
(authenticated bits=0)
by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6QJ5gLe059327;
Wed, 26 Jul 2006 15:05:44 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Date: Wed, 26 Jul 2006 15:05:38 -0400
User-Agent: KMail/1.9.1
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
<20060725201556.GA97140@troutmask.apl.washington.edu>
In-Reply-To: <20060725201556.GA97140@troutmask.apl.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200607261505.38960.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
Wed, 26 Jul 2006 15:05:44 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.87.1/1621/Wed Jul 26 02:13:01 2006 on
server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 19:05:47 -0000
On Tuesday 25 July 2006 16:15, Steve Kargl wrote:
> On Mon, Jul 24, 2006 at 06:23:24PM -0400, John Baldwin wrote:
> > On Monday 24 July 2006 17:50, Steve Kargl wrote:
> > > ACPI gurus,
> > >
> > > My colleague has installed FreeBSD 6.1-table onto his
> > > Alienware MJ-12 laptop. During the boot process, we
> > > see
> > >
> > > acpi0: [MPSAFE]
> > > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in
namespace,
> > AE_NOT_FOUND
> > > SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
> > > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> > AE_NOT_FOUND
> > > SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
> > > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> > AE_NOT_FOUND
> > > SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
> > > ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace,
> > AE_NOT_FOUND
> > > SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
> >
> > Well, that's probably why cardbus is broken. Can you get the output of
> > acpidump? Specifically I'd be interested in the parts that mention LNKH
(as
> > well as where it actually lives in the device tree).
> >
>
> John,
>
> The pattern LNKH appears in multiple places throughout the asl file.
> Instead of sending seemly random chucks to the list, the entire asl
> can be found at (uncompressed and gzipped)
>
> http://troutmask.apl.washington.edu/~kargl/alienware.asl
> http://troutmask.apl.washington.edu/~kargl/alienware.asl.gz
You have some of the most incompetent BIOS writers I've ever seen working on
your machine I'm afraid. First off, there is no LNKH device on your system.
You do have various pci_link devices. Four for APIC: ALKA, ALKB, ALKC, and
ALKD, and four for non-APIC: LNKA, LNKB, LNKC, LNKD. Not only that, but they
all live in \_SB_.PCI0.PCIB. Some places refer to LNKH via
\_SB_.PCI0.PCIB.LNKH (as do all places for LNKA - LNKD it seems) but others
refer to it as \_SB_.PCI0.LNKH. Anyways, I think you might be fine if you
always use 'device apic', as the PCI interrupt routing tables for the APIC
case don't seem to reference LNKH. I think it will only go down in flames
this way if you disable APIC (via hint or not including 'device apic' in your
kernel config).
--
John Baldwin
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 19:23:15 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 98D3116A584;
Wed, 26 Jul 2006 19:23:15 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id DBA1743D62;
Wed, 26 Jul 2006 19:23:07 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6QJL6kO004964; Wed, 26 Jul 2006 12:21:06 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6QJL6sF004963; Wed, 26 Jul 2006 12:21:06 -0700 (PDT)
(envelope-from sgk)
Date: Wed, 26 Jul 2006 12:21:06 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20060726192106.GA4693@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
<20060725201556.GA97140@troutmask.apl.washington.edu>
<200607261505.38960.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200607261505.38960.jhb@freebsd.org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 19:23:15 -0000
On Wed, Jul 26, 2006 at 03:05:38PM -0400, John Baldwin wrote:
>
> You have some of the most incompetent BIOS writers I've ever seen working on
> your machine I'm afraid.
It's a Phoenix BIOS.
> First off, there is no LNKH device on your system.
> You do have various pci_link devices. Four for APIC: ALKA, ALKB, ALKC, and
> ALKD, and four for non-APIC: LNKA, LNKB, LNKC, LNKD. Not only that, but they
> all live in \_SB_.PCI0.PCIB. Some places refer to LNKH via
> \_SB_.PCI0.PCIB.LNKH (as do all places for LNKA - LNKD it seems) but others
> refer to it as \_SB_.PCI0.LNKH. Anyways, I think you might be fine if you
> always use 'device apic', as the PCI interrupt routing tables for the APIC
> case don't seem to reference LNKH. I think it will only go down in flames
> this way if you disable APIC (via hint or not including 'device apic' in your
> kernel config).
Thanks for the help. The asl file might as well be greek or chinese
or any other language that I don't speak. :(
I'll need to follow up tomorrow because the laptop is currently
in another location. I don't recall removing "device apic",
so perhaps I somehow munged the hints files.
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 19:56:29 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 4487E16A4E0
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 19:56:29 +0000 (UTC)
(envelope-from dana.myers@gmail.com)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237])
by mx1.FreeBSD.org (Postfix) with ESMTP id 6E6EF43D72
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 19:56:08 +0000 (GMT)
(envelope-from dana.myers@gmail.com)
Received: by wr-out-0506.google.com with SMTP id i32so982972wra
for <freebsd-acpi@freebsd.org>; Wed, 26 Jul 2006 12:56:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
b=L9Wbpcwa20yf7hz427tGjo5mrEmViMB8j7Z23j2v36pFYbxKfkBk8KYRLhHo887OE5CvDRAMsL/63P+VZbx/JeS4Rg4fgKN3BmypXr6o0jjR/YR281CBIcbnj71DM+qAmS264okC3jMscZSUE6mvC8NUmVte9G47T7LkwGMel3Q=
Received: by 10.64.24.20 with SMTP id 20mr7754168qbx;
Wed, 26 Jul 2006 12:56:05 -0700 (PDT)
Received: from ?192.168.0.2? ( [67.180.22.170])
by mx.gmail.com with ESMTP id 39sm1991761nzk.2006.07.26.12.55.58;
Wed, 26 Jul 2006 12:55:58 -0700 (PDT)
Message-ID: <44C7C8DA.3090402@gmail.com>
Date: Wed, 26 Jul 2006 12:56:10 -0700
From: "Dana H. Myers" <dana.myers@gmail.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu> <200607241823.24477.jhb@freebsd.org> <20060725201556.GA97140@troutmask.apl.washington.edu> <200607261505.38960.jhb@freebsd.org>
<20060726192106.GA4693@troutmask.apl.washington.edu>
In-Reply-To: <20060726192106.GA4693@troutmask.apl.washington.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 19:56:29 -0000
Steve Kargl wrote:
> On Wed, Jul 26, 2006 at 03:05:38PM -0400, John Baldwin wrote:
>> You have some of the most incompetent BIOS writers I've ever seen working on
>> your machine I'm afraid.
>
> It's a Phoenix BIOS.
Actually, I don't think Phoenix gets all the blame. I believe
that Phoenix provides a toolkit which board manufacturers customize.
So it's probably not Phoenix writing the bum ASL you're seeing.
Dana
From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 26 20:14:34 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 50EA516A4EC;
Wed, 26 Jul 2006 20:14:34 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id 6CB1A43DB9;
Wed, 26 Jul 2006 20:14:00 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6QKBmiq005347; Wed, 26 Jul 2006 13:11:48 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6QKBmBm005346; Wed, 26 Jul 2006 13:11:48 -0700 (PDT)
(envelope-from sgk)
Date: Wed, 26 Jul 2006 13:11:48 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "Dana H. Myers" <dana.myers@gmail.com>
Message-ID: <20060726201148.GA5068@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
<20060725201556.GA97140@troutmask.apl.washington.edu>
<200607261505.38960.jhb@freebsd.org>
<20060726192106.GA4693@troutmask.apl.washington.edu>
<44C7C8DA.3090402@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44C7C8DA.3090402@gmail.com>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 20:14:34 -0000
On Wed, Jul 26, 2006 at 12:56:10PM -0700, Dana H. Myers wrote:
> Steve Kargl wrote:
> > On Wed, Jul 26, 2006 at 03:05:38PM -0400, John Baldwin wrote:
> >> You have some of the most incompetent BIOS writers I've ever seen working on
> >> your machine I'm afraid.
> >
> > It's a Phoenix BIOS.
>
> Actually, I don't think Phoenix gets all the blame. I believe
> that Phoenix provides a toolkit which board manufacturers customize.
> So it's probably not Phoenix writing the bum ASL you're seeing.
>
Perhaps. But, it is Phoenix's name that is displayed.
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Thu Jul 27 17:03:50 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 737D916A4DD
for <freebsd-acpi@freebsd.org>; Thu, 27 Jul 2006 17:03:50 +0000 (UTC)
(envelope-from nate@root.org)
Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74])
by mx1.FreeBSD.org (Postfix) with ESMTP id 242DB43D83
for <freebsd-acpi@freebsd.org>; Thu, 27 Jul 2006 17:03:36 +0000 (GMT)
(envelope-from nate@root.org)
Received: from pimout6-ext.prodigy.net (pimout6-int.prodigy.net [207.115.4.22])
by ylpvm43.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id
k6RH3a4O014040
for <freebsd-acpi@freebsd.org>; Thu, 27 Jul 2006 13:03:36 -0400
X-ORBL: [67.119.74.222]
Received: from [10.0.0.53] (adsl-67-119-74-222.dsl.sntc01.pacbell.net
[67.119.74.222])
by pimout6-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id
k6RH3Vij141714; Thu, 27 Jul 2006 13:03:32 -0400
Message-ID: <44C8F1DC.8050201@root.org>
Date: Thu, 27 Jul 2006 10:03:24 -0700
From: Nate Lawson <nate@root.org>
User-Agent: Thunderbird 1.5.0.2 (X11/20060501)
MIME-Version: 1.0
To: "Dana H. Myers" <dana.myers@gmail.com>
References: <20060724215014.GA89464@troutmask.apl.washington.edu> <200607241823.24477.jhb@freebsd.org> <20060725201556.GA97140@troutmask.apl.washington.edu> <200607261505.38960.jhb@freebsd.org> <20060726192106.GA4693@troutmask.apl.washington.edu>
<44C7C8DA.3090402@gmail.com>
In-Reply-To: <44C7C8DA.3090402@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-acpi@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2006 17:03:50 -0000
Dana H. Myers wrote:
> Steve Kargl wrote:
>> On Wed, Jul 26, 2006 at 03:05:38PM -0400, John Baldwin wrote:
>>> You have some of the most incompetent BIOS writers I've ever seen working on
>>> your machine I'm afraid.
>> It's a Phoenix BIOS.
>
> Actually, I don't think Phoenix gets all the blame. I believe
> that Phoenix provides a toolkit which board manufacturers customize.
> So it's probably not Phoenix writing the bum ASL you're seeing.
That's correct. Phoenix produces a tool that has some example ASL. The
Chinese/Taiwanese company that actually makes the laptop (e.g., Compal)
subcontracts out the BIOS customization to an small firm (2 guys) that
bang on it until it boots Windows.
--
Nate
From owner-freebsd-acpi@FreeBSD.ORG Thu Jul 27 17:41:03 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id F248116A4DA
for <freebsd-acpi@freebsd.org>; Thu, 27 Jul 2006 17:41:03 +0000 (UTC)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
[128.208.78.105])
by mx1.FreeBSD.org (Postfix) with ESMTP id 7B56843D55
for <freebsd-acpi@freebsd.org>; Thu, 27 Jul 2006 17:41:03 +0000 (GMT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
[127.0.0.1])
by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
k6RHcr8b013173; Thu, 27 Jul 2006 10:38:53 -0700 (PDT)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
k6RHcrZo013172; Thu, 27 Jul 2006 10:38:53 -0700 (PDT)
(envelope-from sgk)
Date: Thu, 27 Jul 2006 10:38:53 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Nate Lawson <nate@root.org>
Message-ID: <20060727173853.GA13115@troutmask.apl.washington.edu>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
<200607241823.24477.jhb@freebsd.org>
<20060725201556.GA97140@troutmask.apl.washington.edu>
<200607261505.38960.jhb@freebsd.org>
<20060726192106.GA4693@troutmask.apl.washington.edu>
<44C7C8DA.3090402@gmail.com> <44C8F1DC.8050201@root.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44C8F1DC.8050201@root.org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-acpi@freebsd.org
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2006 17:41:04 -0000
On Thu, Jul 27, 2006 at 10:03:24AM -0700, Nate Lawson wrote:
> Dana H. Myers wrote:
> >Steve Kargl wrote:
> >>On Wed, Jul 26, 2006 at 03:05:38PM -0400, John Baldwin wrote:
> >>>You have some of the most incompetent BIOS writers I've ever seen
> >>>working on your machine I'm afraid.
> >>It's a Phoenix BIOS.
> >
> >Actually, I don't think Phoenix gets all the blame. I believe
> >that Phoenix provides a toolkit which board manufacturers customize.
> >So it's probably not Phoenix writing the bum ASL you're seeing.
>
> That's correct. Phoenix produces a tool that has some example ASL. The
> Chinese/Taiwanese company that actually makes the laptop (e.g., Compal)
> subcontracts out the BIOS customization to an small firm (2 guys) that
> bang on it until it boots Windows.
Well, given the ASL that I put up at my website, is there
any hope of patching it?
--
Steve
From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 28 19:38:52 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id CC92316A4DA
for <freebsd-acpi@freebsd.org>; Fri, 28 Jul 2006 19:38:52 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169])
by mx1.FreeBSD.org (Postfix) with ESMTP id 0F94643D6A
for <freebsd-acpi@freebsd.org>; Fri, 28 Jul 2006 19:38:47 +0000 (GMT)
(envelope-from uspoerlein@gmail.com)
Received: by ug-out-1314.google.com with SMTP id m2so966457uge
for <freebsd-acpi@freebsd.org>; Fri, 28 Jul 2006 12:38:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to;
b=ZFELv0E3gvLi5XKtbMvbxFmLcDb9hUVsN6Gxn8lkcSKphu68RGcjhr49ybzdbFCTZhFXK+L9UAdvF4zYOJ2meeh2hFyuVCf2hPzGl8otX78T4HgsBK6irz2pOEPdh2UBecuLDdlcQ44yYT7InXzyBYIHsTOMczdI/x+Ym3rR46E=
Received: by 10.78.142.14 with SMTP id p14mr163629hud;
Fri, 28 Jul 2006 12:38:46 -0700 (PDT)
Received: from roadrunner.q.local ( [217.185.114.53])
by mx.gmail.com with ESMTP id 39sm1164923hui.2006.07.28.12.38.42;
Fri, 28 Jul 2006 12:38:44 -0700 (PDT)
Received: from roadrunner.q.local (localhost [127.0.0.1])
by roadrunner.q.local (8.13.6/8.13.6) with ESMTP id k6SJdLpc004669;
Fri, 28 Jul 2006 21:39:21 +0200 (CEST)
(envelope-from uspoerlein@gmail.com)
Received: (from q@localhost)
by roadrunner.q.local (8.13.6/8.13.6/Submit) id k6SJ3BYk003688;
Fri, 28 Jul 2006 21:03:11 +0200 (CEST)
(envelope-from uspoerlein@gmail.com)
Date: Fri, 28 Jul 2006 21:03:11 +0200
From: Ulrich Spoerlein <uspoerlein@gmail.com>
To: deischen@freebsd.org
Message-ID: <20060728190311.GA1057@roadrunner.informatik.uni-wuerzburg.de>
Mail-Followup-To: deischen@freebsd.org, freebsd-acpi@freebsd.org
References: <Pine.GSO.4.64.0607250953000.19799@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.64.0607250953000.19799@sea.ntplx.net>
Cc: freebsd-acpi@freebsd.org
Subject: Re: Fn keys on Dell E1405
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2006 19:38:52 -0000
Daniel Eischen wrote:
> Greetings and salutations,
>
> Is there anything I can do to get Fn key functionality on
> my Dell E1405 notebook? I've seen the patches for video
> switching and will try them at some point, but it's not
> as important to me as getting suspend/resume and wireless
> radio on/off. Also getting the CD/DVD drive to eject would
> be nice.
On my Inspiron 8600, nearly all Fn keys produce plain key scancodes,
that you can assign to specific commands in X.
I have the following keycodes in .xmodmaprc
keycode 164 = XF86AudioStop
keycode 137 = XF86Eject
keycode 162 = XF86AudioPause
keycode 160 = XF86AudioStop
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 174 = XF86AudioLowerVolume
keycode 176 = XF86AudioRaiseVolume
keycode 160 = XF86AudioMute
Please check those values with xev(1). You would then have to assign
specific commands to these keys with the help of your window manager.
Funny side note: The brightness up/down combo does NOT generate any kind
of keycode ... BUT when I turn the brightness up or down while xpdf(1)
has the focus, xpdf(1) will enter an infinite refresh loop and needs to
be killed. Very strange ....
Ulrich Spoerlein
--
A: Yes.
>Q: Are you sure?
> >A: Because it reverses the logical flow of conversation.
> >>Q: Why is top posting frowned upon?