The extra section from my Garuda-Inxi funstuff
/usr/bin/garuda-inxi: line 84: paclog: command not found
Total system updates: 0
--> Updates per week: 0
That’s not right. I update daily.
The extra section from my Garuda-Inxi funstuff
/usr/bin/garuda-inxi: line 84: paclog: command not found
Total system updates: 0
--> Updates per week: 0
That’s not right. I update daily.
The problem is
game-devices-udev-0.23-1
everything else update fine
Nope. Ignoring that package doesn’t fix the issue for me.
Will wait for Announcement as Garuda dev suggested.
You must read
This install
This is what happens when you play Tomb Raider at the same time as troubleshooting, lol.
Total system updates: 514
--> Updates per week: 6
More like it.
There are no known active issus with chaotic-aur right now. If you’re waiting for something to magically fix itself, it will not.
Stick to the standard troubleshooting steps as if nothing changed. You can safely ignore the warning messages about downgrades as well.
A good hint might be clearing the package cache via sudo pacman -Scc
before attempting the update.
Hi.
I have done:
garuda-update remote fix
sudo pacman -Scc
sudo pacman -S chaotic-mirrorlist
still, garuda-update returns:
:: Starting full system upgrade...
warning: kf6-servicemenus-rootactions: local (1.1.0-5) is newer than chaotic-aur (1.1.0-1)
warning: mullvad-browser-bin: local (13.5.7-1) is newer than chaotic-aur (13.5.6-1)
there is nothing to do
garuda-inxi funstuff:
System:
Kernel: 6.11.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=33fb6288-c50e-42ca-bd8f-2e59a8dca84b rw rootflags=subvol=@
quiet loglevel=3 splash ibt=off
Desktop: KDE Plasma v: 6.2.1 tk: Qt v: N/A info: frameworks v: 6.7.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B550M-PLUS v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3405 date: 12/13/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA20102B
Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB
desc: 12x512 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 1727 min/max: 550/4951 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 1727 2: 1727 3: 1727
4: 1727 5: 1727 6: 1727 7: 1727 8: 1727 9: 1727 10: 1727 11: 1727 12: 1727
13: 1727 14: 1727 15: 1727 16: 1727 17: 1727 18: 1727 19: 1727 20: 1727
21: 1727 22: 1727 23: 1727 24: 1727 bogomips: 177605
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
XT/6600M] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, DP-3, HDMI-A-1,
Writeback-1 bus-ID: 09:00.0 chip-ID: 1002:73ff class-ID: 0300
Device-2: Logitech Webcam C170 driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 046d:082b
class-ID: 0102
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.3
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: DP-1 res: 2133x1200 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
LLVM 18.1.8 DRM 3.59 6.11.4-zen1-1-zen) device-ID: 1002:73ff
memory: 7.81 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 7 device: 0 type: discrete-gpu name: AMD
Radeon RX 6600 (RADV NAVI23) driver: mesa radv v: 24.2.5-arch1.1
device-ID: 1002:73ff surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.2.5-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 09:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech Webcam C170 driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 046d:082b
class-ID: 0102
API: ALSA v: k6.11.4-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.5 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: ASUSTeK driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: ASUSTek ASUS USB-BT500 driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2:2 chip-ID: 0b05:190e
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 2.05 TiB used: 1.11 TiB (54.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Seagate model: FireCuda 520 SSD
ZP500GM30002 size: 465.76 GiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: STNSC014
temp: 33.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-00RKKA0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: FireCuda 120 SSD
ZA500GM10001 size: 465.76 GiB block-size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: C013 scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 315.87 GiB (67.9%) 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: 315.87 GiB (67.9%) 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: 315.87 GiB (67.9%) 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: 315.87 GiB (67.9%) 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: 62.71 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.0 C mobo: 26.0 C gpu: amdgpu temp: 36.0 C
mem: 34.0 C
Fan Speeds (rpm): fan-1: 0 fan-2: 996 fan-3: 0 fan-7: 805 gpu: amdgpu
fan: 0
Info:
Memory: total: 64 GiB note: est. available: 62.71 GiB used: 9.19 GiB (14.7%)
Processes: 488 Power: uptime: 41m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.06 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1661 libs: 441 tools: octopi,pamac,paru
pm: flatpak pkgs: 0 Compilers: gcc: 14.2.1 Shell: garuda-inxi default: fish
v: 3.7.1 running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date: 2024-06-21
Last full system update: 2024-10-20 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
Total system updates: 103
--> Updates per week: 6
I could wait but as @TNE stated there is no magic to expect, I am wondering if I need to do something about it?
Post can’t be empty
Does garuda-update -- -u
do the same thing as pacman -Syuu
?
Thank you @dr460nf1r3 , updating chaotic-mirrorlist and clearing cache (in that order as I read this thread that way) did it for me. Update finished.
sudo pacman -S chaotic-mirrorlist
sudo pacman -Scc
Thanks @SGS
So, I let it go and monitor
No, garuda-update is our in house update script that wraps pacman. You should not be using pacman directly to update your system.
Thanks, I know that, and I do it that way. My question was whether both commands do the same thing.
The commands do not do the same thing. garuda-update
is a script that performs quite a list of other actions before/after the pacman execution.
I was actually interested in the pacman -Syuu
command, to get rid of the annoying messages: x is newer than y. But never mind. It’s not important.
Thank you for your efforts!
garuda-update -- -u
adds and extra -u
to the final pacman command. So in effect, it will “fix” the messages (that do not need fixing, to be clear) via the same method as pacman -Syuu
does.
Thanks, I really appreciate your answers.
I didn’t know about the upd -- -u
command and there must be a reason for how I should handle pacman -Syuu
(y,n,i).
I usually update with upd -a --skip-mirrorlist
.
And the next question: is there a list of Gauda-specific package manager commands?
There is a list in the wiki, along with guidance for using the config file to “permanently” set options.
page.lastEditedBy
BluishHumility
01/14/2024
I really should check for wiki updates more often!
Thanks for pointing it out to me.