tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Sandro-26
The Lenovo X1 Carbon is gaining populairty as it's easily one of the prettiest alternatives to the McBook Air.

For a while, I thought the keyboard backlight couldn't be controlled through tpacpi, period. After asking a question <http://askubuntu.com/questions/383501/> I got an interesting answer:

The keyboard backlight can in fact be turned off using the following command:
echo 0 > /sys/class/leds/tpacpi\:\:thinklight/brightness
It's just that it cannot be turned /on/, which is what I am trying to do .

I can't be certain, but if the current tpacpi can turn the light off, it gives me the impression that turning it on is just a bugfix away.

I cannot find an issuetracker for Github or Sourceforce, so I thought maybe one of the devs (is that still Henrique de Moraes Holschuh AKA Hmh?) will read this.


Met vriendelijke groet,

~Redsandro

http://www.Redsandro.com/
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Henrique de Moraes Holschuh-2
On Sun, 29 Dec 2013, Sandro wrote:

> The Lenovo X1 Carbon is gaining populairty as it's easily one of the
> prettiest alternatives to the McBook Air.
>
> For a while, I thought the keyboard backlight couldn't be controlled
> through tpacpi, period. After asking a question <
> http://askubuntu.com/questions/383501/> I got an interesting answer:
>
> The keyboard backlight can in fact be turned off using the following
> command:
> echo 0 > /sys/class/leds/tpacpi\:\:thinklight/brightness
> It's just that it cannot be turned /on/, which is what I am trying to do.
>
> I can't be certain, but if the current tpacpi can turn the light off, it
> gives me the impression that turning it on is just a bugfix away.
>
> I cannot find an issuetracker for Github or Sourceforce, so I thought maybe
> one of the devs (is that still Henrique de Moraes Holschuh AKA Hmh?) will
> read this.

I am reading this, but I can't do much without access to a X1.  The
thinklight control uses a specific ACPI method, so your X1 has it or it
would not have turned anything off.

It likely wants a different parameter to enable the keyboard backlight
(which stands to reason, since it is not a thinklight).  Since the turn-off
command worked, if we're lucky it is a bitfield and it can be used to
separately control the thinklight and the keyboard backlight.

I won't promise anything, but send me the ACPI dump of your X1 (update it to
the latest BIOS/EFI first).  Use a recent version of the ACPI tools,
preferably "acpidump" from the latest Linux kernel tree (it is inside the
tools/power/acpi directory of the kernel source.  Type Make there to build).
Your linux distro might have it packaged.

I also need the output of dmidecode.  Remove all serial numbers and UUIDs
before you send it to me (replace their digits with "X").

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Chris Schumann
I also have an X1 Carbon (with touchscreen!) model 3443-CTO.

I'm happy to help and will send you the output from my system too.

Chris

On 12/29/2013 08:15 PM, Henrique de Moraes Holschuh wrote:

> On Sun, 29 Dec 2013, Sandro wrote:
>> The Lenovo X1 Carbon is gaining populairty as it's easily one of the
>> prettiest alternatives to the McBook Air.
>>
>> For a while, I thought the keyboard backlight couldn't be controlled
>> through tpacpi, period. After asking a question <
>> http://askubuntu.com/questions/383501/> I got an interesting answer:
>>
>> The keyboard backlight can in fact be turned off using the following
>> command:
>> echo 0 > /sys/class/leds/tpacpi\:\:thinklight/brightness
>> It's just that it cannot be turned /on/, which is what I am trying to do.
>>
>> I can't be certain, but if the current tpacpi can turn the light off, it
>> gives me the impression that turning it on is just a bugfix away.
>>
>> I cannot find an issuetracker for Github or Sourceforce, so I thought maybe
>> one of the devs (is that still Henrique de Moraes Holschuh AKA Hmh?) will
>> read this.
> I am reading this, but I can't do much without access to a X1.  The
> thinklight control uses a specific ACPI method, so your X1 has it or it
> would not have turned anything off.
>
> It likely wants a different parameter to enable the keyboard backlight
> (which stands to reason, since it is not a thinklight).  Since the turn-off
> command worked, if we're lucky it is a bitfield and it can be used to
> separately control the thinklight and the keyboard backlight.
>
> I won't promise anything, but send me the ACPI dump of your X1 (update it to
> the latest BIOS/EFI first).  Use a recent version of the ACPI tools,
> preferably "acpidump" from the latest Linux kernel tree (it is inside the
> tools/power/acpi directory of the kernel source.  Type Make there to build).
> Your linux distro might have it packaged.
>
> I also need the output of dmidecode.  Remove all serial numbers and UUIDs
> before you send it to me (replace their digits with "X").
>

