This morning I got the dreaded grub prompt on boot.
Took me 3 hours to understand what
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade
was talking about. I did a bunch of searching and trying things out before
I hit upon
the configfile grub command.
Am 01.05.19 um 00:03 schrieb Chris Murphy:
Just a heads up that this can be an issue, but I'm not sure how common
it is. It applies to BIOS (not UEFI) firmware, and for systems that
originally had Fedora 20 or older installed and also never had
'grub2-install' issued since then. Therefore it can
On Thu, May 2, 2019 at 8:10 AM Ralf Corsepius wrote:
> On 5/1/19 8:24 AM, Chris Murphy wrote:
>
>> It happens if the most recent 'grub2-install' happened with a Fedora
>> 20 or older GRUB package. e.g. if you installed Fedora 20 clean, then
>> did an OS upgrade every 6-12 months all the way throug
On Wed, May 1, 2019 at 7:19 PM Charles R. Dennett wrote:
> On 5/1/19 11:07 AM, Tom H wrote:
>> On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett
>> wrote:
>>>
>>> Is there any way to tell just by looking for the presence or absence
>>> of any particular file or directory that you would run into
On 5/1/19 8:24 AM, Chris Murphy wrote:
It happens if the most recent 'grub2-install' happened with a Fedora
20 or older GRUB package. e.g. if you installed Fedora 20 clean, then
did an OS upgrade every 6-12 months all the way through to Fedora 30,
then you'd probably run into this bug. But if at
On 5/1/19 11:07 AM, Tom H wrote:
> On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett wrote:
>>
>> Is there any way to tell just by looking for the presence or absence
>> of any particular file or directory that you would run into this
>> bug?
>
> Unless you're multi-booting and grub's managed
On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett wrote:
> On 5/1/19 5:25 AM, Tom H wrote:
>> On Wed, May 1, 2019 at 3:21 AM Todd Zullinger wrote:
>>>
>>> What I took from the prior wording is that if you installed Fedora
>>> 20 or earlier and then only updated the OS since (and had not
>>> manu
On 5/1/19 5:25 AM, Tom H wrote:
> On Wed, May 1, 2019 at 3:21 AM Todd Zullinger wrote:
>>
>> What I took from the prior wording is that if you installed Fedora
>> 20 or earlier and then only updated the OS since (and had not
>> manually run grub2-update), that you would hit this bug.
>
> "grub2
On Wed, May 1, 2019 at 3:21 AM Todd Zullinger wrote:
>
> What I took from the prior wording is that if you installed Fedora
> 20 or earlier and then only updated the OS since (and had not
> manually run grub2-update), that you would hit this bug.
"grub2-install" not "grub2-update".
__
On Wed, May 1, 2019 at 2:49 AM Chris Murphy wrote:
> On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> wrote:
>> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
>>>
>>> Just a heads up that this can be an issue, but I'm not sure how
>>> common it is. It applies to BIOS (not UEFI) firmw
On Tue, Apr 30, 2019 at 7:21 PM Todd Zullinger wrote:
>
> Chris Murphy wrote:
> > On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> > wrote:
> >>
> >> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> >>> Just a heads up that this can be an issue, but I'm not sure how common
> >>> it i
Chris Murphy writes:
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
wrote:
>
> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> > Just a heads up that this can be an issue, but I'm not sure how common
> > it is. It applies to BIOS (not UEFI) firmware, and for systems that
> > origi
Chris Murphy wrote:
> On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> wrote:
>>
>> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
>>> Just a heads up that this can be an issue, but I'm not sure how common
>>> it is. It applies to BIOS (not UEFI) firmware, and for systems that
>>> ori
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
wrote:
>
> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> > Just a heads up that this can be an issue, but I'm not sure how common
> > it is. It applies to BIOS (not UEFI) firmware, and for systems that
> > originally had Fedora 20 or o
On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> Just a heads up that this can be an issue, but I'm not sure how common
> it is. It applies to BIOS (not UEFI) firmware, and for systems that
> originally had Fedora 20 or older installed and also never had
> 'grub2-install' issued since then.
Just a heads up that this can be an issue, but I'm not sure how common
it is. It applies to BIOS (not UEFI) firmware, and for systems that
originally had Fedora 20 or older installed and also never had
'grub2-install' issued since then. Therefore it can be prevented just
by running 'grub2-install'
16 matches
Mail list logo
