Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Jul 2005 08:30:53 -0700
From:      Nate Lawson <nate@root.org>
To:        Markus Brueffer <markus@brueffer.de>
Cc:        freebsd-acpi@freebsd.org
Subject:   Re: Thinkpad t42 fn+f3 (Blank Screen)
Message-ID:  <42DE6E2D.5040202@root.org>
In-Reply-To: <200507201722.10413.markus@brueffer.de>
References:  <42DD2F4B.7020805@root.org>	<6a7033710507200150178fd9a6@mail.gmail.com>	<20050720143707.GK2715@poupinou.org> <200507201722.10413.markus@brueffer.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Markus Brueffer wrote:
> On Wednesday 20 July 2005 16:37, Bruno Ducrot wrote:
>>Thanks you both for sending me the ASLs for your machine.
>>
>>Unfortunately, I can't help yet looking around those ASLs.
>>
>>The problem are:
>>
>>1- the _Q12 method (which should be called if pressing
>>Fn+F3 if I understand correctly a previous email) will call
>>\_SB.PCI0.LPC.EC.HKEY.MHKQ (0x1003)
>>and at the MHKQ() will then call '\UCMS (0x0D) (if Arg0 is 0x1003)',
>>which in turn will call SMI(...) which is a call to a SMI handler (since
>>it will output 'something' to io port 0xb2).  And it's pretty hard to
>>debug SMI handler somehow..
>>
>>2- that method (MHKQ()) will also notify at the very end the device
>>'HKEY'.  That one is 'Name (_HID, EisaId ("IBM0068"))' and therefore is
>>a propritary "device".  We have to write a driver in order to handle
>>that 'notify' (and I must admit I don't know what to do even then).
> 
> 
> We already have one: acpi_ibm(4). Setting
> 
> dev.acpi_ibm.0.events=1
> 
> enables these ACPI events (disabled by default, because it changes the 
> default behaviour of some keys, see manpage) which can be processed by 
> devd.
> 
> On my T41p Fn+F3 doesn't work as advertised as well (without setting the 
> sysctl. Setting the sysctl correctly throws an event). Unfortunately I 
> didn't have time to look into this, yet :(

Right.  The problem with debugging SMM code that Bruno mentions is 
because it is not accessible at runtime (the memory is hidden and 
locked.)  The only way to get to it is to dump the flash and that's a 
lot of work.

-- 
Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42DE6E2D.5040202>