A number of small bugs on fresh install

I have just installed Garuda on a spare drive. But Im having a few minor issues that I cant seem to resolve.

  1. Open Razer isnt working. When I run through the troubleshooting steps it says the driver is missing and that I should install openrazer-driver-dkms. But it is already installed. The openrazer-meta is also installed and I have run the 'sudo gpasswd -a $USER plugdev' command. But Polychromatic still not working.

  2. Bottles wont remeber its directory. Every time I start Bottles it says it cant find the directory. So I select it and all works fine but after reboot it cant find it again. I'm using the Flatpak version of Bottles. I have tried re-installing and deleting all the bottles settings I can find but problem remains.

  3. On startup sometimes I get a grey screen with 3 square dots on it and it sits there for ages before finally booting to the login screen. This doesnt happen every time. What is going on there?

  4. Is it possible to get rid of the shutdown image that comes up when logging off. Its a grey dragon with an orange spinny wheel. Its not a big issue but I dont like it.

Otherwise thank you devs. Im not a fan of the unicorn vomit themeing but a great distro despite that.

Hello Garuda users.

Please read the following template before requesting assistance:

Please post the terminal/konsole input and output as text (no pictures) from the following command:

garuda-inxi

Refusing to post the output of the required "garuda-inxi" on a help request will likely result in you not receiving any help from the Garuda team. A failure to provide your system specs may also result in your thread being closed without notice, (as without this information providing assistance is often next to impossible).

Before opening a new help request, please search the Arch and Garuda Wiki's, and read any relevant sections related to your issue. Also, thoroughly search any error messages in the forum's search engine and on the web. For in depth information on how to search for answers to Linux issues effectively, read the tips on the Garuda Wiki:

Please report in detail everything you have already attempted to solve your problem.

1 Like
System:
Kernel: 6.2.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=6ed18e1f-c722-471d-81c3-e3d110173347 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=5c408958-88ef-49ca-8fbd-6ca48b5905ce loglevel=3
Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x serial: <superuser required>
UEFI: American Megatrends v: F30 date: 09/15/2020
CPU:
Info: model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: N/A
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 3390 high: 3400 min/max: 2200/3400 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3391 2: 3392
3: 3393 4: 3382 5: 3400 6: 3390 7: 3395 8: 3393 9: 3384 10: 3390 11: 3367
12: 3400 13: 3389 14: 3390 15: 3391 16: 3400 bogomips: 108593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] 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,DP-3 empty: DP-2,HDMI-A-1 bus-ID: 0b:00.0 chip-ID: 1002:73bf
class-ID: 0300
Device-2: Logitech HD Webcam C525 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 2-2.4:6 chip-ID: 046d:0826 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
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: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left
model: LG (GoldStar) 27GL650F serial: <filter> built: 2019 res: 1920x1080
hz: 144 dpi: 82 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 609mm (24")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: DP-3 mapped: DisplayPort-2 pos: right
model: LG (GoldStar) 27GL650F serial: <filter> built: 2019 res: 1920x1080
hz: 144 dpi: 82 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 609mm (24")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6800 XT (navi21
LLVM 15.0.7 DRM 3.49 6.2.6-zen1-1-zen) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
bus-ID: 2-2.4:6 pcie: gen: 4 chip-ID: 046d:0826 class-ID: 0e02
speed: 16 GT/s lanes: 16 serial: <filter> bus-ID: 0b:00.1
chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech HD Webcam C525 type: USB driver: snd-usb-audio,uvcvideo
Device-4: Focusrite-Novation Scarlett 2i4 type: USB driver: snd-usb-audio
bus-ID: 2-4.3:8 chip-ID: 1235:800a class-ID: fe01
Sound API: ALSA v: k6.2.6-zen1-1-zen running: yes
Sound Interface: sndio v: N/A running: no
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.67 running: yes
Network:
Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
driver: btusb v: 0.8 bus-ID: 3-3.4.4:9 chip-ID: 0a12:0001 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 19.37 TiB used: 4.86 TiB (25.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket 4.0 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 type: SSD serial: <filter> rev: RKT401.3 temp: 36.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Sabrent model: N/A
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: RKT303.3 temp: 26.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD60EZAZ-00SF3B0 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD60EZAZ-00SF3B0 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
ID-6: /dev/sdd maj-min: 8:48 type: USB vendor: Western Digital
model: WD20EZRZ-00Z5HB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B type: HDD rpm: 5400 serial: <filter> scheme: MBR
ID-7: /dev/sde maj-min: 8:64 type: USB vendor: Western Digital
model: WD20EZRZ-00Z5HB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B type: HDD rpm: 5400 serial: <filter> scheme: MBR
ID-8: /dev/sdg maj-min: 8:96 type: USB vendor: SanDisk model: USB 3.2Gen1
size: 232.88 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 412.4 GiB (22.6%)
fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
used: 412.4 GiB (22.6%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
used: 412.4 GiB (22.6%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
used: 412.4 GiB (22.6%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.29 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.41 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
System Temperatures: cpu: 35.5 C mobo: 27.0 C gpu: amdgpu temp: 52.0 C
mem: 60.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 408 Uptime: 1h 17m wakeups: 0 Memory: 31.29 GiB
used: 4.95 GiB (15.8%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: 1775 pm: pacman pkgs: 1755
libs: 533 tools: gnome-software,pamac,paru pm: flatpak pkgs: 20 Shell: fish
v: 3.6.0 default: Zsh v: 5.9 running-in: konsole inxi: 3.3.25
Garuda (2.6.15-1):
System install date:     2023-03-13
Last full system update: 2023-03-15
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       <superuser required>
Failed units:

Welcome to the Forum!

Sounds Bottles related. What do people on other Forums/Reddit/etc say about that problem? You may well not be the only one with this.

I see that grey screen very rarely on some of my machines but it doesn’t stall there.
However since you want to get rid of your last point, it is possible both points may be related.

To get rid of the Dragon on Login/Reboot/Shutdown you either have to change the Plymouth Theme or remove Plymouth.
For removing Plymouth this is not as straight forward as a simple pacman removal command, you also have to swap display-manager.service for sddm.service and optionally (I think it’s optional) remove plymouth module from dracut initramfs plus proceed with some plymouth files clean-up if you want to keep your system clean.

I suggest you first start with changing the Plymouth Theme!

Some documentation that may help understand about Plymouth:
https://wiki.archlinux.org/title/plymouth

Also it’s good practice to post ONE help request per thread on this Forum. :smiley:

2 Likes

You should resolve the partially upgraded state before troubleshooting any software problems, including Open Razer or Bottles. Run in the terminal:

garuda-update

If you have any problems getting through the update, paste the full input and output of the command into the thread so we can see what is happening.

You should not be seeing this since you have Plymouth set up. You should be getting the Plymouth splash screen (the one you don’t care for, with the dragon and the spinning animation). This could be another side effect of your partially upgraded state, or you may need to enable early kernel module loading for your graphics drivers as described here. Or, since you don’t care for the splash screen anyhow you could just ignore it. As for the prolonged delay:

Press Esc during the splash animation to switch to the console, where you can read the process that is running while it hangs.

Or, after the system boots run:

systemd-analyze critical-chain
3 Likes

regarding partial update. I have 1 program Bitwig-Studio that im holding back due to compatibility with scripts and plugins. This should not have any effect on the rest of the system. It is the only thing im holding back.

regards Bottles. Bottles works as it should on Manajro on the same machine. Im gonna guess that it might be some file permissions thing why its not rembering its settings. As I have copied the .Bottles directory across from Manajro.

Thank you all for some of the pointers. Ill continue to research.

  1. Have you considered/tried to not use the flatpak version? a simple sudo pacman -Sy bottles to install it might sort out the issue. Flatpak AppImages and Snap are not "officially supported" on garuda
3 Likes

OK I will look at this.

Although somehow everything that I reported is workign at the moment.

Im pretty sure I started with the non-flatpak version and couldnt get anything working in it. Which Is why I switched to the Flatpak version. It was early on in my setting the system up though so I didnt exactly persist in trying to fault find.

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