New Update Broke computer

Issues & Assistance
1

My PC feels broken after the new update with tabs and frames stuttering like crazy. Typing words without errror is near impossible because it will stutter back to a point where I hadn’t typed somthings and I miss letters or over type. THIS FEELS AWFUL.

How do I fix this? Even NVIDIA server settings are all barren and broken compared to the last update

System:
Kernel: 6.7.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3e56dd2d-916f-4822-9f3d-d9762a8c38d9 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.1 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG X570S TOMAHAWK MAX WIFI (MS-7D54)
v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.00 date: 07/06/2021
CPU:
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3737 high: 3800 min/max: 2200/4850 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3800 2: 3598
3: 3598 4: 3800 5: 3800 6: 3800 7: 3800 8: 3800 9: 3800 10: 3800 11: 3595
12: 3606 13: 3800 14: 3598 15: 3800 16: 3800 bogomips: 121597
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: ASUSTeK driver: nvidia
v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
(as of 2024-02; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 2 speed: 5 GT/s
lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: none
off: DP-2,HDMI-A-2 empty: DP-1,DP-3,HDMI-A-1 bus-ID: 2d:00.0
chip-ID: 10de:2482 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 3840x1080
display-ID: 0
Monitor-1: DP-2 pos: primary,left res: 1920x1080 size: N/A modes: N/A
Monitor-2: HDMI-A-2 pos: right res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: zink inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
memory: 7.81 GiB display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 11 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 3070 Ti driver: nvidia v: 550.54.14 device-ID: 10de:2482
surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 2d:00.1 chip-ID: 10de:228b class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:2
chip-ID: 0db0:a073 class-ID: 0300
API: ALSA v: k6.7.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.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: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 26:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp38s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 28:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2 chip-ID: 8087:0032
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 4.78 TiB used: 1.03 TiB (21.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 44.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: ST750LM022 HN-M750MBB
size: 698.64 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: MBR
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 333.24 GiB (71.6%) 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: 465.46 GiB size: 465.46 GiB (100.00%)
used: 333.24 GiB (71.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 333.24 GiB (71.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 333.24 GiB (71.6%) 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: 31.26 GiB used: 7 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 41.9 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 6.02 GiB (19.2%)
Processes: 394 Power: uptime: 1h 40m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.47 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1969 libs: 577 tools: octopi,paru Compilers:
clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0
running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2023-12-15
Last full system update: 2024-03-07
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
2

Since you are using Wayland on Nvidia, add the nvidia-drm.modeset=1 kernel parameter using the Garuda Boot Options program. After that, reboot

4

This did not work.

5

adding it after a space should do (do not replace anything).

alternatively, you can try this command instead (although some reason it does not work for everybody)

sudo cp /etc/default/grub /etc/default/grub.bak && sudo sed '/^GRUB_CMDLINE_LINUX_DEFAULT=/s/"$/ nvidia-drm.modeset=1 "/g' -i /etc/default/grub && sudo update-grub

also reboot after

6

Still no dice. Stll a stuttery mess made sure it was spaced and everything is my computer stuck like this?

7

There might be a more complex issue going on with Wayland then. You can try an X11 session from the log-in screen (should be able to click where it says about plasma wayland and select X11 instead) . If that doesn’t work, I would recommend trying rolling back to a prior snapshot and waiting to update for a bit if you can Restoring snapshots to get the system back to working state | Garuda Linux wiki

2 Likes
8

my god… it was wayland the whole time. Whats the difference and why is there a difference and why do they both exist? Thanks for helping me it worked though. Cuz now Im sure something like this has happened before with X11 and wayland.

9

There are many articles you can search for if you are interested. Here is one example:

As for why they both exist, is that Wayland isn’t in a spot where it is perfect for every single user yet. Wayland does have new features its working on like HDR, which x11 can’t ever do.

3 Likes
10

Well X11 isn’t perfect for every user yet either because I have 2 monitors and now am facing a whole different issue of getting my 240 to be 240 and not 60. Do we have a fix for that too?

11

Feel free to correct me if I’m wrong but I think either Wayland or X11 doesn’t support monitors with different refresh rates, I forget which it is. Maybe this is the reason. (?)

12

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