On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
> A faster way to get where I'm going, but will erase any evidence of
> why you're stuck, is to just create a new grub.cfg and then reinstall
> the kernel you want.
>
> $ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
I did the above
On Tue, 2019-05-07 at 11:42 -0600, Chris Murphy wrote:
>
> Is the grub.cfg even present? Maybe it's zero length?
>
> # ls -l /boot/efi/EFI/fedora/grub.cfg
Zero length
> Weird. I'm not sure what happened to the grub.cfg.
My desktop did lockup during the update. I couldn't switch to a tty or
On Tue, May 7, 2019 at 11:53 AM Samuel Sieb wrote:
>
> On 5/7/19 10:42 AM, Chris Murphy wrote:
> > If it's missing or zero length, is curious, but after we know that, it
> > must be be fixed so you can run the grub2-mkconfig command now.
>
> It must be empty because otherwise the "cat" command
On 5/7/19 10:42 AM, Chris Murphy wrote:
If it's missing or zero length, is curious, but after we know that, it
must be be fixed so you can run the grub2-mkconfig command now.
It must be empty because otherwise the "cat" command would have given an
error. A very surprising situation though.
On Tue, May 7, 2019 at 8:11 AM Ranbir wrote:
>
> On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
> >
> > I see two minor anomalies:
> >
> > /boot is XFS, should not be a problem.
> > NVRAM contains dup entries, Boot0001 and Boot0008.
> >
> > Boot0001 is pointing to the new naming for shim,
On 5/7/19 7:10 AM, Ranbir wrote:
On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
NVRAM contains dup entries, Boot0001 and Boot0008.
Boot0001 is pointing to the new naming for shim, and it's also the
default and current boot. Therefore, Boot0008 can be deleted. It's
not
causing the
On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
>
> I see two minor anomalies:
>
> /boot is XFS, should not be a problem.
> NVRAM contains dup entries, Boot0001 and Boot0008.
>
> Boot0001 is pointing to the new naming for shim, and it's also the
> default and current boot. Therefore,
On Mon, May 6, 2019 at 8:25 AM François Patte
wrote:
>
> Le 05/05/2019 à 23:20, Ranbir a écrit :
> > Hi Everyone,
> >
> > I started an update of my F29 system today. Everything seemed to be
> > going fine until the system locked up. I waited for a few minutes and
> > then, hesitantly, I power
On Mon, May 6, 2019 at 7:55 AM Ranbir wrote:
>
> On Sun, 2019-05-05 at 22:16 -0600, Chris Murphy wrote:
> >
> > They should not be broken. It implies a problem with either /boot or
> > /boot/efi depending on the type of firmware you have. What do you get
> > for:
>
> > # cat /etc/fstab
> > #
Le 05/05/2019 à 23:20, Ranbir a écrit :
> Hi Everyone,
>
> I started an update of my F29 system today. Everything seemed to be
> going fine until the system locked up. I waited for a few minutes and
> then, hesitantly, I power cycled the computer. Sure enough, the boot
> didn't start and instead
On Sun, 2019-05-05 at 22:16 -0600, Chris Murphy wrote:
>
> They should not be broken. It implies a problem with either /boot or
> /boot/efi depending on the type of firmware you have. What do you get
> for:
> # cat /etc/fstab
> # blkid
> # efibootmgr -v
Here you go:
On Sun, May 5, 2019 at 3:21 PM Ranbir wrote:
> Running transaction
> Preparing:
>
> 1/1
>
12 matches
Mail list logo
