From owner-freebsd-acpi@FreeBSD.ORG Sat May 26 12:45:44 2012 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 E4818106566C for ; Sat, 26 May 2012 12:45:44 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id 61C618FC19 for ; Sat, 26 May 2012 12:45:43 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mail.0x20.net (Postfix) with ESMTP id C66836A6017; Sat, 26 May 2012 14:45:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.0x20.net Received: from mail.0x20.net ([217.69.76.211]) by mail.0x20.net (mail.0x20.net [217.69.76.211]) (amavisd-new, port 10024) with ESMTP id eMR3svseE3NV; Sat, 26 May 2012 14:45:42 +0200 (CEST) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 83D226A6002; Sat, 26 May 2012 14:45:42 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.4/8.14.4) with ESMTP id q4QCjgsq057632; Sat, 26 May 2012 14:45:42 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.4/8.14.4/Submit) id q4QCjg8d056488; Sat, 26 May 2012 14:45:42 +0200 (CEST) (envelope-from lars) Date: Sat, 26 May 2012 14:45:42 +0200 From: Lars Engels To: Kevin Oberman Message-ID: <20120526124542.GK39168@e-new.0x20.net> References: <20120523151357.GC97037@sigil.instinctive.eu> <20120524065532.GB39168@e-new.0x20.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="++alDQ2ROsODg1x+" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.2-RELEASE-p6 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-acpi@freebsd.org, Natacha =?utf-8?B?UG9ydMOp?= Subject: Re: How can I help with thinkpad x220 issues? 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: Sat, 26 May 2012 12:45:45 -0000 --++alDQ2ROsODg1x+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 25, 2012 at 08:25:47PM -0700, Kevin Oberman wrote: > On Wed, May 23, 2012 at 11:55 PM, Lars Engels wrot= e: > > On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote: > >> On Wed, May 23, 2012 at 8:13 AM, Natacha Port=C3=A9 wrote: > >> > Hello, > >> > > >> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a > >> > recent thread here I gather it almost works with FreeBSD, and the > >> > remaining problems are screen brightness and screen left unpowered at > >> > resume. Is that right? > >> > > >> > So my question is, how can I help make progress in any of these area? > >> > (though I admit I'm more interested in having the brightness problem > >> > solved than the resume one) > >> > > >> > I don't know anything about ACPI or about FreeBSD or Linux internals, > >> > but I'm quite proficient in C and somewhat used to navigate in unkno= wn > >> > huge code bases. > >> > > >> > So I guess the first steps to help would be to first learn stuff. > >> > > >> > However I don't have much time available. I guess FreeBSD 11 would r= each > >> > end-of-life before I could reach a level of understanding I find > >> > satisfying (though I admit I have high standards there), so I would = have > >> > to prioritize. So my question is rather *what* should I learn to pro= vide > >> > help as soon as possible? > >> > > >> > For example, if the brightness issue is just a matter of extracting = the > >> > right numbers from linux kernel code and plug them into FreeBSD, I > >> > probably won't need to learn anything more about ACPI than what I wo= uld > >> > gather looking at the code. I guess if it was that simple someone wo= uld > >> > have already done it, but that illustrate well my point about > >> > prioritizing learning. > >> > > >> > Or is the barrier of entry too high for me to be of any use? > >> > >> If it has not been committed, the minor fix to make acpi_ibm work on > >> modern ThinkPads needs to be committed. Once done, the issues > >> mentioned need to be addressed.This includes getting brightness to be > >> setable from both the keypad hot-keys and from applications. ATM, I > >> can set the brightness, but making the hot-keys work will require the > >> ability to extract the current level so that it may be adjusted > >> plus/minus one. > >> > >> The other issue is volume control keys don't work. I suspect it will > >> be similar to brightness, but I don't know just how to figure it out. > >> > >> I should also mention that I don't have an X220. I have a T520, but > >> the issues seem to be identical, so fixing one will probably fix a lot > >> of recent ThinkPads. > > > > About the key: > > > > Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=3D1", > > "cat /var/run/devd.pipe" and then press the keys. Does anything show up? >=20 > After adding LEN0068 ti the ACPI IDs, I tried this and I get no ACPI > event when pressing either button, but I do get regular key press > events: > KeyPress event, serial 30, synthetic NO, window 0x4600001, > root 0x121, subw 0x0, time 166670035, (96,121), root:(100,750), > state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), > same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False >=20 > KeyRelease event, serial 33, synthetic NO, window 0x4600001, > root 0x121, subw 0x0, time 166670185, (96,121), root:(100,750), > state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), > same_screen YES, > XLookupString gives 0 bytes: > XFilterEvent returns: False >=20 > KeyPress event, serial 33, synthetic NO, window 0x4600001, > root 0x121, subw 0x0, time 166927339, (98,0), root:(102,629), > state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), > same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False >=20 > KeyRelease event, serial 33, synthetic NO, window 0x4600001, > root 0x121, subw 0x0, time 166927451, (98,0), root:(102,629), > state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), > same_screen YES, > XLookupString gives 0 bytes: > XFilterEvent returns: False Hmm, okay, that's not too bad. At least the keys are recognized. >=20 > I can set these up as hot keys and issue a command, but I have no idea > what I can set to adjust the hardware volume. But I will also need to > read out the current volume so I know what value to which is should be > set. (Same issue as with brightness.) Do you have dev.acpi_ibm.0.lcd_brightness and .volume? If you cou can write a script that raises / lowers the values with sysctl. --++alDQ2ROsODg1x+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk/A0HYACgkQKc512sD3afhPkgCgkg7IqsuUxqVO+HQClQxKcPDO 65sAnijVcfDdM1xCgj2A5QwUEfiKEOxY =+/Sg -----END PGP SIGNATURE----- --++alDQ2ROsODg1x+--