Black login screen after update to linux Kernel 7.0.7-339

pcdery

I just installed Solus 4.9 with latest iso on the website. Everything worked just fine with the kernel 6.18. A few minutes after the installation, I did all the updates from the Discover app. After the reboot, I see the solus logo, and then a black screen (i supposed the login screen is black). Unable to log in. When reboot with the linux kernel 6.18, I see the log screen just fine. I will keep booting with the kernel 6.18 for the moment, hope this bug will be fixe.

TraceyC

pcdery

Please open an issue (if there isn't one already) on our bug tracker for this. By opening an issue, it will allow our developers to get details, look into it and keep track of progress. Thanks.

pomon

It would be helpful to get the logs from the boot on kernel 7.0.7. Here is my suggestion. While booted into kernel 6.18, create a file named e.g. logs.sh and paste the following:

sudo dmesg | grep -iE 'kernel|error|amdgpu|lightdm' > ~/dmesg_error.txt
journalctl -p err -b 0 -n 100 > ~/journal_error.txt
cp ~/.local/share/xorg/Xorg.0.log ~/Xorg.0.log.7.0.7

Make it executable by running chmod +x logs.sh.

Then, reboot and switch to kernel 7.0.7, drop into TTY (Ctrl+Alt+F2/3), log in, and run ./logs.sh.

After that, boot back into 6.18. You should have 3 files in your home directory. Look through them or upload them to a pastebin and share the links here.

pcdery

pomon unable to drop in TTY when on the black screen after booting on kernel 7.0.7

majunia28

pomon

Same issue here:

I don't have a ~/.local/share/xorg/ folder neither a Xorg.0.log file

dmesg_error.txt

**[    0.029206] Booting paravirtualized kernel on bare hardware
[    0.108256] Kernel command line: initrd=\EFI\com.solus-project\initrd-com.solus-project.current.7.0.9-341 root=PARTUUID=4e900c7f-d37a-4d84-9e2f-a95c40477611 rd.vconsole.keymap=us quiet splash rw resume=UUID=d1090cb2-f024-47a3-8817-fd486a7625fe
[    0.108487] Unknown kernel command line parameters "splash", will be passed to user space.
[    0.318873] mitigations: Enabled attack vectors: user_kernel, user_user, guest_host, guest_guest, SMT mitigations: auto
[    0.500182] MCE: In-kernel MCE decoding enabled.
[    0.508123] Memory: 6878884K/7301136K available (18861K kernel code, 3397K rwdata, 15776K rodata, 4612K init, 4472K bss, 413756K reserved, 0K cma-reserved)
[    0.517164] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
[    0.517801] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.518436] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.609907] acpi PNP0A08:00: _OSC: platform retains control of PCIe features (AE_ERROR)
[    2.897212] Loaded X.509 cert 'Build time autogenerated kernel key: 425cae40190c88c72cb27e6795b88e8be8aa42c4'
[    2.904181] RAS: Correctable Errors collector initialized.
[    2.914683] Freeing unused kernel image (initmem) memory: 4612K
[    2.914831] Write protecting the kernel read-only data: 36864k
[    2.916541] Freeing unused kernel image (text/rodata gap) memory: 1616K
[    2.917063] Freeing unused kernel image (rodata/data gap) memory: 608K
[    2.992756] autofs4: module verification failed: signature and/or required key missing - tainting kernel
[    3.195464] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[    3.201865] systemd[1]: systemd-modules-load.service - Load Kernel Modules skipped, no trigger condition checks were met.
[    3.204072] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
[    3.234185] systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables.
[    4.382717] [drm] radeon kernel modesetting enabled.
[    4.384276] [drm] initializing kernel modesetting (MULLINS 0x1002:0x9851 0x103C:0x81E6 0x45).
[    9.514057] amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.VGA_.ATPX handle
[    9.514850] amdgpu: ATPX version 1, functions 0x00000003
[    9.520979] amdgpu: Virtual CRAT table created for CPU
[    9.521031] amdgpu: Topology: Add CPU node
[    9.521168] amdgpu 0000:01:00.0: SI support provided by amdgpu.
               Use radeon.si_support=1 amdgpu.si_support=0 to override.
