supergfxctl fails to detect a perfectly working RTX 4050 on ASUS Laptop
Hello! I'm reporting a bug where supergfxctl -s only returns [Integrated] on my ASUS laptop, even though the Nvidia driver is loading and initializing perfectly.
Diagnostics Summary:
Hardware: ASUS Laptop, Ryzen 7 7435HS, NVIDIA RTX 4050 (detected by BIOS & lspci).
Kernel Args: nvidia-drm.modeset=1 and nouveau blacklisting are correctly set in /proc/cmdline.
dmesg log: My dmesg shows the nvidia driver (version 580.82.07) loading and initializing successfully with no errors at all.
The Bug: Despite the driver working perfectly at the kernel level, the user-space tools (supergfxctl, asusd) do not detect the dGPU.
This appears to be a bug within supergfxctl/asusctl rather than a driver or system configuration issue.
Logs: https://paste.centos.org/view/43323e40
Device Info: https://paste.centos.org/view/9002ec15
Thank you for your hard work on this project. Let me know if I can provide any more information to help debug this.
UPDATE: I tried to perform an rpm-ostree rollback to a previous working state, but my deployment history shows that my current and previous deployments are identical (Version 42.20250903). This means I cannot roll back to an older OS version to test. The issue may have started when this version was installed.
Diagnostics Summary:
Hardware: ASUS Laptop, Ryzen 7 7435HS, NVIDIA RTX 4050 (detected by BIOS & lspci).
Kernel Args: nvidia-drm.modeset=1 and nouveau blacklisting are correctly set in /proc/cmdline.
dmesg log: My dmesg shows the nvidia driver (version 580.82.07) loading and initializing successfully with no errors at all.
The Bug: Despite the driver working perfectly at the kernel level, the user-space tools (supergfxctl, asusd) do not detect the dGPU.
This appears to be a bug within supergfxctl/asusctl rather than a driver or system configuration issue.
Logs: https://paste.centos.org/view/43323e40
Device Info: https://paste.centos.org/view/9002ec15
Thank you for your hard work on this project. Let me know if I can provide any more information to help debug this.
UPDATE: I tried to perform an rpm-ostree rollback to a previous working state, but my deployment history shows that my current and previous deployments are identical (Version 42.20250903). This means I cannot roll back to an older OS version to test. The issue may have started when this version was installed.
