I am working on an appliance system based on CentOS 6. I have created a custom boot splash, but I can't find any information on how I would disable the feature to switch to text mode (switching the splash on and off) through a keypress. I do not want a user to be able to drop the splash and view the boot messages. Can anyone point me in the right direction?

in RHEL 7 and 8 I have always done: - /etc/default/grub - GRUB_CMDLINE_LINUX=... verbose and removing rhgb quiet followed by doing a - grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg This does not have an affect in RHEL 9. What is the correct way to do this now in RHEL 9? I noticed grub.cfg is now located in /boot/ in RHEL, and I tried that location in the -o option but still didn't work.

I am trying to get the boot splash I built into my unified kernel image to remain on screen for more of the boot process. Currently the transition from the UEFI logo to the boot splash is completely seamless, but the boot splash shuts off a considerable amount of time before my login screen appears. I'm not expecting a perfectly seamless transition from splash to login, as nice as that would be, but there must be some way to at least hang onto it for a little longer while things that don't need the display are initializing. As far as I can tell based on the research I've done, some process is clearing the initial frame buffer set up by the kernel, which I've taken a few steps to address, but I'm not entirely sure if I've done everything I can. Here's a quick overview of all my different settings. Splash built into the unified kernel image using /etc/mkinitcpio.d/linux.preset default_uki="/boot/arch-linux.efi" default_options="--splash=/etc/mkinitcpio.d/bootsplash.bmp" KMS removed from mkinitcpio.conf hooks to prevent early modesetting by the GPU HOOKS=(systemd autodetect microcode modconf keyboard sd-vconsole block filesystems) amdgpu.seamless=1 added to kernel parameters to smooth the transition to amdgpu when it inevitably does takeover, as well as various output silencing parameters quiet loglevel=3 systemd.show_status=auto rd.udev.log_level=3 vt.global_cursor_default=0 amdgpu.seamless=1 I've also added the line TTYVTDisallocate=no to both systemd-vconsole-setup.service and getty@tty1.service Can anyone think of anything else I should be changing/adding/trying? Please refrain from suggesting I use Plymouth, it is notoriously buggy unless you specifically use software and hardware that integrates well with it. I tried for two days straight, the only way I could get a seamless transition from UEFI to splash was by configuring it to use the simpledrm driver which completely borked the resolution. Opting for the amdgpu driver and kernel mode setting with Plymouth causes there to be a black screen between the UEFI logo and the splash screen due to the time it takes for the amdgpu to actually initialize. This is a well documented problem if you take the time to look into it. Again, please do not suggest I use Plymouth. I'm not looking for splash screen alternatives, I'm looking for an answer to the question in the post title. It may be that there is no way to do so, and if that is the case then so be it, but that's what I'm here to find out. Thank you for taking the time to read.

