Re: [Bug 221437] New: asus-wmi: gpu_fan RPM reads 0 on M6500XV when dGPU has no driver (fan physically spinning)

[Denis Benato]

On 6/12/26 05:37, Borislav Petkov wrote:
> Forwarding to mail...
>
> On Thu, Apr 30, 2026 at 01:39:35AM +0000, bugzilla-daemon@xxxxxxxxxx wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=221437
>>
>>             Bug ID: 221437
>>            Summary: asus-wmi: gpu_fan RPM reads 0 on M6500XV when dGPU has
>>                     no driver (fan physically spinning)
>>            Product: Platform Specific/Hardware
>>            Version: 2.5
>>           Hardware: All
>>                 OS: Linux
>>             Status: NEW
>>           Severity: normal
>>           Priority: P3
>>          Component: x86-64
>>           Assignee: platform_x86_64@xxxxxxxxxxxxxxxxxxxx
>>           Reporter: nix.sasl@xxxxxxxxx
>>         Regression: No
>>
>> Summary of the issue:
>> On ASUS Vivobook M6500XV with dGPU (RTX 4060) running without a driver
>> (D3cold), the GPU fan physically spins under load but fan2_input always reads 0
>> RPM. Writing to pwm2_enable fails with EIO.
>>
>> Hardware:
>> Product: Vivobook_ASUSLaptop M6500XV_M6500XV
>> Board:   M6500XV
>> BIOS:    M6500XV.309
>> Kernel:  7.0.2-arch1-1
>> linux-firmware-git: 20260429.56a13f98-1
>> Relevant dmesg:
>> asus_wmi: BIOS WMI version: 9.4
>> asus_wmi: SFUN value: 0x21
>> asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
>> asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
>> asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
>>
>> Findings:
>>
>> fan2_input always 0 even when fan is physically spinning
>> pwm2_enable node exists in sysfs but writes fail with EIO
>> asus-ec-sensors rejects hardware with ENODEV
>> ec_sys accessible but dump returns all zeros (interrupt-driven EC mode)
>> dev_id reads 0x00000000
>>
>> Expected behavior: fan2_input should report actual GPU fan RPM.
>>
>> -- 
>> You may reply to this email to add a comment.
>>
>> You are receiving this mail because:
>> You are watching the assignee of the bug.
Hi!

This is because new models use EC shared memory and this driver cannot
handle those models at all.

In the asus-linux Discord (now ogc) you will find someone writing a driver
for these devices in case you want to help, otherwise your best bet is to wait
for the new driver or try to decompile the official windows application
and get the correct EC memory offsets.

Best regards,
Denis