Am 23.04.2014 07:00, schrieb Lennart Poettering:
> On Thu, 27.03.14 23:41, Thomas Bächler (tho...@archlinux.org) wrote:
>
>> On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded.
>> It exposes a backlight device despite the lack of any physical backlight
>> devices. This fake back
On Thu, 27.03.14 23:41, Thomas Bächler (tho...@archlinux.org) wrote:
> On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded.
> It exposes a backlight device despite the lack of any physical backlight
> devices. This fake backlight device has max_brightness set to 0. Since
> the in
On Wed, Apr 2, 2014 at 8:20 PM, Thomas Bächler wrote:
> Am 27.03.2014 23:41, schrieb Thomas Bächler:
>> On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded.
>> It exposes a backlight device despite the lack of any physical backlight
>> devices. This fake backlight device has max_
Am 27.03.2014 23:41, schrieb Thomas Bächler:
> On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded.
> It exposes a backlight device despite the lack of any physical backlight
> devices. This fake backlight device has max_brightness set to 0. Since
> the introduction of the clamp_b
On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded.
It exposes a backlight device despite the lack of any physical backlight
devices. This fake backlight device has max_brightness set to 0. Since
the introduction of the clamp_brightness function, systemd-backlight
tries to write
