linux-kernel - Re: PROBLEM: asus_nb_wmi sends KEY_BRIGHTNESSDOWN on pressing CAPS Lock and PrntScrn on Zenbook S 13 UX5304VA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <fc826113b0fdb26e99e9e1f3faa84db327a19035@dividebyzero.it>
Date:   Mon, 04 Dec 2023 15:52:26 +0000
From:   juri@...idebyzero.it
To:     "Hans de Goede" <hdegoede@...hat.com>,
        "James John" <me@...jajo.com>,
        "Corentin Chary" <corentin.chary@...il.com>,
        "Ilpo Järvinen" <ilpo.jarvinen@...ux.intel.com>,
        "Mark Gross" <markgross@...nel.org>
Cc:     platform-driver-x86@...r.kernel.org,
        acpi4asus-user@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: asus_nb_wmi sends KEY_BRIGHTNESSDOWN on pressing CAPS 
 Lock and PrntScrn on Zenbook S 13 UX5304VA

Thank you for the reply.

December 4, 2023 at 14:54, "Hans de Goede" <hdegoede@...hat.com> wrote:

> 
> Ok, that is good to know. Is there any specific reason why you are passing
>  "acpi_osi=!Windows 2012" on the kernel commandline?
>  
>  Generally speaking passing any other kernel arguments then those used
>  to specify the root filesystem and things like "quiet" is not advisable.
>  
>  Everything should just work without passing any special options and if things
>  do not work without special options then that is a bug which needs to be fixed.
>  
>  Regards,
>  
>  hans
> 

Honestly I don't remember the exact reason, but I had it since the beginning, possibly due to not working hotkeys.
I removed it now, and everything seems to be working without any issue, other that now the brightness is no longer being controlled by the EC and cannot be adjusted outside of a graphical interface.
I'm going to keep it like this, I'll let you know if any issue should arise.

As for the other cmdline arguments (which I had quite too many) I realized that the only non-standard one I really need is `nouveau.modeset=0`, without which the driver - and sometimes the whole system - hangs (as this laptop has an old NVidia GPU I don't use but keep always disabled).
Do you suggest opening another thread regarding that on this mailing list, or should it be better somewhere else?

Regards,

Juri