TLDR: https://github.com/systemd/systemd/issues/10435 Systemd decided framebuffer with no graphics acceleration up doesn't count as "graphics capable" anymore. Someone pointed out it will probably break AMD and Nvidia proprietary drivers that doesn't report the device via the open source DRM interface but they did it anyways leaving driver vendors to figure out how to get it working again. 8-O Symptom: After upgrading to systemd-240, SDDM (and probably any DM that uses the CanGraphical flag) no longer start and system is stuck in text mode. Not much errors produced in usual places since it fails too early before we even start the X server. journalctl -e -u sddm: Jan 01 18:49:00 bliss sddm[2955]: Initializing... Jan 01 18:49:00 bliss sddm[2955]: Starting... Jan 01 18:49:00 bliss sddm[2955]: Logind interface found (Stuck after this message, listening on DBus for a graphical terminal to show up.) Workarounds: 1. Switch to another VT (ctrl-alt-f2) and login in text mode. Start X manually. For e.g., "startx /usr/bin/startkde". 2. Go to /lib/udev/rules.d/71-seat.rules and revert their change. 3. Downgrade to systemd-239 and mask systemd-240 if you use proprietary drivers. Long term fix: They speculated that it will be fixable with some udev rule and someone provided examples from Ubuntu. https://github.com/tseliot/ubuntu-drivers-common/blob/master/share/hybrid/71-u-d-c-gpu-detection.rules https://github.com/tseliot/ubuntu-drivers-common/blob/master/share/hybrid/u-d-c-print-pci-ids No idea how other distros plan to handle this.
Please take this discussion upstream.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55b9c69178b4518b06b29c3f156c2f1e33211224 commit 55b9c69178b4518b06b29c3f156c2f1e33211224 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2019-01-24 14:47:16 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-01-24 14:47:16 +0000 sys-apps/systemd: backports for 240 based on v240-stable branch Bug: https://bugs.gentoo.org/674520 Bug: https://bugs.gentoo.org/674292 Bug: https://bugs.gentoo.org/674152 Package-Manager: Portage-2.3.56_p3, Repoman-2.3.12_p50 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd/Manifest | 1 + sys-apps/systemd/systemd-240-r4.ebuild | 457 +++++++++++++++++++++++++++++++++ 2 files changed, 458 insertions(+)
The exact same thing (described by Clement in #1) happens with systemd-241, which is stabilized now. Meaning that stable nvidia-drivers + stable systemd = no display manager right now. X can only be started manually after login.
I don't have hardware that is supported by the proprietary Nvidia or AMD drivers, so there is very little I can to to troubleshoot this. Patches welcome.
