> On Jun 27, 2019, at 5:49 AM, Robert Moskowitz wrote:
>
>
>
>> On 6/26/19 11:27 PM, Chris Murphy wrote:
>> You can insert 'set debug=all' and 'set debug=off' at different points
>> in the grub.cfg to track it down, but you want to be really discreet
>> with it because it's incredibly verbose
On 6/28/19 1:31 PM, Samuel Sieb wrote:
On 6/28/19 6:18 AM, Robert Moskowitz wrote:
The error message is:
error: ../../include/grub/misc.h:323:overflow is detected.
After this flashes on the screen, the screen is then blanked with
just a flashing cursor. This stays for some real measurable
On 6/28/19 6:18 AM, Robert Moskowitz wrote:
The error message is:
error: ../../include/grub/misc.h:323:overflow is detected.
After this flashes on the screen, the screen is then blanked with just a
flashing cursor. This stays for some real measurable time (probably
still less than a minute b
On 6/28/19 2:36 AM, Robert Moskowitz wrote:
On 6/28/19 2:16 AM, Samuel Sieb wrote:
That message means that you are booting in legacy mode, not EFI mode.
So probably another BIOS setting set strangely? This unit has a
Lenovoe EDU series sticker. It may have "special" defaults in the BIOS
f
On 6/26/19 12:04 PM, Samuel Sieb wrote:
On 6/26/19 6:39 AM, Robert Moskowitz wrote:
All I can see for the brief time it is on the screen are the words in
a path of grub and I think loader
I do not see any messages in /var/log/messages that include 'grub'
that look anything like an error.
On 6/28/19 2:16 AM, Samuel Sieb wrote:
On 6/27/19 5:53 AM, Robert Moskowitz wrote:
On 6/27/19 5:49 AM, Robert Moskowitz wrote:
# efibootmgr -v
EFI variables are not supported on this system.
It is interesting that the older x120e does support this. Though it
may be that the BIOS on this x1
On 6/27/19 5:53 AM, Robert Moskowitz wrote:
On 6/27/19 5:49 AM, Robert Moskowitz wrote:
# efibootmgr -v
EFI variables are not supported on this system.
It is interesting that the older x120e does support this. Though it may
be that the BIOS on this x140e is a little old and they fixed this o
On 6/27/19 5:49 AM, Robert Moskowitz wrote:
On 6/26/19 11:27 PM, Chris Murphy wrote:
You can insert 'set debug=all' and 'set debug=off' at different points
in the grub.cfg to track it down, but you want to be really discreet
with it because it's incredibly verbose. If you were to 'set
debug=
On 6/26/19 11:27 PM, Chris Murphy wrote:
You can insert 'set debug=all' and 'set debug=off' at different points
in the grub.cfg to track it down, but you want to be really discreet
with it because it's incredibly verbose. If you were to 'set
debug=all' as the first line in grub.cfg and then 'se
dnf install efibootmgr
> Sent: Thursday, June 27, 2019 at 5:34 AM
> From: "Robert Moskowitz"
> To: "Community support for Fedora users" ,
> "Chris Murphy"
> Subject: Re: F30 - Grub error message
>
>
>
> On 6/26/19 11:27 PM, Chris
On 6/26/19 11:27 PM, Chris Murphy wrote:
You can insert 'set debug=all' and 'set debug=off' at different points
in the grub.cfg to track it down, but you want to be really discreet
with it because it's incredibly verbose. If you were to 'set
debug=all' as the first line in grub.cfg and then 'se
You can insert 'set debug=all' and 'set debug=off' at different points
in the grub.cfg to track it down, but you want to be really discreet
with it because it's incredibly verbose. If you were to 'set
debug=all' as the first line in grub.cfg and then 'set debug=off' as
the last line, it might take
On 6/26/19 12:04 PM, Samuel Sieb wrote:
On 6/26/19 6:39 AM, Robert Moskowitz wrote:
All I can see for the brief time it is on the screen are the words in
a path of grub and I think loader
I do not see any messages in /var/log/messages that include 'grub'
that look anything like an error.
On 6/26/19 6:39 AM, Robert Moskowitz wrote:
All I can see for the brief time it is on the screen are the words in a
path of grub and I think loader
I do not see any messages in /var/log/messages that include 'grub' that
look anything like an error.
This will be before the kernel is loaded, s
14 matches
Mail list logo
