Hello fellow garuda users, hope you’re doing well. Today I require your precious help!
When i am at the login screen Breeze (post boot/logged out), the screen goes black for some period of time, and turns back on. It keeps doing it, in a blinking fashion when at login screen. (Sometimes it would block on a black screen without any action possible)
Once i’m able to setup up my password, and attempt to get to the desktop, the screen goes black and then i’m force to retype my password on another login screen Dr460nized .
After retyping it, it would go black again, until eventually i can manage to brute force into the desktop, and at that point the system operates correctly.
Install graphic drivers as my GPU is Intel Iris Xe Graphics and according to Intel graphics :sudo pacman -S vulkan-intel
Reinstall the desktop environment :sudo pacman -S plasma kde-applications
Install gdm and try to use x11 windowing system instead of wayland: i had same issue, simply worst;
I tried GNOME (Wayland), GNOME on Xorg, Plasma (X11), but most stable is Plasma (Wayland);
Swap to lts;
Add the following to ~/.config/kwinrc:[Compositing]
Backend=OpenGL
GLCore=true
GLLegacy=false
OpenGLIsUnsafe=false
XRenderSmoothScale=false
Here is my garuda-inxi :
System:
Kernel: 6.10.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=81e02914-51a5-4dda-a5c5-0d549f649aa1 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.5.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Laptop System: SAMSUNG product: 750XED v: P08CFG
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: SAMSUNG model: SAMSUNG_NP_750XED
v: SAMSUNG_SW_REVISION_12345+0.0.0000 serial: <superuser required>
part-nu: SCAI-A5A5-A5A5-ADLP-PCFG uuid: <superuser required> UEFI: American
Megatrends LLC. v: P08CFG.033.220913.HQ date: 09/13/2022
Battery:
ID-1: BAT1 charge: 11.8 Wh (22.0%) condition: 53.6/54.4 Wh (98.6%)
volts: 14.7 min: 15.4 model: SAMSUNG Electronics SR Real Battery
type: Li-ion serial: <filter> status: discharging cycles: 158
CPU:
Info: model: 12th Gen Intel Core i7-1255U bits: 64 type: MST AMCP
arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
microcode: 0x433
Topology: cpus: 1x cores: 10 mt: 2 tpc: 2 st: 8 threads: 12 smt: enabled
cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB
L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 860 high: 1033 min/max: 400/4700:3500 scaling:
driver: intel_pstate governor: powersave cores: 1: 832 2: 875 3: 1000 4: 400
5: 613 6: 926 7: 847 8: 1033 9: 1000 10: 1000 11: 794 12: 1010
bogomips: 62668
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] vendor: Samsung Co
driver: i915 v: kernel alternate: xe arch: Gen-12.2 process: Intel 10nm
built: 2021-22+ ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:46a8 class-ID: 0300
Device-2: SunplusIT 720p HD Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-8:3 chip-ID: 5959:1502
class-ID: 0e02 serial: <filter>
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 res: 1600x900 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
device-ID: 8086:46a8 memory: 7.48 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 3 device: 0 type: integrated-gpu name: Intel
Graphics (ADL GT2) driver: mesa intel v: 24.2.1-arch1.1
device-ID: 8086:46a8 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.2.1-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Samsung Co
driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel, snd_soc_avs,
snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8 class-ID: 0401
API: ALSA v: k6.10.6-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.3 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 Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:51f0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 476.94 GiB used: 27.24 GiB (5.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLQ512HBLU-00B
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: FXM7AK1Q temp: 27.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 27.23 GiB (5.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
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:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 27.23 GiB (5.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 27.23 GiB (5.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 27.23 GiB (5.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.32 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.32 GiB used: 3.71 GiB (24.2%)
Processes: 314 Power: uptime: 11h 7m states: freeze,mem,disk
suspend: s2idle avail: deep wakeups: 6 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 6.12 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1296 libs: 373 tools: octopi,paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.35
Garuda (2.6.26-1):
System install date: 2024-08-07
Last full system update: 2024-09-01 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
Here you have extra logs (if needed):
are you attempting to install garuda linux? “setup up my password”
I have it installed already. I’m struggling all the time to reach desktop.
maybe set all your theme and login stuff to breeze dark or something.
This has no effect, and i don’t think this is whats causing the black screen-sleep effect.
I have already followed this tutorial couple times, this does not solve my issue, also the
sudo reflector -a6 -f5 --save /etc/pacman.d/mirrorlist
leads to this:
and sudo dkms autoinstall prints nothing.
SGS
2 September 2024 21:16
8
Please no pictures from terminal and system settings,
I use up alias, from time to time, to refresh the mirror list, but garuda-update will do the same for the user worldwide.
alias up='sudo reflector --country Germany --latest 5 --age 2 --fastest 5 --protocol https --sort rate --save /etc/pacman.d/mirrorlist && bat /etc/pacman.d/mirrorlist && sudo pacman -Syu'
Sorry for the picture was unaware. I like the tip, unfortunately the result: 'there is nothing to do'. (Yes i did change the country).
SGS
2 September 2024 21:31
10
If you got a lot of warnings, maybe the internet connection failed or something else but
--> Updating AUR packages with paru...
:: Check for devel upgrades...
there is nothing to do
System updated! 🐧
show you the system is up-to-date.
Best is, to post the full terminal command and the output preformatted as text
Well i’ve finally regrouped the informations that explains this behavior:
sept. 02 23:26:30 kodascii kernel: Low-power S0 idle used by default for system suspend
sept. 02 23:26:31 kodascii kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
sept. 02 23:26:56 kodascii ModemManager[764]: <msg> [sleep-monitor-systemd] system is about to suspend
sept. 02 23:26:56 kodascii NetworkManager[713]: <info> [1725312416.8880] manager: sleep: sleep requested (sleeping: no enabled: yes)
sept. 02 23:26:56 kodascii NetworkManager[713]: <info> [1725312416.8881] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 02 23:26:56 kodascii NetworkManager[713]: <info> [1725312416.8887] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
sept. 02 23:26:57 kodascii NetworkManager[713]: <info> [1725312417.0072] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
sept. 02 23:26:57 kodascii NetworkManager[713]: <info> [1725312417.0415] device (wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 02 23:26:57 kodascii systemd-sleep[1352]: Successfully froze unit 'user.slice'.
sept. 02 23:26:57 kodascii systemd-sleep[1352]: Performing sleep operation 'suspend'...
sept. 02 23:26:57 kodascii kernel: PM: suspend entry (s2idle)
sept. 02 23:27:24 kodascii kernel: printk: Suspending console(s) (use no_console_suspend to debug)
sept. 02 23:27:24 kodascii systemd-sleep[1352]: System returned from sleep operation 'suspend'.
sept. 02 23:27:24 kodascii kernel: PM: suspend exit
sept. 02 23:27:24 kodascii systemd-sleep[1352]: Successfully thawed unit 'user.slice'.
sept. 02 23:27:24 kodascii systemd[1]: systemd-suspend.service: Deactivated successfully.
sept. 02 23:27:24 kodascii systemd-logind[721]: Operation 'suspend' finished.
sept. 02 23:27:24 kodascii ModemManager[764]: <msg> [sleep-monitor-systemd] system is resuming
sept. 02 23:27:24 kodascii NetworkManager[713]: <info> [1725312444.7612] manager: sleep: wake requested (sleeping: yes enabled: yes)
sept. 02 23:27:46 kodascii systemd-logind[721]: The system will suspend now!
sept. 02 23:27:46 kodascii NetworkManager[713]: <info> [1725312466.4391] manager: sleep: sleep requested (sleeping: no enabled: yes)
sept. 02 23:27:46 kodascii ModemManager[764]: <msg> [sleep-monitor-systemd] system is about to suspend
sept. 02 23:27:46 kodascii NetworkManager[713]: <info> [1725312466.4393] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 02 23:27:46 kodascii NetworkManager[713]: <info> [1725312466.4397] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
sept. 02 23:27:46 kodascii NetworkManager[713]: <info> [1725312466.5809] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
sept. 02 23:27:46 kodascii NetworkManager[713]: <info> [1725312466.5986] device (wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 02 23:27:46 kodascii systemd-sleep[2675]: Successfully froze unit 'user.slice'.
sept. 02 23:27:46 kodascii systemd-sleep[2675]: Performing sleep operation 'suspend'...
sept. 02 23:27:46 kodascii kernel: PM: suspend entry (s2idle)
sept. 02 23:28:36 kodascii kernel: printk: Suspending console(s) (use no_console_suspend to debug)
sept. 02 23:28:36 kodascii systemd-sleep[2675]: System returned from sleep operation 'suspend'.
sept. 02 23:28:36 kodascii kernel: PM: suspend exit
sept. 02 23:28:36 kodascii systemd-sleep[2675]: Successfully thawed unit 'user.slice'.
sept. 02 23:28:36 kodascii systemd[1]: systemd-suspend.service: Deactivated successfully.
sept. 02 23:28:36 kodascii systemd-logind[721]: Operation 'suspend' finished.
sept. 02 23:28:36 kodascii NetworkManager[713]: <info> [1725312516.7839] manager: sleep: wake requested (sleeping: yes enabled: yes)
sept. 02 23:28:36 kodascii ModemManager[764]: <msg> [sleep-monitor-systemd] system is resuming
sept. 03 00:28:09 kodascii systemd-logind[721]: The system will suspend now!
sept. 03 00:28:09 kodascii NetworkManager[713]: <info> [1725316089.8683] manager: sleep: sleep requested (sleeping: no enabled: yes)
sept. 03 00:28:09 kodascii NetworkManager[713]: <info> [1725316089.8684] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 03 00:28:09 kodascii ModemManager[764]: <msg> [sleep-monitor-systemd] system is about to suspend
sept. 03 00:28:09 kodascii NetworkManager[713]: <info> [1725316089.8690] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
sept. 03 00:28:09 kodascii NetworkManager[713]: <info> [1725316089.9837] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
sept. 03 00:28:10 kodascii NetworkManager[713]: <info> [1725316090.0035] device (wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 03 00:28:10 kodascii systemd-sleep[10468]: Successfully froze unit 'user.slice'.
sept. 03 00:28:10 kodascii systemd-sleep[10468]: Performing sleep operation 'suspend'...
sept. 03 00:28:10 kodascii kernel: PM: suspend entry (s2idle)
sept. 03 00:29:19 kodascii kernel: printk: Suspending console(s) (use no_console_suspend to debug)
sept. 03 00:29:19 kodascii systemd-sleep[10468]: System returned from sleep operation 'suspend'.
sept. 03 00:29:19 kodascii kernel: PM: suspend exit
sept. 03 00:29:19 kodascii ModemManager[764]: <msg> [sleep-monitor-systemd] system is resuming
sept. 03 00:29:19 kodascii systemd-sleep[10468]: Successfully thawed unit 'user.slice'.
sept. 03 00:29:19 kodascii systemd[1]: systemd-suspend.service: Deactivated successfully.
sept. 03 00:29:19 kodascii systemd-logind[721]: Operation 'suspend' finished.
sept. 03 00:29:19 kodascii NetworkManager[713]: <info> [1725316159.7920] manager: sleep: wake requested (sleeping: yes enabled: yes)
I manage to make it much better, I have a problem with the Power Management settings.
Here are what changes i’ve made :
So i have found multiple of theses in my journalctl:
sept. 03 16:45:11 kodascii systemd-logind[733]: Suspending...
sept. 03 16:45:11 kodascii ModemManager[771]: <msg> [sleep-monitor-systemd] system is about to suspend
sept. 03 16:45:11 kodascii ModemManager[771]: <wrn> [sleep-monitor-systemd] inhibit failed: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running
sept. 03 16:45:11 kodascii systemd-sleep[1402]: Successfully froze unit 'user.slice'.
sept. 03 16:45:11 kodascii systemd-sleep[1402]: Performing sleep operation 'suspend'...
now i have no idea why its suspending my system when its at login screen, or after i have enter my password. I tried multiple solutions but one that helped was to change my Power Management settings, by setting Do nothing to both “After a period of inactivity” and “When laptop lid closed” , for each power state:
Do somebody knows why is this happening ?
