My feedback (garuda linux dragonized gaming edition)

My system specs

garuda-inxi
System:
Kernel: 5.16.10-246-tkg-cfs-llvm x86_64 bits: 64 compiler: clang v: 13.0.1,
parameters: BOOT_IMAGE=/vmlinuz-linux516-tkg-cfs-llvm
root=UUID=eaada518-9789-45a6-96d5-9ea2e9563ec6 rw [email protected]
cryptdevice=UUID=12d783ca-85f9-4344-8e01-a57b4947f1a0:luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
root=/dev/mapper/luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
rd.udev.log_priority=3 vt.global_cursor_default=0 intel_pstate=passive
nvidia-drm.modeset=1 nowatchdog systemd.unified_cgroup_hierarchy=1
loglevel=3 kernel.unprivileged_userns_clone=0 kernel.yama.ptrace_scope=2
lsm=landlock,lockdown,yama,apparmor,bpf net.core.bpf_jit_harden=2
apparmor=1 security=apparmor delayacct
Desktop: KDE Plasma 5.24.1 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Server System: Supermicro product: X9DRi-LN4+/X9DR3-LN4+
v: 0123456789 serial: <superuser required> Chassis: type: 17 v: 0123456789
serial: <superuser required>
Mobo: Supermicro model: X9DRi-LN4+/X9DR3-LN4+ v: REV:1.20A
serial: <superuser required> BIOS: American Megatrends v: 3.4
date: 11/20/2019
CPU:
Info: model: Intel Xeon E5-2670 v2 bits: 64 type: MT MCP SMP
arch: Ivy Bridge family: 6 model-id: 0x3E (62) stepping: 4 microcode: 0x42E
Topology: cpus: 2x cores: 10 tpc: 2 threads: 20 smt: enabled cache:
L1: 2x 640 KiB (1.2 MiB) desc: d-10x32 KiB; i-10x32 KiB
L2: 2x 2.5 MiB (5 MiB) desc: 10x256 KiB L3: 2x 25 MiB (50 MiB)
desc: 1x25 MiB
Speed (MHz): avg: 2900 min/max: 1200/3300 scaling: driver: intel_cpufreq
governor: performance cores: 1: 2900 2: 2900 3: 2900 4: 2900 5: 2900
6: 2900 7: 2900 8: 2900 9: 2900 10: 2900 11: 2900 12: 2900 13: 2900
14: 2900 15: 2900 16: 2900 17: 2900 18: 2900 19: 2900 20: 2900 21: 2900
22: 2900 23: 2900 24: 2900 25: 2900 26: 2900 27: 2900 28: 2900 29: 2900
30: 2900 31: 2900 32: 2900 33: 2900 34: 2900 35: 2900 36: 2900 37: 2900
38: 2900 39: 2900 40: 2900 bogomips: 200268
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: Micro-Star MSI
driver: nvidia v: 510.54 alternate: nouveau,nvidia_drm bus-ID: 83:00.0
chip-ID: 10de:1b06 class-ID: 0300
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 92 s-size: 707x402mm (27.8x15.8")
s-diag: 813mm (32")
Monitor-1: HDMI-0 res: 2560x1440 hz: 144 dpi: 93
size: 698x393mm (27.5x15.5") diag: 801mm (31.5")
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 510.54 direct render: Yes
Audio:
Device-1: NVIDIA GP102 HDMI Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 83:00.1 chip-ID: 10de:10ef
class-ID: 0403
Device-2: Creative SB X-Fi Surround 5.1 Pro type: USB
driver: snd-usb-audio bus-ID: 2-1.3:4 chip-ID: 041e:3237 class-ID: 0102
serial: <filter>
Sound Server-1: ALSA v: k5.16.10-246-tkg-cfs-llvm running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.47 running: yes
Network:
Device-1: Intel I350 Gigabit Network vendor: Super Micro driver: igb
v: kernel port: 6060 bus-ID: 07:00.0 chip-ID: 8086:1521 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Intel I350 Gigabit Network vendor: Super Micro driver: igb
v: kernel port: 6040 bus-ID: 07:00.1 chip-ID: 8086:1521 class-ID: 0200
IF: eno2 state: down mac: <filter>
Device-3: Intel I350 Gigabit Network vendor: Super Micro driver: igb
v: kernel port: 6020 bus-ID: 07:00.2 chip-ID: 8086:1521 class-ID: 0200
IF: eno3 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-4: Intel I350 Gigabit Network vendor: Super Micro driver: igb
v: kernel port: 6000 bus-ID: 07:00.3 chip-ID: 8086:1521 class-ID: 0200
IF: eno4 state: down mac: <filter>
IF-ID-1: br-43e377a74c7b state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
IF-ID-3: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
RAID:
Hardware-1: Adaptec Series 7 6G SAS/PCIe 3 driver: aacraid
v: 1.2.1[50983]-custom port: 7000 bus-ID: 04:00.0 chip-ID: 9005:028c
rev: N/A class-ID: 0104
Drives:
Local Storage: total: 21.83 TiB used: 6.79 TiB (31.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: root size: 21.83 TiB block-size:
physical: 512 B logical: 512 B type: N/A serial: N/A rev: V1.0 scheme: GPT
Partition:
ID-1: / raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.79 TiB (31.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 341.2 MiB (33.4%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.79 TiB (31.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
ID-4: /var/log raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.79 TiB (31.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
ID-5: /var/tmp raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.79 TiB (31.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram size: 125.85 GiB used: 12 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.0 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): cpu: 3629 mobo: 6108 fan-2: 2537 fan-3: 2586
fan-4: 3648 fan-5: 3708 fan-6: 3668 fan-7: fan-8: 3678 fan-9: 0 fan-10: 0
gpu: nvidia fan: 47%
Info:
Processes: 632 Uptime: 57m wakeups: 0 Memory: 125.85 GiB
used: 23.05 GiB (18.3%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 alt: 10 clang: 13.0.1 Packages: 3164 pacman: 3120 lib: 607
flatpak: 44 Shell: fish v: 3.3.1 default: Zsh v: 5.8.1 running-in: konsole
inxi: 3.3.12
Garuda (2.5.4-2):
System install date:     2021-07-06
Last full system update: 2022-02-19
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       <superuser required>
Snapshots:               Snapper
Failed units:            snapper-cleanup.service

Hello, everyone. I work in blender, meshroom, colmap, natron, kdenlive. Garuda linux KDE is perfect for these tasks. It works very stable (much better than manjaro, which has huge update delays and less stability). On my hardware everything works perfectly. Now let's look at the advantages and disadvantages.
Let's start with the advantages.

  1. Good support (arch and garuda forums, archwiki)
  2. Correct system settings (perfomance-tweaks)
  3. The default linux-zen kernel (does not work well on all hardware)
  4. Disk partitioning by default in btrfs with compression already enabled (it would be nice to add to calamares during installation the option to set degree and type of compression)
  5. A handy program garuda-assistant
  6. Snapper and the ability to boot into snapshots out of the box
    Disadvantages:
  1. Latte-dock. It works poorly, causes lags in 3D programs and games. CPU consumption was around 10%, at the time I had 2x xeon e5-2650v2. I also caught a 32GB memory leak at the time. (How much has changed now, I don't know, this information is current as of Fall 2021. Moreover, I like the standard KDE bottom panel much better)
  1. KDE's default theme and settings. This is already my personal opinion, I didn't like it. Others may well disagree with me.
  2. Huge amount of unnecessary software in garuda kde dragonized gaming edition.
  3. Incorrect mount options for SSD by default. Disable autodefrag!
    I definitely recommend garuda linux to those who know at least a bit about arch-like system administration. Thanks to developers
    (I use a translator, there may be inaccuracies)

Having a huge amount of pre-installed software is one of the defining features of the gaming edition. If you don't want that, a different edition might be more appropriate.

10 Likes

Hi :smiley:

Latte-dock. It works poorly, causes lags in 3D programs and games.

To my knowledge Latte-Dock will turn off animations once the compositor is off. so whenever you start a game the compositor should turn off and the performance loss should be gone.

now i am aware that there are some games out there which arent detected by KDE Desktop and just leaves the compositor on, but in that case just turn off the compositor manually.

Huge amount of unnecessary software in garuda kde dragonized gaming edition.

Methinks that this is the reason why there are different standalone versions of dragonized. one has less software, the other has more. i dont see any problem here.

Incorrect mount options for SSD by default. Disable autodefrag!

I dont know much about mounting, but i thought all modern systems dont do any defrag with SSD. how to turn off autodefrag?

1 Like

Edit your /etc/fstab and remove autodefrag from mount options.

On my hardware, there is no difference in games with the composer turned on and off. The processor is obviously redundant for all modern games at all graphics settings and resolutions, the load barely exceeds 20%. This is a problem specifically latte-dock (was at the time, as now I can not say, since I do not use it)

Why disable autodefrag outta interest? I'm not that knowledgeable on this other than I know defragging SSDs is bad and can shorten its life. Is your suggestion because of this or more related to the Btrfs filesystem?

autodefrag increases the number of write by several times under certain circumstances. Usually 1.5-2 times. For HDD it should be enabled, and for SSD/flash it should be disabled.

Oh that's not good at all. Why would the dev team have this enabled then haha. I guess they forgot? I'll definitely look at disabling this so thanks for making it known. Last thing I need is my SSD dying anytime soon

To disable it, simply delete autodefrag from the fstab. Moreover, autodefrag should be disabled now (garuda-hotfixes). Since the 5.16 kernel has a regression in btrfs autodefrag, which provokes a huge amount of writes.

Apparently you guys overlooked the hotfix Garuda released to mitigate this issue.

Other distros also used this setting because it was the default in the Calamares installer. We were one of the first distros to identify this and actually push a fix to our users.

Perhaps you should speak to something you actually have an understanding of, rather than spreading FUDD.

Here is one thread on this topic at the EOS forum:

If you'd actually searched our forum you would have seen it covered in depth on our forum and known about the hotfix we released. How out of date must your systems be, if you never received the hotfix notification? Perhaps you should either update your systems, or start reading the hotfix notifications when they are pushed to our users.

7 Likes

Yes just checked my FSTAB it says modified by Garuda hot fixes you guys need to stay upto date Garuda is a rolling release

7 Likes

I got this fix. Very good that you did it, thank you very much for that. You have saved a huge amount of SSD drives (and owners data) this way.

2 Likes

Defragmenting btrfs SSDs is kind of a complicated discussion with compelling arguments both for and against its use. Although it is true that SSDs do not experience performance penalties from disk fragmentation the same way that spinning rust does, there are still drawbacks to letting COW filesystems get very fragmented.

This is from an old but still interesting discussion here:

There's still some cost to fragmentation, however -- each file fragment
is an IOPS count on access, and while modern SSDs are rated pretty high
IOPS, copy-on-write (COW) based filesystems like btrfs can heavily
fragment "internally rewritten" (as opposed to written once and never
changed, or new data always appended at the end like a log file or
streaming media recording) files. We've seen worst-cases internal-
rewritten files such as multi-gig VMs reported here, with 100K extents or
more! That WILL eat up IOPS, even on SSDs, and there's other serious
issues with that heavily fragmented a file as well, not least the
additional chance of damage to it given all the work btrfs has to do
tracking all those extents!

As for this:

This is apparently a purposeful decision. Some installers (like Calamares) trigger fragmentation during their process to an extent that brand new installations can be heavily fragmented if the install is mounted on btrfs without autodefrag. Even if you do not wish to keep auto-defrag options on your system on a regular basis, keeping it enabled as the default during the install has a noted and potentially substantial benefit.

The hotfix mentioned addressed a kernel regression that occurred somewhere in 5.16, as opposed to something fundamentally wrong with auto-defrag on btrfs SSDs in general. The regression caused btrfs defragmentation to infinitely loop on some systems, which resulted huge I/O loads and excessive disk writes. This is not normal behavior and isn't indicative of a problem with defragmentation on btrfs SSDs in general.

6 Likes

Well you have explained that very well lets hope others read this and take note,

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