Right at boot a message flashes on the screen. Something about an error.
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 comes before the IRQ messages which stay on the screen for long enough to easily read them.
Is there some way to catch this message so I can figure out what is the problem?
thanks
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, so no logging.
Is there some way to catch this message so I can figure out what is the problem?
I would recommend using a video camera or cell phone. I don't know of any other way to catch it.
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.
This will be before the kernel is loaded, so no logging.
Is there some way to catch this message so I can figure out what is the problem?
I would recommend using a video camera or cell phone. I don't know of any other way to catch it.
Neat idea. Will set up the phone to film it on the next boot (soon to get that broadcom-wl loaded).
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 you 5 minutes of pressing space bar to page through hundreds of pages of debug lines.
Depending on where you see the message is where you'd insert it. If you see it right after choosing a menu entry, then that means it's happening in one of the commands in that menu entry stanza. So you'd restrict the debug insertion to that area.
Anyway, the cell phone idea is a really good idea. Good chance at least one frame will have some text you can make out that'll give a hint what the complaint is.
Also, what do you get for:
$ efibootmgr -v
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 'set debug=off' as the last line, it might take you 5 minutes of pressing space bar to page through hundreds of pages of debug lines.
Depending on where you see the message is where you'd insert it. If you see it right after choosing a menu entry, then that means it's happening in one of the commands in that menu entry stanza. So you'd restrict the debug insertion to that area.
Anyway, the cell phone idea is a really good idea. Good chance at least one frame will have some text you can make out that'll give a hint what the complaint is.
I almost got it, but it is out of focus. Next time I will be careful to get it focused on the word Lenovo before starting the unit.
Also, what do you get for:
$ efibootmgr -v
# efibootmgr -v bash: efibootmgr: command not found
dnf install efibootmgr
Sent: Thursday, June 27, 2019 at 5:34 AM From: "Robert Moskowitz" rgm@htt-consult.com To: "Community support for Fedora users" users@lists.fedoraproject.org, "Chris Murphy" lists@colorremedies.com Subject: Re: F30 - Grub error message
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 'set debug=off' as the last line, it might take you 5 minutes of pressing space bar to page through hundreds of pages of debug lines.
Depending on where you see the message is where you'd insert it. If you see it right after choosing a menu entry, then that means it's happening in one of the commands in that menu entry stanza. So you'd restrict the debug insertion to that area.
Anyway, the cell phone idea is a really good idea. Good chance at least one frame will have some text you can make out that'll give a hint what the complaint is.
I almost got it, but it is out of focus. Next time I will be careful to get it focused on the word Lenovo before starting the unit.
Also, what do you get for:
$ efibootmgr -v
# efibootmgr -v bash: efibootmgr: command not found
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
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 'set debug=off' as the last line, it might take you 5 minutes of pressing space bar to page through hundreds of pages of debug lines.
Depending on where you see the message is where you'd insert it. If you see it right after choosing a menu entry, then that means it's happening in one of the commands in that menu entry stanza. So you'd restrict the debug insertion to that area.
Anyway, the cell phone idea is a really good idea. Good chance at least one frame will have some text you can make out that'll give a hint what the complaint is.
Also, what do you get for:
$ efibootmgr -v
# efibootmgr -v EFI variables are not supported on this system.
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=all' as the first line in grub.cfg and then 'set debug=off' as the last line, it might take you 5 minutes of pressing space bar to page through hundreds of pages of debug lines.
Depending on where you see the message is where you'd insert it. If you see it right after choosing a menu entry, then that means it's happening in one of the commands in that menu entry stanza. So you'd restrict the debug insertion to that area.
Anyway, the cell phone idea is a really good idea. Good chance at least one frame will have some text you can make out that'll give a hint what the complaint is.
Also, what do you get for:
$ efibootmgr -v
# 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 on a later BIOS.
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 on a later BIOS.
That message means that you are booting in legacy mode, not EFI mode.
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 x140e is a little old and they fixed this on a later BIOS.
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 for the EDU crowd.
If EFI is off in BIOS and I turn it on, will this impact my F30 installation?
Thanks
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 for the EDU crowd.
If EFI is off in BIOS and I turn it on, will this impact my F30 installation?
If the installed OS was installed in legacy mode, then switching to EFI now will not boot. If it's working, then it's probably best to just let it be.
On Jun 27, 2019, at 5:49 AM, Robert Moskowitz rgm@htt-consult.com 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=all' as the first line in grub.cfg and then 'set debug=off' as the last line, it might take you 5 minutes of pressing space bar to page through hundreds of pages of debug lines.
Depending on where you see the message is where you'd insert it. If you see it right after choosing a menu entry, then that means it's happening in one of the commands in that menu entry stanza. So you'd restrict the debug insertion to that area.
Anyway, the cell phone idea is a really good idea. Good chance at least one frame will have some text you can make out that'll give a hint what the complaint is.
Also, what do you get for:
$ efibootmgr -v
# efibootmgr -v EFI variables are not supported on this system. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Try 60 FPS on ur camera if u can...
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.
This will be before the kernel is loaded, so no logging.
Is there some way to catch this message so I can figure out what is the problem?
I would recommend using a video camera or cell phone. I don't know of any other way to catch it.
I had to put a tag on the center of the screen so the camera would be in focus on a blank screen.
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 but probably more than 30sec) and then the Fedora spin dizzy appears.
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 but probably more than 30sec) and then the Fedora spin dizzy appears.
There is some delay expected. It depends on how fast grub can read the kernel and initrd from the drive. Since you're not in EFI mode, you could try running "grub2-install" to make sure you have the latest version of the bootloader installed.
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 time (probably still less than a minute but probably more than 30sec) and then the Fedora spin dizzy appears.
There is some delay expected. It depends on how fast grub can read the kernel and initrd from the drive. Since you're not in EFI mode, you could try running "grub2-install" to make sure you have the latest version of the bootloader installed.
But should I go into the BOIS settings and enable EFI mode? Do I put my installation at risk at this point?
thanks
-
Chris Murphy -
Nate Pearlstein -
Patrick Dupre -
Robert Moskowitz -
Samuel Sieb