--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Henrique de Moraes Holschuh-2
On Mon, 30 Dec 2013, Chris Schumann wrote:
> >I am reading this, but I can't do much without access to a X1.  The
> >thinklight control uses a specific ACPI method, so your X1 has it or it
> >would not have turned anything off.

Meh.  The "off" command uses the generic "update-cmos" handler (UCMS), which
often just stores info in come nvram instead of doing something.  In the
keyboard backlight case, the OFF command for the lights (thinklight and
apparently backlight) actually turns them off, but if there is an ON
command, it is command 0x0e (which is supposed to just toggle the
thinklight).

Please test it, see if thinkpad-acpi will give you the /proc/acpi/ibm/cmos
file.  If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.

The DSDT has KBLT to get the status, KBLS to get/set the status (generic SMI
trap), as well as several loosely related EC events reported to userspace.

There are two higher-level ACPI methods: MLCG (get) and MLCS (set), the
later issues EC events 0x6001 (unknown) and 0x1012.  0x1012 is known: it is
the hotkey event for FN+PGUP (thinklight key on older thinkpads).

What's in the FN+PGUP key of a X1 carbon?  This is weird, I'd expect it to
be mapped to FN+SPACE (event 0x1014)...

Anyway, looks like FN+SPACE is supposed to mess with a light, the EC handle
for that one (_Q63) does issue event 0x1014, and calls CMOS command 0x0B,
which used to be related to screen expansion.

Are any of you X1 carbon owners confortable with kernel hacking?

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Henrique de Moraes Holschuh-2
On Tue, 31 Dec 2013, Henrique de Moraes Holschuh wrote:

> On Mon, 30 Dec 2013, Chris Schumann wrote:
> > >I am reading this, but I can't do much without access to a X1.  The
> > >thinklight control uses a specific ACPI method, so your X1 has it or it
> > >would not have turned anything off.
>
> Meh.  The "off" command uses the generic "update-cmos" handler (UCMS), which
> often just stores info in come nvram instead of doing something.  In the
> keyboard backlight case, the OFF command for the lights (thinklight and
> apparently backlight) actually turns them off, but if there is an ON
> command, it is command 0x0e (which is supposed to just toggle the
> thinklight).
>
> Please test it, see if thinkpad-acpi will give you the /proc/acpi/ibm/cmos
> file.  If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
> might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.

It is also available in sysfs (far more likely to be supported than the
/proc node in a recent kernel).  It is likely at
/sys/bus/platform/drivers/thinkpad_acpi/cmos_command.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Sandro-26
In reply to this post by Sandro-26
I've sent you the dumps. I had to run the Lenovo updater thingie until I got a BIOS update. God that Lenovo software is annoying. Unlike Chris, I do not have touch.

@Chris did you have the touch-less version before that? I am wondering if the screen quality or laptop weight had to suffer for this upgrade or if it's pretty much the same.

Also, Linux desktop and touch? Can you use those two things together?


Met vriendelijke groet,

~Sander

http://www.Redsandro.com/
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Chris Schumann
In reply to this post by Henrique de Moraes Holschuh-2
On 12/31/2013 07:29 AM, Henrique de Moraes Holschuh wrote:

> On Mon, 30 Dec 2013, Chris Schumann wrote:
>>> I am reading this, but I can't do much without access to a X1.  The
>>> thinklight control uses a specific ACPI method, so your X1 has it or it
>>> would not have turned anything off.
> Meh.  The "off" command uses the generic "update-cmos" handler (UCMS), which
> often just stores info in come nvram instead of doing something.  In the
> keyboard backlight case, the OFF command for the lights (thinklight and
> apparently backlight) actually turns them off, but if there is an ON
> command, it is command 0x0e (which is supposed to just toggle the
> thinklight).
>
> Please test it, see if thinkpad-acpi will give you the /proc/acpi/ibm/cmos
> file.
I'm not sure what to test here, but I have this:
$ cat /proc/acpi/ibm/cmos
status:        supported
commands:    <cmd> (<cmd> is 0-21)

> If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
> might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.
Not so useful:
$ sudo echo "0x0e" > /proc/acpi/ibm/cmos
bash: /proc/acpi/ibm/cmos: Permission denied

> The DSDT has KBLT to get the status, KBLS to get/set the status (generic SMI
> trap), as well as several loosely related EC events reported to userspace.
>
> There are two higher-level ACPI methods: MLCG (get) and MLCS (set), the
> later issues EC events 0x6001 (unknown) and 0x1012.  0x1012 is known: it is
> the hotkey event for FN+PGUP (thinklight key on older thinkpads).
>
> What's in the FN+PGUP key of a X1 carbon?  This is weird, I'd expect it to
> be mapped to FN+SPACE (event 0x1014)...
>
> Anyway, looks like FN+SPACE is supposed to mess with a light, the EC handle
> for that one (_Q63) does issue event 0x1014, and calls CMOS command 0x0B,
> which used to be related to screen expansion.
>
> Are any of you X1 carbon owners confortable with kernel hacking?
>
Fn+SPACE works the keyboard backlight through 3 states: low, high, off.
The intensity does not jump, but ramps, so there's some spiffy hardware
in there.

I used to write embedded firmware (for printers and communication
devices), so I'm pretty comfy with that aspect. Just haven't done much
of that in Linux. I'm happy to help if I can.

Chris

--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Chris Schumann
In reply to this post by Henrique de Moraes Holschuh-2
On 12/31/2013 07:42 AM, Henrique de Moraes Holschuh wrote:

> On Tue, 31 Dec 2013, Henrique de Moraes Holschuh wrote:
>> On Mon, 30 Dec 2013, Chris Schumann wrote:
>>>> I am reading this, but I can't do much without access to a X1.  The
>>>> thinklight control uses a specific ACPI method, so your X1 has it or it
>>>> would not have turned anything off.
>> Meh.  The "off" command uses the generic "update-cmos" handler (UCMS), which
>> often just stores info in come nvram instead of doing something.  In the
>> keyboard backlight case, the OFF command for the lights (thinklight and
>> apparently backlight) actually turns them off, but if there is an ON
>> command, it is command 0x0e (which is supposed to just toggle the
>> thinklight).
>>
>> Please test it, see if thinkpad-acpi will give you the /proc/acpi/ibm/cmos
>> file.  If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
>> might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.
> It is also available in sysfs (far more likely to be supported than the
> /proc node in a recent kernel).  It is likely at
> /sys/bus/platform/drivers/thinkpad_acpi/cmos_command.
>
That directory doesn't exist for me, but I have
/sys/bus/platform/drivers/thinkpad_acpi/thinkpad_acpi/ and a whole bunch
of stuff under that.

Chris

--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Chris Schumann
In reply to this post by Sandro-26
On 12/31/2013 12:01 PM, Sandro wrote:

