4

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?

1 Answer 1

0

You should add plymouth quit to your rc.local file. plymouth quit should do the trick..Here is a post of mine when I ran into a problem with plymouth: rc.local with read will not echo key strokes

I also found it useful to add nomodeset to the isolinux.cfg file

default linux
prompt 1
timeout 0
display boot.msg
F1 boot.msg
F2 options.msg
F3 general.msg
F4 param.msg
F5 rescue.msg
label linux
  kernel vmlinuz
  append initrd=initrd.img text ks=cdrom:/ks.cfg nousb nomodeset

Also, check out your ks.cfg file and make sure that rhgb quiet are NOT in the --apend= parm on your bootloader line.

CentOS 6.4 Kickstart bootloader problem

10
  • Thanks for the response, but quitting the bootsplash is not the issue. Currently, the plymouth splash image comes up fine, but it is possible to press a key and have the splash image drop. This allows the user to view the boot messages, which I do not want. Would the nomodeset option prevent this functionality?
    – GROND
    Apr 1, 2015 at 14:20
  • nomodeset will not help you with what you're after. Is this for installation only or every time the machine boots?? You might want to check out the rc.local file..Also, you probably do want rhgb quiet on your bootloader line in your ks.cfg file. I should've read your post a bit closer before answering..
    – GoinOff
    Apr 1, 2015 at 14:48
  • I would like this behavior at all times following the installation. My kickstart infrastructure does not have any issues (I've appended rhgb quiet vga=791 to my grub.conf boot line), and adding nomodeset actually causes the bootsplash to be disabled. I was thinking that I would need to supply a parameter to plymouthd when it is started (I think by rc.sysinit) or perhaps remove a parameter.
    – GROND
    Apr 2, 2015 at 13:31
  • I ran into this post centos.org/forums/viewtopic.php?t=2588 looks like it's a pain in the $ss. Here is another link: tejasbarot.com/2009/01/19/enable-graphical-boot-with-plymouth/…
    – GoinOff
    Apr 2, 2015 at 13:55
  • Maybe try: Try /usr/sbin/plymouth-set-default-theme --list Then try yum search plymouth-plugin I had a number of different plugins that can be used plymouth-plugin-fade-throbber.i686 : Plymouth "Fade-Throbber" plugin plymouth-plugin-label.i686 : Plymouth label plugin plymouth-plugin-script.i686 : Plymouth "script" plugin plymouth-plugin-space-flares.i686 : Plymouth "space-flares" plugin plymouth-plugin-throbgress.i686 : Plymouth "Throbgress" plugin plymouth-plugin-two-step.i686 : Plymouth "two-step" plugin
    – GoinOff
    Apr 2, 2015 at 14:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .