Manjaro boots into console instead of KDE

Hi,

Manjaro boots just into the console instead of the graphical login screen, and I have no clue how to get it back to rightaway showing the graphical login screen to start KDE. Now, I get the user prompt and after entering username and password I have the console prompt, where I can run startx in order to start KDE, which works fine then.
I don't remember exactly if I changed it on purpose some time ago to boot into the console, because I had severe problems with KDE. Consequently I don't remember what (if) I did to make it happen. Otherwise I would have redone it probably. I checked the grub boot command, there is no "3" at the end of the linux line. The last words are "quiet splash", nothing else.
Any help will be appreciated!

Maybe check

systemctl status sddm
1 Like

I did that. The response was "inactive", so I enabled it with

systemctl enable sddm

But the next time I booted I got the console again. Then I ran

systemctl start sddm

and the login screen popped up. Now the result of

systemctl status sddm

is the following:

● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2019-10-10 08:13:49 CEST; 3min 45s ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
 Main PID: 955 (sddm)
    Tasks: 3 (limit: 4915)
   Memory: 70.4M
   CGroup: /system.slice/sddm.service
           ├─955 /usr/bin/sddm
           └─957 /usr/lib/xorg-server/Xorg -nolisten tcp -auth /var/run/sddm/{3e9662ab-cb48-444f-8e6a-dc4178499441} -background none -noreset -displayf>

However, I'm not yet sure if that solved the problem, because I didn't do a reboot yet. Do you see anything that is not how it should be?