> I've sent you the dumps. I had to run the Lenovo updater thingie until
> I got a BIOS update. God that Lenovo software is annoying. Unlike
> Chris, I do not have touch.
>
> @Chris did you have the touch-less version before that? I am wondering
> if the screen quality or laptop weight had to suffer for this upgrade
> or if it's pretty much the same.
>
> Also, Linux desktop and touch? Can you use those two things together?
>
I never had the touchless version. Weight definitely suffered -
something like 185g.

The touchscreen works in Linux - I can touch it to click or select. The
gestures like scrolling and such do not work for the desktop or in a
browser.

Chris

--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Evgeni Golov-3
In reply to this post by Chris Schumann
On 01/01/2014 03:22 PM, Chris Schumann wrote:
>
>> If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
>> might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.
> Not so useful:
> $ sudo echo "0x0e" > /proc/acpi/ibm/cmos
> bash: /proc/acpi/ibm/cmos: Permission denied

use either 'echo "0x0e" | sudo tee /proc/acpi/ibm/cmos'
or become root via 'sudo su -' and do the echo .. > .. then.
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Joachim Breitner-2
In reply to this post by Sandro-26
Hi,

Am Sonntag, den 29.12.2013, 17:29 +0100 schrieb Sandro:
> For a while, I thought the keyboard backlight couldn't be controlled
> through tpacpi, period. After asking a question
> <http://askubuntu.com/questions/383501/> I got an interesting answer:
>
> The keyboard backlight can in fact be turned off using the following
> command:
> echo 0 > /sys/class/leds/tpacpi\:\:thinklight/brightness
> It's just that it cannot be turned /on/, which is what I am trying to
> do .

this sounds as if it might not be specific to X1, but most newer
thinkpads, as mentioned for example on
http://unix.stackexchange.com/questions/96666/pidgin-blinklight-not-working-with-thinkpad-acpi-t430

I’m looking forward to what you might find; I’d really like to be able
to use pidgin-blinklight again (using a T430s here).

Greetings,
Joachim


--
Joachim “nomeata” Breitner
  [hidden email]http://www.joachim-breitner.de/
  Jabber: [hidden email]  • GPG-Key: 0x4743206C
  Debian Developer: [hidden email]

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Chris Schumann
In reply to this post by Evgeni Golov-3
On 01/01/2014 08:36 AM, Evgeni Golov wrote:
> On 01/01/2014 03:22 PM, Chris Schumann wrote:
>>> If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
>>> might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.
>> Not so useful:
>> $ sudo echo "0x0e" > /proc/acpi/ibm/cmos
>> bash: /proc/acpi/ibm/cmos: Permission denied
> use either 'echo "0x0e" | sudo tee /proc/acpi/ibm/cmos'
> or become root via 'sudo su -' and do the echo .. > .. then.
$ echo "0x0e" | sudo tee /proc/acpi/ibm/cmos
0x0e

Helpful?
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Sandro-26
In reply to this post by Sandro-26
Thanks for looking into this.

 echo "0x0e" > /proc/acpi/ibm/cmos might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.

All four (?) commands don't seem to do anything.

What's in the FN+PGUP key of a X1 carbon?  This is weird, I'd expect it to be mapped to FN+SPACE (event 0x1014)...

I guess Fn + Space is the PgUp equivalent? The Carbon has three states for keyboard-backlighting . Off, low-light and bright-light and pressing Fn + Space cycles between the three.

Are any of you X1 carbon owners confortable with kernel hacking?

Not me :D I hardly know what you are talking about except for the questions I answered.
I thought, since we can already turn the lights off, that it would be a breeze to figure how to turn them on. I underestimated that. :)

Too bad there isn't a "default-on" option in the BIOS (yet).

Met vriendelijke groet,

~Sander
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Henrique de Moraes Holschuh-2
On Thu, 02 Jan 2014, Sandro wrote:

> Thanks for looking into this.
> >  echo "0x0e" > /proc/acpi/ibm/cmos might be useful.  Other interesting
> cmos commands might be 0x0b to 0x0d.
>
> All four (?) commands don't seem to do anything.
>
> > What's in the FN+PGUP key of a X1 carbon?  This is weird, I'd expect it
> to be mapped to FN+SPACE (event 0x1014)...
>
> I guess Fn + Space is the PgUp equivalent? The Carbon has three states for

That would be extremely annoying, but it is easy enough to test for.  Do you
have an utility to dump input device events?  In Debian/Ubuntu, it is called
input-events and lsinput (package input-utils).

If you do, set the thinkpad-acpi hotkey_mask to all ones to leak all hotkey
events to userspace, run the input events dump utility attached to the
thinkpad-acpi input device (lsinput will help you locate it), and check
which events are reported for each key.  You want the scancodes (events with
type EV_MSC MSC_SCAN) that are reported when you press a hotkey.

The documentation for thinkpad-acpi is attached.  The hoktey_mask and other
sysfs nodes will be somewhere under /sys/devices/platform/thinkpad_acpi/

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Henrique de Moraes Holschuh-2
In reply to this post by Chris Schumann
On Wed, 01 Jan 2014, Chris Schumann wrote:

> On 12/31/2013 07:42 AM, Henrique de Moraes Holschuh wrote:
> >On Tue, 31 Dec 2013, Henrique de Moraes Holschuh wrote:
> >>On Mon, 30 Dec 2013, Chris Schumann wrote:
> >>>>I am reading this, but I can't do much without access to a X1.  The
> >>>>thinklight control uses a specific ACPI method, so your X1 has it or it
> >>>>would not have turned anything off.
> >>Meh.  The "off" command uses the generic "update-cmos" handler (UCMS), which
> >>often just stores info in come nvram instead of doing something.  In the
> >>keyboard backlight case, the OFF command for the lights (thinklight and
> >>apparently backlight) actually turns them off, but if there is an ON
> >>command, it is command 0x0e (which is supposed to just toggle the
> >>thinklight).
> >>
> >>Please test it, see if thinkpad-acpi will give you the /proc/acpi/ibm/cmos
> >>file.  If it still does in your kernel, echo "0x0e" > /proc/acpi/ibm/cmos
> >>might be useful.  Other interesting cmos commands might be 0x0b to 0x0d.
> >It is also available in sysfs (far more likely to be supported than the
> >/proc node in a recent kernel).  It is likely at
> >/sys/bus/platform/drivers/thinkpad_acpi/cmos_command.
> >
> That directory doesn't exist for me, but I have
> /sys/bus/platform/drivers/thinkpad_acpi/thinkpad_acpi/ and a whole
> bunch of stuff under that.

Try at /sys/devices/platform/thinkpad_acpi.  If it is there, it is a more
stable node path.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Henrique de Moraes Holschuh-2
In reply to this post by Henrique de Moraes Holschuh-2
On Thu, 02 Jan 2014, Henrique de Moraes Holschuh wrote:
> The documentation for thinkpad-acpi is attached.  The hoktey_mask and other
> sysfs nodes will be somewhere under /sys/devices/platform/thinkpad_acpi/

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/laptops/thinkpad-acpi.txt

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

Yves-Alexis Perez-2
In reply to this post by Joachim Breitner-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, Jan 01, 2014 at 09:55:50PM +0100, Joachim Breitner wrote:

> Hi,
>
> Am Sonntag, den 29.12.2013, 17:29 +0100 schrieb Sandro:
> > For a while, I thought the keyboard backlight couldn't be controlled
> > through tpacpi, period. After asking a question
> > <http://askubuntu.com/questions/383501/> I got an interesting answer:
> >
> > The keyboard backlight can in fact be turned off using the following
> > command:
> > echo 0 > /sys/class/leds/tpacpi\:\:thinklight/brightness
> > It's just that it cannot be turned /on/, which is what I am trying to
> > do .
>
> this sounds as if it might not be specific to X1, but most newer
> thinkpads, as mentioned for example on
> http://unix.stackexchange.com/questions/96666/pidgin-blinklight-not-working-with-thinkpad-acpi-t430
>
> I’m looking forward to what you might find; I’d really like to be able
> to use pidgin-blinklight again (using a T430s here).

