Garuda-update issues

Hi, there!

I have been using Garuda Gnome as my daily driver since a long time ago (as can be seen in the inxi output below).

When I first installed it, it used the Arch Zen kernel, I have never used the stock Arch kernel but I have the Arch LTS kernel, and currently I use XanMod LTS as my main one.

I am not sure if it is related to my setup, but I experience two issues with garuda-update

  1. I have SKIP_MIRRORLIST=1 in /etc/garuda/garuda-update/config, basically because I want to use my region mirrors for Chaotic-AUR, but every time garuda-update is updated it overwrites the config. Is there any way to make it create a “.pacnew” or “.pacsave” file instead of simply overwriting the custom config? Does it support drop-ins, something like /etc/garuda/garuda-update/config.d/01-skip-mirror?

  2. Although I do not have the stock Arch kernel, every time I run garuda-update is builds and signs the Nvidia modules for it, what is a big waste of time. By the other hand, the Nvidia modules for the kernels that I actually have are left unsigned (I do not use secure boot, so it is not needed, I just think that maybe it is a bug, since it signs the modules for -arch1 kernel).

Thank you for Garuda and all the related (online) services, mainly Chaotic-AUR. Keep up the good work!

  Kernel: 6.1.63-x64v1-xanmod1-1-lts arch: x86_64 bits: 64 compiler: gcc
    v: 13.2.1 clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-xanmod-lts
    root=UUID=9669c171-2745-4424-8de7-ceaed8e22c46 rw rootflags=subvol=@
    quiet splash zswap.enabled=0 rd.udev.log_priority=3
    systemd.unified_cgroup_hierarchy=1 loglevel=3 nowatchdog psi=1
    video=efifb:off ibt=on
  Desktop: GNOME v: 45.1 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM
    v: 45.0.1 Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: Acer product: Aspire A515-55G v: V1.13
    serial: <superuser required>
  Mobo: IL model: Doc_IL v: V1.13 serial: <superuser required> UEFI: Insyde
    v: 1.13 date: 10/15/2020
  ID-1: BAT1 charge: 39.0 Wh (100.0%) condition: 39.0/47.8 Wh (81.5%)
    volts: 12.2 min: 11.2 model: LGC AP18C8K type: Li-ion serial: <filter>
    status: full
  Info: model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake
    gen: core 10 level: v4 note: check built: 2019-21 process: Intel 10nm
    family: 6 model-id: 0x7E (126) stepping: 5 microcode: 0xC2
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 625 high: 1000 min/max: 400/3600 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 1000 3: 400 4: 400
    5: 400 6: 400 7: 1000 8: 1000 bogomips: 19046
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
  Device-1: Intel Iris Plus Graphics G1 vendor: Acer Incorporated ALI
    driver: i915 v: kernel arch: Gen-11 process: Intel 10nm built: 2019-21
    ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:8a56
    class-ID: 0300
  Device-2: NVIDIA GP107M [GeForce MX350] vendor: Acer Incorporated ALI
    driver: nvidia v: 545.29.02 alternate: nvidiafb,nouveau,nvidia_drm
    non-free: 545.xx+ status: current (as of 2023-10; EOL~2026-12-xx)
    arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 1
    speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 02:00.0 chip-ID: 10de:1c94 class-ID: 0302
  Device-3: Quanta HD User Facing driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:4 chip-ID: 0408:a061
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
    compositor: gnome-shell driver: X: loaded: intel,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: i965 gpu: i915
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP1 model: ChiMei InnoLux 0x1509 built: 2018
    res: 1920x1080 hz: 60 dpi: 143 gamma: 1.2 size: 340x190mm (13.39x7.48")
    diag: 394mm (15.5") ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: iris inactive: wayland,device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 23.2.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (ICL GT1)
    device-ID: 8086:8a56 memory: 7.36 GiB unified: yes
  API: Vulkan v: 1.3.269 layers: 18 device: 0 type: integrated-gpu
    name: Intel UHD Graphics (ICL GT1) driver: mesa intel v: 23.2.1-arch1.2
    device-ID: 8086:8a56 surfaces: xcb,xlib device: 1 type: discrete-gpu
    name: NVIDIA GeForce MX350 driver: nvidia v: 545.29.02
    device-ID: 10de:1c94 surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
    (LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
    16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Acer Incorporated ALI
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_icl
    bus-ID: 00:1f.3 chip-ID: 8086:34c8 class-ID: 0403
  API: ALSA v: k6.1.63-x64v1-xanmod1-1-lts status: kernel-api with: 1: osspd
    status: off 2: aoss type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 0.3.85 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
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Lite-On driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 bus-ID: 04:00.0 chip-ID: 168c:003e class-ID: 0280 temp: 44.0 C
  IF: wlp4s0 state: up mac: <filter>
  Device-1: Lite-On driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-10:5 chip-ID: 04ca:3016 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
  Local Storage: total: 704.24 GiB used: 505.81 GiB (71.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: IM2P33F8ABR2-256GB
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: U0513A0L temp: 33.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Apple model: HDD HTS545050A7E362
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: B990 scheme: GPT
  ID-1: / raw-size: 173.19 GiB size: 173.19 GiB (100.00%)
    used: 138.74 GiB (80.1%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 57.7 MiB (22.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 173.19 GiB size: 173.19 GiB (100.00%)
    used: 138.74 GiB (80.1%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-4: /var/log raw-size: 173.19 GiB size: 173.19 GiB (100.00%)
    used: 138.74 GiB (80.1%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-5: /var/tmp raw-size: 173.19 GiB size: 173.19 GiB (100.00%)
    used: 138.74 GiB (80.1%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
  Kernel: swappiness: 100 (default 60) cache-pressure: 500 (default 100)
    zswap: no
  ID-1: swap-1 type: zram size: 7.5 GiB used: 2 MiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
  ID-2: swap-2 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swap/swapfile
  System Temperatures: cpu: 58.0 C mobo: N/A
  Fan Speeds (rpm): N/A
  Processes: 317 Uptime: 1d 12h 22m wakeups: 5 Memory: total: 8 GiB
  available: 7.54 GiB used: 2.97 GiB (39.4%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 alt: 12
  clang: 16.0.6 Packages: 2178 pm: nix-default pkgs: 0 pm: nix-sys pkgs: 0
  pm: nix-usr pkgs: 48 libs: 9 pm: pacman pkgs: 2130 libs: 554
  tools: pamac,paru pm: flatpak pkgs: 0 Shell: Zsh v: 5.9 default: Bash
  v: 5.2.21 running-in: gnome-terminal inxi: 3.3.31
Garuda (2.6.19-2):
  System install date:     2021-11-20
  Last full system update: 2023-11-23 ↻
  Is partially upgraded:   No
  Relevant software:       timeshift NetworkManager mkinitcpio nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

This sounds very much like it shouldn’t happen. Currently, drop-ins are not supported as far as I know, but they would be a great solution to this particular issue. Even better would be providing the default in another place, so /etc would be the user-chosen configuration.


I have basically set that file as immutable so that updates don’t affect it.

sudo chattr +i /etc/garuda/garuda-update/config

to make it mutable and editable again,

sudo chattr -i /etc/garuda/garuda-update/config

to view the attributes of a file,

lsattr /path/to/file
1 Like

I agree this would be a better way to handle this.

It looks like it may be as simple as adding a backup= line to the PKGBUILD:

I won’t have a chance to get in front of a computer today (happy Thanksgiving everyone! :turkey:), but tomorrow I’ll take a crack at it.


Yes, this would be really good!

Thank you for your tip. This would be a workaround, indeed, but then whenever it adds a new option, like what happened recently, one would not notice it.

Fixed in garuda-update 4.3.3:


Very cool, thanks! :hugs:

1 Like

i had issues with setting the immutable flag on a file that gets copied into a snapshot, it rendered all snapshots that contained that file unable to be deleted normally and filled my ssd up.

i couldn’t even change the file in the snapshot because it had inherited its status from the original, so i had to remove the flag on the original and then go and manually remove that flag on all the snapshot copies before removing the old snapshots in their entirety.

here’s a link to my adventures with the immutable flag:


Damn. Well thankfully the file is fixed now (hopefully).

1 Like

Works :slight_smile:



@Michael_joseph Hey, thanks for sharing your experience, I did no know that setting the immutable flag could cause such huge problems with snapshots.

Thanks, this was a quick fix. I can confirm it works:

$ paru -Q | grep garuda-update
garuda-update 4.3.3-1

Also, about the NVidia modules for the -arch1 kernel, it seems that it was my fault: in the past I followed some tip to avoid dependence problems with WINE (I had a game that would not run on my new machine, it ended being a problem with the newer CPU, and the fix was actually changing something in the winblows registry), at the long command also installed linux-headers.

But still I think it is weird that garuda-update only tries to build and sing the NVidia modules for this kernel and not the others that I actually have installed. Anyway, it is a minor issue (for me) since I do not use secure boot.

1 Like

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