Bugzilla – Bug 1213199
Could not start Display server with kernel 5.14.21-150500.53.2
Last modified: 2023-07-13 19:51:04 UTC
Updated opensuse leap 15.4 to the new version 15.5 After restarting the system it does not boot with kernel 5.14.21-150500.53.2 (black screen). Works with previous kernel 5.14.21-150400.24.66 /var/log/messages (using kernel 5.14.21-150500.53.2) 2023-07-11T09:31:28.531712+03:00 linux sddm[1976]: Failed to read display number from pipe 2023-07-11T09:31:28.531842+03:00 linux sddm[1976]: Attempt 1 starting the Display server on vt 7 failed 2023-07-11T09:31:30.515326+03:00 linux sddm[1976]: Display server starting... 2023-07-11T09:31:30.515448+03:00 linux sddm[1976]: Running: /usr/bin/X -dpi 96 -auth /run/sddm/{0d007211-cf28-4774-92ee-f5f008d0e1ca} -background none -noreset -displayfd 17 -seat seat0 vt7 2023-07-11T09:31:30.634858+03:00 linux sddm[1976]: Failed to read display number from pipe 2023-07-11T09:31:30.634978+03:00 linux sddm[1976]: Attempt 2 starting the Display server on vt 7 failed 2023-07-11T09:31:32.537201+03:00 linux sddm[1976]: Display server starting... 2023-07-11T09:31:32.537353+03:00 linux sddm[1976]: Running: /usr/bin/X -dpi 96 -auth /run/sddm/{0d007211-cf28-4774-92ee-f5f008d0e1ca} -background none -noreset -displayfd 17 -seat seat0 vt7 2023-07-11T09:31:32.654239+03:00 linux sddm[1976]: Failed to read display number from pipe 2023-07-11T09:31:32.654365+03:00 linux sddm[1976]: Attempt 3 starting the Display server on vt 7 failed 2023-07-11T09:31:32.693907+03:00 linux sddm[1976]: Could not start Display server on vt 7 inxi -SGa (using kernel 5.14.21-150400.24.66) System: Host: linux Kernel: 5.14.21-150400.24.66-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150400.24.66-default root=UUID=55eb4950-5b5b-4458-9231-ca4362673481 resume=/dev/disk/by-uuid/f292c4d7-df81-4fc5-938a-d9d65bb0a634 splash=silent quiet showopts Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: openSUSE Leap 15.5 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Gigabyte driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: none empty: HDMI-A-1,HDMI-A-2,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300 Device-2: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: ASUSTeK driver: nouveau v: kernel non-free: 520.xx+ status: current (as of 2022-10) arch: Turing code: TUxxx process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1 empty: DP-2, DP-3, HDMI-A-3, HDMI-A-4 bus-ID: 01:00.0 chip-ID: 10de:1e84 class-ID: 0300 temp: 28.0 C Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11 driver: X: loaded: modesetting,nouveau unloaded: fbdev,vesa failed: nv alternate: intel,nvidia dri: nouveau,crocus gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.00x12.48") s-diag: 599mm (23.57") Monitor-1: DP-1 model: Asus PA249 serial: G6LMQS080448 built: 2016 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 518x324mm (20.39x12.76") diag: 611mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 720x400 API: OpenGL v: 4.3 Mesa 22.3.5 renderer: NV164 direct render: Yes
Booting symptoms are similar to this bug https://bugzilla.opensuse.org/show_bug.cgi?id=1209436
Please don't touch the Priority field of Bugzilla. It's only for devs. Could you give the dmesg output from Leap 15.5 kernel? Please use the attachment.
Created attachment 868139 [details] dmesg output dmesg output with kernel 5.14.21-150400.24.46
Created attachment 868155 [details] System info
It has nothing to do with bug 1209436 (that was a bug in i915 and it rather crashes). How is the graphics set up? Is Nvidia chip used for the primary output (with nouveau driver)? Or is it Intel graphics? And, the next step is to check the latest kernel in OBS Kernel:SLE15-SP5 repo. If the problem still happens with that kernel, boot with drm.debug=0x1e boot option, and attach the dmesg output.
The problem is with the graphics card driver. I am using the nouveau driver and with the boot option 'nouveau.force_probe=1' the system works with the latest kernel. Such a dmesg log entry was: linux kernel: nouveau 0000:01:00.0: Probe of device 1e84 skipped due to experimental state of this driver. You can enable nouveau driver via force_probe=1 option (kernel boot parameter 'nouveau.force_probe=1') However we recommend the usage of nVidia's openGPU driver meanwhile. Sorry to bother you for nothing!
It's not a bug.