[EN] After full-upgrade, transition from grub to graphical target is broken

[dibl]

It looks a like failure to boot, with the last visible message on tty1 like this:

Code: [Select]

[    4.902533] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
This message also appears, in red color, near the end of dmesg output:

Code: [Select]

[    4.809519] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[    4.886689] Bluetooth: hci0: Waiting for firmware download to complete
[    4.887421] Bluetooth: hci0: Firmware loaded in 1871281 usecs
[    4.887582] Bluetooth: hci0: Waiting for device to boot
[    4.902502] Bluetooth: hci0: Device booted in 14694 usecs
[    4.902533] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    4.909349] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[    4.911481] Bluetooth: hci0: Applying Intel DDC parameters completed
[    4.912493] Bluetooth: hci0: Firmware revision 0.4 build 15 week 45 2022
[    4.978678] Bluetooth: MGMT ver 1.22
[  15.018726] pci 0000:00:0d.0: deferred probe pending
[  33.726082] systemd-journald[478]: Time jumped backwards, rotating.
But, the system is actually booted. The user can log in on tty2 and issue

Code: [Select]

startx && exit
and get the expected plasma desktop.

There are some forum reports on arch forum, but no solutions that I can find. The error seems to be mostly cosmetic.

I saw sddm got updated today -- I wonder whether that might be involved in this issue?

[towo]

No Problem here™.

[dibl]

  OK thanks towo.

After tty1 hangs, I can go to tty2, login as root, and issue

Code: [Select]

systemctl isolate multi-user.target && exit
Then I can go back to tty1, login as root, and issue

Code: [Select]

systemctl isolate graphical.target && exit
and plasma-desktop launches as normal. It seems like the transition to sddm isn't working automatically. I reinstalled sddm and the 3 needed wayland packages, but no change. The nvidia driver seems to be working OK -- I guess I could reinstall that too.

[towo]

Code: [Select]

[    4.978678] Bluetooth: MGMT ver 1.22
[  15.018726] pci 0000:00:0d.0: deferred probe pending
[  33.726082] systemd-journald[478]: Time jumped backwards, rotating.That's a long time!
What hardware is

Code: [Select]

pci 0000:00:0d.0?

[dibl]

Code: [Select]

