On 01/08/2014 02:42 PM, Adam Williamson wrote:
On Wed, 2014-01-08 at 11:38 -0800, Adam Williamson wrote:
On Wed, 2014-01-08 at 14:29 -0500, Robert Moskowitz wrote:
On 01/08/2014 02:14 PM, Adam Williamson wrote:
On Tue, 2014-01-07 at 15:06 -0500, Robert Moskowitz wrote:
On 01/07/2014 01:03 PM, Chris Murphy wrote:
On Jan 7, 2014, at 8:13 AM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
Booting is a bit strange. It starts with the Penguin on top and a large font, and then switches off the Penguin and a smaller font. I never get the Fedora logo that I have to press <alt-d> to see the start up log.
Right. So efibootmgr is being called before /etc/default/grub is written, so I bet you don't have that.
No I don't.
And if you don't have that, grub2-mkconfig is producing grub.cfgs that don't contain boot params 'rhgb quiet' which is what cause the Fedora logo splash startup screen to show (via plymouth).
So what do I add to /boot/efi/EFI/fedora/grub.cfg ? I greped it for
'quiet' and nothing was reported.
And anything else to add?
Just adding 'rhgb' should turn the splash screen on.
To which line. I use to be able to understand grub.cfg, but it has
gotten a bit complicated over the years.
The one(s) with all the other kernel parameters on it. grub.cfg has
grown a lot more Stuff with grub2, but if you ignore the extra Stuff,
the lines for a given kernel haven't changed too much - there's a line
specifying the kernel to load and all the parameters to pass to it,
followed by a line specifying the initramfs to load. One pair per entry
on the menu. Edit the menu entries you're likely to boot. When a new
kernel is installed, the top entry in the list is cloned and edited, so
as long as you change the top entry in the list, new kernels will get
the same options.
The other place you can change the parameters is in /etc/default/grub .
Finally took the time to make the change and.... NO /etc/default/grub!!!!
Perhaps there are other interesting files that did not get on the
system? But then how did grub2-mkconfig work when I ran it from
rescue? It used what was on the CD?
Whenever grub2-mkconfig is run it uses the parameters specified there.
But we don't run grub2-mkconfig on kernel installs - we use grubby to
edit grub.cfg directly - so changes in /etc/default/grub won't do
anything unless you then call grub2-mkconfig yourself to re-generate the
config.
I'd probably edit it in both places, just so that if you have call to
run grub2-mkconfig for any reason in future, you don't lose the change.
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
