New to Garuda - My Garuda freezes for like 5 minutes after start/loading

Hello Community:

My name is Lorena and Im from Argentina (so english is not my first language).

Im new to Garuda and I have basic knowledge of linux (sometimes is hard for me to use/understand Konsole.

Im very happy with my experience with Dragonized so far but Im having some weird issues.

When I turn on the computer, Garuda loads fine but after a minute the system freezes for like 5 minutes or so.Then after waiting,the computer is responsive again. I dont know why this happens…

I was reading in the forum about it but to be honest Im not really sure what to do and how to do all the things that are posted there.

For example,how to do the inxi thing you ask or how to post long texts that I get from Konsole.

Please if somebody can help me and take me step by step I promise I will read and try every possible solution (and at the same time, learn more about this linux garuda).

Thank you in advance

Lorena

╰─λ garuda-inxi
System:
Kernel: 6.7.2-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=2593406b-196e-4d41-b5bd-2f2b9d8294bd rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: A320M-S2H V2 v: N/A
serial:
Mobo: Gigabyte model: A320M-S2H V2-CF v: x.x serial:
UEFI: American Megatrends LLC. v: F54 date: 06/23/2022
CPU:
Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000D
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 835 high: 3039 min/max: 400/4464 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 2990
4: 400 5: 400 6: 3039 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
bogomips: 93423
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities:
Graphics:
Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: Micro-Star MSI
driver: nvidia v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2023-10; EOL~2026-12-xx) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 2
link-max: lanes: 16 ports: active: none off: HDMI-A-1 empty: DVI-D-1,VGA-1
bus-ID: 01:00.0 chip-ID: 10de:1380 class-ID: 0300
Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
vendor: Gigabyte driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: none
empty: DP-1,DVI-D-2,HDMI-A-2 bus-ID: 0a:00.0 chip-ID: 1002:1638
class-ID: 0300 temp: 43.0 C
Display: x11 server: [X.Org](http://x.org/) v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71")
s-diag: 554mm (21.82")
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Samsung S22D300
built: 2013 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2
size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2
memory: 1.95 GiB
API: Vulkan v: 1.3.276 layers: 14 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 750 Ti driver: nvidia v: 545.29.06 device-ID: 10de:1380
surfaces: xcb,xlib device: 1 type: integrated-gpu name: AMD Radeon
Graphics (RADV RENOIR) driver: mesa radv v: 23.3.5-arch1.1
device-ID: 1002:1638 surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.3.5-arch1.1 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA GM107 High Definition Audio [GeForce 940MX]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 2 link-max: lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:0fbc class-ID: 0403
Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 0a:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.6 chip-ID: 1022:15e3
class-ID: 0403
Device-4: Kingston HyperX 7.1 Audio
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 0951:16a4 class-ID: 0300
serial:
API: ALSA v: k6.7.2-zen1-2-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.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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac:
Drives:
Local Storage: total: 1.35 TiB used: 204.02 GiB (14.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT480BX500SSD1
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: fw-rev: 054 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-08WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial:
fw-rev: 1A02 scheme: MBR
Partition:
ID-1: / raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 204.02 GiB (45.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 204.02 GiB (45.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 204.02 GiB (45.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 204.02 GiB (45.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 14.99 GiB used: 2.21 GiB (14.7%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.5 C mobo: 41.0 C
Fan Speeds (rpm): N/A
GPU: device: nvidia screen: :0.0 temp: 44 C fan: 32% device: amdgpu
temp: 44.0 C
Info:
Processes: 357 Uptime: 40m wakeups: 0 Memory: total: 16 GiB note: est.
available: 14.99 GiB used: 2.53 GiB (16.9%) Init: systemd v: 255
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1900 libs: 573 tools: octopi,pamac,paru Shell: fish
v: 3.7.0 running-in: konsole inxi: 3.3.31
Garuda (2.6.22-1):
System install date: 2023-11-25
Last full system update: 2024-02-01
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units: packagekit.service

╭─fleetwood1970@Fleetwood1970 in ~ took 5s
╰─λ~~~

Is this the garuda inxi u are talking about? Hope it is

that is exactly the garuda-inxi, but please instead add it to your main post, and add ~~~ above and blow, so that the inxi gets formatted, which makes it much more readable.

You could look at the clock to find out when it freezes, and then you run journalctl -x, and find the time that your system froze at. Maybe you can find some errors in that timeframe? In case you find something weird, why don’t you just post it here :slight_smile:

1 Like

oook so you want me to see the hour when the compu freezes and look in journalctl -x . Is that journal command that I must put in Konsole? Hope I did the inxi right now… sorry Im learning. and thank you for your help UltraBlack

The inxi is fine now, and please delete that now obsolete comment which has the unformatted inxi :wink:

the hours are gonna be too crude of a scale by themselves. Check for minutes and seconds.

Yes put that into konsole after it just recovered from its freeze and find the time of the freeze in the journal. If you’re in luck, you might be able to find your problem there.

You could also try systemd-analyze blame | head -n 20 right now (please again paste the results here). Maybe you installed something that just takes really long to start.

1 Like
╭─fleetwood1970@Fleetwood1970 in ~
╰─λ journalctl -x
feb 01 22:20:31 Fleetwood1970 kernel: Linux version 6.7.2-zen1-2-zen (linux-zen@archlinux) (gcc (GCC) 13.2.1 >
feb 01 22:20:31 Fleetwood1970 kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=2593406b-1>
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-provided physical RAM map:
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009c3efff] usable
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x0000000009c3f000-0x0000000009ffffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20efff] ACPI NVS
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x000000000a20f000-0x000000000affffff] usable
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000b8a65fff] usable
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000b8a66000-0x00000000ba1a9fff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000ba1aa000-0x00000000ba200fff] ACPI data
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000ba201000-0x00000000bbcbafff] ACPI NVS
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000bbcbb000-0x00000000bcbfefff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000bcbff000-0x00000000bdffffff] usable
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000be000000-0x00000000bfffffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd6fffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
feb 01 22:20:31 Fleetwood1970 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved

╭─fleetwood1970@Fleetwood1970 in ~ took 35s
[🧱] ×

thats what I get… the computer freezes at 14:45 ans again at 15:03… I dont see times there… and that data sayd feb1 and today is feb 2 here

╭─fleetwood1970@Fleetwood1970 in ~
╰─λ systemd-analyze blame | head -n 20
3.284s systemd-modules-load.service
2.251s dev-disk-by\x2duuid-D171\x2d2AFC.device
2.251s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
2.251s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1\x2dpart1.device
2.251s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1.0\x2dpart1.device
2.251s dev-disk-by\x2did-wwn\x2d0x500a0751e632166e\x2dpart1.device
2.251s dev-disk-by\x2dpartuuid-bf9fabed\x2d7283\x2d4412\x2db991\x2d2ad70c9b0529.device
2.251s dev-sda1.device
2.251s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2220E632166E\x2dpart1.device
2.251s dev-disk-by\x2ddiskseq-1\x2dpart1.device
2.227s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1.0\x2dpart2.device
2.227s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1\x2dpart2.device
2.227s dev-disk-by\x2dpartlabel-root.device
2.227s dev-disk-by\x2duuid-2593406b\x2d196e\x2d4d41\x2db5bd\x2d2f2b9d8294bd.device
2.227s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
2.227s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2220E632166E\x2dpart2.device
2.227s dev-disk-by\x2did-wwn\x2d0x500a0751e632166e\x2dpart2.device
2.227s dev-sda2.device
2.227s dev-disk-by\x2dpartuuid-75d4560b\x2d2651\x2d4489\x2d9d96\x2d1d433a49e4c0.device
2.227s dev-disk-by\x2ddiskseq-1\x2dpart2.device

╭─fleetwood1970@Fleetwood1970 in ~ took 402ms
╰─λ

this is what I get from second command you asked - hope i did it ok (absolute chinesse for me)
again thanks for you time and help

  • Format terminal output as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text
1 Like

Is it possible that DISCOVER is doing all this problems??? The computer again freezes when it pops up saying there is an update. Just wondering…ok wait Mr. SGS Garuda is frozen again… Hard resetting.
This is a Titanic Quest with Garuda freezing everytime I start my computer.

Possibly. Please do not use Discover to update, even more so if you install packagekit as an optional dependency because that causes all sorts of issues. Please open up Konsole and use the garuda-update command to update.

3 Likes

Ok then… Can I keep discover to install software? Or should I uninstall? And how do I update the Garuda without it?

Get rid of packagekit.

5 Likes

https://archlinux.org/packages/extra/x86_64/discover/
Even here says “not recommended, use at your own risk” for packagekit.

1 Like

Is there a reason you want to use Discover? if it’s just for flatpak’s then you could use GNOME software instead

What is that? Package kit thing. How I get rid of it.

I didn’t know that

Discover app I read about it somewhere and thought would be easier to find programs and install with it. I’m new to Linux so apps like discover are easy for to use than konsole or octopi

sudo pacman -Rns packagekit

Don’t install stuff you don’t know about.

Bad idea. Install flatpak & flatpak-kcm in KDE, with or without Discover.

4 Likes

Computer still frozen

Reboot. If no solution, at least it’s one down.

You also have nVidia, a major PIA. :frowning:

1 Like