Plymouth Boot Splash - Turn off switching to text

up vote
3
down vote

favorite

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?

asked Mar 28 '15 at 17:07

GROND

1168

bumped to the homepage by Community♦ 2 days ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment |

up vote
3
down vote

favorite

asked Mar 28 '15 at 17:07

GROND

1168

bumped to the homepage by Community♦ 2 days ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment |

up vote
3
down vote

favorite

asked Mar 28 '15 at 17:07

GROND

1168

centos bootsplash plymouth

asked Mar 28 '15 at 17:07

GROND

1168

asked Mar 28 '15 at 17:07

GROND

1168

asked Mar 28 '15 at 17:07

GROND

1168

asked Mar 28 '15 at 17:07

GROND

1168

asked Mar 28 '15 at 17:07

GROND

1168

bumped to the homepage by Community♦ 2 days ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

bumped to the homepage by Community♦ 2 days ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment |

1 Answer
1

active

oldest

votes

up vote
0
down vote

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

edited Apr 13 '17 at 12:36

Community♦

answered Mar 31 '15 at 15:00

GoinOff

3563925

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 '15 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 '15 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 '15 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 '15 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 '15 at 14:05

|
show 5 more comments

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f193109%2fplymouth-boot-splash-turn-off-switching-to-text%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
0
down vote

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

edited Apr 13 '17 at 12:36

Community♦

answered Mar 31 '15 at 15:00

GoinOff

3563925

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 '15 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 '15 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 '15 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 '15 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 '15 at 14:05

|
show 5 more comments

up vote
0
down vote

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

edited Apr 13 '17 at 12:36

Community♦

answered Mar 31 '15 at 15:00

GoinOff

3563925

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 '15 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 '15 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 '15 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 '15 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 '15 at 14:05

|
show 5 more comments

up vote
0
down vote

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

edited Apr 13 '17 at 12:36

Community♦

answered Mar 31 '15 at 15:00

GoinOff

3563925

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

edited Apr 13 '17 at 12:36

Community♦

answered Mar 31 '15 at 15:00

GoinOff

3563925

edited Apr 13 '17 at 12:36

Community♦

edited Apr 13 '17 at 12:36

Community♦

edited Apr 13 '17 at 12:36

Community♦

answered Mar 31 '15 at 15:00

GoinOff

3563925

answered Mar 31 '15 at 15:00

GoinOff

3563925

answered Mar 31 '15 at 15:00

GoinOff

3563925

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 '15 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 '15 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 '15 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 '15 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 '15 at 14:05

|
show 5 more comments

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 '15 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 '15 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 '15 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 '15 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 '15 at 14:05

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 '15 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 '15 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 '15 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 '15 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 '15 at 14:05

|
show 5 more comments

draft saved

draft discarded

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Sstrhsrtj