Asus Vivobook Pro 15 (Core Ultra 7 / RTX 3050): Suspend "Coma" & Unable to Load Proprietary Nvidia Driver on F43 (Kernel 6.17)

Ask Fedora
,
1

Hardware:

  • Model: Asus Vivobook 15 Pro Q533mj

  • CPU: Intel Core Ultra 7 155H (Meteor Lake)

  • GPU: Nvidia RTX 3050 (Laptop) + Intel Arc Graphics

  • RAM: 40 GB

  • OS: Fedora 43 (Rawhide)

  • Kernel: 6.17.12-300.fc43.x86_64

The Issue:

I am experiencing a hard system freeze when suspending (closing the lid).

  1. I close the lid.

  2. The laptop enters sleep.

  3. When I open the lid to resume, the screen remains black.

  4. Diagnostic: If I toggle the Caps Lock key, the LED turns on and off (suggesting the kernel is alive), but the screen never wakes, and the system eventually becomes totally unresponsive, requiring a hard power button reset.

Current State & Diagnostics:

My system seems stuck using the Nvidia Open Kernel Module, which I suspect is the cause of the suspend crash on this hardware. I have been unable to successfully switch to the proprietary driver despite multiple attempts.

1. Nvidia License Check (Confirms Open Driver active):

$ modinfo -F license nvidia
Dual MIT/GPL

2. Sleep Mode:

$ cat /sys/power/mem_sleep
[s2idle] deep

3. Current GRUB Config:

GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 pcie_aspm=off"
  1. LSPCI
0000:00:00.0 Host bridge: Intel Corporation Meteor Lake-H 6p+8e cores Host Bridge/DRAM Controller (rev 04)
0000:00:01.0 PCI bridge: Intel Corporation Meteor Lake-H PCIe Root Port #12 (rev 10)
0000:00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Arc Graphics] (rev 08)
0000:00:04.0 Signal processing controller: Intel Corporation Meteor Lake-P Dynamic Tuning Technology (rev 04)
0000:00:07.0 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 10)
0000:00:08.0 System peripheral: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator (rev 20)
0000:00:0a.0 Signal processing controller: Intel Corporation Meteor Lake-P Platform Monitoring Technology (rev 01)
0000:00:0b.0 Processing accelerators: Intel Corporation Meteor Lake NPU (rev 04)
0000:00:0d.0 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller (rev 10)
0000:00:0d.2 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0 (rev 10)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
0000:00:12.0 Serial controller: Intel Corporation Meteor Lake-P Integrated Sensor Hub (rev 20)
0000:00:14.0 USB controller: Intel Corporation Meteor Lake-P USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
0000:00:14.2 RAM memory: Intel Corporation Meteor Lake-H/U Shared SRAM (rev 20)
0000:00:15.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #0 (rev 20)
0000:00:15.1 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #1 (rev 20)
0000:00:16.0 Communication controller: Intel Corporation Meteor Lake-P CSME HECI #1 (rev 20)
0000:00:19.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #4 (rev 20)
0000:00:1c.0 PCI bridge: Intel Corporation Device 7e3e (rev 20)
0000:00:1c.7 PCI bridge: Intel Corporation Meteor Lake-H/U PCIe Root Port #8 (rev 20)
0000:00:1f.0 ISA bridge: Intel Corporation Meteor Lake-H eSPI Controller (rev 20)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Meteor Lake-P HD Audio Controller (rev 20)
0000:00:1f.4 SMBus: Intel Corporation Meteor Lake-P SMBus Controller (rev 20)
0000:00:1f.5 Serial bus controller: Intel Corporation Meteor Lake-P SPI Controller (rev 20)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA107BM / GN20-P0-R-K2 [GeForce RTX 3050 6GB Laptop GPU] (rev a1)
0000:01:00.1 Audio device: NVIDIA Corporation GA107 High Definition Audio Controller (rev a1)
0000:2c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
0000:2d:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)
10000:e0:06.0 System peripheral: Intel Corporation RST VMD Managed Controller
10000:e0:06.2 PCI bridge: Intel Corporation Device 7ecb (rev 10)
10000:e1:00.0 Non-Volatile memory controller: Micron Technology Inc 2400 NVMe SSD (DRAM-less) (rev 03)

What I Have Tried:

  1. Driver Installation: I have the RPMFusion Non-Free repositories enabled and installed akmod-nvidia, xorg-x11-drv-nvidia-cuda, and kernel-devel.

  2. Forced Rebuild: I ran sudo akmods --force and sudo dracut --force.

  3. Secure Boot: I have disabled Secure Boot in the BIOS to rule out signing issues.

  4. Kernel Parameters: tried pcie_aspm=off (to fix Meteor Lake bus lockups) and nvidia-drm.modeset=1.

The Question:

It seems that despite installing akmod-nvidia, the system persists in loading the Open Kernel module (Dual MIT/GPL), which is unstable for suspend on the RTX 3050.

Is there a known incompatibility with Kernel 6.17 (Rawhide) preventing the proprietary driver from building/loading? Or is there a specific step required for Meteor Lake/Asus devices to force the proprietary driver over the open module?

Any guidance on debugging the akmods build failure or stabilizing the Open Driver for suspend would be appreciated.

4

I think that akmods (akmod-nvidia) does not fail, but choose to use the Open Kernel module
if it sees that your card supports it. I don’t see if one can force akmods to not do that.

Ref: Howto/NVIDIA Kernel Open

In addition you may perhaps enable the nvidia-{suspend,resume,hibernate} services.
Ref: Howto/NVIDIA Suspend

5

It should work w/o nvidia-drm.modeset=1 pcie_aspm=off

You could try to use the deep (old style S3 ) instead of s2idle

Can you switch to a text console? CTRL + ALT + F3

You could also try the new 590.48.01 drivers available in the rawhide repos.

6

See perhaps also: NVIDIA GPU - Failure to suspend

7

I found this post on reddit:

Try thus the following:

  • set the two flags by security
  • calling dracut is not necessary I think
  • akmods --force is not needed
sudo sh -c '(echo %_with_kmod_nvidia_open 0; echo %_without_kmod_nvidia_detect 1) > /etc/rpm/macros.nvidia-kmod'

sudo akmods --rebuild --akmod nvidia

Notes:

  • those flags are still used in the nvidia-kmod.spec file one found in
    /usr/src/akmods/nvidia-kmod-580.119.02-1.fc42.src.rpm
  • this post says that this used to be documented in the rpmfusion Howto/NVIDIA
    but not any more