I have created a custom Plymouth theme (based on MIB Ossigeno) configured to process fsck's messages coming from systemd-fsckd by implementing the communication protocol whose message has the following format: fsckd::: According documentation (8-systemd-fsckd.service ) When executed it, in test mode ("post-boot"), using the command: plymouthd; plymouth --show-splash ; for ((I=0; I<10; I++)); do plymouth --update=fsck:sda1:$I ; sleep 1; done; plymouth quit With special FSCK messages, plymouth shows desired messages, like "Checking disk 1 of 1 (2% complete)". See: Plymouth . So far, so good. But when restarting the system, the fsck messages are not displayed on bootsplash. But if I switch to console by pressing Esc key, fsck progress messages are visible. To force fsck to run at boot, I have alternately used tune2fs and grub (GRUB_CMDLINE_LINUX_DEFAULT="quiet splash fsck.mode=force fsck.repair=yes") to see if there were any implications. For some reason the communication between fsck and Plymouth is not working or working well. The default theme, futureprototype, does not work either. I guess the problem is in systemd-fsckd, How does one determine whether systemd-fsckd's tasks were performed at bootup?, Is there a report or status that shows whether any issues were found? I look in /run/initramfs/fsck.log (this looks good): ~# cat /run/initramfs/fsck.log Log of fsck -C -f -y -T -t ext4 /dev/sda1 Wed Feb 28 15:26:27 2024 e2fsck 1.47.0 (5-Feb-2023) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda1: 212266/593344 files (0.2% non-contiguous), 1705537/2371072 blocks Wed Feb 28 15:26:30 2024 Journal... ~# journalctl -u systemd-fsck* -- Boot f8b976dfd857400085057901577c56f9 -- feb 28 10:40:53 debian12 systemd[1] : Started systemd-fsckd.service - File System Check Daemon to report status. feb 28 10:41:23 debian12 systemd[1] : systemd-fsckd.service: Deactivated successfully. feb 28 10:51:02 debian12 systemd[1] : Started systemd-fsckd.service - File System Check Daemon to report status. feb 28 10:51:32 debian12 systemd[1] : systemd-fsckd.service: Deactivated successfully And systemctl ~# systemctl status systemd-fsckd.socket ● systemd-fsckd.socket - fsck to fsckd communication Socket Loaded: loaded (/lib/systemd/system/systemd-fsckd.socket; static) Active: active (listening) since Wed 2024-02-28 15:26:31 -03; 16min ago Triggers: ● systemd-fsckd.service Docs: man:systemd-fsckd.service(8) man:systemd-fsck@.service(8) man:systemd-fsck-root.service(8) Listen: /run/systemd/fsck.progress (Stream) CGroup: /system.slice/systemd-fsckd.socket ~# systemctl status systemd-fsckd.service ○ systemd-fsckd.service - File System Check Daemon to report status Loaded: loaded (/lib/systemd/system/systemd-fsckd.service; static) Active: inactive (dead) TriggeredBy: ● systemd-fsckd.socket Docs: man:systemd-fsckd.service(8) The goal is to notify the user that the boot process is delayed by fsck's disk check and to view its progress. I have exhausted all my resources and have found nothing on the web. In general, all I find is about hiding boot messages. ~# more /etc/debian_version 10.13 ~# uname -a Linux debian 4.19.0-26-686-pae #1 SMP Debian 4.19.304-1 (2024-01-09) i686 GNU/Linux For reasons that are not relevant, the development is on OS Debian 10, although I have also tried with Debian 12 with the same result. PD: A detail that may be relevant: the tests with Debian 10 and Debian 12 were both carried out on virtual machines on Virtual Box. More test: **Case one:** Debian 10 on Virtual Box. The fsck messages do not appear and the journal shows the following: root@debian:~# systemctl list-sockets | grep fsckd /run/systemd/fsck.progress systemd-fsckd.socket systemd-fsckd.service root@debian:~# journalctl -b /usr/lib/systemd/systemd-fsck -- No entries -- root@debian:~# journalctl -b /usr/lib/systemd/systemd-fsckd -- No entries -- root@debian:~# journalctl --boot | grep systemd-fsck* mar 04 13:07:01 debian systemd[1] : Listening on systemd-fsckd.socket - fsck to fsckd communication Socket. mar 04 13:07:01 debian systemd[1] : systemd-fsck-root.service - File System Check on Root Device was **skipped** because of an unmet condition check (**ConditionPathExists=!/run/initramfs/fsck-root**). root@debian:~# cat /run/initramfs/fsck.log Log of fsck -C -a -T -t ext4 /dev/sda1 Mon Mar 4 13:06:59 2024 /dev/sda1: clean, 212351/593344 files, 1708897/2371072 blocks Mon Mar 4 13:06:59 202 **Case Two:** Debian 10 on physical PC (amd64). In this case the messages are visible, but at the end of the process and very few seconds. Nothing is displayed during execution of fsck. root@Dell:~# systemctl list-sockets | grep fsckd /run/systemd/fsck.progress systemd-fsckd.socket systemd-fsckd.service root@Dell:~# journalctl -b /usr/lib/systemd/systemd-fsck -- Logs begin at Mon 2024-03-04 15:58:16 -03, end at Mon 2024-03-04 19:25:01 -03. -- mar 04 15:58:21 Dell systemd-fsck: e2fsck 1.44.5 (15-Dec-2018) mar 04 15:58:21 Dell systemd-fsck: Pass 1: Checking inodes, blocks, and sizes mar 04 15:58:21 Dell systemd-fsck: Pass 2: Checking directory structure mar 04 15:58:21 Dell systemd-fsck: Pass 3: Checking directory connectivity mar 04 15:58:21 Dell systemd-fsck: Pass 4: Checking reference counts mar 04 15:58:21 Dell systemd-fsck: Pass 5: Checking group summary information mar 04 15:58:22 Dell systemd-fsck: /dev/sda1: 1034/69360 files (0.7% non-contigu root@Dell:~# journalctl -b /usr/lib/systemd/systemd-fsckd -- Logs begin at Mon 2024-03-04 15:58:16 -03, end at Mon 2024-03-04 19:25:01 -03. -- -- No entries -- root@Dell:~# journalctl --boot | grep systemd-fsck* mar 04 15:58:21 Dell systemd-fsck: e2fsck 1.44.5 (15-Dec-2018) mar 04 15:58:21 Dell systemd-fsck: Pass 1: Checking inodes, blocks, and sizes mar 04 15:58:21 Dell systemd-fsck: Pass 2: Checking directory structure mar 04 15:58:21 Dell systemd-fsck: Pass 3: Checking directory connectivity mar 04 15:58:21 Dell systemd-fsck: Pass 4: Checking reference counts mar 04 15:58:21 Dell systemd-fsck: Pass 5: Checking group summary information mar 04 15:58:22 Dell systemd-fsck: /dev/sda1: 1034/69360 files (0.7% non-contiguous), 189933/276480 blocks mar 04 15:59:01 Dell systemd[1] : systemd-fsckd.service: Succeeded. root@Dell:~# cat /run/initramfs/fsck.log Log of fsck -C -f -y -T -t ext4 /dev/sda2 Mon Mar 4 18:57:36 2024 e2fsck 1.44.5 (15-Dec-2018) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda2: 673194/9551872 files (0.8% non-contiguous), 29651430/38200576 blocks Mon Mar 4 18:58:11 2024 ---------------- **Case three:** Debian 10 on physical PC (amd64) with multiple entries grub menu (Debian and other bootable partitions with Windows). root@5VQU7SN:~# systemctl list-sockets | grep fsckd /run/systemd/fsck.progress systemd-fsckd.socket systemd-fsckd.service root@5VQU7SN:~# journalctl -b /usr/lib/systemd/systemd-fsck -- Logs begin at Mon 2024-03-04 15:38:25 -03, end at Mon 2024-03-04 20:39:47 -03. -- -- No entries -- root@5VQU7SN:~# journalctl -b /usr/lib/systemd/systemd-fsckd -- Logs begin at Mon 2024-03-04 15:38:25 -03, end at Mon 2024-03-04 20:39:47 -03. -- -- No entries -- root@5VQU7SN:~# journalctl --boot | grep systemd-fsck* -- No entries -- root@5VQU7SN:~# cat /run/initramfs/fsck.log Log of fsck -C -f -y -T -t ext4 /dev/sda6 Mon Mar 4 18:37:59 2024 e2fsck 1.44.5 (15-Dec-2018) /dev/sda6: recovering journal Clearing orphaned inode 15992282 (uid=1000, gid=1000, mode=0100644, size=32768) Clearing orphaned inode 15991323 (uid=1000, gid=1000, mode=0100600, size=460) Clearing orphaned inode 15990858 (uid=1000, gid=1000, mode=0100644, size=4132) Clearing orphaned inode 15990852 (uid=1000, gid=1000, mode=0100600, size=131072) Clearing orphaned inode 15990840 (uid=1000, gid=1000, mode=0100644, size=4132) Clearing orphaned inode 15990827 (uid=1000, gid=1000, mode=0100644, size=4132) Clearing orphaned inode 15990826 (uid=1000, gid=1000, mode=0100644, size=4132) Clearing orphaned inode 15990859 (uid=1000, gid=1000, mode=0100644, size=4132) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (112010854, counted=112010689). Fix? yes Free inodes count wrong (28961618, counted=28961585). Fix? yes /dev/sda6: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda6: 292047/29253632 files (0.3% non-contiguous), 4981311/116992000 blocks fsck exited with status code 1 Mon Mar 4 18:38:19 2024 ---------------- This issue is becoming quite complex and I don't see where to move forward. I hope there is some expert collegue who can help me in this matter. STATUS UPDATE: I found that the default Plymouth theme worked on another PC, and when I installed my theme, it worked too. I spent days checking grub, fsck, and plymouth configurations, but I couldn't find a difference. Until I noticed that on that PC the /boot directory was mounted on a different partition from the root. Install Debian from scratch on a physical and a virtual PC, with /boot separately. And it worked!!! Could it be a bug of systemd-fsck?