On my x230, thinklight and keyboard backlight work just fine using
Fn+space.

Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBCgAGBQJSzHREAAoJEG3bU/KmdcClaAYH/AjXdjSJa16oBoUIURZ+rbpL
jjE1SlC3pRqvtzxU/BGDTPAADXlbMSLuaAlhSGuY+cR2S5veU0uqkv0mCD50UaLd
JmKFqrhyyHllU0yX4HK5GNV77O6Szjuv6TZwTeVT/9pMp3S7xLCAmFhPiSbvLtzp
TnA05K1eBMA4BebR5LFGONaMQbkGcxUeXNjaCP0HuPdnqExtSKtyKA5uSBiljOUQ
u0BwjYUpgShtqJAD1wShy05Hq8mw/Go70xxpgAqAKdDs/Ju02X+IU6tG27IllSJo
K/teR25Lflx0bgjt2/LeuqrX6OK0tja1qiFgzV2xXqGhHvXH1nlxRHQW8dPCf3o=
=nG4Q
-----END PGP SIGNATURE-----
--
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
Reply | Threaded
Open this post in threaded view
|

Re: tpacpi bug in tpacpi::thinklight/brightness for X1 Carbon

flip
In reply to this post by Henrique de Moraes Holschuh-2
Hi,

I have the same problem on W530 which has backlight keyboard and thinklight. Pressing Fn+Space toggles between 4 different states: keyboard with low brightness, high brightness, thinklight (without keyboard backlight), and off.
I tried to do what you wrote with input-events:

root@flipc /home/flip # input-events 5
/dev/input/event5
   bustype : BUS_HOST
   vendor  : 0x17aa
   product : 0x5054
   version : 16641
   name    : "ThinkPad Extra Buttons"
   phys    : "thinkpad_acpi/input0"
   bits ev : EV_SYN EV_KEY EV_MSC EV_SW

waiting for events
13:12:44.872288: EV_MSC MSC_SCAN 17
13:12:44.872288: EV_KEY KEY_KBDILLUMTOGGLE pressed
13:12:44.872288: EV_SYN code=0 value=0
13:12:44.872305: EV_MSC MSC_SCAN 17
13:12:44.872305: EV_KEY KEY_KBDILLUMTOGGLE released
13:12:44.872305: EV_SYN code=0 value=0
13:12:47.523113: EV_MSC MSC_SCAN 17
13:12:47.523113: EV_KEY KEY_KBDILLUMTOGGLE pressed
13:12:47.523113: EV_SYN code=0 value=0
13:12:47.523126: EV_MSC MSC_SCAN 17
13:12:47.523126: EV_KEY KEY_KBDILLUMTOGGLE released
13:12:47.523126: EV_SYN code=0 value=0
13:12:49.598790: EV_MSC MSC_SCAN 17
13:12:49.598790: EV_KEY KEY_KBDILLUMTOGGLE pressed
13:12:49.598790: EV_SYN code=0 value=0
13:12:49.598803: EV_MSC MSC_SCAN 17
13:12:49.598803: EV_KEY KEY_KBDILLUMTOGGLE released
13:12:49.598803: EV_SYN code=0 value=0
13:12:52.409091: EV_MSC MSC_SCAN 17
13:12:52.409091: EV_KEY KEY_KBDILLUMTOGGLE pressed
13:12:52.409091: EV_SYN code=0 value=0
13:12:52.409103: EV_MSC MSC_SCAN 17
13:12:52.409103: EV_KEY KEY_KBDILLUMTOGGLE released
13:12:52.409103: EV_SYN code=0 value=0
timeout, quitting

I hope this helps in any way.