Garuda Freezes

Hello.
After installing Garuda ISO into my PC’s second HDD (First SDD has WIndows), Garuda desktop frezzes completely. The cursor still works during a frezze. It starts when moving a windows, cliking, hovering over the dock…
This happened a month ago. I stopped using Garuda regularly hoping to be fixed in a fututre update. Today, I updated via terminal:

sudo pacman -Syu

When finished, I was hovering the cursor over the dock and Garuda freezed.

Note: In the past, I had Fedora and Garuda on the same HDD. Didn’t have problems except to being slow at opening windows and right-click menus. I formated the HDD completely to install Garuda only and improve it (Garuda doesn’t support dual booting)

inxi -Faz

System:
Kernel: 5.15.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=ca4d1028-78e7-45eb-9df1-c821c32402f0 rw rootflags=subvol=@
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUSTeK product: G11CD v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: G11CD v: Rev 1.xx serial: <superuser required>
UEFI: American Megatrends v: 0802 date: 02/03/2016
Battery:
Device-1: hidpp_battery_0 model: Logitech M570 serial: <filter> charge: 40%
rechargeable: yes status: Discharging
CPU:
Info: model: Intel Core i5-6400 bits: 64 type: MCP arch: Skylake-S
family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xEA
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz): avg: 3204 high: 3286 min/max: 800/3300 scaling:
driver: intel_pstate governor: performance cores: 1: 3127 2: 3138 3: 3265
4: 3286 bogomips: 21599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ASUSTeK
driver: nvidia v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
chip-ID: 10de:1c03 class-ID: 0300
Display: x11 server: X.Org 1.21.1.2 compositor: kwin_x11 driver:
loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 75 s-size: 1300x732mm (51.2x28.8")
s-diag: 1492mm (58.7")
Monitor-1: DP-0 res: 3840x2160 hz: 60 dpi: 163
size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
class-ID: 0403
Device-2: NVIDIA GP106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f1
class-ID: 0403
Device-3: Samson Meteor condenser microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-3:3 chip-ID: 17a0:0310
class-ID: 0300
Sound Server-1: ALSA v: k5.15.12-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.42 running: yes
Network:
Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter
vendor: AzureWave driver: rtl8821ae v: kernel port: d000 bus-ID: 03:00.0
chip-ID: 10ec:8821 class-ID: 0280
IF: wlp3s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: c000 bus-ID: 04:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 1-7:4 chip-ID: 13d3:3414 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 6.95 TiB used: 93.11 GiB (1.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SD8SB8U512G1002
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1002 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: DT01ACA100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A7L0
scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate
model: Expansion Desk size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: <filter> rev: 0915 scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Patriot model: N/A
size: 118 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> rev: PMAP scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 23.89 GiB (2.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 23.89 GiB (2.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 23.89 GiB (2.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 23.89 GiB (2.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 50.0 C mobo: 27.8 C gpu: nvidia temp: 43 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 26%
Info:
Processes: 235 Uptime: 21m wakeups: 7 Memory: 15.55 GiB
used: 3.26 GiB (21.0%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1773 lib: 526 Shell: fish
v: 3.3.1 default: Bash v: 5.1.12 running-in: konsole inxi: 3.3.11

Be sure to restart the computer after you had an update to your kernel (even more so since you said you haven't updated in a long time). Your inxi -Faz should report the latest 5.16 zen kernel if you updated recently.

Also, there is an updated bios for your motherboard that "Improve System Stability" , so I would highly recommend to update that. G11CD - Support

2 Likes

In addition to that, I'd suggest a full btrfs balance and maybe giving a look at the compositor settings and play around with them.

2 Likes

If you have installed any plasma widgets be sure to remove them one at a time to find out if any one of them might be responsible.

As your mouse is still working, this is not a complete lock up. That is good, because you should likely have some helpful information regarding errors stored in your logs. If you want tips on which commands to run to find your journal errors, run man journalctl in a terminal window (or perform an internet search).

The cause of freezes is a list of endless possibilities. Every time someone asks this question it is a huge drain on forum resources because the thread can drag on forever.

It is incumbent upon you to make this process as painless as possible for everyone involved. What you need to do is search the forum first, (and then the internet) for possible fixes to this issue.

Start by running a forum search on the following terms:

freeze
frozen
lock up
system freeze
hard lock
hard power down

Any variations of those terms should return tons of hits to comb through. Start writing a list of all suggestions for fixes you uncover and record all results, and inputs and outputs of any commands run. Post regularly the results of your progress. There have been tons of suggestions already given on the forum to fix freezing issue. It is your job to sift through all the possible fixes already posted in the many preexisting threads on this topic on our forum.

Be precise about reporting all your troubleshooting efforts and there is a high probability a solution will be found to your issue.

Good Luck.

Edit:

Oh ya that reminds me of something:

So in a month since this issue began you have attempted no fixes? or did you simply not post the background information as I requested on your last post on this topic.

4 Likes

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