Few days ago I discovered wakeup from sleep is working on my laptop. Earlier, only black screen with blinking cursor is displayed.
It works on kernel 7.0.9-2-default. I update kernel to 7.0.10 and have need to test it again (more use cases, like watching video on FF) and discovered wakeup from sleep do not work again (the same effect with black screen).
How to gather info and report this bug?
Black screen with blinking cursor might be a sign for a graphic driver issues.
inxi -GSaz
There are also reports for black screen after suspend:
https://bugzilla.opensuse.org/show_bug.cgi?id=1264698
inxi -GSaz
System:
Kernel: 7.0.10-2-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: hpet avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-7.0.10-2-default
root=UUID=589e5f7b-afcf-4539-b4f5-f76f2363e243 splash=silent
systemd.show_status=yes quiet security=apparmor
rd.driver.blacklist=nouveau psi=1 rd.shell=0 mitigations=auto
Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A info: frameworks v: 6.26.0
wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
Tumbleweed 20260527
Graphics:
Device-1: NVIDIA GP107M [GeForce MX350] vendor: ASUSTeK driver: nvidia
v: 580.159.03 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
chip-ID: 10de:1c96 class-ID: 0302
Device-2: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series /
Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5
code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1,eDP-1 empty: none bus-ID: 04:00.0
chip-ID: 1002:1636 class-ID: 0300 temp: 86.0 C
Device-3: IMC Networks USB2.0 HD IR UVC WebCam driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2 chip-ID: 13d3:56cb
class-ID: 0e02 serial: <filter>
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.11
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: vesa alternate: fbdev,nouveau,nv dri: radeonsi gpu: amdgpu
d-rect: 4480x1440 display-ID: 0
Monitor-1: HDMI-A-1 pos: right model: Idek Iiyama PL2770QS
serial: <filter> built: 2023 res: mode: 2560x1440 hz: 144 scale: 100% (1)
dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 640x480
Monitor-2: eDP-1 pos: primary,left model: BOE Display 0x07d8 built: 2018
res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 1 drv: nvidia-drm device: 2 drv: radeonsi device: 3
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: amd mesa v: 26.1.0 glx-v: 1.4
direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
3.64 7.0.10-2-default) device-ID: 1002:1636 memory: 500 MiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.4.350 layers: 8 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 26.1.0
device-ID: 1002:1636 surfaces: N/A device: 1 type: discrete-gpu
name: NVIDIA GeForce MX350 driver: nvidia v: 580.159.03
device-ID: 10de:1c96 surfaces: N/A device: 2 type: cpu name: llvmpipe
(LLVM 22.1.5 256 bits) driver: mesa llvmpipe v: 26.1.0 (LLVM 22.1.5)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Because I have hardware that is related to this topic I decided to compile kernels using git bisect and understand, which commit made problems. Any advice on what I should take a look? Is there any dangerous case, which I should avoid? Are there any descriptions, which patch requires which other patch? How long kernel is compiling?
I today updated to kernel 7.0.12-1-default. Mok asks to add (hash?) of nvidia kernel module. Sleep/Wakeup works, but nvidia-smi respond:
~> nvidia-smi
NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.`
I wonder, what did the trick?
It seems nvidia driver cause problems. But why it is not loaded? Mok asks me for password to import certificate or hash.
But we have probably reason wakup did not work. What to do next?
I need a way to sign nvidia-modules. Once type modprobe nvidia, I got key rejected by service, but when I type:
> mokutil -i /usr/share/nvidia-pubkeys/MOK-nvidia-driver-G06-580.159.03-60.1-default.der
SKIP: /usr/share/nvidia-pubkeys/MOK-nvidia-driver-G06-580.159.03-60.1-default.der is already enrolled
Show your installed packages.
zypper se -si nvidia
Force the reinstallation of the kmp package.
Enroll the Key in the MOK screen.
Tumbleweed is at kernel 7.1.2 now?
I use the cuda repository, so did force the re-install of the nvidia kmp (610.43.02) to ensure it rebuilt for the running kernel (as indicated by @hui)
Sorry for write in this thread.
I do sudo zypper dup --force kernel-default nvidia-driver-G06-kmp-default . Everything works well, but after reboot, there only one kernel inside /boot and it is 7.0.12 .
> rpm -qi nvidia-driver-G06-kmp-default
Name : nvidia-driver-G06-kmp-default
Version : 580.159.03_k7.0.12_1
Release : 60.1
Architecture: x86_64
Install Date: sob, 4 lip 2026, 16:04:10
Group : System/Kernel
Size : 277413863
License : SUSE-NonFree
Signature : RSA/SHA512, wto, 23 cze 2026, 20:33:10, Key ID b1d0d788db27fd5a
Source RPM : nvidia-driver-G06-580.159.03-60.1.nosrc.rpm
Build Date : pon, 22 cze 2026, 12:54:00
Build Host : reproducible
Vendor : obs://build.suse.de/Proprietary:X11:Drivers
URL : https://www.nvidia.com/object/unix.html
Summary : NVIDIA graphics driver kernel module for GeForce 700 series and newer
Description :
This package provides the closed-source NVIDIA graphics driver kernel
module for GeForce 700 series and newer GPUs.
Distribution: Proprietary:X11:Drivers / openSUSE_Tumbleweed
slawomir@opensuse:~> rpm -qi kernel-default
Name : kernel-default
Version : 7.0.12
Release : 1.1
Architecture: x86_64
Install Date: pon, 29 cze 2026, 11:13:56
Group : System/Kernel
Size : 219908518
License : GPL-2.0-only
Signature : RSA/SHA512, pią, 12 cze 2026, 20:35:42, Key ID 35a2f86e29b700a4
Source RPM : kernel-default-7.0.12-1.1.nosrc.rpm
Build Date : śro, 10 cze 2026, 07:06:17
Build Host : reproducible
Packager : https://bugs.opensuse.org
Vendor : openSUSE
URL : https://www.kernel.org/
Summary : The Standard Kernel
Description :
The standard kernel for both uniprocessor and multiprocessor systems.
Source Timestamp: 2026-06-10 05:12:39 +0000
GIT Revision: 8beab0b488b42c3b23259067bfa850985d902846
GIT Branch: stable
Distribution: openSUSE Tumbleweed
Name : kernel-default
Version : 7.1.2
Release : 1.1
Architecture: x86_64
Install Date: sob, 4 lip 2026, 16:03:45
Group : System/Kernel
Size : 220763679
License : GPL-2.0-only
Signature : RSA/SHA512, czw, 2 lip 2026, 21:29:45, Key ID 35a2f86e29b700a4
Source RPM : kernel-default-7.1.2-1.1.nosrc.rpm
Build Date : czw, 2 lip 2026, 07:05:55
Build Host : reproducible
Packager : https://bugs.opensuse.org
Vendor : openSUSE
URL : https://www.kernel.org/
Summary : The Standard Kernel
Description :
The standard kernel for both uniprocessor and multiprocessor systems.
Source Timestamp: 2026-07-02 05:05:55 +0000
GIT Revision: 992f18cb95b845e627c10687648dd04f93f18720
GIT Branch: stable
Distribution: openSUSE Tumbleweed
You need to check at the grub menu and ensure your booting to the new 7.1.2 kernel, then once booted to the new kernel, then force the re-install.
Thanks.
I reinstall my system one week (maybe) ago. It now uses systemd-boot. I see there are directories like:
# ls /boot/efi/opensuse-tumbleweed/
7.0.12-1-default 7.1.2-1-default
But 7.0.12-1-default contain kernel and initrd and 7.1.2.1-default is empty. Also, inside /boot there are only 7.0.12-1 kernel.
I do: zypper remove kernel-default-7.1.2-1 and zypper in kernel-default-7.1.2-1 . I got message explaining everything: ERROR: No free space in /boot/efi for new kernel
. So should I create additional efi partition?
So you did not prepare for systemd-boot… needs ~2-4GB, maybe 1GB will suffice…
lsblk -f /dev/sda1
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda1 vfat FAT32 ESP 4FEA-283B 3.5G 11% /boot/efi
du -sh /boot/efi
470M /boot/efi
Parition is old. It has 256 MiB . So - use GRUB2?
Well you could switch back, or since it’s a fresh install, re-install and prepare a bigger partition. Then if/when grub2 disappears you won’t need to re-install or fix…
Yast2-bootloader says switching from systemd-boot to grub2 is not supportred.
I see:
system plików rozm. użyte dost. %uż. zamont. na
/dev/nvme0n1p4 90G 17G 73G 20% /
devtmpfs 7,4G 8,0K 7,4G 1% /dev
tmpfs 7,6G 4,0K 7,6G 1% /dev/shm
efivarfs 128K 88K 36K 72% /sys/firmware/efi/efivars
tmpfs 3,1G 2,1M 3,1G 1% /run
none 1,0M 0 1,0M 0% /run/credentials/systemd-journald.service
/dev/nvme0n1p4 90G 17G 73G 20% /.snapshots
/dev/nvme0n1p4 90G 17G 73G 20% /root
/dev/nvme0n1p4 90G 17G 73G 20% /opt
/dev/nvme0n1p4 90G 17G 73G 20% /srv
/dev/nvme0n1p3 41G 14G 27G 35% /mnt/DockerAndVM
tmpfs 7,6G 36K 7,6G 1% /tmp
/dev/nvme0n1p4 90G 17G 73G 20% /usr/local
/dev/nvme0n1p4 90G 17G 73G 20% /var
/dev/nvme0n1p1 256M 5,1M 251M 2% /boot/efi
/dev/nvme0n1p6 809G 713G 97G 89% /home
none 1,0M 0 1,0M 0% /run/credentials/getty@tty1.service
tmpfs 1,6G 92K 1,6G 1% /run/user/1000
/dev/mmcblk0p1 938G 867G 24G 98% /run/media/slawomir/53b4e8b6-f0c1-4976-b395-ae8618d9f262
There exist 27G inside /mnt/DockerAndVM. I backup data on this partition. Does Btrfs allow to change size of partition, so I do not have to format it? How many space give to new EFI partition?
Yes you can, but this only changes the filesystem, NOT the partition. Maybe gparted would work when booted from a live USB rescue system.
I destroy my system and must reinstall. GParted correctly shrink btrfs filesystem and create EFI partition. I set it is EFI using Yast-Partitioner, as I remember. But, before this, I remove move some files (I think it was old files) form /boot/efi. After use partitioning, I copy rest of files to new EFI, remove efi flag from old FS, to some think and reboot. And it does not boot. Empty systems/kernel list. I uses chroot from LiveCD, trying to repair and nothing. I boot my installed system using grub2 from LiveCD, everything worked, try to repair. Kernel list exists, but it would not boot. It complains about it cannot apply kernel variables. No matter, what I do, same effect. So I reinstall system.
With Nvidia modules, it would not wake up. I also do: systemctl enable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service , but this not give effect.
Which kernel modules blacklist to ensure it is caused by nvidia"
@Lachu Hard to say, I know my Nvidia systems here will suspend to ram, no hibernation as they use secure boot.