Log in Screen not Displaying when CSM Bios Option Disabled

Hi I am trying to enable ReBar on my system. The issue I am facing is when I disable the CSM as the Arch wiki says my log in screen vanishes. It just goes to a black screen. I am still able to log in by typing the password. However, I am not able to switch between Wayland and X11 as a result. So I have to go into bios each time to turn CSM back on to switch sessions. When CSM is back on the log in screen displays again as normal.

Is there was way to switch session from inside an already open session? Or is there a way to fix the log in screen?

garuda-inxi

System:
Kernel: 6.9.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f7654786-2530-47dd-a555-f4f0cbab7b4c rw rootflags=subvol=@
amdgpu.ppfeaturemask=0xffffffff quiet quiet rd.udev.log_priority=3
vt.global_cursor_default=0
resume=UUID=4e7e8ee2-0a7e-4f67-8cf1-2a2aa97cfbe3 loglevel=3
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.2.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X570 AORUS MASTER v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X570 AORUS MASTER serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: F37b
date: 02/08/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 9 3950X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 3548 high: 3962 min/max: 2200/4761 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3500 2: 3500
3: 3600 4: 3500 5: 3500 6: 3500 7: 3590 8: 3500 9: 3500 10: 3500 11: 3500
12: 3596 13: 3613 14: 3500 15: 3536 16: 3500 17: 3500 18: 3500 19: 3500
20: 3500 21: 3500 22: 3600 23: 3582 24: 3500 25: 3598 26: 3500 27: 3500
28: 3500 29: 3639 30: 3962 31: 3628 32: 3617 bogomips: 224017
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Intel DG2 [Arc A310] driver: i915 v: kernel alternate: xe
arch: Gen-12.7 code: Alchemist process: TSMC n6 (7nm) built: 2022+ pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 ports: active: none empty: DP-1, DP-2,
HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 07:00.0 chip-ID: 8086:56a6
class-ID: 0300
Device-2: Blackmagic Design DeckLink Quad HDMI Recorder
driver: blackmagic-io v: 12.9a3 alternate: blackmagic_io pcie: gen: 3
speed: 8 GT/s lanes: 1 link-max: lanes: 8 bus-ID: 0c:00.0
chip-ID: bdbd:a14e class-ID: 0400
Device-3: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
vendor: Sapphire NITRO+ driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x
process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: HDMI-A-4 empty: DP-3, DP-4, HDMI-A-5, Writeback-1
bus-ID: 12:00.0 chip-ID: 1002:744c class-ID: 0300
Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6.2.1:7
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting unloaded: radeon
alternate: fbdev,intel,vesa dri: radeonsi,iris gpu: amdgpu display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: HDMI-A-4 mapped: HDMI-A-3 model: Samsung QBQ90S
serial: <filter> built: 2022 res: 3840x2160 dpi: 52 gamma: 1.2
size: 1872x1053mm (73.7x41.46") diag: 1630mm (64.2") ratio: 16:9 modes:
max: 3840x2160 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris drv: amd radeonsi platforms: device: 0
drv: iris device: 1 drv: radeonsi device: 2 drv: swrast surfaceless:
drv: iris x11: drv: radeonsi inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
navi31 LLVM 17.0.6 DRM 3.57 6.9.3-zen1-1-zen) device-ID: 1002:744c
memory: 23.44 GiB unified: no
API: Vulkan v: 1.3.279 layers: 16 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 XTX (RADV NAVI31) driver: mesa radv v: 24.1.1-arch1.1
device-ID: 1002:744c surfaces: xcb,xlib device: 1 type: discrete-gpu
name: Intel Arc A310 Graphics (DG2) driver: mesa intel v: 24.1.1-arch1.1
device-ID: 8086:56a6 surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
(LLVM 17.0.6 256 bits) driver: mesa llvmpipe v: 24.1.1-arch1.1 (LLVM
17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel DG2 Audio driver: snd_hda_intel v: kernel pcie:
speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s bus-ID: 08:00.0
chip-ID: 8086:4f92 class-ID: 0403
Device-2: Blackmagic Design DeckLink Quad HDMI Recorder
driver: blackmagic-io v: 12.9a3 alternate: blackmagic_io pcie: gen: 3
speed: 8 GT/s lanes: 1 link-max: lanes: 8 bus-ID: 0c:00.0
chip-ID: bdbd:a14e class-ID: 0400
Device-3: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 12:00.1 chip-ID: 1002:ab30
class-ID: 0403
Device-4: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 14:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-5: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6.2.1:7
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Device-6: Blue Microphones Yeti Stereo Microphone
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-2:3 chip-ID: b58e:9e84 class-ID: 0300
serial: <filter>
Device-7: Nam Tai E&E Products or OmniVision Sony Playstation Eye
driver: ov534,snd-usb-audio type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-4:7 chip-ID: 1415:2000 class-ID: 0102
API: ALSA v: k6.9.3-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.0.7 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: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 09:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp9s0 state: down mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: Gigabyte driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 0a:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 0b:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp11s0 state: down mac: <filter>
Device-4: Microsoft Xbox Wireless Adapter for Windows driver: N/A
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6.3:5
chip-ID: 045e:02fe class-ID: 0000 serial: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:2 chip-ID: 8087:0029
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.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 21.39 TiB used: 14.41 TiB (67.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital
model: WD BLACK SN770 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 731100WD temp: 39.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T1XHE-00AFY0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 614600WD temp: 42.9 C
ID-3: /dev/sda maj-min: 8:0 model: Gigaston Prime Series size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 8A0 scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 010
ID-5: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 010
ID-6: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q
ID-7: /dev/sde maj-min: 8:64 vendor: Western Digital
model: WD80EDBZ-11B0ZA0 size: 7.28 TiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1031 scheme: GPT
ID-8: /dev/sdf maj-min: 8:80 vendor: Western Digital
model: WD80EDBZ-11B0ZA0 size: 7.28 TiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1031 scheme: GPT
Partition:
ID-1: / raw-size: 1.75 TiB size: 1.75 TiB (100.00%) used: 588.08 GiB (32.8%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:2
ID-3: /home raw-size: 1.75 TiB size: 1.75 TiB (100.00%)
used: 588.08 GiB (32.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
ID-4: /var/log raw-size: 1.75 TiB size: 1.75 TiB (100.00%)
used: 588.08 GiB (32.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
ID-5: /var/tmp raw-size: 1.75 TiB size: 1.75 TiB (100.00%)
used: 588.08 GiB (32.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.71 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
ID-2: swap-2 type: partition size: 68.99 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:4
Sensors:
System Temperatures: cpu: 43.4 C mobo: 37.0 C gpu: amdgpu temp: 46.0 C
mem: 60.0 C
Fan Speeds (rpm): fan-1: 1061 fan-2: 0 fan-3: 0 gpu: amdgpu fan: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 gpu: amdgpu watts: 15.00
Info:
Memory: total: 64 GiB note: est. available: 62.71 GiB used: 6.31 GiB (10.1%)
Processes: 658 Power: uptime: 24m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.06 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2150 libs: 596 tools: octopi,pamac,paru,pikaur
Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi default: Bash
v: 5.2.26 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-04-19
Last full system update: 2024-06-10
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

Well, you can change this in KDE’s Settings per user; this setting should stick around until changed, so once you get into a new session you should be set.

Open up KDE’s Settings, then go to to SDDM settings and hit the “behavior” button on top. The first line of settings there will let you change the session type per user.

3 Likes

Thanks. Had no clue it could be changed from there.

This will save me having to open the bios each time I want to do something with HDR on Wayland until SDDM starts playing with rebar or I upgrade my PC. Just need to remember to set it back to X11 after each Wayland session. The last system update I ran caused some strange boot behaviour with Wayland and I had to go into X11 before Wayland would boot properly.

Yes the KDE devs are pretty much regretting pushing Wayland instead of waiting for the one x11 replacement to be finalized and just sticking with x11 for now. Not everything needs to beshinny and new, cause a lot of times this day and age shinny and new means broken. Myself I wouldn’t of concentrated on Wayland at all. I would of put all my time in to creating the best Plasma 6.0.0 for x11, and THEN slowly worked towards getting the issues with Wayland fixed for the 6.5.0 release.

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