On 08/09/2017 07:59 AM, mitchell@member.fsf.org wrote:
> Rick Stevens writes:
>
>>
>>
>> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
>> /lib64/ld-linux-x86-64.so.2
>> /boof
>> /dev
>> /boot/grub/menu.lst
>> /etc/grub2-efi.cfg
>> /boot/grub/grub.cfg
>> /etc/grub.d/
>> /boot/
Rick Stevens writes:
>
>
> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
> /lib64/ld-linux-x86-64.so.2
> /boof
> /dev
> /boot/grub/menu.lst
> /etc/grub2-efi.cfg
> /boot/grub/grub.cfg
> /etc/grub.d/
> /boot/grub2/grubenv
> /etc/mtab
> /boot
> /etc/sysconfig/grub
> /proc/mdstat
>
On 8 August 2017 at 20:59, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
>
>> Note that on your next kernel upgrade, however, the "rhgb quiet" will
>> reappear unless you edit the /etc/default/grub file and those bits from
>> the "GRUB_CMDLINE_LINUX" variable in ther
On 08/08/2017 12:26 PM, Bob Goodwin wrote:
> On 08/08/17 14:50, Rick Stevens wrote:
>> So, yes, you're using UEFI to boot. All you need to do is edit the
>> /boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
>> reboot. You should be fine.
>>
>> Note that on your next kernel upgr
On 08/08/17 14:50, Rick Stevens wrote:
So, yes, you're using UEFI to boot. All you need to do is edit the
/boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
reboot. You should be fine.
Note that on your next kernel upgrade, however, the "rhgb quiet" will
reappear unless you e
On 08/08/2017 11:59 AM, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
>
>> Note that on your next kernel upgrade, however, the "rhgb quiet" will
>> reappear unless you edit the /etc/default/grub file and those bits from
>> the "GRUB_CMDLINE_LINUX" variable in there a
On Tue, 8 Aug 2017 11:50:54 -0700
Rick Stevens wrote:
> Note that on your next kernel upgrade, however, the "rhgb quiet" will
> reappear unless you edit the /etc/default/grub file and those bits from
> the "GRUB_CMDLINE_LINUX" variable in there as well.
That hasn't been my experience. The "grubby
On 08/08/2017 11:24 AM, Bob Goodwin wrote:
> On 08/08/17 14:02, Rick Stevens wrote:
>>> I see two boot partitions:
>>>
>>> /dev/sda2 976M 167M 742M 19% /boot
>>> /dev/sda1 200M 9.5M 191M 5% /boot/efi
>>>
>>> But it says "efi" not "uefi" and I dunno what the difference is.
>
On 08/08/17 14:02, Rick Stevens wrote:
I see two boot partitions:
/dev/sda2 976M 167M 742M 19% /boot
/dev/sda1 200M 9.5M 191M 5% /boot/efi
But it says "efi" not "uefi" and I dunno what the difference is.
There really isn't. "efi" and "uefi" are synonymous in this conte
On 08/08/2017 10:24 AM, Bob Goodwin wrote:
> On 08/08/17 13:10, Tom Horsley wrote:
>> (The main problem being finding
>> the grub.cfg file if you have a uefi system - it is hidden
>> pretty well :-).
>
> +
>
> Then that must be my problem?
>
> I see two boot partitions:
>
> dev/sda2
On 08/08/17 13:10, Tom Horsley wrote:
(The main problem being finding
the grub.cfg file if you have a uefi system - it is hidden
pretty well :-).
+
Then that must be my problem?
I see two boot partitions:
dev/sda2 976M 167M 742M 19% /boot
/dev/sda1 200M 9.5M 191M 5
On Tue, 8 Aug 2017 13:03:46 -0400
Bob Goodwin wrote:
> Obviously this is wrong? Whay should I be doing or is this something I
> can no longer change?
Nothing ever looks at /etc/default/grub or runs grub2-mkconfig unless
you manually run it.
I just edit the grub.cfg file itself. It works perfect
I prefer not watching the blank screen with the egg turning into an F
and normally remove rhgb from /etc/default/grub.
That is not having the desired effect on this Fedora-26 system.
[root@Box10 bobg]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux ima
13 matches
Mail list logo
