** Description changed:

  SUMMARY
  After suspending the laptop (via systemctl suspend or lid close) and
  resuming, the internal display never comes back on. The system is
  otherwise fully functional — confirmed via SSH that networking, the
  GNOME session, and the GPU are all alive and responsive. The backlight
  is physically on, but no image is displayed. Only a hard reboot
  recovers the display.
  
  HARDWARE
  - Laptop: Lenovo LOQ
  - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04)
  - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1),
-   hybrid/Optimus graphics
+   hybrid/Optimus graphics
  - Secure Boot: enabled
  
  SOFTWARE
  - Ubuntu 26.04 LTS (Resolute Raccoon)
  - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic)
  - Display server: Wayland, GNOME Shell (mutter 50.1), GDM
  - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1
  - PRIME mode: on-demand (default)
  
  STEPS TO REPRODUCE
  1. Boot normally (panel works fine).
  2. Suspend: `systemctl suspend`, or close the lid.
  3. Wake the system (open lid / press a key).
  
  EXPECTED
  Panel lights up and shows the lock screen / desktop, same as after a
  normal cold boot.
  
  ACTUAL
  Screen stays completely black. Backlight is on (confirmed via
  /sys/class/backlight/*/actual_brightness). The rest of the system is
  fully alive: SSH'd in and confirmed networking, GNOME session, and
  GPU are all responsive; `nvidia-smi` works; gnome-shell process is
  running normally.
  
  ROOT CAUSE (as far as I could trace it)
  Every single boot — cold or resumed — logs this i915 message:
  
-   i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to
-   retrieve link info, disabling eDP
+   i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to
+   retrieve link info, disabling eDP
  
  On a cold boot, i915 evidently recovers from this before GDM starts,
  and the panel works normally. After an S3 resume, it does NOT
  recover: I confirmed via /sys/class/drm/ that the real internal panel
  connector never comes back under the i915 (or nvidia-drm) device —
  instead, `card0` remains bound to the `simple-framebuffer` driver
  (the generic EFI/firmware fallback framebuffer), which is what
  continues to "own" the panel indefinitely, with no active KMS
  scanout ever taking over. This matches the visible symptom exactly:
  the panel is electrically powered (backlight on) but nothing is
  being drawn to it because no real GPU driver has claimed the output.
  
  WHAT I'VE RULED OUT
  - NVIDIA/PRIME as the cause: reproduced identically with
-   `sudo prime-select intel` (NVIDIA driver fully unloaded,
-   `nvidia-smi` returning "couldn't communicate with the NVIDIA
-   driver"). Bug persists with NVIDIA completely out of the picture,
-   so this is purely an i915/Intel-side issue.
+   `sudo prime-select intel` (NVIDIA driver fully unloaded,
+   `nvidia-smi` returning "couldn't communicate with the NVIDIA
+   driver"). Bug persists with NVIDIA completely out of the picture,
+   so this is purely an i915/Intel-side issue.
  - Panel power-saving states: tried `i915.enable_psr=0
-   i915.enable_dc=0` kernel parameters — no change in behavior.
+   i915.enable_dc=0` kernel parameters — no change in behavior.
  - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no
-   kernel oops/BUG in dmesg around the resume window. The kernel and
-   compositor both report healthy state; the panel output is just
-   never actually reclaimed from simple-framebuffer.
+   kernel oops/BUG in dmesg around the resume window. The kernel and
+   compositor both report healthy state; the panel output is just
+   never actually reclaimed from simple-framebuffer.
  
  ADDITIONAL NOTES
  - Suspend mode in use is real S3 ("deep"), not s2idle
-   (/sys/power/mem_sleep shows "s2idle [deep]").
+   (/sys/power/mem_sleep shows "s2idle [deep]").
  - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1`
-   did not recover the panel.
+   did not recover the panel.
  - Will attach dmesg output spanning a full suspend/resume cycle.
  
- 
  Note: I found this to be the same issue in latest Fedora and CachyOS
- 
- Note: I'm not very technical on this (LLMs helped with this) and I'll
- really appreciate the support on this, thanks in advance.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 26.04
  Package: linux-image-7.0.0-27-generic 7.0.0-27.27
  ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6
  Uname: Linux 7.0.0-27-generic x86_64
  ApportVersion: 2.34.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USER        PID ACCESS COMMAND
-  /dev/snd/controlC2:  zizo       4608 F.... wireplumber
-  /dev/snd/controlC0:  zizo       4608 F.... wireplumber
-  /dev/snd/controlC1:  zizo       4608 F.... wireplumber
-  /dev/snd/seq:        zizo       4587 F.... pipewire
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC2:  zizo       4608 F.... wireplumber
+  /dev/snd/controlC0:  zizo       4608 F.... wireplumber
+  /dev/snd/controlC1:  zizo       4608 F.... wireplumber
+  /dev/snd/seq:        zizo       4587 F.... pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 17:07:28 2026
  InstallationDate: Installed on 2026-06-20 (14 days ago)
  InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 
(20260423.1)
  MachineType: LENOVO 83JE
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=<set>
  ProcFB: 0 nvidia-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic 
root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash 
i915.enable_psr=0 i915.enable_dc=0 
lsm=capability,landlock,yama,apparmor,ima,evm 
resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2025
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R3CN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LOQ 15IRX10
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10:
  dmi.product.family: LOQ 15IRX10
  dmi.product.name: 83JE
  dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10
  dmi.product.version: LOQ 15IRX10
  dmi.sys.vendor: LENOVO

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2159568

Title:
  [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black
  after suspend/resume (S3) — i915 eDP link fails to recover, unlike on
  cold boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159568/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to