From: Harvey <harv@gmx.de>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: Jonathan Woithe <jwoithe@just42.net>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Kernel error messages: leds fujitsu::radio_led: Setting an LED's brightness failed
Date: Wed, 25 Oct 2017 15:17:56 +0200 [thread overview]
Message-ID: <7af5f592-df89-fd9d-916c-2e7bf941cf1f@gmx.de> (raw)
In-Reply-To: <20171025043957.GA13202@kmp-mobile.hq.kempniu.pl>
[-- Attachment #1.1: Type: text/plain, Size: 1376 bytes --]
Am 25.10.2017 um 06:39 schrieb Michał Kępień:
>>> - Investigating the E LED. This requires taking a look at the DSDT
>>> dump from your laptop and searching for clues as to how this LED is
>>> handled. I will be happy to do that, but again, no promises about
>>> how much time it will take. (And given the nature of this task, I
>>> cannot promise I will find anything reasonable at all. I also might
>>> ask you to do some further experiments as I do not have an E751
>>> myself.)
>
> I feel stupid for only suggesting this now, but can this simply be the
> eco LED? The DSDT dump from your laptop suggests so, as well as the
> description of the E LED in the manual. Have you tried playing around
> with /sys/class/leds/fujitsu::eco_led?
No, I haven't.
I tried to set brightness to 255 and back to 0:
[root@gruenix ~]# echo 255 >/sys/class/leds/fujitsu::eco_led/brightness
=> eco LED lights up!
[root@gruenix ~]# cat /sys/class/leds/fujitsu::eco_led/brightness
=> eco LED off!
Tadaaa!
So yes, this is the eco LED of my E751.
>> Don't forget to take a look at the I LED...
>
> I could not find anything in the DSDT dump from your laptop that would
> suggest this LED can be controlled using ACPI.
>
Greetings
Harvey
--
I am root. If you see me laughing, you'd better have a backup!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2017-10-25 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fede7169-e944-3ca8-8b8d-e17a95b8dcfe@gmx.de>
2017-07-20 6:42 ` Michał Kępień
2017-07-23 6:14 ` Jonathan Woithe
2017-07-25 12:14 ` Harvey
2017-08-01 7:53 ` Harvey
2017-08-03 10:21 ` Harvey
2017-08-04 6:13 ` Michał Kępień
2017-08-04 8:55 ` Harvey
2017-10-25 4:39 ` Michał Kępień
2017-10-25 13:17 ` Harvey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7af5f592-df89-fd9d-916c-2e7bf941cf1f@gmx.de \
--to=harv@gmx.de \
--cc=jwoithe@just42.net \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®