14
8
How do you get RHEL6 to display the "traditional" display of startup information instead of the tiered/stacked progress bar?
The standard info dump is displayed during shutdown.
14
8
How do you get RHEL6 to display the "traditional" display of startup information instead of the tiered/stacked progress bar?
The standard info dump is displayed during shutdown.
9
plymouth-set-default-theme text
/usr/libexec/plymouth/plymouth-update-initrd
or, remove "rhgb quiet" from the Grub configuration (/boot/grub/menu.lst
).
On a fresh install of Scientific Linux 6.5, with 'quite' removed from kernel cmdline (but 'rhgb' kept), the 'text' theme didn't show any log text, but the 'details' theme did. – alexei – 2014-09-15T23:04:04.523
Just type this: 'plymouth-set-default-theme details --rebuild-initrd' and reboot. – Kriston – 2015-01-06T06:03:30.090
11
If you boot in text mode which is how most servers would be set up you have to do the following. In text mode, plymouth paints a colorful text bar which is difficult to completely remove. It's NOT in chkconfig and disabling "rhgb" and "quiet" do not disable this feature. Here's how to do it properly in CentOS 6.x. Steps 1 and 2 also disable features that can cause trouble on a server or virtual machine that should not be provisioned with a graphical console.
1) Remove rhgb
and quiet
from the "kernel" line(s) in /boot/grub/grub.conf
.
2) Remove or comment out the splashimage
and hiddenmenu
lines.
3) Type plymouth-set-default-theme details --rebuild-initrd
.
4) Restart and see if it works.
On the bright side the boot time messages are all saved in /var/spool/plymouth/boot.log
and /var/log/boot.log
.
When I think about it a little more, I realized that since I'm usually not in front of the server's screen anyway, the plymouth system is not a terrible thing. However, when I'm debugging startup problems when I am in front of the server's screen, plymouth is a nuisance that should have been made easier to remove.
2steps 3 and 4 can be combined into a single operation: plymouth-set-default-theme details --rebuild-initrd
– hakamadare – 2012-04-13T15:12:07.173
4
The program that shows you the fancy loading screen is called Plymouth.
See if you can find it with checkconfig --list
, and disabled the service if needed.
If that isn't the cause, it's probably the "quiet" option in Grub.
Disable it by removing the word quiet from the boot options in your /boot/grub/menu.lst
file.
3
Just found this method, and it seems the cleanest way:
grubby --update-kernel=ALL --remove-args="rhgb quiet"
1
Actually, removing rhgb, which I presume stands for "RedHatGraphicalBoot" solved this issue for me on CentOS6.
Just add this line to your post install ks.conf script:
#Save original, just in case
rsync /boot/grub/grub.conf /boot/grub/grub.conf.orig
#edit and output to /tmp/grub.conf
cat /boot/grub/grub.conf |sed -e s/rhgb// > /tmp/grub.conf
#replace & remove temp
cat /tmp/grub.conf > /boot/grub/grub.conf ; rm -f /tmp/grub.conf
1
Or in one line (less maintenance and at least as easy to understand):
sed -i .orig s/rhgb///g /boot/grub/grub.conf
Creates a backup first, and edits the file inline.
The same occurs in Fedora and should not be limited to RHEL6. – bwDraco – 2012-01-19T17:56:21.870
@DragonLord - haven't dealt with Fedora - but will add the tag for future reference – warren – 2012-02-10T15:33:58.153
1Just hit the ESC key the moment the bar show up. – None – 2013-11-06T20:11:08.237