Hi all
My system are 65% of the time serving a black screen, after the kernel has been started through GRUB. Iβm able to start tty2, and run systemctl restart sddm.service
. Hereafter the login-screen shows up in the tty2 session.
But Iβm searching for a bit of help, to get this fixed. Thereβs a few brilliant threads on this forum, too. But sadly Iβve not found the proper commands and insights. Therefore Iβm trying with my own thread.
Problem
After selecting the kernel in GRUB (normal boot), itβs ending with a black screen, insted of searching the login-screen.
How itβs currently fixed
By opening tty2, Iβm able to call system restart sddm.service
and the login-screen shows, with no problem.
System information
System: Host: exetico-workstation Kernel: 5.9.16-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.21.5 Distro: Manjaro Linux
Machine: Type: Desktop Mobo: ASUSTeK model: TUF Z390M-PRO GAMING (WI-FI) v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2820 date: 01/06/2021
CPU: Info: 6-Core model: Intel Core i7-8700 bits: 64 type: MT MCP cache: L2: 12 MiB
Speed: 4296 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 4296 2: 4300 3: 4300 4: 4300 5: 4300 6: 4300 7: 4300
8: 4300 9: 4300 10: 4300 11: 4301 12: 4298
Graphics: Device-1: Intel UHD Graphics 630 driver: vfio-pci v: 0.2
Device-2: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu
v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu resolution: 1: 2560x1440~60Hz 2: 2560x1440~60Hz
OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.39.0 5.9.16-1-MANJARO LLVM 12.0.0) v: 4.6 Mesa 21.1.2
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.9.16-1-MANJARO running: yes
Sound Server-2: PipeWire v: 0.3.30 running: yes
Network: Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi
IF: wlo1 state: up mac: -removed-
Device-2: Intel Ethernet I219-V driver: e1000e
IF: eno2 state: down mac: -removed-
Bluetooth: Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Drives: Local Storage: total: 1.84 TiB used: 402.05 GiB (21.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 PRO 512GB size: 476.94 GiB
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 PRO 512GB size: 476.94 GiB
ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
Partition: ID-1: / size: 468.16 GiB used: 402.04 GiB (85.9%) fs: ext4 dev: /dev/nvme1n1p2
ID-2: /boot/efi size: 299.4 MiB used: 284 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 33.5 C mobo: 26.0 C gpu: amdgpu temp: 49.0 C
Fan Speeds (RPM): fan-1: 0 fan-2: 2136 fan-3: 983 fan-4: 0 fan-5: 0 fan-6: 1016 fan-7: 0 gpu: amdgpu fan: 0
Info: Processes: 358 Uptime: 4m Memory: 62.68 GiB used: 23.42 GiB (37.4%) Shell: fish inxi: 3.3.04
ββββββββββββββββββ ββββββββ exetico@exetico-workstation
ββββββββββββββββββ ββββββββ OS: Manjaro 21.0.7 Ornara
ββββββββββββββββββ ββββββββ Kernel: x86_64 Linux 5.9.16-1-MANJARO
ββββββββββββββββββ ββββββββ Uptime: 11m
ββββββββ ββββββββ Packages: 1702
ββββββββ ββββββββ ββββββββ Shell: fish 3.2.2
ββββββββ ββββββββ ββββββββ Resolution: 5120x1440
ββββββββ ββββββββ ββββββββ DE: KDE 5.82.0 / Plasma 5.21.5
ββββββββ ββββββββ ββββββββ WM: KWin
ββββββββ ββββββββ ββββββββ GTK Theme: Breath [GTK2/3]
ββββββββ ββββββββ ββββββββ Icon Theme: Deepin Dark
ββββββββ ββββββββ ββββββββ Disk: 404G / 502G (85%)
ββββββββ ββββββββ ββββββββ CPU: Intel Core i7-8700 @ 12x 4.6GHz [48.0Β°C]
ββββββββ ββββββββ ββββββββ GPU: AMD Radeon RX 5700 XT (NAVI10, DRM 3.39.0, 5.9.16-1-MANJARO, LLVM 12.0.0)
RAM: 26717MiB / 64185MiB
So, what can I do?
I would like to know that I can do, to fix this. The most wierd thing is, thatβs itβs working on/off, Iβd guess every 1/3 time or so (by booting normally, and login-screen shows on tty1, with no issues). By booting it multiple times, Iβve fixed it in the part - but normally it takes many reboots. Therefore Iβm now going to tty2 instantly.
UPDATED: Solution
More details here:
Hi @megavolt Thanks for the answer! Itβs a bit fun, cause Iβve thought about a timing issue myself. However, it just didnβt work out in my head, maybe use to the lack of knowledge related to boot-up procedure and service start-ups with GUI-based elements. I must say, I forgot to share the most important informationβ¦ With that said, everything works great - except for the wierd maybe timing-related issue. More details My system are a bit of a mixed bag, cause my Intel Onboard-β¦