I am trying to add a Grub2 custom graphic background to my system running AlmaLinux 9 (RedHat 9 clone). My */etc/default/grub* file is: GRUB_FONT=fonts/unicode.pf2 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true #GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/almalinux-swap rd.lvm.lv=almalinux/root rd.lvm.lv=almalinux/swap rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true GRUB_TERMINAL_OUTPUT="gfxterm" GRUB_BACKGROUND="/boot/grub2/images/mylogo.png" I have tried a 24bit PNG, 24bit JPG, and 8bit JPG (updating the background line accordingly), and after each change rerunning: grub2-mkconfig -o /boot/efi/EFI/almalinux/grub.cfg grub2-mkconfig -o /boot/grub2/grub.cfg My menu is present, as is the correct font, yet I still don't see ANY graphic background. What am I missing? My background image is 640x480. Do I have to exactly match a screen size? (I thought it would scale).

How can I get back the GRUB boot theme which changed when I upgraded the GNOME desktop environment. I am also getting a Fedora 12 image on rebooting or shutdown This is the original theme I want back: This is the current one: Where can I find the full assets of my desired theme so I can replace it in the boot/grub/theme?

So, I've installed Linux many times in the past, generally from a liveUSB, as I'm using now. It's a 32 GB SamData SD101, on USB 2.0. (Probably excessive for an installer, but it's what I had on hand and it was empty.) I am currently running Linux Mint 20.4, and it's past time for an upgrade, so in this island between projects, I'm attempting to try KUbuntu on it. I download the iso for 22.04.3 and burn it to said drive with Mint's USB Image Writer app, plug it into a USB 2.0 port, and restart; then, I hit F11 for my boot device selector and choose the USB. A moment later, I'm greeted with the basic installer options, specifically Try/Install KDE, etc., and I choose Try/Install. After that, the weirdness happens. I get the power-on boot splash, as if it's stuck in POST. This is hard data on the motherboard, and after I select from the boot menu. There's a little LED blinking on the USB drive, but I've seen it go on like that, with the POST splash, for more than ten minutes. (Figured I would get some household chores done and come back to it, in case it's just taking a little while; but the mobo splash was still there.) As far as I can tell, it's just stuck. On concluding this, I remove the drive from the USB 2.0 slot, and depress the power button to manually power-off my machine; then I wait at least twenty seconds (old habit to protect my HDD) and turn it on. Mint 20.3 boots normally. Current OS acts like nothing happened. Aside from that initial GRUB-like menu, I never get the option to try or install KUbuntu. (Clearly I installed Mint on this machine some time ago, and do not know if I've dealt with this before... it's been a busy few years.) Just a hang on the splash screen, and a potentially irrelevant red light on the thumb drive, seemingly indefinitely. I've got some ideas, but I do not know what I'm doing wrong, and need some advice. Additional data: The motherboard is an MSI MPG x570 Tomahawk Wifi. None of the debug LEDs are informing me of an error with power, RAM, CPU, or detection of a disk; they're behaving normally, so I'm assuming it isn't the mobo. I very recently installed a 4 TB Crucial NVMe M.2 drive, which runs fine on my current OS and doesn't seem to be defective at all; it's been formatted and auto-mounts, and I've had no difficulty storing on it or reading from it (in fact it's KUbuntu's target disk, if it can ever get around to that part). My USB is plugged into an otherwise well-behaved USB 2.0 slot on the front of my machine, which I regularly use for writing to storage, though it is attached through the case and is not directly on the motherboard. Lastly, my graphics card installed is currently an RTX 3050, but that shouldn't matter to a LiveUSB, should it? I recently installed the last LTS of KUbuntu onto an Ideapad without issue, so this is a little weird. Thanks for any assist.

