X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220882] New: mfd_aaeon incorrectly binds on ASUS TUF Gaming A16 (FA608UM), preventing asus_nb_wmi
Date: Sat, 20 Dec 2025 10:38:58 +0000	[thread overview]
Message-ID: <bug-220882-215701@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220882

            Bug ID: 220882
           Summary: mfd_aaeon incorrectly binds on ASUS TUF Gaming A16
                    (FA608UM), preventing asus_nb_wmi
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: preeny@gmail.com
        Regression: No

I'm not the greatest with this stuff so I'll be honest, ChatGPT was to the
rescue here.

I am running Faustus and Aurora to control keyboard backlight which worked
perfectly, until setting secureboot for a couple of games on Windows (dual
boot, separate physical drives) I had to create a MOK for Faustus so it would
load correctly.

Let me know if I can be of more help.

------------

Chatty G output:

On ASUS TUF Gaming A16 (board FA608UM), the kernel module mfd_aaeon binds early
and prevents asus_nb_wmi from loading. This causes asusd to fail with
"MissingFunction('asus-nb-wmi not found')" and breaks keyboard backlight
control
and other ASUS WMI features.

Symptoms:
- asus_nb_wmi fails with "No such device"
- asusd fails to start

This occurs regardless of Secure Boot state.
Blacklisting mfd_aaeon restores correct behavior.

Expected behavior:
asus_nb_wmi should bind to the device on this system, or mfd_aaeon should not
bind on this DMI match.

Workaround:
blacklist mfd_aaeon

-------

Hardware:

System manufacturer: ASUS
Product name: TUF Gaming A16
Board name: FA608UM

-------

$ dmesg | grep -E "aaeon|asus_nb_wmi|asus_wmi"
[    3.733678] asus_wmi: ASUS WMI generic driver loaded
[    3.738550] asus_wmi: Initialization: 0x1
[    3.738692] asus_wmi: SFUN value: 0x21
[    3.767492] asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
[   13.315905] asus_wmi: Unknown key code 0x4f

--------

$ sudo dmidecode -s system-manufacturer
sudo dmidecode -s system-product-name
sudo dmidecode -s baseboard-product-name
[sudo] password for preen:     
ASUSTeK COMPUTER INC.
ASUS TUF Gaming A16 FA608UM_FA608UM
FA608UM

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2025-12-20 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20 10:38 bugzilla-daemon [this message]
2025-12-20 12:03 ` [Bug 220882] mfd_aaeon incorrectly binds on ASUS TUF Gaming A16 (FA608UM), preventing asus_nb_wmi bugzilla-daemon

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=bug-220882-215701@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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