Manjaro not booting in to GUI after kernel upgrade to linux510

Hi there,

I’m here to get some expert help. I’ve been using Manjaro Community i3wm for more than a 1.5 years now. I stated off with Kernel 4.19 and then moved to 5.4 and everything was just fine.

Now when I moved to kernel 5.10 (also installed others 5.15, 5.19 to get to GUI) but nothing seems to work. I would like to get some expert help to get my system booting in to GUI. Thank you for your help :slight_smile:

As of now things that I have tried:

  1. Installing new kernel 5.10 and attempting to get to GUI > Failed
  2. I can get to grub selection just fine without any issues. After choosing 5.10 kernel I just have blinking cursor. In case of 5.15 kernel cursor is not even blinking.


System > Dell XPS 13" 7390

Output of inxi -Fza while in chroot:

sh-5.1# inxi -Fazy --color=0
  Kernel: 5.15.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_XFCE_2137 quiet
    systemd.show_status=1 apparmor=1 security=apparmor driver=free
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
  Desktop: Xfce v: 4.16.5 info: xfce4-panel wm: xfwm vt: 7 dm: N/A
    Distro: Manjaro Linux base: Arch Linux
  Type: Laptop System: Dell product: XPS 13 7390 v: N/A serial: <filter>
    Chassis: type: 10 serial: <filter>
  Mobo: Dell model: 068V0G v: A00 serial: <filter> UEFI: Dell v: 1.11.0
    date: 09/28/2021
  ID-1: BAT0 charge: 38.1 Wh (100.0%) condition: 38.1/52.0 Wh (73.3%)
    volts: 8.3 min: 7.6 model: LGC-LGC6.73 DELL H754V0C type: Li-ion
    serial: <filter> status: full
  Info: model: Intel Core i7-10710U socket: BGA1528 bits: 64 type: MT MCP
    arch: Comet Lake gen: core 10 level: v3 note: check built: 2020
    process: Intel 14nm family: 6 model-id: 0xA6 (166) stepping: 0
    microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 727 high: 800 min/max: 400/4700 base/boost: 3267/1600
    scaling: driver: intel_pstate governor: powersave volts: 1.0 V
    ext-clock: 100 MHz cores: 1: 800 2: 800 3: 700 4: 700 5: 700 6: 700 7: 700
    8: 700 9: 700 10: 700 11: 800 12: 733 bogomips: 38415
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: Intel Comet Lake UHD Graphics vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,DP-2,DP-3 bus-ID: 00:02.0 chip-ID: 8086:9bca class-ID: 0300
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:3 chip-ID: 0c45:6723 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
    compositor: xfwm driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: AU Optronics 0x5b2d built: 2018 res: 1920x1080
    hz: 60 dpi: 166 gamma: 1.2 size: 293x162mm (11.54x6.38") diag: 335mm (13.2")
    ratio: 16:9 modes: 1920x1080
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo missing.
  Device-1: Intel Comet Lake PCH-LP cAVS vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403
  Sound API: ALSA v: k5.15.60-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.59 running: yes
  Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-7:4
    chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
  Local Storage: total: 491.38 GiB used: 187.78 GiB (38.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA
    model: KXG60ZNV512G NVMe 512GB size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 10604107 temp: 37.9 C
  ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Kingston
    model: DataTraveler 3.0 size: 14.44 GiB block-size: physical: 512 B
    logical: 512 B type: N/A serial: <filter> rev: PMAP
  ID-1: / raw-size: 459.77 GiB size: 451.49 GiB (98.20%)
    used: 187.53 GiB (41.5%) fs: ext4 block-size: 4096 B dev: /dev/dm-0
    maj-min: 254:0 mapped: r
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 254.2 MiB (84.9%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1
  Alert: No swap data was found.
  System Temperatures: cpu: 46.0 C pch: 43.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0 fan-2: 0
  Processes: 300 Uptime: 1h 13m wakeups: 7789 Memory: 15.33 GiB
  used: 2.92 GiB (19.1%) Init: systemd v: 251 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: dpkg
  pkgs: 0 pm: pacman pkgs: 1843 libs: 408 tools: pamac,yay
  Client: Unknown Client: systemd inxi: 3.3.23

Output mhwd -li while in chroot:

sh-5.1# mhwd -li
> Installed PCI configs:
                  NAME               VERSION          FREEDRIVER           TYPE
           video-linux            2018.05.04                true            PCI
            video-vesa            2017.03.12                true            PCI
     video-modesetting            2020.01.13                true            PCI

Warning: No installed USB configs!

As per the posts I went through earlier video-vesa and video-modesetting can be removed. I attempted to do that but it never got me to the GUI after grub menu. Also I can not get to other TTY console by hitting Ctrl + Alt + F# keys when I’m looking at blinking cursor.

Since you have installed video-vesa, I would expect a configuration file: /etc/X11/xorg.conf.d/90-mhwd.conf. Otherwise it will fail.

Have a look at /var/log/Xorg.0.log :wink:

Yes the file is present, here’s the content of /etc/X11/xorg.conf.d/90-mhwd.conf :

sh-5.1# cat /etc/X11/xorg.conf.d/90-mhwd.conf 
## Generated by mhwd - Manjaro Hardware Detection
Section "Device"
    Identifier  "Device0"
    Driver      "vesa"
    BusID       "PCI:0:2:0"
	Option      "DRI"    "true"
Section "DRI"
        Group  "video"
        Mode   0666
Section "Extensions"
    Option "Composite" "Enable"
    Option "RENDER"    "Enable"
Section "InputClass"
    Identifier          "Keyboard Defaults"
    MatchIsKeyboard        "yes"
    Option              "XkbOptions" "terminate:ctrl_alt_bksp"

I’m going through the Xorg.0.log now. Can you please tell me what I should look for in /var/log/Xorg.0.log?


Look for errors :smile:

Can you explain why you would use the generic vesa driver when you can use the intel (i915) driver? Make literally no sense to me.

LOL :sweat_smile: @megavolt

Got the error about vesa:

sh-5.1# cat /var/log/Xorg.0.log | grep vesa 
[    13.134] (==) Matched vesa as autoconfigured driver 2
[    13.135] (II) LoadModule: "vesa"
[    13.135] (WW) Warning, couldn't open module vesa
[    13.135] (EE) Failed to load module "vesa" (module does not exist, 0)

Should I just remove video-vesa and attempt to boot?

Yes and keep sure the config file is deleted or empty.

Is it okay to keep video-modesetting or I should get rid of that as well? I’m in chroot now. Just want to make sure if video-modesetting should be there or not.

Thank you @megavolt for your help :slight_smile:

It is okay… the intel driver runs in modsetting mode anyway:

Btw… next time disable colors for inxi to avoid all these “12”: inxi -Fazy --color=0 Some consoles copy that aswell (Konsole of KDE?)

Cool. Just updated the inxi -Fazy --color=0 in the original post. Let me try to see if I can get to the GUI. Moment of truth :crossed_fingers:

Nope that didn’t help. Getting the same blinking cursor screen with message:

0.173010] Spectre V2 : WARNING: Unprivileged eBPF is enabled with elBRS on,
data leaks possible via Spectre v2 BHB attacks!

I’m not sure which logs to get to. I can not get to other TTY console with CTRL+ALT+F# keys while on the blinking cursor :frowning:

Well that is a security risk. Typically it is not enabled by default, so guess you enabled it.

This is a warning about something completely unrelated.

Yeah the warning is not related to the underlying issue here. Can you please tell me what I need to do in this case to get to successful boot in to the GUI? Which logs I need to inspect?