[gentoo-user] Asus laptop & brightness keys

[gentoo-user] Asus laptop & brightness keys

[Emmanuel Vasilakis]

Hi!

I got a new Asus Zenbook laptop, with a ryzen 4500U processor. Most 
things run great, except those brightness keys!

Nothing is reported when pressing them, either with showkeys or 
acpi_listen, so I can't bind them to a shortcut. Brightness by changing 
the value in /sys/class/backlight/amdgpu_b10/brightness works fine.

I have asus_wmi and asus_nb_wmi modules loaded, so things like 
multitouch pad and keyboard backlight work fine.

I'm running a 5.10.27 gentoo sources kernel. Most people on the net say 
that using the 'acpi_osi= ' parameter fixes it, but in my case it just 
hangs at kernel boot. Did try e.g. acpi_osi=Linux, but nothing changed.

At the same time, using a live Manjaro usb both brightness keys work 
fine, and they are usable under Gnome.

I'm sure I'm missing something in my kernel configuration.... Any ideas?

Thanks!

Re: [gentoo-user] Asus laptop & brightness keys

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Saturday, 15 May 2021 11:46:46 BST Emmanuel Vasilakis wrote:
> Hi!
> 
> I got a new Asus Zenbook laptop, with a ryzen 4500U processor. Most
> things run great, except those brightness keys!
> 
> Nothing is reported when pressing them, either with showkeys or
> acpi_listen, so I can't bind them to a shortcut. Brightness by changing
> the value in /sys/class/backlight/amdgpu_b10/brightness works fine.
> 
> I have asus_wmi and asus_nb_wmi modules loaded, so things like
> multitouch pad and keyboard backlight work fine.
> 
> I'm running a 5.10.27 gentoo sources kernel. Most people on the net say
> that using the 'acpi_osi= ' parameter fixes it, but in my case it just
> hangs at kernel boot. Did try e.g. acpi_osi=Linux, but nothing changed.
> 
> At the same time, using a live Manjaro usb both brightness keys work
> fine, and they are usable under Gnome.
> 
> I'm sure I'm missing something in my kernel configuration.... Any ideas?
> 
> Thanks!

Assuming the Manjaro Live-USB is running the same version of kernel/modules 
and firmware, then it is worth checking /proc/config.gz for the running 
kernel's configuration and comparing it with your gentoo configuration.

Also while you're there you could check with lsmod what modules were loaded by 
the Manjaro kernel to see if you're missing something.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Asus laptop & brightness keys

[Emmanuel Vasilakis]

On 15/05/2021 14:12, Michael wrote:
> On Saturday, 15 May 2021 11:46:46 BST Emmanuel Vasilakis wrote:
>> Hi!
>>
>> I got a new Asus Zenbook laptop, with a ryzen 4500U processor. Most
>> things run great, except those brightness keys!
>>
>> Nothing is reported when pressing them, either with showkeys or
>> acpi_listen, so I can't bind them to a shortcut. Brightness by changing
>> the value in /sys/class/backlight/amdgpu_b10/brightness works fine.
>>
>> I have asus_wmi and asus_nb_wmi modules loaded, so things like
>> multitouch pad and keyboard backlight work fine.
>>
>> I'm running a 5.10.27 gentoo sources kernel. Most people on the net say
>> that using the 'acpi_osi= ' parameter fixes it, but in my case it just
>> hangs at kernel boot. Did try e.g. acpi_osi=Linux, but nothing changed.
>>
>> At the same time, using a live Manjaro usb both brightness keys work
>> fine, and they are usable under Gnome.
>>
>> I'm sure I'm missing something in my kernel configuration.... Any ideas?
>>
>> Thanks!
> 
> Assuming the Manjaro Live-USB is running the same version of kernel/modules
> and firmware, then it is worth checking /proc/config.gz for the running
> kernel's configuration and comparing it with your gentoo configuration.
> 
> Also while you're there you could check with lsmod what modules were loaded by
> the Manjaro kernel to see if you're missing something.
> 

Ah, I had gone through that! Looked at almost line by line the two 
dmesg, lsmod, configs etc. Of course Manjaro's config is .... big!

Turns out there was something in ACPI page of kernel config that did the 
trick (not sure what exactly to be honest - might be Video).

Thanks though!