This https://unix.stackexchange.com/questions/165110/grub-quiet-splash says: > The splash (which eventually ends up in your /boot/grub/grub.cfg ) > causes the splash screen to be shown. > > At the same time you want the boot process to be quiet, as otherwise > all kinds of messages would disrupt that splash screen. > > Although specified in GRUB these are kernel parameters influencing the > loading of the kernel or its modules, not something that changes GRUB > behaviour. However, I have not found splash on https://www.kernel.org/doc/html/v5.0/admin-guide/kernel-parameters.html , but AFAIK it works on modern distros which are kernel 5+ based. Why?

I am using linux-live kit to produce a debian live distribution. However at the moment, the boot process involves only text output with a lot of [OK]. I would like to create a boot splash animation while the system is initialising instead of all this text output. Sort of like Zorin, Kali etc that show a logo while the system is booting. The initramfs image is created on the fly to allow for bundles overlays. You can view all the code here: https://github.com/Tomas-M/linux-live and specifically here: https://github.com/Tomas-M/linux-live/tree/master/initramfs How can I modify the initramfs_create script in order to implement plymouth boot animation? I already chose the animation I want. PS: I am not asking for ready-made code but just steps that I need to follow in order to add plymouth implementation in the generated initramfs image.

Depending on the detected hardware I need to start one of two executables of psplash with different images, so in my psplash_%.bbappend I have SPLASH_IMAGES = "file://bootscreen1.png;outsuffix=type1 \ file://bootscreen2.png;outsuffix=type2" And if I bitbake it, I find a psplash-type1 and psplash-type2 executable in the tmp/work/.../psplash/build as well as in package and packages-split and even in image, but it doesn't get included in the final rootfs (there I only find psplash-write). Do I really need to explicitly install the executables, while a psplash-default along with the psplash link is created automatically and the custom executables are also created magically?

