Why is she there then?
Hello all. Have the links changed? I have a 404 trying to access this:
https://iso.builds.garudalinux.org/iso/garuda/dr460nized/250131/garuda-dr460nized-linux-zen-250131.iso
Sorry if this has been discussed, I did not read the entire post.
Ah yes, they might in fact have been cleared (we build those daily, but don’t want to keep every of them).
Instead take the newest from here (they should include fixes for Ventoy as well):
https://iso.builds.garudalinux.org/iso/garuda/
Updated the first post with this notice.
6 Likes
Perfect, thanks!
1 Like
Thank you, Thank you, Thank you 
2 Likes
just a test with Audio Production Software on new Garuda Test iso worked fine. I also have Mixx and LLMS installed=)
2 Likes
I just installed the Garuda DG from today using Ventoy and all went perfectly. Just over 4 minute 36 second install. Very nice.
8 Likes
Just tried the latest Mokka ISO on a new machine I just threw together today. About the only thing I’ve noticed that was weird so far is that on a multi monitor setup, some reason the Plasma panels and such only show up on the monitor that is not the primary display. I’m using two monitors currently with this setup.
garuda-inxi just in case
System:
Kernel: 6.13.1-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=1e50281d-1ae7-4677-a7c2-fc4774e397ff rw rootflags=subvol=@
vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X870 AORUS ELITE WIFI7 ICE
v: -CF-WCP serial: <superuser required>
Mobo: Gigabyte model: X870 AORUS ELITE WIFI7 ICE v: x.x
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: F2 date: 08/14/2024
CPU:
Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP arch: N/A level: v4
note: check family: 0x1A (26) model-id: 0x44 (68) stepping: 0
microcode: 0xB40401A
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 3412 min/max: 600/5269 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 3412 2: 3412 3: 3412
4: 3412 5: 3412 6: 3412 7: 3412 8: 3412 9: 3412 10: 3412 11: 3412 12: 3412
13: 3412 14: 3412 15: 3412 16: 3412 bogomips: 150108
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 31 [Radeon RX 7900 XT/7900
XTX/7900 GRE/7900M] vendor: XFX RX-79XMERCB9 driver: amdgpu v: kernel
arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1,DP-2
empty: DP-3,HDMI-A-1,Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:744c
class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Gigabyte driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none empty: DP-4, DP-5, HDMI-A-2, HDMI-A-3,
Writeback-2 bus-ID: 75:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 38.0 C
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 3840x2160 display-ID: 0
Monitor-1: DP-1 pos: bottom-l model: Dell AW2521HF serial: <filter>
built: 2021 res: mode: 1920x1080 hz: 240 scale: 100% (1) dpi: 90 gamma: 1.2
size: 544x303mm (21.42x11.93") diag: 623mm (24.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: DP-2 pos: top-right model: AOC G2460 serial: <filter>
built: 2015 res: mode: 1920x1080 hz: 144 scale: 178% (1.78) to: 1080x1920
dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24")
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: radeonsi device: 2 drv: swrast gbm: drv: radeonsi
surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
navi31 LLVM 19.1.7 DRM 3.59 6.13.1-zen1-1-zen) device-ID: 1002:744c
memory: 23.44 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 4 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 XTX (RADV NAVI31) driver: N/A device-ID: 1002:744c
surfaces: xcb,xlib,wayland device: 1 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: N/A device-ID: 1002:13c0
surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 75:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 75:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.13.1-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.7 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: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 08:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp8s0 state: down mac: <filter>
Device-2: MEDIATEK vendor: Foxconn driver: mt7925e v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 14c3:7925
class-ID: 0280
IF: wlp9s0 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:3 chip-ID: 0489:e124
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
lmp-v: 13 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 4.55 TiB used: 9.86 GiB (0.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: TeamGroup
model: T-FORCE TM8FF1004T size: 3.64 TiB block-size: physical: 512 B
logical: 512 B speed: 126 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EQFM22.3 temp: 41.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: Extreme 55AE
size: 931.48 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 3001 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 3.64 TiB size: 3.64 TiB (100.00%) used: 9.86 GiB (0.3%)
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: 3.64 TiB size: 3.64 TiB (100.00%)
used: 9.86 GiB (0.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 9.86 GiB (0.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 9.86 GiB (0.3%) 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: 60.44 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 42.1 C mobo: N/A
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 38.0 C device: amdgpu temp: 48.0 C mem: 58.0 C
fan: 10 watts: 65.00
Info:
Memory: total: 60 GiB note: est. available: 60.44 GiB used: 5.04 GiB (8.3%)
Processes: 458 Power: uptime: 0m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 24.17 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1392 libs: 398 tools: octopi,pacseek,paru
Compilers: gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.37
Garuda (2.6.26-1.1):
System install date: 2025-02-04
Last full system update: 2025-02-04
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
1 Like
After fresh installing garuda-dr460nized-linux-zen-250205 iso from Ventoy here is what I have found to help testing .
- Empty community repository still enabled
- Annoying kwallet issue when connecting wifi still exist
- Password typed on terminal shows as asterisk *
- Plymouth-theme-dr460nized r5.630da28-1 and other plymouth themes does not work even after following archwiki and other possible solutions on Garuda but dr460nized plymouth theme worked for other distros having dracut or mkinitcpio any
- When booting into garuda linux the system initialization messages displaying font looks weird
I saw Snapper was updated. It now follows the dark theme (even with admin authorization) and the settings button is functioning. Thanks for the update!
5 Likes
I don’t use snapper-tools, but when I read your post I remembered the non-working “settings” button 
Greetz fly out to the Garuda Team for the quick fix 
4 Likes
Good catch, thanks! fix(pacman.conf): remove community repo, add new upstream config options (0ae3ee6f) · Commits · Garuda Linux 🦅 / Tools / garuda-tools · GitLab
This is a feature, not a bug. 
etc/sudoers.d/pwfeedback · master · Garuda Linux 🦅 / Themes and Settings / Settings / Garuda common settings · GitLab
For issues, please open a separate topic.
1 Like
Yea I didn’t particularly like being bothered with Wallet straight out of the gate since it’s one thing I disable when tweaking System Settings. I also need to ask has anyone figured out the bug with the default theme having to be changed to be able to add widgets? The iss is with the theme itself cause I’ve added it in Reborn and Arch and the issue crops up.
This is likely due to how you have them connected to the gpu.
Whats best is to see which port is DP1 or DP0 (which ever is lowest) and plug the main screen into that. Then the extras into the other ports. this is more of a general Linux issue then garuda.
My monitors are sorted by the ports already. This is not the issue. Some reason the Plasma setup in Mokka is confused what is set for the default monitor in System Settings as it bounces what is set up out of the box to the monitor that is not set as the default. I can change the setting and it shifts it around; though of course if my main monitor is not set as the default for real it will cause issues on priorities for other things like gaming, windows popping up, etc.
As you can see here the Dell is DP-1 (what I use for the main monitor) and the AOC is DP-2:
Because of this, recently I’ve also did a work-around by making extensive Plasma changes so I could have Plasma panels on my primary display. By doing this, I ran into a old bug that when placing widgets into the panel would crash and reload Plasma.
There was a thread about this a while back but I’m having troubles finding it again. If I remember correctly though, I think while using some kind of out of the box theme settings it would cause the crashing 
… Well anyways, had to work around that by putting widgets on the desktop instead and then dragging them into the panel. (instead of directly from the list of widgets into the panel)
1 Like
I think the crash should be fixed in 6.3? but don’t quote me ha. Multi monitor in linux has always been “fun”. I hope one day we get it solved for good.
Has it? If you can find the source I would greatly appreciate it. 
I know in 6.3 you can clone panels so that could alleviate some issues at least with multi monitors at least. (long as you can clone it to a different monitor that is)
Edit: also wanted to state I don’t think I had that weird default monitor bug with the panels showing up on the wrong screen with older Dragonized installations. (though I could test some old live ISOs to be sure)
I think the bug might need to be reported I cant find it at all in kde bugs. If it is theme related is it something in the themes code from plasma 5? I know from experience they cause some issues. But I haven’t looked into it in a while.
I think I might of found the thread I was thinking about:
Seems to be the closest thing I could find to what I was experiencing, although I could place what would be panel widgets to the desktop fine and then drag them to the panel.
1 Like
Not sure if this was appropriate for this thread. As I was playing (testing) around the new release I was reminded of some personal settings for LibreOffice (out of the box, it clashes with dark themes). You might want to try some of these (the fonts are important for MS docs):
# View > User Interface > Select Your Preferred User Interface - 'Select' Tabbed
# Home > Fonts > Arial, Times New Roman, Calibri, Cambria (pacman install ttf-ms-fonts)
# Top Right Corner (3 Bars) > Options > Libre Office > View > Icon Theme - Theme - "Colibre (SVG+dark)" (was Breeze)
# Top Right Corner (3 Bars) > Options > Libre Office > Application Colors > Custom Colors - Automatic - "System Theme or Dark" (was Light)
# Top Right Corner (3 Bars) > Options > Load/Save > Microsoft Office - Embedded Objects - 'Check' SmartArt to LibreOffice Shapes or reverse
# Top Right Corner (3 Bars) > Options > LibreOffice Writer > Compatibility > 'Check' "Word-compatible trailing blanks"