The problem is not solved. I continue to see the console when Manjaro boots up. Using systemctl start sddm fires up the graphical login screen and runs KDE in a different way, it seems (it loads faster than by running startx - at least it feels faster, and some other things work which otherwise wouldn't). I would be glad for some more help, because I'm really at a loss with this.

inxi -Fxxxza --no-host
journalctl -p 3 -xb 

I'm sorry I didn't send a reply earlier, but I didn't get a notification about a new reply to this thread (or I missed it) and was busy with other things.

System:    Kernel: 4.14.149-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.14-x86_64 root=UUID=c5303561-8dbd-4c72-87a3-4789eacda253 rw 
           resume=UUID=fd3c5b9c-411d-4413-be06-b14427915900 quiet splash 
           Desktop: KDE Plasma 5.16.5 tk: Qt 5.13.1 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: Micro-Star model: X470 GAMING PRO (MS-7B79) v: 1.0 serial: <filter> UEFI: American Megatrends 
           v: 1.60 date: 12/17/2018 
CPU:       Topology: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ family: 17 (23) model-id: 8 stepping: 2 
           microcode: 800820B L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 81625 
           Speed: 1376 MHz min/max: 1550/3400 MHz boost: enabled Core speeds (MHz): 1: 1377 2: 1375 3: 1378 4: 1377 5: 1376 
           6: 1377 7: 1376 8: 1374 9: 1494 10: 1384 11: 1377 12: 1377 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Barts LE [Radeon HD 6790] vendor: XFX Pine driver: radeon v: kernel 
           bus ID: 1d:00.0 chip ID: 1002:673e 
           Display: x11 server: X.Org 1.17.4 driver: fbdev FAILED: modesetting unloaded: vesa alternate: ati 
           compositor: kwin_x11 resolution: 1920x1080~N/A 
           OpenGL: renderer: N/A v: N/A direct render: N/A 
Audio:     Device-1: AMD Barts HDMI Audio [Radeon HD 6790/6850/6870 / 7720 OEM] vendor: XFX Pine driver: snd_hda_intel 
           v: kernel bus ID: 1d:00.1 chip ID: 1002:aa88 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
           bus ID: 1f:00.3 chip ID: 1022:1457 
           Sound Server: ALSA v: k4.14.149-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: 2.3LK-NAPI 
           port: f000 bus ID: 18:00.0 chip ID: 10ec:8168 
           IF: enp24s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 11.03 TiB used: 2.37 TiB (21.5%) 
           ID-1: /dev/sda vendor: Western Digital model: WD30EZRX-00SPEB0 size: 2.73 TiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0A80 scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD30EZRX-00D8PB0 size: 2.73 TiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0A80 scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 840 Series size: 111.79 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 6B0Q scheme: MBR 
           ID-4: /dev/sde vendor: Seagate model: ST6000DM003-2CY186 size: 5.46 TiB block size: physical: 4096 B logical: 512 B 
           speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> rev: 0001 scheme: GPT 
Partition: ID-1: / raw size: 73.82 GiB size: 72.54 GiB (98.26%) used: 68.95 GiB (95.0%) fs: ext4 dev: /dev/sdc2 
           ID-2: /home raw size: 5.46 TiB size: 5.41 TiB (99.19%) used: 970.00 GiB (17.5%) fs: ext4 dev: /dev/sde1 
Sensors:   System Temperatures: cpu: 85.4 C mobo: N/A gpu: radeon temp: 41 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 374 Uptime: 6m Memory: 31.43 GiB used: 6.40 GiB (20.4%) Init: systemd v: 242 target: multi-user.target 
           Compilers: gcc: 9.2.0 alt: 6 clang: 9.0.0 Shell: bash v: 5.0.11 running in: konsole inxi: 3.0.36
Okt 27 08:32:47 drmartin-desktop kernel: usb 1-9: device descriptor read/64, error -71
Okt 27 08:32:47 drmartin-desktop kernel: usb 1-9: device descriptor read/64, error -71
Okt 27 08:32:47 drmartin-desktop kernel: usb 1-9: device descriptor read/64, error -71
Okt 27 08:32:47 drmartin-desktop kernel: usb 1-9: device descriptor read/64, error -71
Okt 27 08:32:47 drmartin-desktop kernel: usb 1-9: device not accepting address 4, error -71
Okt 27 08:32:47 drmartin-desktop kernel: usb 1-9: device not accepting address 5, error -71
Okt 27 08:32:47 drmartin-desktop kernel: usb usb1-port9: unable to enumerate USB device
Okt 27 08:32:47 drmartin-desktop systemd-udevd[359]: GOTO 'not_Nvidia' has no matching label in: '/usr/lib/udev/rules.d/51-android.rules'
Okt 27 08:32:47 drmartin-desktop kernel: sp5100_tco: I/O address 0x0cd6 already in use
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90005, and key code 212: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90018, and key code 226: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x9001c, and key code 120: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x9001f, and key code 108: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90020, and key code 103: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x9002d, and key code 217: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x9003d, and key code 148: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90041, and key code 421: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90042, and key code 423: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90043, and key code 397: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90044, and key code 149: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90045, and key code 202: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90046, and key code 203: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x90048, and key code 430: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x9004b, and key code 136: Invalid argument
Okt 27 08:32:48 drmartin-desktop systemd-udevd[424]: event1: Failed to call EVIOCSKEYCODE with scan code 0x9004c, and key code 162: Invalid argument
Okt 27 08:32:49 drmartin-desktop kernel: kfd kfd: kgd2kfd_probe failed
Okt 27 08:32:49 drmartin-desktop systemd-coredump[747]: Process 193 (plymouthd) of user 0 dumped core.
-- Subject: Speicherabbild für Prozess 193 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- Documentation: man:core(5)
-- 
-- Prozess 193 (plymouthd) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.
-- 
-- Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

If you need a translation of the German text:
"... process 193 (plymouthd) was cancelled and a memory dump was created.
Usually this is a hint towards a program bug and should be reported to the respective producer as a bug."

obvious things :
you have a ryzen and kernel 4.14 ... also driver is fbdev instead of amdgpu ... so upgrade your kernel to something new like 5.3 .. and make sure you get amdgpu working by reinstalling open drivers through mhwd.

1 Like

and

are enough to break a system's Xorg :laughing:
...unless you know what you are doing...

Test booting without the splash boot parameter (edit grub menu command line).

Using old radeon driver with legacy xorg server (v.17) is only when nothing else works.

Hi, sorry again for the delay in replying. I installed the 5.3 kernel. I tried the mhwd tool. I get the following, when running mhwd -l -d:

--------------------------------------------------------------------------------
> PCI Device: /devices/pci0000:00/0000:00:03.1/0000:1d:00.0 (0300:1002:673e)
  Display controller ATI Technologies Inc Barts LE [Radeon HD 6790]
--------------------------------------------------------------------------------
  > INSTALLED:

   NAME:        video-ati
   ATTACHED:    PCI
   VERSION:     2017.03.24
   INFO:        X.org ati video driver. Standard open source driver for AMD graphic cards.
   PRIORITY:    2
   FREEDRIVER:  true
   DEPENDS:     -
   CONFLICTS:   video-catalyst video-hybrid-intel-radeon-prime video-hybrid-radeon-amdgpu-prime video-hybrid-intel-ati-bumblebee 
   CLASSIDS:    0300 0380 
   VENDORIDS:   1002 



  > AVAILABLE:

   NAME:        video-catalyst
   ATTACHED:    PCI
   VERSION:     2017.03.12
   INFO:        Closed source catalyst drivers for linux.
   PRIORITY:    5
   FREEDRIVER:  false
   DEPENDS:     -
   CONFLICTS:   -
   CLASSIDS:    0300 
   VENDORIDS:   1002 

   NAME:        video-linux
   ATTACHED:    PCI
   VERSION:     2018.05.04
   INFO:        Standard open source drivers.
   PRIORITY:    2
   FREEDRIVER:  true
   DEPENDS:     -
   CONFLICTS:   -
   CLASSIDS:    0300 0380 0302 
   VENDORIDS:   1002 8086 10de 

   NAME:        video-vesa
   ATTACHED:    PCI
   VERSION:     2017.03.12
   INFO:        X.org vesa video driver.
   PRIORITY:    0
   FREEDRIVER:  true
   DEPENDS:     -
   CONFLICTS:   -
   CLASSIDS:    0300 
   VENDORIDS:   * 


--------------------------------------------------------------------------------
> PCI Device: /devices/pci0000:00/0000:00:01.3/0000:03:00.2/0000:16:01.0/0000:18:00.0 (0200:10ec:8168)
  Network controller Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
--------------------------------------------------------------------------------
  > AVAILABLE:

   NAME:        network-r8168
   ATTACHED:    PCI
   VERSION:     2016.04.20
   INFO:        RealTek RTL-8168 Gigabit Ethernet driver
   PRIORITY:    0
   FREEDRIVER:  true
   DEPENDS:     -
   CONFLICTS:   -
   CLASSIDS:    0200 
   VENDORIDS:   1186 10ec 

When running inxi -G, I get this:

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Barts LE [Radeon HD 6790] driver: radeon v: kernel 
           Display: x11 server: X.Org 1.17.4 driver: fbdev FAILED: modesetting unloaded: vesa resolution: 1920x1080~N/A 
           OpenGL: renderer: N/A v: N/A 

Somehow this seems to contradict, doesn't it? mhwd says that the open source driver is installed (I assume it's amdgpu, but probably I'm wrong), inxi says that fbdev is installed. I'm not sure what to do from here. I consulted the mhwd page and wanted to remove the video-catalyst driver, as this seems to be the only non-free driver. But mhwd replies:

Error: config 'video-catalyst' is not installed!

Thanks for your input so far. I will now try remnoving the splash parameter and tell in a moment what's happened after that.

Removing splash didn't do anything except list the things that were done before showing the login prompt (terminal). Since that passed so quickly that I couldn't grasp anything from the screen, I guess there was no error.

How would I solve the problem (I do not know how this situation came to life, but I'm pretty sure it doesn't need to be that way), i.e. get the newer driver and an up-to-date xorg server?

Normal version of xorg-server is at 1.20.
Yours is at 1.17. It's because you installed catalyst xorg server, which has serious problems, but some users prefer to solve those problems, for their own reasons.

When/while you have decided to do that, you broke your system.

Now you have to install the normal xorg-server.

I don't know a one-line command for this, but I may tell you how you do it.
In terminal TTY

  • Try to install xorg-server with
sudo pacman -Syu "xorg-server>=1.20"

If asked to replace other packages answer yes.

I would search the forum for other similar issues (about catalyst-server), to get an idea what maybe needed.

I did that, but now I can't get to KDE at all. startx or systemctl start sddm produce only a screen with a blinking cursor in the top left corner.
I had to remove before that the catalyst-server with pacman -Rdd.
Edit: startxdoesn't produce that screen, but some error message:

Nö screens found (EE) 

In the X server log I find the message

Failed to load Module "vesa" (Module does not exist, 0)

So you have xorg-server installed. Check

pacman -Qs xorg-
inxi -Gxxxz
mhwd -li

Re-install video drivers

sudo mhwd -i -f video-linux

Thanks a lot for not giving me up. :slight_smile: I did what you suggested. To install the divers, I had to remove a few conflicting libraries, then that worked fine. However, even now I get the same error from startxand systemctl start sddmproduces the blank screen with the blinking cursor.
Output of

is too long (I currently use my mobile), but I see xorg-server 1.20.5-4.1 in the list.

Indicates:

driver: radeon v: Kernel.... 
Display: server: X.org 1.20.5 driver: none alternate: vesa tty: 240x67 
No advanced graphics data found on this system. 

I installed video-linux, it's listed when I run mhwd - li (Version 2018.05.04)

Ok, I'm back in KDE. There seemed to be a problem with the /etc/X11/xorg.conf file. After replacing it with an older copy, it works. Thanks for your help. However, the initial problem still remains: I still boot into the console (tty) instead of the GUI.

1 Like

It's better to delete this file (backup for reference )

Then let's start a new round of providing logs. But better use a pastebin service.
Either follow this:


Or instal pastebinit and pipe all outup into it like this

cat /var/log/Xorg.0.log | pastebinit
cat journalctl -p 3 -xb | pastebinit

Ok, here is the output of cat /var/log/Xorg.0.log | pastebinit:
https://pastebin.com/VCUyUf40

This command didn't give any output, only error message about a wrong option.

should be
journalctl -p 3 -xb | pastebinit

Forum kindly sponsored by