don@dibl-oryxpro$ lspci
00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05)
00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05)
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05)
00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05)
00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05)
00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11)
00:14.3 Network controller: Intel Corporation Tiger Lake PCH CNVi WiFi (rev 11)
00:15.0 Serial bus controller: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11)
00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11)
00:19.0 Serial bus controller: Intel Corporation Device 43ad (rev 11)
00:19.2 Communication controller: Intel Corporation Device 43a7 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #5 (rev 11)
00:1d.0 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #9 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11)
00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-H SPI Controller (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GA104 High Definition Audio Controller (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
24:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
25:00.0 Non-Volatile memory controller: Sandisk Corp Device 5019 (rev 01)

[dibl]

Code: [Select]

Looks like a USB bluetooth chip, consistent with

Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 3.0

[dibl]

Digging deeper with journalctl:

Code: [Select]

Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mInitializing...
Feb 22 10:08:51 dibl-oryxpro dbus-daemon[869]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 22 10:08:51 dibl-oryxpro systemd[1]: Started colord.service - Manage, Install and Generate Color Profiles.
Feb 22 10:08:51 dibl-oryxpro dbus-daemon[869]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 22 10:08:51 dibl-oryxpro systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mStarting...
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mLogind interface found
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mAdding new display on vt 7 ...
Feb 22 10:08:51 dibl-oryxpro NetworkManager[932]: <info>  [1677078531.0303] hostname: hostname: using hostnamed
Feb 22 10:08:51 dibl-oryxpro NetworkManager[932]: <info>  [1677078531.0304] hostname: static hostname changed from (none) to "dibl-oryxpro"
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mLoading theme configuration from ""
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mDisplay server starting...
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mAdding cookie to "/var/run/sddm/{fd250785-639e-4389-ae44-6bdb111db96f}"
Feb 22 10:08:51 dibl-oryxpro NetworkManager[932]: <info>  [1677078531.0310] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Feb 22 10:08:51 dibl-oryxpro NetworkManager[932]: <info>  [1677078531.0327] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill0) (driver iwlwifi)
Feb 22 10:08:51 dibl-oryxpro NetworkManager[932]: <info>  [1677078531.0330] manager[0x55c091021000]: rfkill: Wi-Fi hardware radio set enabled
Feb 22 10:08:51 dibl-oryxpro NetworkManager[932]: <info>  [1677078531.0330] manager[0x55c091021000]: rfkill: WWAN hardware radio set enabled
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;38;5;245m^[[0;38;5;245mRunning: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{fd250785-639e-4389-ae44-6bdb111db96f} -background none -noreset -displayfd 17 -seat seat0 vt7
a little later

Code: [Select]

Feb 22 10:08:51 dibl-oryxpro systemd[1]: Started bluetooth.service - Bluetooth service.
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: Starting SDP server
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mprofiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: ^[[0;1;39msrc/plugin.c:plugin_init() Failed to init vcp plugin
Feb 22 10:08:51 dibl-oryxpro systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mprofiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: ^[[0;1;39msrc/plugin.c:plugin_init() Failed to init mcp plugin
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mprofiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Feb 22 10:08:51 dibl-oryxpro bluetoothd[3595]: ^[[0;1;39msrc/plugin.c:plugin_init() Failed to init bap plugin
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;1;39mFailed to read display number from pipe
Feb 22 10:08:51 dibl-oryxpro sddm[1093]: ^[[0;1;39mCould not start Display server on vt 7

[hendrikL]

mh, sddm, starting on vt7?

[hendrikL]

journalctl | grep sddm
with X11

Feb 22 17:16:47 hhl sddm-helper[27604]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket [/color]
Feb 22 17:16:47 hhl sddm-helper[27568]: pam_env(sddm:session): deprecated reading of user environment enabled
Feb 22 17:16:47 hhl sddm-helper[27568]: Starting: "/etc/sddm/Xsession \"/usr/bin/startplasma-x11\""
Feb 22 17:16:47 hhl sddm-helper[27606]: Adding cookie to "/home/hhl/.Xauthority"
Feb 22 17:16:47 hhl sddm[1257]: Session started

or with wayland

Feb 22 16:32:24 hhl sddm-helper[3996]: Starting: "/etc/sddm/wayland-session /usr/lib/x86_64-linux-gnu/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Feb 22 16:32:24 hhl sddm-helper[4036]: Jumping to VT 1
Feb 22 16:32:24 hhl sddm-helper[4036]: VT mode didn't need to be fixed
Feb 22 16:32:24 hhl sddm[1257]: Session started

It should look like that, normally™

I apologize for the double post, i like that new editor.

[dibl]

Thanks Hendrik!

I thought this situation was starting to look familiar -- I have been here before:

https://forum.siduction.org/index.php?topic=8682.msg69272#msg69272

EDIT:  YES, the sddm update yesterday reset the /etc/systemd/system/display-manager.service back to the defaults, which on my Intel GPU tries to start too early. I inserted a 5 second sleep before the "ExecStart" line, and all is working again as expected.


BTW, this is totally unrelated to the bluetooth errors. I don't care, I don't need bluetooth on this system.  

[DeepDayze]

@dibl, you can simply go into your BIOS and turn off Bluetooth there and the messages about BT will disappear

I've seen a similar situation on another system where the display manager (LightDM in that case) would tend to start too early before the Intel driver is even loaded but a config change fixed that. Wonder if there's a config setting for SDDM to check for when it can safely start (driver loaded).

[dibl]

@dibl, you can simply go into your BIOS and turn off Bluetooth there and the messages about BT will disappear

....

That would be true for most modern laptops ... unfortunately, System 76 doesn't think I need that capability.

It would be nice if sddm could detect the hardware and change the timing of X start by itself at installation, but as far as I can see, my modification of /etc/systemd/system/display-manager.service appears to be the only lever for this setting.