You are not logged in.

#1 2026-05-19 00:19

txm0523
Member
Registered: 2022-07-26
Posts: 3

New Install

I just installed Q4OS on an old Thinkpad laptop.
How do I stop all the scrolling of text when I boot up the laptop and when it shuts down ?

Thank you for any help.

txm0523

Offline

#2 2026-05-19 06:59

bin
Member
From: U.K.
Registered: 2016-01-28
Posts: 1,577

Re: New Install

You cannot actually stop it since it is the start up and shutdown process.
If you mean 'can I hide it?' then yes you can by installing plymouth.
However it does beg the question whether it is a good idea to hide it,
Seeing the process rolling up the screen is useful because it tells you all is working properly.
If that is hidden behind a pretty progress bar which then stops moving you'll have no way of seeing where it has stopped.
Also plymouth just wastes resources.

Offline

#3 2026-05-19 08:28

chn97
Member
Registered: 2026-05-18
Posts: 5

Re: New Install

sudo nano /etc/default/grub
in the Linux Default section there should "quiet splash loglevel=3" options
Only keep "quiet splash" and remove entries like loglevel etc
This way it'll minimize text flood.

Offline

#4 2026-05-19 21:02

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 6,212
Website

Re: New Install

You need to select a profile - just left-click on one, and make sure the “Remove superfluous packages” box is unticked. Then click "Install" button.

Offline

#5 2026-05-20 11:45

seb3773
Member
From: France
Registered: 2023-11-01
Posts: 249

Re: New Install

bin wrote:

Seeing the process rolling up the screen is useful because it tells you all is working properly.
If that is hidden behind a pretty progress bar which then stops moving you'll have no way of seeing where it has stopped.

I no longer use Plymouth myself, but I seem to recall that you can press [F4] to display the boot logs (toggle between bootscreen and text mode).


bin wrote:

Also plymouth just wastes resources.

Yes, that’s exactly right—one of the reasons I no longer use it: background service, noticeable boot overhead on low-resource machines. I’ve come to the conclusion that Plymouth is clearly overkill for a boot splash.
You might be interested in what I coded for a lightweight bootsplash: https://github.com/seb3773/xbootsplash.
It’s a system for installing single-binary bootsplashes, with ultra-minimal overhead, minimal complexity, and standard initramfs integration. I use it and it works perfectly. However, it’s currently CLI-only; I plan to add a graphical frontend for Trinity.
The system supports static images, animations, a mix of animations and static images, loops, cycles, etc., and manages its own secure package format (since it touches the initramfs, I don’t want it to be used to spread viruses, so the system performs exhaustive security checks and has its own internal signature system).
If you want, I can also provide the test packages I made (many are conversions from Plymouth bootscreens). Or you can wait for the graphical frontend version wink

Last edited by seb3773 (2026-05-20 11:46)


Debian & Q4OS (TDE!!), low-level C, ASM (z80/68k/x86/ARM64), embedded systems, CPU architectures (RISC-V, binary formats, assembly), retro-computing, metal music, guitar and sci-fi.

Offline

Board footer

Powered by FluxBB