After upgrading from kernel 6.14 to 6.16 on Fedora 42, the screen did not turn on?

Ask Fedora
1

i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error

My notebook hardware includes an Intel Ultra 9 275 HX GPU and an NVIDIA RTX 5070 Ti. It boots with the iGPU at startup, and everything works fine with 6.14 with drivers functioning properly. However, after upgrading to 6.16, there seems to be a kernel issue affecting the iGPU. I will provide the system log files attached and below. What exactly is the problem, how can it be fixed, or how can I help the Fedora team to resolve this kernel issue? I saw an error with the following title: fedora kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error

errors:

journalctl -b -1 -p err
fedora kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error

fedora kernel: intel_pmc_core INT33A1:00: pmc_core: couldn’t get DMU telem endpoint -
fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [_TZ.ETMD], AE_NOT_FOUND (20250404/psargs-332)

fedora kernel: ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20250404/psparse-529)

fedora kernel: btrfs: Unknown parameter ‘errors’

fedora kernel: i915 0000:00:02.0: [drm] Found meteorlake (device ID 7d67) integrated display version 14.00 stepping D0

fedora kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access

fedora kernel: i915 0000:00:02.0: vgaarb: deactivate vga console

fedora kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages

fedora kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem

fedora kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.23)

fedora kernel: i915 0000:00:02.0: [drm] [CONNECTOR:262:eDP-1] Panel is missing HDR static metadata. Possible support for Intel HDR backlight interface is not used.If your backlight controls don’t work try booting with i915.enable_dpcd_backlight=3.

fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.44.1

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC: submission enabled

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC: SLPC enabled

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC: RC enabled

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.44.1

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear media

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC: submission enabled

Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC: SLPC enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC: RC enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initializedAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll errorAğu 29 20:22:07 fedora kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1Ağu 29 20:22:07 fedora kernel: fbcon: i915drmfb (fb0) is primary deviceAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer deviceAğu 29 20:22:09 fedora kernel: i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)Ağu 29 20:22:09 fedora kernel: i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloadsAğu 29 20:22:09 fedora kernel: mei_gsc_proxy 0000:00:16.0-07f3db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915])Ağu 29 20:22:10 fedora kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915])Ağu 29 20:22:25 fedora gnome-shell[2648]: Added device ‘/dev/dri/card1’ (i915) using atomic mode setting.


Eyl 06 04:41:24 fedora kernel:Eyl 06 04:41:29 fedora gdm-autologin][17248]: gkr-pam: couldn’t unlock the login keyring.Eyl 06 04:42:30 fedora gdm[17241]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatableEyl 06 04:42:30 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.GeoClue2’ failed.Eyl 06 04:42:30 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.ColorManager’ failed.Eyl 06 04:42:31 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [_TZ.ETMD], AE_NOT_FOUND (20250404/psargs-332)Eyl 06 04:42:31 fedora kernel: ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20250404/psparse-529)Eyl 06 04:42:31 fedora dnsmasq[9912]: error binding DHCP socket to device lxdbr0Eyl 06 04:42:31 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.Eyl 06 04:42:33 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.Eyl 06 04:42:33 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.Eyl 06 04:42:33 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.Eyl 06 04:42:34 fedora dbus-broker-launch[1434]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.



Ağu 29 20:22:06 fedora kernel: ACPI: bus type drm_connector registeredAğu 29 20:22:06 fedora kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panicAğu 29 20:22:06 fedora kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0Ağu 29 20:22:06 fedora kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer deviceAğu 29 20:22:07 fedora kernel: intel_vpu 0000:00:0b.0: [drm] Firmware: intel/vpu/vpu_37xx_v1.bin, version: 20250611MTL_CLIENT_SILICON-NVRNN-deployment5437076a4c995fd1be21c3019f522b56db98f5437076a4c995fd1be21c3019f522b56db98f*5437076a4cAğu 29 20:22:07 fedora kernel: [drm] Scheduler mode: HWAğu 29 20:22:07 fedora kernel: [drm] Initialized vpu 1.0.0 for 0000:00:0b.0 on minor 0Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] Found meteorlake (device ID 7d67) integrated display version 14.00 stepping D0Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] VT-d active for gfx accessAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: vgaarb: deactivate vga consoleAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] Using Transparent HugepagesAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+memAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.23)Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] [CONNECTOR:262:eDP-1] Panel is missing HDR static metadata. Possible support for Intel HDR backlight interface is not used.If your backlight controls don’t work try booting with i915.enable_dpcd_backlight=3.Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.44.1Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC: submission enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC: SLPC enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT0: GuC: RC enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.44.1Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear mediaAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC: submission enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC: SLPC enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: GuC: RC enabledAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initializedAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll errorAğu 29 20:22:07 fedora kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1Ağu 29 20:22:07 fedora kernel: fbcon: i915drmfb (fb0) is primary deviceAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer deviceAğu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)Ağu 29 20:22:07 fedora kernel: i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloadsAğu 29 20:22:08 fedora systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm…Ağu 29 20:22:08 fedora systemd[1]: modprobe@drm.service: Deactivated successfully.Ağu 29 20:22:08 fedora systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.Ağu 29 20:22:09 fedora kernel: [drm] Loading driver: nvidia-drmAğu 29 20:22:09 fedora kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 0Ağu 29 20:22:09 fedora kernel: [drm] Connector for card0 uses atomic modesettingAğu 29 20:22:09 fedora gnome-shell[2648]: Added device ‘/dev/dri/card0’ (nvidia-drm) using atomic mode setting.


inxi -Fzxx
System:
  Kernel: 6.14.0-63.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.0.1
  Desktop: GNOME v: 48.4 tk: GTK v: 3.24.49 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 42 (Workstation Edition)
Machine:
  Type: Laptop System: GAME GARAJ product: SLAYER 5XL v: REV:1.0
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: GAME GARAJ model: SLAYER 5XL v: REV:1.0 serial: <superuser required>
    part-nu: 140 UEFI: American Megatrends LLC. v: E17S3IE2.10B date: 05/12/2025
Battery:
  ID-1: BAT1 charge: 82.1 Wh (93.6%) condition: 87.7/87.4 Wh (100.4%)
    volts: 17.12 min: 15.4 model: MSI BIF0_9 serial: N/A charging:
    status: not charging cycles: N/A
CPU:
  Info: 24-core model: Intel Core Ultra 9 275HX bits: 64 type: MCP
    arch: Arrow Lake rev: 2 cache: L1: 2.4 MiB L2: 40 MiB L3: 36 MiB
  Speed (MHz): avg: 800 min/max: 800/5400:5300:4700:6500 cores: 1: 800
    2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800
    12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
    21: 800 22: 800 23: 800 24: 800 bogomips: 147456
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Arrow Lake-S [Intel Graphics] vendor: Micro-Star MSI
    driver: i915 v: kernel arch: Xe2-LPG ports: active: eDP-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:7d67
  Device-2: NVIDIA GB205M [GeForce RTX 5070 Ti Mobile]
    vendor: Micro-Star MSI driver: nvidia v: 580.82.09 arch: Lovelace pcie:
    speed: 32 GT/s lanes: 8 ports: active: none empty: DP-1, DP-2, HDMI-A-1,
    eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2f18
  Device-3: Bison FHD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-4:2 chip-ID: 5986:1193
  Display: wayland server: Xwayland v: 24.1.8 compositor: gnome-shell
    driver: X: loaded: nvidia gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0x84a6 res: 2560x1600 dpi: 178
    diag: 431mm (17")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.1.9 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (ARL) device-ID: 8086:7d67
    display-ID: :0.0
  API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:7d67 device: 1 type: discrete-gpu
    driver: nvidia device-ID: 10de:2f18 device: 2 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: clinfo, glxinfo, vulkaninfo gpu: gputop, intel_gpu_top,
    lsgpu, nvidia-settings, nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:2f80
  Device-2: Intel vendor: Micro-Star MSI driver: sof-audio-pci-intel-mtl
    bus-ID: 80:1f.3 chip-ID: 8086:7f50
  API: ALSA v: k6.14.0-63.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 83:00.0
    chip-ID: 10ec:8125
  IF: enp131s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
    vendor: Rivet Networks driver: iwlwifi v: kernel pcie: speed: 16 GT/s
    lanes: 1 bus-ID: 84:00.0 chip-ID: 8086:272b
  IF: wlp132s0f0 state: down mac: <filter>
  Device-3: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-8:4 chip-ID: 148f:7601
  IF: wlp128s20f0u8 state: up mac: <filter>
  IF-ID-1: lxdbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: vethbe437546 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Intel BE200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-14:6 chip-ID: 8087:0036
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
    lmp-v: 13
Drives:
  Local Storage: total: 1.82 TiB used: 61.78 GiB (3.3%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNV3S2000G size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 35.9 C
Partition:
  ID-1: / size: 1.82 TiB used: 61.43 GiB (3.3%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 342.3 MiB (35.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 1.82 TiB used: 61.43 GiB (3.3%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 46.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB available: 62.2 GiB used: 5.47 GiB (8.8%)
  Processes: 565 Power: uptime: 31m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: 73 pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 59
    pm: snap pkgs: 14 Compilers: clang: 20.1.8 alt: 15 gcc: 15.2.1 Shell: Bash
    v: 5.2.37 running-in: ptyxis-agent inxi: 3.3.39

inxi -Fzxx
System:
  Kernel: 6.14.0-63.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.0.1
  Desktop: GNOME v: 48.4 tk: GTK v: 3.24.49 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 42 (Workstation Edition)
Machine:
  Type: Laptop System: GAME GARAJ product: SLAYER 5XL v: REV:1.0
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: GAME GARAJ model: SLAYER 5XL v: REV:1.0 serial: <superuser required>
    part-nu: 140 UEFI: American Megatrends LLC. v: E17S3IE2.10B date: 05/12/2025
Battery:
  ID-1: BAT1 charge: 82.1 Wh (93.6%) condition: 87.7/87.4 Wh (100.4%)
    volts: 17.12 min: 15.4 model: MSI BIF0_9 serial: N/A charging:
    status: not charging cycles: N/A
CPU:
  Info: 24-core model: Intel Core Ultra 9 275HX bits: 64 type: MCP
    arch: Arrow Lake rev: 2 cache: L1: 2.4 MiB L2: 40 MiB L3: 36 MiB
  Speed (MHz): avg: 800 min/max: 800/5400:5300:4700:6500 cores: 1: 800
    2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800
    12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
    21: 800 22: 800 23: 800 24: 800 bogomips: 147456
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Arrow Lake-S [Intel Graphics] vendor: Micro-Star MSI
    driver: i915 v: kernel arch: Xe2-LPG ports: active: eDP-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:7d67
  Device-2: NVIDIA GB205M [GeForce RTX 5070 Ti Mobile]
    vendor: Micro-Star MSI driver: nvidia v: 580.82.09 arch: Lovelace pcie:
    speed: 32 GT/s lanes: 8 ports: active: none empty: DP-1, DP-2, HDMI-A-1,
    eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2f18
  Device-3: Bison FHD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-4:2 chip-ID: 5986:1193
  Display: wayland server: Xwayland v: 24.1.8 compositor: gnome-shell
    driver: X: loaded: nvidia gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0x84a6 res: 2560x1600 dpi: 178
    diag: 431mm (17")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.1.9 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (ARL) device-ID: 8086:7d67
    display-ID: :0.0
  API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:7d67 device: 1 type: discrete-gpu
    driver: nvidia device-ID: 10de:2f18 device: 2 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: clinfo, glxinfo, vulkaninfo gpu: gputop, intel_gpu_top,
    lsgpu, nvidia-settings, nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:2f80
  Device-2: Intel vendor: Micro-Star MSI driver: sof-audio-pci-intel-mtl
    bus-ID: 80:1f.3 chip-ID: 8086:7f50
  API: ALSA v: k6.14.0-63.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 83:00.0
    chip-ID: 10ec:8125
  IF: enp131s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
    vendor: Rivet Networks driver: iwlwifi v: kernel pcie: speed: 16 GT/s
    lanes: 1 bus-ID: 84:00.0 chip-ID: 8086:272b
  IF: wlp132s0f0 state: down mac: <filter>
  Device-3: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-8:4 chip-ID: 148f:7601
  IF: wlp128s20f0u8 state: up mac: <filter>
  IF-ID-1: lxdbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: vethbe437546 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Intel BE200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-14:6 chip-ID: 8087:0036
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
    lmp-v: 13
Drives:
  Local Storage: total: 1.82 TiB used: 61.78 GiB (3.3%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNV3S2000G size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 35.9 C
Partition:
  ID-1: / size: 1.82 TiB used: 61.43 GiB (3.3%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 342.3 MiB (35.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 1.82 TiB used: 61.43 GiB (3.3%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 46.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB available: 62.2 GiB used: 5.47 GiB (8.8%)
  Processes: 565 Power: uptime: 31m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: 73 pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 59
    pm: snap pkgs: 14 Compilers: clang: 20.1.8 alt: 15 gcc: 15.2.1 Shell: Bash
    v: 5.2.37 running-in: ptyxis-agent inxi: 3.3.39

Ekran Görüntüsü 2025-08-29 21-27-07
Ekran Görüntüsü 2025-08-29 21-27-072527×1488 440 KB

Ekran Görüntüsü 2025-08-29 21-26-03
Ekran Görüntüsü 2025-08-29 21-26-032540×1132 333 KB

2

I upgraded to kernel version 6.16.7, but the same issue still persists. When will this problem be fixed, or where should I report this bug?

3

I tried the 6.16.9 and 6.17 kernels, but I keep getting the same error. How can this error be fixed? Is there light at the end of the tunnel?

4

No “me too” responses in over a month, suggests you need to make the effort to reach a broader community than just Fedora users, likely because your hardware is not widely used. You should check for probes with your model on the LHDB. Sometimes there are user comments describing configuration tweaks required by a particular model.

You can a) look for answers in the broader linux community yourself or b) make it easy for others with similar hardware and issues to find this topic. You should try to provide enough detail to allow others to reproduce your issue. This means posting hardware details (e.g., output from running inxi -Fzxx in a terminal) and relevant error messages as web searchable pre-formatted text (use the </> button from the top line of the text entry panel). You should mention if Fedora 42 is a fresh install or upgrade, and whether you are booting any other OS’s.

5

As you suggested, I updated the post, hopefully someone can help. I also reported my issue to the Red Hat team: https://bugzilla.redhat.com/show_bug.cgi?id=2393611

6

I’m struggling to see what the error actually is - I see nothing that would give me any cause for concern, other than you somehow seem to have an “errors” parameter in your mount option for one of your BTRFS partitions, which is nothing to do with your i915 chipset.

Do any external panels/screens work ok when the primary panel stays black?

7

Please edit the text by adding “```” lines before and after each section of text to preserve the original formatting.

The ACPI_BIOS errors are not unusual – many vendors have ACPI bugs.

Many newer laptops with both Intel iGPU and Nvidia dGPU use the dGPU to render portions of the screen and pass the rendered portion to the iGPU for display. Is it possible that your system is using the dGPU to send display output to a port for an external monitor?

8

The exact error is: kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error

i915 → Intel’s graphics driver.

0000:00:02.0 → PCI address, meaning the location of the Intel GPU device in my system.

[drm] → Direct Rendering Manager.

CRTC:88:pipe A → Display output controller (CRTC). ‘Pipe A’ usually refers to the primary display output pipeline.

DSB 0 poll error → DSB (Display Stream Buffer / Display Subsystem Buffer) hardware block. ‘poll error’ means the hardware failed to give the expected response or there was an inconsistency in register read/write operations.

9

Yep - just a polling error. It then goes on to be initialised without any further issues being reported. It’s not a fatal error, which is why I wondered if the backlight on the internal display ever activates and whether any external monitors display any output, assuming you have an external displays.

Given that you have a relatively new device, the i915 gpu drivers and/or firmware likely aren’t ready for this particular revision of this particular hardware it seems - kernel updates will eventually catch up with you. As for when…

10

I’ve made the necessary corrections in the post and the exact error is: kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error

11

Yes, my system can be considered relatively new, but what I don’t really understand is how they updated the kernel in such a way that something which worked perfectly on the previous 6.14.0-63 kernel is now broken. It’s really strange.

12

Perhaps someone fixed an old bug which triggered your issue. Regressions happen quite a lot, but the more people who are impacted by it, the more eyes are on it and the sooner it gets found, fixed and deployed.

Given that the i915 chipset is extremely common, it should have quite a lot of people noticing that this. Your arrow lake chipset is a pretty new version - released in early 2025, apparently. Perhaps there are firmware bugs which are being triggered by the newer kernels. It’s baked into your CPU itself, so you may find some benefit to checking to see if new firmware is available via fwupdmgr update and checking to see if a new BIOS has been released for your motherboard. Yours is only a few months old, but given how new this revision of the chipset is, they should be squashing bugs thick and fast.

I’m still pretty surprised you get a black screen from this - there’s nothing in the log to indicate there is any issue that I can see, but if you get a black LCD panel there evidently is a problem. If you hadn’t mentioned it in the title, I’d have no idea that you had anything wrong!

13

The BIOS is up to date. I’ve tried everything. My machine is stuck in a swamp, and the more it moves, the deeper it sinks. Every day I write to the Red Hat team asking if there’s any progress, and I think in the end they’re just going to tell me to go use Windows :slight_smile:

14

If you switch the in-use display card over to the GTX5070 do you get a screen display then?

Can you (or have you) plugged in an external monitor - does it also display nothing when the LCD panel is dead?

15

If I have to connect to an external LCD, I’d feel bad for having bought a notebook with a 240Hz screen. I’m saving my RTX 5070 Ti GPU for gaming :slight_smile: The Intel iGPU should do its job so that I can say I have a notebook with an iGPU—otherwise, knowing the iGPU is just sitting there idle doesn’t feel good to me :slight_smile:

16

It’s part of your CPU so it’s never really idle! :slight_smile:

Given that you know it worked with a 6.14 kernel, have you tried regressing back to one of those versions, so that you are’nt utterly stuck until the i915 issue is fixed?

17

Right now I’m holding on with 6.14, otherwise I’d really be frustrated :slight_smile: It seems like there’s no choice but to wait.

1 Like
18

In cases like this you need to have a workaround that allows you do important things while waiting for a fix. You can speed things up if you can find others with the same issue. Try searching for your hardware and linux kernel version.

Connecting to an external monitor would help narrow down the problem. I don’t see other reports with errors similar to i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error. Many such “errors” are transient and don’t impact normal operation,but sometimes such errors are side effects of actual bugs.

19

If the issue isn’t fixed in Fedora 43 either, I’ll build my own customized kernel, I’m exhausted from asking for help :slight_smile:

20

I’ve had a couple issues that were unintentional side effects of changes made for good reasons (security, efficiency, support for newer hardware) where the changes had simple mistakes. Because the mistakes only affected a small number systems, it was up to users with affected systems to discover and report the mistake. By the time discovered and tested my fix by buiding a corrected module and reported the mistake, several other people has also reported it. I have also encountered cases where a vendor substituted a less capable but cheaper or easier to obtiain part, resulting in a system that didn’t meet the specifications of similar systems using parts from one of the major vendors.

Linux developers are often overworked so it should not be surprising that they sometimes make mistakes.

There is a YouTube Review of a similar system. Maybe the channel owner would be interested in trying Fedora. If he sees the same issue that could get the attention of someone who can explain root cause.