Date: Tue, 25 Jul 2006 14:12:46 -0700 From: "Dana H. Myers" <dana.myers@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-acpi@freebsd.org Subject: Re: Alienware acpi problem Message-ID: <44C6894E.1010606@gmail.com> In-Reply-To: <20060725201556.GA97140@troutmask.apl.washington.edu> References: <20060724215014.GA89464@troutmask.apl.washington.edu> <200607241823.24477.jhb@freebsd.org> <20060725201556.GA97140@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C6894E.1010606>