I am trying to remove the splash screen or whatever that is called in Fedora 34 but I am unable because I am still seeing the following every time I reboot: I have tried the following: - Change the default Plymouth theme (https://fedoramagazine.org/howto-change-the-plymouth-theme/)

sudo plymouth-set-default-theme text -R

- Edited the GRUB config file and "disabled" Plymouth

sudo nano /etc/default/grub 
    // "rhgb quiet" from GRUB_CMDLINE_LINUX

Any other ideas? What I am missing here?

I'm running manjaro with full disk encryption. I want to have "themed" boot experience and so I installed bootsplash. Unfortunately it doesn't theme the initial disk password prompt. Is it possible to do this with bootsplash or do I have switch to plymouth instead? Secondary question: What's the effective difference between plymouth and bootsplash? On Debian based systems I always use plymouth, but the arch wiki says it's been superseded by bootsplash. The only thing I found is that it's supposed to slow the boot process down less.

I would like to take a screenshot of the KDE Plasma 5 splash screen as I am creating a new splash theme. But pressing PrtSc during the splash doesn't launch spectacle (my screenshooter) until after the splash screen is gone and the screenshot it takes is of the desktop as it appears *after* the splash screen.

I was wondering if Unix systems use the GPU for the startup splash/loading screen because I've been having some trouble with an overheating Mac with graphics issues. Unix-type systems (such as MacOS 10.6, 10.10 and different versions of Ubuntu) show the splash screen, but never actually boot into the GUI (typically just a plain black/blue/white screen after the startup splash). Windows, however, starts up (I assume this is what's happening as I can hear hard drive activity) and only shows a black screen (no splash or loading screen). This just made me curious as I have a cursed 2008 ATI iMac. I plan later to try reapplying thermal paste to see if that does any good, and then try a reflow (I know this'll only be a very temporary solution but I just want to see if anything will work), but if all else fails, it'll probably go into the bin.

I am running Gentoo currently. I don't want to see the boot messages it shows me. My

/etc/default/grub

has these lines:

="quiet splash"

and

="quiet splash"

, and updated grub with

-mkconfig -o /boot/grub/grub.cfg

It still shows me boot messages. Do I have to do something else? Thanks!

I changed the spinner theme image in plymouth to add a custom background, and I tried to load it on boot. I have changed /etc/mkinitcpio.conf to add the plymouth hook, and run plymouth-set-default-theme -R spinner multiple times. [My plymouth debug log](https://paste.ubuntu.com/p/3p3hTQtTH9/) When I try to test the theme using commands plymouthd plymouth --show-splash It shows up correctly. But during boot, three boxes are shown near the bottom, with question marks above. I have tried the same procedure with spinfinity theme, with no luck. I can't figure out what is going wrong? Some help please!

# ASK: How can I properly configure my Plymouth Boot Screen? - I have Debian Buster 10.4 **XFCE**. - I set quiet and splash boot parameters in my grub. - sudo plymouth --show-splash doesn't work. - At shutdown, Plymouth just doesn't appear. - At startup, Plymouth is shown as a strange colored screen that doesn't fit my screen resolution. That screen has three blocks of text (square symbols) blinking with the common loading pattern (**X**XX - X**X**X - XX**X** - **X**XX - etc) - I did try to change the Plymouth Theme without success. It is to note that I have the NVIDIA Proprietary Drivers installed on my system, but the official configuration of the Debian Wiki just shows the below way for the /etc/initramfs-tools/modules: > For **Nouveau** (nVidia) > > # KMS > drm > nouveau modeset=1

I want to change my Linux Mint 17 Cinnamon boot image manually. So, I replaced the image located at: /lib/plymouth/themes/mint-logo/logo.png with mine. The logo changes at shutdown but not at boot.

I would like to execute a command instantly after system is powered. My project is realized in an embedded Linux environment (Yocto-based, with U-boot bootloader), therefore I would like to show a splash screen -almost instantly after powered- on a framebuffer, which involves: - Initializing display driver (modprobe command) - Export an environment variable (to set up framebuffer for QT) - Displaying a picture on the screen (QT app)(or any more viable suggestion?) Now, I know psplash helps to display some logo in the boot screen, but that is not what I'm trying to accomplish. What I want is to show this image on a framebuffer (and not on the display that X11 is connected to) whilst the bootloader is loading. I already have an initscript recipe in Yocto which accomplishes setting up my main application using update-rc.d myapp 10 90 defaults. However, this happens after boot, naturally. Is there any way to simply do what I'm trying to accomplish here? Any help is greatly appreciated. I have a TFT display which I want to run with framebuffer, I don't have another display but X11 is forwarded to HDMI, so I can make use of that in the future. However, I want to display splash screen on TFT with framebuffer, then run my app on it. Nothing with the other display. Guidance on running u-boot splash screen / psplash on framebuffer is also appreciated.

on my Debian box, I have installed Plymouth for a splash screen. I have tried updating the theme but everytime I use the commands: /usr/sbin/plymouth-set-default-theme myTHEME and then try to update it with: update-initramfs -u and add the word splash to the /etc/default/grub file and update the grub by: update-grub the theme i get are simple blue and white bars at the bottom of the screen and the word Debian appears. I've tried changing to the default installed themes and still i have the same theme. Is there something I'm not doing to update it properly?