Page 1 of 1
nvidia driver with systemd causes no sddm at start
Posted: Mon Jan 15, 2024 6:35 pm
by Amunhateb
Hello MX Linux community,
I am experiencing some strange behavior with nvidia driver and systemd enabled by default. When it's sysv, everything boots fine with nvidia proprietary driver. But with systemd it looks like sddm starts and after 1 sec PC switches to TTY1. I have to always manually press ctrl-alt-f7 to get back to sddm at every boot. Seems like some boot order issue.
I am using MX 23.1 x64 with latest kernel and updates. Also I have two configurations. Two different PCs with nvidia card. Issue persists on both.
Re: nvidia driver with systemd causes no sddm at start
Posted: Fri Jan 19, 2024 10:46 am
by CharlesV
Welcome in!
Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )
Re: nvidia driver with systemd causes no sddm at start
Posted: Fri Jan 19, 2024 11:15 am
by Charlie Brown
Does this change anything?
Code: Select all
sudo apt update ; sudo apt purge sddm-modified-init -y ; sudo apt reinstall sddm -y
Reboot.
Re: nvidia driver with systemd causes no sddm at start
Posted: Fri Jan 19, 2024 2:07 pm
by Amunhateb
my quick system info
Code: Select all
System:
Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=<filter> ro quiet splash
resume=UUID=<filter> resume_offset=14256128
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64 Libretto
October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 0806 date: 07/31/2017
CPU:
Info: model: AMD Ryzen 5 1600X bits: 64 type: MT MCP arch: Zen level: v3 note: check
built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 1 stepping: 1 microcode: 0x8001126
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 576 KiB
desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 2104 high: 3074 min/max: 2200/3600 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1895 2: 1853 3: 2650 4: 3074 5: 1958 6: 1825
7: 1886 8: 2169 9: 2006 10: 1882 11: 1882 12: 2172 bogomips: 86228
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow mitigation: safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI driver: nvidia v: 525.147.05
non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 25:00.0 chip-ID: 10de:1c82
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x333mm (23.70x13.11") s-diag: 688mm (27.09")
Monitor-1: HDMI-0 res: 2560x1440 hz: 60 dpi: 108 size: 600x330mm (23.62x12.99")
diag: 685mm (26.96") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 25:00.1 chip-ID: 10de:0fb9 class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 27:00.3 chip-ID: 1022:1457 class-ID: 0403
API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 23:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: br-130e13e2bbef state: down mac: <filter>
IF-ID-2: br-2a43a2d96a91 state: down mac: <filter>
IF-ID-3: docker0 state: down mac: <filter>
IF-ID-4: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
Local Storage: total: 5.94 TiB used: 1.94 TiB (32.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 71E0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DL003-9VT166 size: 1.82 TiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5900 serial: <filter>
rev: CC31 scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 vendor: XrayDisk model: 2TB SSD size: 1.86 TiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 8B0 scheme: MBR
ID-4: /dev/sdd maj-min: 8:48 model: SSD 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 8A0 scheme: MBR
Partition:
ID-1: / raw-size: 97.66 GiB size: 95.57 GiB (97.86%) used: 69.19 GiB (72.4%) fs: ext4
dev: /dev/sdd2 maj-min: 8:50
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 34.9 MiB (36.4%) fs: vfat
dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 19.55 GiB used: 1.74 GiB (8.9%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 50.5 C mobo: N/A gpu: nvidia temp: 50 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 38%
Repos:
Packages: 2768 pm: dpkg pkgs: 2754 libs: 1524 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 14
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/ddev.list
1: deb [signed-by=/etc/apt/keyrings/ddev.gpg] https://pkg.ddev.com/apt/ * *
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
2: deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb-src http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
3: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
4: deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/docker.list
1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian bookworm stable
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.truenetwork.ru/mxlinux/mx/repo/ bookworm main non-free
2: deb http://mirror.truenetwork.ru/mxlinux/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/php.list
1: deb [signed-by=/usr/share/keyrings/deb.sury.org-php.gpg] https://packages.sury.org/php/ bookworm main
Active apt repos in: /etc/apt/sources.list.d/yandex-browser.list
1: deb [arch=amd64] https://repo.yandex.ru/yandex-browser/deb stable main
Info:
Processes: 403 Uptime: 6h 52m wakeups: 0 Memory: 15.55 GiB used: 13.94 GiB (89.6%) Init: systemd
v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: nvidia driver with systemd causes no sddm at start
Posted: Wed Jan 24, 2024 3:51 pm
by Amunhateb
Charlie Brown wrote: Fri Jan 19, 2024 11:15 am
Does this change anything?
Code: Select all
sudo apt update ; sudo apt purge sddm-modified-init -y ; sudo apt reinstall sddm -y
Reboot.
thanks for your suggestion but I tried and nothing changed :(
Re: nvidia driver with systemd causes no sddm at start
Posted: Sat Feb 24, 2024 4:45 am
by catalex54
I don't want to cross-post, but I have some unresolved issues that have some similarities to yours.
I have recently participated in this forum in the section dedicated to Italian-speaking users.
https://www.forum.mxlinux.org/viewtopic.php?t=79438
It would be interesting if you tried to do what I did to have a temporary workaround, inserting the text
"systemd.unit=rescue.target" into the kernel boot parameters (after quiet splash).
When the system starts, the following message will appear at the end of the boot text: (or press control-d to continue).
I just press
control+d, and everything starts on the desktop in Systemd mode with Nvidia graphics working, excellently.
I don't know the technical reason for this temporary solution or even what the cause is, but I would be curious if you could try it and say what the result is.
Thanks and take care.
Alex
Re: nvidia driver with systemd causes no sddm at start
Posted: Sat Feb 24, 2024 4:49 am
by Eadwine Rose
I get your intentions, but please make sure that you are not ending up stealing the topic of this user. When folks start responding to your situation in here, direct them to yours. Thanks.
Re: nvidia driver with systemd causes no sddm at start
Posted: Sat Feb 24, 2024 5:22 am
by catalex54
Eadwine Rose wrote: Sat Feb 24, 2024 4:49 am
I get your intentions, but please make sure that you are not ending up stealing the topic of this user. When folks start responding to your situation in here, direct them to yours. Thanks.
You're right Rose, I'll take your advice.
Thank you