Hello, i am VERY satisfied with Garuda (i am using xfce), the system works great and it has a better performance now, but i am having a little issue...
When i try to change my plymouth splash screen, i can select any and all of the default ones, they work properly all the time, however, when i try to select the one i installed (aperture laboratories), most of the times, it just shows the "default" three dots, and some times, it only shows the console text.
I also installed other grub themes, but those work perfectly fine.
I understand that i will need to supply information on my system settings, i have no problem with that.
Thank you so much for your help.
If my post if offending or disturbing somebody, i offer my apologies, maybe this seems like a simple issue, but i have not been able to solve it, while i was able to solve the issue with grub.
Again, thank you all in advance.
Please, just follow the template + post your garuda-inxi.
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 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.
The template above should be deleted before posting your help request.
3 Likes
OK, thank you very much for the clarification, i will make sure to follow these instructions as close as possible from now on.
the command "garuda-inxi" reported this:
System:
Kernel: 6.1.15-1-lts arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=90bc3502-e7a8-449a-bd8a-22f3b4526d77 rw rootflags=subvol=@
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: M5A99FX PRO R2.0 v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 2501
date: 04/07/2014
CPU:
Info: model: AMD FX-8370 bits: 64 type: MT MCP arch: Piledriver level: v2
built: 2012-13 process: GF 32nm family: 0x15 (21) model-id: 2 stepping: 0
microcode: 0x6000852
Topology: cpus: 1x cores: 8 smt: enabled cache: L1: 384 KiB
desc: d-8x16 KiB; i-4x64 KiB L2: 8 MiB desc: 4x2 MiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 4004 high: 4013 min/max: 1400/4000 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4011 2: 4000
3: 4003 4: 4000 5: 4013 6: 4000 7: 4000 8: 4006 bogomips: 64232
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: ASUSTeK driver: nvidia
v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
status: current (as of 2023-02) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s
lanes: 16 link-max: gen: 2 speed: 5 GT/s bus-ID: 01:00.0
chip-ID: 10de:2184 class-ID: 0300
Display: x11 server: X.Org v: 21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: nvidia unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
gpu: nvidia display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
s-diag: 485mm (19.11")
Monitor-1: DVI-D-0 res: 1600x900 hz: 60 dpi: 94
size: 432x240mm (17.01x9.45") diag: 494mm (19.46") modes: N/A
API: OpenGL Message: Unable to show GL data. Required tool glxinfo
missing.
Audio:
Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:14.2 chip-ID: 1002:4383 class-ID: 0403
Device-2: NVIDIA TU116 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 2 speed: 5 GT/s bus-ID: 01:00.1 chip-ID: 10de:1aeb
class-ID: 0403
Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 1102:0012 class-ID: 0403
Sound API: ALSA v: k6.1.15-1-lts running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.66 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK P8 series driver: r8168 v: 8.051.02-NAPI modules: r8169
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 09:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 4.09 TiB used: 447.66 GiB (10.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD20EZRZ-00Z5HB0 size: 1.82 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-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DL003-9VT166
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 5900 serial: <filter> rev: CC32 scheme: MBR
ID-3: /dev/sdd maj-min: 8:48 type: USB vendor: Western Digital
model: WD5000AAKS-00TMA0 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> scheme: MBR
Partition:
ID-1: / raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 447.66 GiB (24.1%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%)
used: 608 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 1.81 TiB size: 1.81 TiB (100.00%)
used: 447.66 GiB (24.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 1.81 TiB size: 1.81 TiB (100.00%)
used: 447.66 GiB (24.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 1.81 TiB size: 1.81 TiB (100.00%)
used: 447.66 GiB (24.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 5.01 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
ID-2: swap-2 type: zram size: 15.52 GiB used: 1.5 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 39.6 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 53%
Info:
Processes: 328 Uptime: 35m wakeups: 0 Memory: 15.53 GiB
used: 4.6 GiB (29.6%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1574
libs: 472 tools: octopi,paru Shell: Bash v: 5.1.16
running-in: xfce4-terminal inxi: 3.3.25
Garuda (2.6.15-1):
System install date: 2022-11-22
Last full system update: 2023-03-10
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units: [email protected]
The way i proceeded, was to download the splash from github, then format it the same way as the other ones (that already work) are formatted, i noticed that the images for the animation were calling for the files from a subfolder (of the same animation), since my folder did not contain any subfolder, i edited the configuration files and theme files to reflect that, and i also make sure that the files being called by the scripts had the proper names. Then, i placed the folder along the other animation folders.
If any more information is needed, just let me know please.
Can you link to the software you downloaded?
If you paste the configs into the thread and identify the parts that you edited, perhaps someone will be able to spot a misconfiguration or other clue that can help you get it fixed.
1 Like
I downloaded this theme: "GitHub - irth/plymouth-theme-aperture"
I manually place the folder "aperture", inside "/usr/share/plymouth/themes/", with root privileges.
My edit of the files consisted in making them "look the same" as the ones in "/usr/share/plymouth/themes/garuda/", but keeping the sizes, timings and file settings of the originals. I also changed the descriptions and authors to the originals.
Is the script executable?
chmod +x /path/to/aperture.script
2 Likes
Actually no, the system reports "no such file or directory". But it SHOULD be, that place actually exists.
What aperture folder? There is none in the github repository, nor is that itself called “aperture”. I think you got your filenames wrong.
The path is not literally /path/to/aperture.script
Please provide more info. This all is very vague
I am sorry, but i am not sure of what you are asking me here, was "/path/to/aperture.script" an example command?, maybe i should clarify that English is not my main language. The folder "aperture" is not on github, it is on my installation, the full path on my system is "/usr/share/plymouth/themes/aperture/". All the files are located there, INCLUDING "aperture.script".
I can tell
yes …
/path/to/aperture.script is /usr/share/plymouth/themes/aperture/aperture.script in your case
OK then, the command ran properly now, the output indicates that there was an attempt to change the permissions on the file, but the operation was not permitted. I guess i need to run it as "sudo"?, or it was just for probing?
yes sudo...
then reboot and check if your theme works.
OK, i did it with sudo now, no output this time, i will restart the system.
OK, there was no change, i still only have the "three dots" splash. I am going to reinstall the theme, i will keep the original file placements and subfolders, but i am going to point them to the proper locations again.
are you sure you applied the theme in plymouth itself? IIRC garuda-boot-options can do that.
Yes, i used "Garuda boot options", i was originally going to be editing system files, but then i found out that Garuda has this utility, and that its usage is recommended, so i used it.
There was no luck, the issue is the same, the boot splash does not change. Perhaps there is some configuration i can post here, so you can review it?, perhaps i could send you the splash folder?
^
Config is /etc/plymouth/plymouthd.conf it seems
I have not made any manual editing of configuration files of the system, i used "garuda boot options".
I will search for that file and post its contents now.