Should Wayland be working with that combo?
If I choose Wayland, it returns to login screen.
This isn’t a terrible problem, I wanted to install best Garuda distribution to a slower laptop. Maybe thinking to get a best processor available to that laptop later. It works about ok now…
Just using it to check internet, mail etc. simple…
System:
Kernel: 6.12.26-1-lts arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: hpet avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=41a9809c-25b6-4bae-a5ec-4a6c3d4e2ead rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
with: xfce4-panel tools: xfce4-screensaver avail: xautolock vt: 7
dm: LightDM v: 1.32.0 Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 7661HS7 v: ThinkPad T61
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 7661HS7 serial: <superuser required>
uuid: <superuser required> BIOS: LENOVO v: 7LETC9WW (2.29 ) date: 03/18/2011
CPU:
Info: model: Intel Core2 Duo T7100 bits: 64 type: MCP arch: Core2 Merom
level: v1 built: 2006-09 process: Intel 65nm family: 6 model-id: 0xF (15)
stepping: 0xD (13) microcode: 0xA4
Topology: cpus: 1x dies: 1 clusters: 1 cores: 2 smt: <unsupported> cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 2 MiB desc: 1x2 MiB
Speed (MHz): avg: 1796 min/max: 800/1801 boost: enabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 1796 2: 1796
bogomips: 7185
Flags: ht lm nx pae sse sse2 sse3 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Lenovo
driver: i915 v: kernel arch: Gen-4 process: Intel 65n built: 2006-07 ports:
active: LVDS-1 empty: DVI-D-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:2a02
class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 compositor: xfwm4 v: 4.20.0 driver:
X: loaded: modesetting alternate: fbdev,intel,vesa dri: crocus gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31")
s-diag: 398mm (15.69")
Monitor-1: LVDS-1 model: Lenovo 0x4031 built: 2007 res: mode: 1280x800
hz: 60 scale: 100% (1) dpi: 107 gamma: 1.2 size: 304x190mm (11.97x7.48")
diag: 358mm (14.1") ratio: 16:10 modes: 1280x800
API: Vulkan v: 1.4.309 layers: 7 device: 0 type: cpu name: llvmpipe (LLVM
19.1.7 128 bits) driver: mesa llvmpipe v: 25.0.5-arch1.1 (LLVM 19.1.7)
device-ID: 10005:0000 surfaces: xcb,xlib
API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Info: Tools: api: vulkaninfo de: xfce4-display-settings
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 82801H HD Audio vendor: Lenovo ThinkPad T61/R61
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:284b
class-ID: 0403
API: ALSA v: k6.12.26-1-lts status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.2 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 82566MM Gigabit Network vendor: Lenovo ThinkPad T61/R61
driver: e1000e v: kernel port: 1840 bus-ID: 00:19.0 chip-ID: 8086:1049
class-ID: 0200
IF: enp0s25 state: down mac: <filter>
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:08b1 class-ID: 0280
IF: wls3 state: up mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Broadcom BCM2045B (BDC-2) [Bluetooth Controller] driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2
chip-ID: 0a5c:2110 class-ID: fe01
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.0
lmp-v: 3 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 223.57 GiB used: 15.73 GiB (7.0%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0102 scheme: MBR
Partition:
ID-1: / raw-size: 215.3 GiB size: 215.3 GiB (100.00%) used: 15.73 GiB (7.3%)
fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 215.3 GiB size: 215.3 GiB (100.00%)
used: 15.73 GiB (7.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 215.3 GiB size: 215.3 GiB (100.00%)
used: 15.73 GiB (7.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 215.3 GiB size: 215.3 GiB (100.00%)
used: 15.73 GiB (7.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 3.75 GiB used: 152.8 MiB (4.0%)
priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
max-streams: 2 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 64.0 C mobo: N/A
Fan Speeds (rpm): fan-1: 3151 fan-2: 3151
Info:
Memory: total: 4 GiB available: 3.75 GiB used: 1.32 GiB (35.3%)
Processes: 233 Power: uptime: 4m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 1.48 GiB services: upowerd,xfce4-power-manager
Init: systemd v: 257 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1395 libs: 428 tools: octopi,pamac,paru
pm: flatpak pkgs: 0 Compilers: gcc: 15.1.1 Shell: garuda-inxi default: fish
v: 4.0.2 running-in: alacritty inxi: 3.3.38
Garuda (2.7.2-1):
System install date: 2025-04-17
Last full system update: 2025-05-06 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: <superuser required>
Failed units:
This CPU does not have an iGPU.
The GPU is part of the chipset and only supports max OpenGL 1.5.
These are the minimum GPU requirements of Garuda Linux:
A graphics card supporting at least OpenGL 3.3
Strangely on KDE-based Garuda distro(s), Wayland worked properly…
Though they were slower.
Anyway, I’ll just be using it with X11, then…
The wayland support under XFCE is experimental. I don’t have XFCE on bare metal - but in a VM, and there the exact same error pattern happens, login to a wayland session results in jumping back to the login screen.
Just use x11, it makes more sense on the old hardware anyway. 
Yes, this was (more or less) how I understood it.
Like, it would be on beta state at 4.20-release…
Haven’t read more about it.
But yes, I’m fine with X11 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.