[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem after update with grub and --unrestricted on i386

From: Andrei Borzenkov
Subject: Re: Problem after update with grub and --unrestricted on i386
Date: Sat, 13 Sep 2014 20:26:47 +0400

В Fri, 05 Sep 2014 19:17:23 +0800
address@hidden пишет:

> On Friday, September 05, 2014 03:25 AM, Jordan Uggla wrote:
> > On Wed, Sep 3, 2014 at 5:36 AM, Michael D. Setzer II
> > <address@hidden> wrote:
> >> Most of my systems are x64 machines, but have 3 32 bit machines and on
> >> these after to a grub2-mkconfig -o /boot/grub2/grub.cfg had the machine
> >> giving an error message about --unrestricted being invalid??
> >
> > On BIOS based systems grub, at boot, is always 32 bit. So the
> > difference you're seeing is not about 32 vs 64 bit, even though they
> > seem to be correlated. It may actually be a difference between BIOS
> > and UEFI, or more importantly Fedora's UEFI secure boot scheme vs a
> > more standard upstream grub configuration in BIOS or UEFI. It could
> > also be that even though you have the same version of Fedora
> > installed, you (for whatever reason) have a different version of grub
> > actually installed as a bootloader (as opposed to the userland tools).
> >
> >>
> >> I was able to use the edit option to remove it, and then it would boot, 
> >> but got
> >> a number of file not found message. No such problem on the x64 machine.
> >> All running Fedora 20 with grub 2.00.
> >>
> >> The x64 machines have the --unrestricted and it works with no problem.
> >> Found that this appears in the 10_LINUX file on the class line. Removed it,
> >> and redid the grub2-mkconfig and that gets ride of the rebooting option, 
> >> but it
> >> still shows file not found error messages. Was looking for a log file or
> >> something to see what is causing these messages.
> >
> > Due to the problems of safely writing to a filesystem, grub does not
> > do any logging to disk. For saving logs of error messages your options
> > are unfortunately only logging output via serial, taking a picture of
> > the screen with a camera, or pen and paper. What files specifically
> > are listed as not found?
> >
> Is there any way to ask grub to pause, by pressing a certain key, for 
> example, so that the output from the screen can be examined or a photo 
> taken, screen by screen?


set pager=1

in command line (press 'c' in menu).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]