seems minor so no huge rush.
❯ garuda-inxi funstuff
System:
Kernel: 6.6.1-zen1-1-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=63f3c83e-5747-44de-974f-c89d4101bd95 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=c0d4fb48-27bb-458a-9d32-db4bea9d7420 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: MSI model: Z77A-GD55 (MS-7751) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.11
date: 11/20/2013
CPU:
Info: model: Intel Core i7-3770K bits: 64 type: MT MCP arch: Ivy Bridge
gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3368 high: 3900 min/max: 1600/3900 scaling:
driver: intel_cpufreq governor: performance cores: 1: 3900 2: 1672 3: 3900
4: 3900 5: 3900 6: 3900 7: 3900 8: 1872 bogomips: 56002
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-1 code: Navi-1x
process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-3 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 03:00.0
chip-ID: 1002:731f class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: DP-3 mapped: DisplayPort-2 model: Asus VX238 serial: <filter>
built: 2015 res: 1920x1080 hz: 60 dpi: 96 gamma: 1.2
size: 510x290mm (20.08x11.42") diag: 587mm (23.1") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5600 XT (navi10 LLVM
16.0.6 DRM 3.54 6.6.1-zen1-1-zen) device-ID: 1002:731f memory: 5.86 GiB
unified: no
API: Vulkan v: 1.3.269 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon RX 5600 XT (RADV NAVI10) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:731f surfaces: xcb,xlib device: 1 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
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio
vendor: Micro-Star MSI 7 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:1e20 class-ID: 0403
Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab38
class-ID: 0403
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.84 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: Intel 82579V Gigabit Network vendor: Micro-Star MSI driver: e1000e
v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
mac: <filter>
IF-ID-2: proton0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
IF-ID-3: pvpnksintrf0 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives:
Local Storage: total: 2.91 TiB used: 449.93 GiB (15.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SH103S3120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: BBF0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: SH103S3120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: BBF0 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0107 scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0107 scheme: GPT
ID-5: /dev/sde maj-min: 8:64 vendor: Western Digital
model: WD20EZRX-00D8PB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
scheme: MBR
Partition:
ID-1: / raw-size: 39.75 GiB size: 39.75 GiB (100.00%)
used: 16.61 GiB (41.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /boot/efi raw-size: 513 MiB size: 512 MiB (99.80%)
used: 576 KiB (0.1%) fs: vfat dev: /dev/sda4 maj-min: 8:4
ID-3: /home raw-size: 71.04 GiB size: 71.04 GiB (100.00%)
used: 17.04 GiB (24.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 39.75 GiB size: 39.75 GiB (100.00%)
used: 16.61 GiB (41.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-5: /var/tmp raw-size: 39.75 GiB size: 39.75 GiB (100.00%)
used: 16.61 GiB (41.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 23.42 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
ID-2: swap-2 type: partition size: 512 MiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A gpu: amdgpu temp: 41.0 C
mem: 40.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Processes: 311 Uptime: 3m wakeups: 0 Memory: total: 24 GiB
available: 23.42 GiB used: 2.84 GiB (12.1%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 2044 libs: 583 tools: octopi,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
Garuda (2.6.17-1):
System install date: 2023-04-12
Last full system update: 2023-11-08 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager mkinitcpio
Windows dual boot: Probably (Run as root to verify)
Failed units:
Total system updates: 52
--> Updates per week: 1
Uptime: 3 mins
all i’ve done is redo some minor grub theme changes since the newest update to grub-theme-garuda-dr460nized-r3.b40584e-1 earlier today, since this package update always resets my chosen background image and my GRUB_GFXMODE=1920x1080x32 resolution setting.
how i set the grub background is to use dolphin as root to copypasta a replacement image with an identical file name into the theme’s installation folder at /usr/share/grub/themes/garuda-dr460nized.
i also removed GRUB_TOP_LEVEL="/boot/vmlinuz-linux-lts" from etc/default/grub to resume booting the zen kernel as normal.
i made the changes and then used ‘update-grub’ to set them and my only currently known issue is that garuda-inxi is reporting a reset needed even after a system reset and full shutdown/restart.
thanks G-team =-)
Bro
9 November 2023 03:08
2
Do it again once or twice, if that doesn’t work, then try ‘garuda-update’ and/or ‘update remote fix’ in a terminal. Any help?
1 Like
SGS
9 November 2023 05:03
4
Is the path and name
/usr/share/grub/themes/garuda/background.png
sudo cp your.pic.png /usr/share/grub/themes/garuda/background.png
1 Like
yeah, i copy/paste a different image with the same name so i don’t have to mess with configs beyond the gfxmode setting.
Hm, the “should reboot” logic is here:
fish❯ bat /bin/garuda-inxi
...
61 │ generate_system_update() {
62 │ local last_update
63 │ last_update="$(date -r /var/lib/garuda/last_update +%s 2> /dev/null)" || { echo "Unknown/Never"; return; }
64 │ local reboot=""
65 │ if [ "$last_update" -gt "$(date -r /proc +%s)" ]; then
66 │ reboot=" ${c_131}↻${c_off}"
67 │ fi
68 │ echo -e "$(date -d"@$last_update" +%F)${reboot}"
69 │ }
70 │
I’d say the date on /var/lib/garuda/last_update got messed up, but why?
3 Likes
The script appears to retrieve the last update timestamp from a file in /var/lib/garuda/last_update and store it as the last_update variable, then it checks whether the last_update timestamp is greater than the timestamp of /proc (which should represent the current system time). If last_update is greater, it sets the reboot variable to the reboot icon (“↻”).
Check the timestamps in /var/lib/garuda/last_update and /proc directly and see if you can spot any weirdness there.
Is your system time accurate? The time zones are correctly configured?
3 Likes
this file is completely blank and is 0 bytes, i opened it with kate as user and as admin to double-check.
That is normal, it’s just a “placeholder” file to record the date.
fish❯ ll /var/lib/garuda/last_update
.rw-r--r-- 0 root 9 nov 11:00 /var/lib/garuda/last_update
1 Like
okay cool.
my area had a power grid failure last night while my system was active - twice my machine was hard-reset due to this.
my garuda-inxi from a few moments ago:
❯ garuda-inxi funstuff
System:
Kernel: 6.6.1-zen1-1-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=63f3c83e-5747-44de-974f-c89d4101bd95 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=c0d4fb48-27bb-458a-9d32-db4bea9d7420 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: MSI model: Z77A-GD55 (MS-7751) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.11
date: 11/20/2013
CPU:
Info: model: Intel Core i7-3770K bits: 64 type: MT MCP arch: Ivy Bridge
gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 2847 high: 3836 min/max: 1600/3900 scaling:
driver: intel_cpufreq governor: performance cores: 1: 1600 2: 3486 3: 3828
4: 1600 5: 3033 6: 1600 7: 3836 8: 3797 bogomips: 56001
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-1 code: Navi-1x
process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-3 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 03:00.0
chip-ID: 1002:731f class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: DP-3 mapped: DisplayPort-2 model: Asus VX238 serial: <filter>
built: 2015 res: 1920x1080 hz: 60 dpi: 96 gamma: 1.2
size: 510x290mm (20.08x11.42") diag: 587mm (23.1") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5600 XT (navi10 LLVM
16.0.6 DRM 3.54 6.6.1-zen1-1-zen) device-ID: 1002:731f memory: 5.86 GiB
unified: no
API: Vulkan v: 1.3.269 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon RX 5600 XT (RADV NAVI10) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:731f surfaces: xcb,xlib device: 1 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
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio
vendor: Micro-Star MSI 7 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:1e20 class-ID: 0403
Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab38
class-ID: 0403
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.84 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: Intel 82579V Gigabit Network vendor: Micro-Star MSI driver: e1000e
v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
mac: <filter>
IF-ID-2: proton0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
IF-ID-3: pvpnksintrf0 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives:
Local Storage: total: 2.91 TiB used: 447.65 GiB (15.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SH103S3120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: BBF0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: SH103S3120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: BBF0 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0107 scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0107 scheme: GPT
ID-5: /dev/sde maj-min: 8:64 vendor: Western Digital
model: WD20EZRX-00D8PB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
scheme: MBR
Partition:
ID-1: / raw-size: 39.75 GiB size: 39.75 GiB (100.00%)
used: 14.49 GiB (36.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /boot/efi raw-size: 513 MiB size: 512 MiB (99.80%)
used: 576 KiB (0.1%) fs: vfat dev: /dev/sda4 maj-min: 8:4
ID-3: /home raw-size: 71.04 GiB size: 71.04 GiB (100.00%)
used: 16.88 GiB (23.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 39.75 GiB size: 39.75 GiB (100.00%)
used: 14.49 GiB (36.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-5: /var/tmp raw-size: 39.75 GiB size: 39.75 GiB (100.00%)
used: 14.49 GiB (36.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 23.42 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
ID-2: swap-2 type: partition size: 512 MiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 46.0 C mobo: N/A gpu: amdgpu temp: 41.0 C
mem: 40.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Processes: 310 Uptime: 34m wakeups: 0 Memory: total: 24 GiB
available: 23.42 GiB used: 3.53 GiB (15.1%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 2043 libs: 583 tools: octopi,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
Garuda (2.6.17-1):
System install date: 2023-04-12
Last full system update: 2023-11-08
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: Probably (Run as root to verify)
Failed units:
Total system updates: 54
--> Updates per week: 1
Uptime: 34 mins
2 Likes
Michael_joseph:
power grid failure
Yep I guess that was the cause of the glitch.
1 Like
power outage fixed the glitch, not caused it.
i updated twice yesterday and noticed the swish sticking around as i was perusing my hardware info in the system stats page of the garuda assistant for the new boot-time thread and then double checked it by running garuda-inxi.
the power outage happened 7 hours ago and was just fixed by linemen within the last hour.
i’m not sure what caused the glitch or what fixed it, but either way i’m gonna scrub and balance my brtfs drives now >.>
system
11 November 2023 14:00
13
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.