My garuda linux kde is freezing and showing half of the screen after boot
We need more information to be able to help. Please follow this:
my device is totally frozen. How can I run a command like inxi -Fxxxza
?
Try changing TTY by pressing ctrl + alt + f3, you can login & type any command there then
inxi -Fxxxza
is not running there
Restore a snapshot.
I already clean install Garuda linux kde.
I don't have snapshot. It's first time install
You don't say much, so how anyone can know?
Get in your BIOS and recheck your settings.
Maybe... provide info/details about your system? If you want to, of course...
System:
Kernel: 5.10.4-107-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: intel_pstate=passive
BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq
root=UUID=1519ba5a-3fdd-49de-93e2-5d190615d056 rw rootflags=subvol=@
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1
resume=UUID=093ed383-cb1b-4f22-9d70-7c37a90c29bf loglevel=3
Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
dm: SDDM Distro: Garuda Linux
Machine:
Type: Desktop Mobo: Micro-Star model: A320M-A PRO MAX (MS-7C52) v: 1.0
serial: <filter> UEFI [Legacy]: American Megatrends v: 2.60
date: 06/10/2020
CPU:
Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics
bits: 64 type: MT MCP arch: Zen/Zen+ note: check family: 17 (23)
model-id: 18 (24) stepping: 1 microcode: 8108109 L2 cache: 2 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 59263
Speed: 2861 MHz min/max: N/A Core speeds (MHz): 1: 2861 2: 3023 3: 1250
4: 1392 5: 3021 6: 2957 7: 1668 8: 2449
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Picasso vendor: Micro-Star MSI driver: amdgpu v: kernel
bus ID: 29:00.0 chip ID: 1002:15d8
Display: x11 server: X.Org 1.20.10 compositor: kwin_x11
driver: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa
display ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: HDMI-A-0 res: 1366x768 hz: 60 dpi: 81
size: 430x255mm (16.9x10.0") diag: 500mm (19.7")
OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0
5.10.4-107-tkg-bmq LLVM 11.0.1)
v: 4.6 Mesa 20.3.3 direct render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel bus ID: 29:00.1 chip ID: 1002:15de
Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 29:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k5.10.4-107-tkg-bmq
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: f000
bus ID: 25:00.0 chip ID: 10ec:8168
IF: enp37s0 state: down mac: <filter>
Device-2: Realtek RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter
type: USB driver: usb-network bus ID: 3-4:3 chip ID: 0bda:f179
serial: <filter>
IF-ID-1: enp18s0f0u9 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives:
Local Storage: total: 447.13 GiB used: 17.73 GiB (4.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s serial: <filter> rev: 0102
Partition:
ID-1: / raw size: 100 GiB size: 100 GiB (100.00%)
used: 17.73 GiB (17.7%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-2: /home raw size: 100 GiB size: 100 GiB (100.00%)
used: 17.73 GiB (17.7%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-3: /var/log raw size: 100 GiB size: 100 GiB (100.00%)
used: 17.73 GiB (17.7%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-4: /var/tmp raw size: 100 GiB size: 100 GiB (100.00%)
used: 17.73 GiB (17.7%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
Swap:
Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
ID-2: swap-2 type: zram size: 743.1 MiB used: 516 KiB (0.1%)
priority: 32767 dev: /dev/zram0
ID-3: swap-3 type: zram size: 743.1 MiB used: 412 KiB (0.1%)
priority: 32767 dev: /dev/zram1
ID-4: swap-4 type: zram size: 743.1 MiB used: 532 KiB (0.1%)
priority: 32767 dev: /dev/zram2
ID-5: swap-5 type: zram size: 743.1 MiB used: 436 KiB (0.1%)
priority: 32767 dev: /dev/zram3
ID-6: swap-6 type: zram size: 743.1 MiB used: 512 KiB (0.1%)
priority: 32767 dev: /dev/zram4
ID-7: swap-7 type: zram size: 743.1 MiB used: 448 KiB (0.1%)
priority: 32767 dev: /dev/zram5
ID-8: swap-8 type: zram size: 743.1 MiB used: 228 KiB (0.0%)
priority: 32767 dev: /dev/zram6
ID-9: swap-9 type: zram size: 743.1 MiB used: 244 KiB (0.0%)
priority: 32767 dev: /dev/zram7
Sensors:
System Temperatures: cpu: 39.6 C mobo: N/A gpu: amdgpu temp: 39.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 287 Uptime: 1h 07m wakeups: 0 Memory: 5.81 GiB
used: 2.99 GiB (51.6%) Init: systemd v: 247 Compilers: gcc: 10.2.0
clang: 11.0.1 Packages: pacman: 1573 lib: 494 Shell: fish v: 3.1.2
running in: konsole inxi: 3.2.01
it's my device info from a previous issue
First make all cats go out of your place.
Then we may be able to help.
okay, so what should I do to make it work?
It is well known that cats like to eat human tongues, so people don’t open mouth to talk.
Tell your story, nobody listens.
Why did you install, while you had a system already?
Did you have similar problems on your other system, or they are new?
How did you install it, what selections have you done in the installer?
Is it the 1st boot?
etc., etc,…
Specificity is the watch word!
Looking at the Archwiki, you might try adding a boot parameter in grub
https://wiki.archlinux.org/index.php/Ryzen#Soft_lock_freezing
I also found that people added amd_iommu=on iommu=pt
to boot parameter with success, might try that as well.
okay, So last time when i upgrade my kde it's make the same problem after update. so, I just restore the snapshot and then unfortunately I update that again and then I crashes from every side. I don't have any option. So, I reinstall it , but same issue here
And did you wipe everything thoroughly clean before re-install, or just went immediately the install?
how may I able to add that parameter?
clean the whole partition