[    9.521365] amdgpu 0000:01:00.0: enabling device (0002 -> 0003)
[    9.521506] amdgpu 0000:01:00.0: initializing kernel modesetting (HAINAN 0x1002:0x6660 0x103C:0x81E6 0x83).
[    9.522341] amdgpu 0000:01:00.0: register mmio base: 0xF2B00000
[    9.522347] amdgpu 0000:01:00.0: register mmio size: 262144
[    9.523040] amdgpu 0000:01:00.0: detected ip block number 0 <common_v1_0_0> (si_common)
[    9.523049] amdgpu 0000:01:00.0: detected ip block number 1 <gmc_v6_0_0> (gmc_v6_0)
[    9.523054] amdgpu 0000:01:00.0: detected ip block number 2 <ih_v1_0_0> (si_ih)
[    9.523060] amdgpu 0000:01:00.0: detected ip block number 3 <gfx_v6_0_0> (gfx_v6_0)
[    9.523064] amdgpu 0000:01:00.0: detected ip block number 4 <sdma_v1_0_0> (si_dma)
[    9.523069] amdgpu 0000:01:00.0: detected ip block number 5 <smu_v6_0_0> (si_dpm)
[    9.613547] amdgpu 0000:01:00.0: Fetched VBIOS from ATRM
[    9.613557] amdgpu 0000:01:00.0: [drm] ATOM BIOS: BR46766.001
[    9.613594] amdgpu 0000:01:00.0: Trusted Memory Zone (TMZ) feature not supported
[    9.613600] amdgpu 0000:01:00.0: PCIE atomic ops is not supported
[    9.613607] amdgpu 0000:01:00.0: GPU posting now...
[    9.620675] amdgpu 0000:01:00.0: vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[    9.621235] amdgpu 0000:01:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[    9.621243] amdgpu 0000:01:00.0: GART: 256M 0x0000000000000000 - 0x000000000FFFFFFF
[    9.621255] amdgpu 0000:01:00.0: [drm] Detected VRAM RAM=2048M, BAR=256M
[    9.621260] amdgpu 0000:01:00.0: [drm] RAM width 64bits DDR3
[    9.621497] amdgpu 0000:01:00.0:  2048M of VRAM memory ready
[    9.621504] amdgpu 0000:01:00.0:  3445M of GTT memory ready.
[    9.621549] amdgpu 0000:01:00.0: [drm] GART: num cpu pages 65536, num gpu pages 65536
[    9.622774] amdgpu 0000:01:00.0: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[    9.626386] amdgpu 0000:01:00.0: [drm] Internal thermal controller without fan control
[    9.626412] amdgpu 0000:01:00.0: [drm] si dpm initialized
[    9.934265] amdgpu 0000:01:00.0: SE 1, SH per SE 1, CU per SH 5, active_cu_number 5
[   10.517817] amdgpu 0000:01:00.0: Using ATPX for runtime pm
[   10.518073] [drm] Initialized amdgpu 3.64.0 for 0000:01:00.0 on minor 1
[   19.067078] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[   19.095369] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
[   19.097706] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
[   19.112005] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
[   19.114630] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
[   19.120569] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[   19.125314] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
[   19.131273] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
[   19.133876] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
[   19.153995] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[   19.155954] systemd[1]: Starting systemd-network-generator.service - Generate Network Units from Kernel Command Line...
[   19.158405] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
[   19.171466] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
[   19.171692] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
[   19.173653] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.
[   19.174627] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[   19.175500] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[   19.176424] systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
[   19.177415] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
[   19.219901] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[   19.305101] systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
[   19.351216] systemd[1]: Finished systemd-network-generator.service - Generate Network Units from Kernel Command Line.
[   19.402408] systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
[   19.404704] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
[   24.966725] amdgpu 0000:01:00.0: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[   26.858161] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20251212/dsopcode-133)
[   26.858185] ACPI Error: Aborting method \_SB.WMID.WQBC due to previous error (AE_AML_OPERAND_VALUE) (20251212/psparse-529)
[   26.860802] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20251212/dsopcode-133)
[   26.860846] ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error (AE_AML_OPERAND_VALUE) (20251212/psparse-529)
[   27.066304] hp_bioscfg: Returned error 0x4, "Invalid command type"
[   34.533467] amdgpu 0000:01:00.0: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).**

journal_error.txt

