How to switch from Wayland to X11 in Garuda Mokka?

Issues & Assistance
,
21

Please don’t take this the wrong way, but @nepti wants to help you.

From one Austrian to another, I ask that you:

  1. Follow all instructions from the helpers from now on
  2. Stop attempting your own troubleshooting
  3. Stop assuming wayland is the issue.
  4. Stop assuming wayland and Nvidia aren’t compatibile.

Remember that all of us are volunteers and we will not help you if you do not want to be helped.

Well look at that, I have a gaming laptop with a 3070ti + Intel CPU and it works perfectly fine for me.

Seems x11 isn’t working either, right?

I suggest that you let @nepti help you:

  1. Remove envycontrol’s leftovers
  2. Switch to the Intel XE driver

And we will go from there.

3 Likes
22

It was an Optimus laptop (not Advanced Optimus), but the linked nvidia topic also includes some w/o MUX, and they have the same issues as you.

It’s been known for ages that Nvidia doesn’t give a damn about the end-user business, neither on Windows nor on Linux. And no matter what Nvidia messes up, people still buy it and complain. It’s a never-ending story. :wink:

And if that doesn’t help:

then install plasma-x11-session again, try to log into an x11 session (w/o the external monitors!) and post a complete journal of it as soon as something goes wrong. That should help us figure out why x11 isn’t working for you.

2 Likes
23

Hello, I don’t really understand what you mean by Intel XE drivers. Isn’t that for Intel GPUs, rather than integrated ones?

Otherwise could you please tell me the exact name of the driver?

24

Your iGPU is XE architecture.

I already linked to the relevant topic above. This is a kernel driver that you don’t need to install separately:

1 Like
25

I did exactly what you said, changed the intel-xe.cfg, removed unnecessary intel old drivers, updated grub, plasma_x11 installed and tried logging in and I am still stuck at Loading linux-zen kernel and got the black screen. I have disconnected all external monitors and left the hybrid mode on.

Here is the journal snippet of the time I tried logging in with Plasma X11: https://bin.garudalinux.org/?57d6317b962714d0#A7fcQrmJphBiJ76U4pG8jLTkLFTUq1QFymktkoX3sh1E

Also here is a 54k line journal ctl from yesterday + today, when I tried switching to plasma_x11: https://bin.garudalinux.org/?1abe15b8757cc6a4#JE8WjfjtscqHZL4KAysaHuG3VL5fry9AFMzo2z6P888z

26

UPD: Also, apparently I cannot boot with NVIDIA GPU Only mode anymore, which I can change in BIOS. I tried booting without iGPU with disconnected ext monitors, which is what should happen, but I only got black screen (even on Wayland).

27

The ID has to be updated. “a788” in this case.

2 Likes
28

Thanks for the hint.

Regardless, I no longer assume that the Intel iGPU is the cause, but am leaning more towards Nvidia. The first journal is unremarkable and the second too unspecific to indicate a precise cause. You have changed so much in your system during troubleshooting that the actual cause is now more like a moving target that is difficult to hit, and the whole thing has become like looking for a needle in a haystack.

We don’t like to recommend this, and I don’t like to say it, but your installation is still quite new, so a fresh installation makes more sense in order to get a solid and clean starting point.

My suggestion is a clean install (enable hybrid mode in the BIOS and don’t change it again), after which we will try to get x11 running w/o issues (all without external monitors!). As soon as difficulties arise, post a helpful error description and corresponding error messages/logs. Only then, when the system is running w/o issues, will we take care of the multi-monitor setup. Step by step.

1 Like
29

Okay, I will try to fresh install Garuda without any external monitors, exclusively in hybrid mode, then set the grub config with the updated values and install plasma-x11 package.

If the issue persists, I will post a full journal

1 Like
30

Before you install plasma-x11-session, please post a new garuda-inxi. And remember not to connect the external monitors until we ask you to.

1 Like
31

Hello again, I have reinstalled the fresh garuda. The first thing I did is opened the forums to post garuda-inxi: https://bin.garudalinux.org/?8ed6da8ea7d2d1ed#976J6C75yWhGmZGRCdJ1tCKgoy2TADYx9P1yqrmWqFtB
Edit by @nepti:

System:
Kernel: 6.17.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/vmlinuz-linux-zen
root=UUID=51eac4b0-25b6-4040-b6dc-562604310d38 rw rootflags=subvol=@
vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
quiet resume=UUID=71848095-6ed4-4bdb-9ad9-38ffcce98c99 loglevel=3
Desktop: KDE Plasma v: 6.4.5 tk: Qt v: N/A info: frameworks v: 6.19.0
wm: kwin_wayland vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: Razer product: Blade 18 - RZ09-0509 v: 10.04
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Razer model: KI8100 v: 4 serial: <superuser required>
part-nu: RZ09-0509TGK3 uuid: <superuser required> UEFI: Razer v: 1.04
date: 05/06/2024
Battery:
ID-1: BAT0 charge: 46.1 Wh (49.5%) condition: 93/91.7 Wh (101.4%)
volts: 15.37 min: 15.4 model: Razer Blade type: Unknown serial: <filter>
charging: status: not charging cycles: 72
Device-1: ps-controller-battery-a4:ae:12:ca:ac:f4 model: N/A serial: N/A
charge: N/A status: full
CPU:
Info: model: Intel Core i9-14900HX bits: 64 type: MST AMCP arch: Raptor Lake
gen: core 14 level: v3 note: check built: 2022+ process: Intel 7 (10nm)
family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x12F
Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 800 min/max: 800/5600:5800:4100 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800 22: 800 23: 800
24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800
bogomips: 154828
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Raptor Lake-S UHD Graphics vendor: Razer USA driver: i915
v: kernel alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports:
active: eDP-2 empty: DP-4,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:a788
class-ID: 0300
Device-2: NVIDIA AD104M [GeForce RTX 4080 Max-Q / Mobile]
vendor: Razer USA driver: nvidia v: 580.95.05 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-08) arch: Lovelace
code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1, DP-2, DP-3,
HDMI-A-1, eDP-1 bus-ID: 01:00.0 chip-ID: 10de:27e0 class-ID: 0300
Device-3: Luxvisions Innotech Integrated Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 30c9:009e
class-ID: fe01 serial: <filter>
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: gpu: i915 display-ID: 0
Monitor-1: eDP-2 model: BOE Display 0x0c87 built: 2023 res:
mode: 2560x1600 hz: 300 scale: 125% (1.25) to: 2048x1280 dpi: 168 gamma: 1.2
size: 388x242mm (15.28x9.53") diag: 457mm (18") ratio: 16:10
modes: 2560x1600
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: iris device: 3 drv: swrast gbm: drv: iris
surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
inactive: device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.2.4-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
device-ID: 8086:a788 memory: 30.25 GiB unified: yes display-ID: :0.0
API: Vulkan v: 1.4.328 layers: 7 device: 0 type: integrated-gpu
name: Intel Graphics (RPL-S) driver: mesa intel v: 25.2.4-arch1.2
device-ID: 8086:a788 surfaces: N/A device: 1 type: discrete-gpu
name: NVIDIA GeForce RTX 4080 Laptop GPU driver: nvidia v: 580.95.05
device-ID: 10de:27e0 surfaces: N/A device: 2 type: cpu name: llvmpipe
(LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.2.4-arch1.2 (LLVM
20.1.8) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Razer USA
driver: sof-audio-pci-intel-tgl alternate: snd_soc_avs,
snd_sof_pci_intel_tgl, snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:7a50
class-ID: 0401
Device-2: NVIDIA AD104 High Definition Audio vendor: Razer USA
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
Device-3: Sony DualShock 4 [CUH-ZCT2x]
driver: playstation,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-3.3:6 chip-ID: 054c:09cc class-ID: 0300
API: ALSA v: k6.17.2-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.9 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 RTL8125 2.5GbE vendor: Razer USA driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 55:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp85s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
driver: iwlwifi v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 1 link-max:
gen: 4 speed: 16 GT/s bus-ID: 56:00.0 chip-ID: 8086:272b class-ID: 0280
IF: wlp86s0f0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel BE200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:8 chip-ID: 8087:0036
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.4 lmp-v: 13
status: discoverable: no pairing: no
Drives:
Local Storage: total: 1.84 TiB used: 14.64 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVL21T0HCLR-00B00 size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: GXA7801Q temp: 31.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000P310SSD8
size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 10 Gb/s lanes: 1 mode: 3.2 gen-2x1 tech: SSD
serial: <filter> fw-rev: 1.00 scheme: GPT
Partition:
ID-1: / raw-size: 60 GiB size: 60 GiB (100.00%) used: 14.19 GiB (23.6%)
fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-2: /boot raw-size: 10 GiB size: 10 GiB (100.00%) used: 353.2 MiB (3.4%)
fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-3: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 632 KiB (0.1%) fs: vfat dev: /dev/sda2 maj-min: 8:2
ID-4: /home raw-size: 298.5 GiB size: 298.5 GiB (100.00%)
used: 107.3 MiB (0.0%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-5: /var/log raw-size: 60 GiB size: 60 GiB (100.00%)
used: 14.19 GiB (23.6%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-6: /var/tmp raw-size: 60 GiB size: 60 GiB (100.00%)
used: 14.19 GiB (23.6%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.97 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
ID-2: swap-2 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda5 maj-min: 8:5
Sensors:
System Temperatures: cpu: 44.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.97 GiB used: 4.42 GiB (14.3%)
Processes: 572 Power: uptime: 2m states: freeze,mem,disk suspend: s2idle
avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.32 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1328 libs: 347 tools: octopi,paru Compilers:
gcc: 15.2.1 Shell: Bash v: 5.3.3 default: fish v: 4.1.2 running-in: konsole
inxi: 3.3.39
Garuda (2.11.1-1):
System install date:     2025-10-17
Garuda release:          251002
Last full system update: 2025-10-17
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard
Windows dual boot:       Probably (Run as root to verify)
Failed units:
--- System Health Check Report ---
23/24 checks run in 0.84 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.

I will try the grub parameter and plasma-x11 now

32

UDP: Alright, I couldn’t log into the X11 session now again. I’ve booted back (because I was stuck on black screen I had to reboot) and got the journalctl of the last 2 minutes of the X11 issue boot on the system: https://bin.garudalinux.org/?e8ddb5b7ecff6eeb#G7ECeshquQTkZAu3TJQU6ntAKqJsjMbgywLZRfHxM1Hv I hope this is the correct log (I tried cutting the log file to around the time I started with the X11 session). Otherwise (journalctl –list-boots):

image
image1258×467 82.5 KB

So my previous boot is with IDX -1 (X11 logon failure). Here’s the full log of journalctl -b 4a113…SNIP…ae136: https://bin.garudalinux.org/?511981273d81cc1f#33y8pnXDqYYsHGruUeWnCPJyUcKqDZqMj1v4TAEPi4yi

33

I would also like to suggest that you disregard anyone else’s suggestions until @,nepti has completed his troubleshooting efforts. I’m pretty sure that he has a plan with a logical progression to eliminate and identify the causes of your issues. Following other’s suggestions at this point will only further muddy the waters again and make it next to impossible for @nepti to make progress with your issue.

Best to follow @nepti 's plan until he has either resolved your issue, or handed off assistance to others.

You are in good hands with @nepti.

4 Likes
34

Ok, remove the intel-xe.cfg:

sudo rm /etc/default/grub.d/intel-xe.cfg

then:

sudo update-grub

and reboot. After that, try logging into an x11 session again. If you end up with a black screen again, let us know if you can move the mouse pointer, if a tty can be called up, if the system freezes, or whatever else happens.

If you end up on a black screen again and can call up a tty, then:

garuda-diag

and post the generated link here.

I don’t mind when competent people like @TNE get involved - three eyes see more than one…or something like that. :slightly_smiling_face:

5 Likes
35

Of course, but…

:wink:

36

Okay, so I removed the config file.

Just to be clear, this is what I get:

IMG_20251019_185023
IMG_20251019_1850231892×1761 193 KB

So, unfortunately I cannot call a TTY here :frowning:

It goes past this screen on Wayland two times successfully, but on X11 it hangs here. I am not really sure what this is.

I tried clicking any buttons on my keyboard, but to no avail.

37

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.