You are not logged in.
Pages: 1
Everytime I do a fresh q4os installation, first thing i do is enable the systemd log colors in grub.cfg. the colors just feel nicer to me.
Also, instead of logging the systemd startup stuff, I'd appreciate it if there could be an option to just show Q4OS logo while booting up, like mint or windows
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
Also, instead of logging the systemd startup stuff, I'd appreciate it if there could be an option to just show Q4OS logo while booting up, like mint or windows
We can consider creating Q4OS dedicated Plymouth theme sooner or later, but honestly it's not a priority now. If you would create some Q4OS Plymouth theme draft project, we may consider to share development and make a dedicated .qsi installer.
Nonetheless, we don't consider adding Plymouth to the default Q4OS system at the moment, it loads system with additional services. Moreover it's not too reliable sometimes and must be configured manually hardware by hardware.
Offline
i made one, i'd be great if it could be added to the repo with a dedicated qsi (would appreciate credits
)
https://www.q4os.org/forum/viewtopic.php?id=5793
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
Yes, we'll check it out
It would be valuable to create a new project on Github for wider collaboration and source code sharing. Do you want to create your own project, or should we create one as the Q4OS team, based on your code ?
Offline
I'll make a project and add you to it ^^
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
+1
Offline
Please specify a license of this project https://github.com/TheAsmitKid/Q4Riv so we can add a code and the .qsi installer.
Offline
Added
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
See the pull request https://github.com/TheAsmitKid/Q4Riv/pull/2
- Added .qsi build option.
- Format Debian files as a debhelper standard.
Build instructions for .qsi as well as .deb:
$ dpkg-buildpackage -b -uc -us -tc
Offline
Merged
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
Well, so you could now build the .qsi installer and publish both .qsi and .deb as a release https://github.com/TheAsmitKid/Q4Riv/releases
Offline
Released!
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
Good work. A small tip, if you want to extract and inspect a .qsi file, copy it to an arbitrary folder, navigate to the folder and run "xqtrsetup" command. It will extract the .qsi file in this directory.
Offline
Oh wow that's interesting! I was just wondering how to extract this. Also would this work with QuarkOS? Technically, it should work with every linux distro with Plymouth support. But the qsi needs q4os-devpack-base, does QuarkOS also have this?
Also, it would be great if appsetup2.exu could be renamed to something like qsi or q4installer
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
... Also would this work with QuarkOS? ... But the qsi needs q4os-devpack-base, does QuarkOS also have this?
Yes
Also, it would be great if appsetup2.exu could be renamed to something like qsi or q4installer
You can simply make a bash alias.
Last edited by q4osteam (2025-11-24 14:32)
Offline
You have missed "update-grub" command in the install instructions https://github.com/TheAsmitKid/Q4Riv . Plymouth will not show without this.
Offline
Ah it's not like I need an alias, it's more of a "feature request", as qsi (Q4OS software installer) or q4installer would simply sound much more cooler
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
... qsi (Q4OS software installer) or q4installer would simply sound much more cooler
![]()
Offline
You have missed "update-grub" command in the install instructions https://github.com/TheAsmitKid/Q4Riv . Plymouth will not show without this.
Oh yes, since plymouth-set-default-theme automatically runs update-initramfs, I missed it
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
readme updated
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
It would be great if the installer could detect environment and possibly configure the Plymouth theme so that the user doesn't have to manually configure grub, edit "/etc/default/grub" and so on. If it's too difficult at the moment, the installer could carry some sort of helper script to make configuration easier. https://github.com/TheAsmitKid/Q4Riv/issues/3
Offline
i915.modeset=1 flag is for Intel HD graphics drivers (older cpus).. since Plymouth uses SimpleDRM, I think there is no need for such flags on amd devices, however since I don't have an amd device, i cannot confirm.
On old UEFI systems where efifb does not come up in native mode, but rather in 640x32, 800x600 or 1024x768, Plymouth will not use SimpleDRM by default. source
I guess a post install script could detect the va driver in use and add the flags accordingly, as well as make other grub updates. Along with that, it could (ask whether to) set q4riv as default theme (which would execute plymouth-set-default-theme -R q4riv).
I'm quite busy these days and can't spend too much time on development, PRs are appreciated though ![]()
Last edited by theasmitkid (2025-11-24 17:04)
coding & robotics enthusiast | Q4OS 6.4 TDE/XFCE + Win10 1903 on ASUS-E202SA (N3060 | 2GB RAM | 500GB HDD)
Offline
Pages: 1