**may 26 22:19:52 solus kernel: No irq handler for 1.55
may 26 22:19:52 solus kernel: No irq handler for 2.55
may 26 22:19:52 solus kernel: No irq handler for 3.55
may 26 22:19:53 solus kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
may 26 22:20:13 hp-red systemd-udevd[484]: /usr/lib64/udev/rules.d/90-alsa-restore.rules:16 GOTO="alsa_restore_std" has no matching label, ignoring.
may 26 22:20:13 hp-red systemd-udevd[484]: /usr/lib64/udev/rules.d/90-alsa-restore.rules:20 GOTO="alsa_restore_std" has no matching label, ignoring.
may 26 22:20:16 hp-red kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20251212/dsopcode-133)
may 26 22:20:16 hp-red kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous error (AE_AML_OPERAND_VALUE) (20251212/psparse-529)
may 26 22:20:16 hp-red kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20251212/dsopcode-133)
may 26 22:20:16 hp-red kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error (AE_AML_OPERAND_VALUE) (20251212/psparse-529)
may 26 22:20:18 hp-red bluetoothd[654]: Failed to set default system config for hci0
may 26 22:20:18 hp-red bluetoothd[654]: Failed to set mode: Failed (0x03)
may 26 22:20:24 hp-red wpa_supplicant[766]: bgscan simple: Failed to enable signal strength monitoring
may 26 22:20:36 hp-red systemd[1]: Failed to start lightdm.service - Light Display Manager.**

ℹ Moderator Note
I have edited your post to have the code output in a code fence.
Please always use the code button or manually add 3 backticks before and after code blocks.
This makes it a lot more readable. Thanks.
TraceyC

pcdery

I'll do that tonight, thx.

pcdery

Tried to solce the issue with Claude, but broke my system :

Here a summary by Claude:

Kernel 7.0.7 — DMCUB firmware crash looping at boot (`dc_dmub_srv_log_diagnostic_data: DMCUB error`), followed by repeated failures on `dpcd_set_link_settings` (DP_DOWNSPREAD_CTRL, DP_LANE_COUNT_SET, DP_LINK_BW_SET). LightDM starts but the internal display receives no signal. No issues under kernel 6.18 LTS. APU: AMD Ryzen 5 7430U / integrated Radeon graphics.

Logs:

May 19 17:02:21 pcdery-solus systemd-udevd[558]: /usr/lib64/udev/rules.d/90-alsa-restore.rules:16 GOTO="alsa_restore_std" has no matching label, ignoring.

May 19 17:02:21 pcdery-solus systemd-udevd[558]: /usr/lib64/udev/rules.d/90-alsa-restore.rules:20 GOTO="alsa_restore_std" has no matching label, ignoring.

May 19 17:02:21 pcdery-solus kernel: Bluetooth: hci0: No support for _PRR ACPI method

May 19 17:02:23 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:02:23 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:02:23 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:02:24 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:02:24 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed

May 19 17:02:25 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed

May 19 17:02:25 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed

May 19 17:02:25 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed

May 19 17:02:25 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed

May 19 17:02:25 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed

May 19 17:02:26 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed

May 19 17:02:26 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed

May 19 17:02:26 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed

May 19 17:03:02 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:02 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:09 pcdery-solus lightdm[1104]: gkr-pam: unable to locate daemon control file

May 19 17:03:10 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:10 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:10 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:11 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:12 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed

May 19 17:03:12 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed

May 19 17:03:12 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed

May 19 17:03:12 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed

May 19 17:03:12 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed

May 19 17:03:12 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed

May 19 17:03:13 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed

May 19 17:03:13 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed

May 19 17:03:13 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed

May 19 17:03:14 pcdery-solus bluetoothd[1769]: Failed to set default system config for hci0

May 19 17:03:42 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:03:42 pcdery-solus kernel: amdgpu 0000:04:00.0: [drm] \*ERROR\* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

May 19 17:04:01 pcdery-solus budgie-screensaver-dialog[3283]: PAM _pam_load_conf_file: unable to open config for pam_deny.so

May 19 17:04:12 pcdery-solus systemd[1365]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.

May 19 17:04:13 pcdery-solus systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

May 19 17:04:13 pcdery-solus systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

May 19 17:04:13 pcdery-solus systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

May 19 17:04:13 pcdery-solus systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

May 19 17:04:13 pcdery-solus systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

May 19 17:06:31 pcdery-solus sudo[6272]: pam_unix(sudo:auth): conversation failed

May 19 17:06:31 pcdery-solus sudo[6272]: pam_unix(sudo:auth): auth could not identify password for [pcdery]

ℹ Moderator Note
I have edited your post to have the code output in a code fence.
Please always use the code button or manually add 3 backticks before and after code blocks.
This makes it a lot more readable. Thanks.
TraceyC

pcdery

majunia28

majunia28 you can go add your details there getsolus/packages9073

pcdery

TraceyC getsolus/packages9073

majunia28

pcdery

Got it. I add my info on the open bug tracker.
Thanks guys for the help

TraceyC

Folks... please use code fences around code blocks, here and in the bug tracker. It makes code blocks readable. Thanks.