On Mon, Oct 12, 2020 at 3:32 PM Samuel Sieb wrote:
> On 10/12/20 12:12 PM, Richard Shaw wrote:
> > I figured out the what, but not the why!
> >
> > Apparently having my Logitech USB dongle inserted locked up grub, but
> > that's a strange issue...
>
> You aren't the first to run into that. There
On 10/12/20 12:12 PM, Richard Shaw wrote:
I figured out the what, but not the why!
Apparently having my Logitech USB dongle inserted locked up grub, but
that's a strange issue...
You aren't the first to run into that. There are some suggestions
around. Try upgrading the firmware on the rec
I figured out the what, but not the why!
Apparently having my Logitech USB dongle inserted locked up grub, but
that's a strange issue...
Thanks,
Richard
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le.
I used my laptop all weekend without issue, I don't recall updating, but
this morning when I boot I see grub but no buttons work and the 5s
countdown doesn't change.
Ideas?
Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsub
On 6/2/20 2:31 AM, Stephen Morris wrote:
On 2/6/20 10:38 am, Samuel Sieb wrote:
I don't know the all the specific details, but this entry describes
how to load the grub bootloader to start Fedora:
"HD(1,GPT,5a166b43-c099-429b-9587-4cc29389e1cf,0x800,0x12c000)"
identifies the hard drive and EFI
On Tue, Jun 02, 2020 at 07:31:33PM +1000, Stephen Morris wrote:
> I understand this is the entry that is being booted from, but I don't
> understand why it is that entry rather than boot0003, which looks to be the
> vm disk partition, when I am running fedora within a vm. I don't understand
> how t
On 2/6/20 10:38 am, Samuel Sieb wrote:
On 6/1/20 4:10 PM, Stephen Morris wrote:
I am confused by this process as well. If I issue the command
efibootmgr -v I get the following output, and, I don't understand how
that information relates to the segmented disk image that is being
used when Fedor
On 6/1/20 4:10 PM, Stephen Morris wrote:
I am confused by this process as well. If I issue the command efibootmgr
-v I get the following output, and, I don't understand how that
information relates to the segmented disk image that is being used when
Fedora is run from a virtualbox vm running un
On 6/1/20 4:05 PM, Stephen Morris wrote:
On 2/6/20 3:44 am, stan via users wrote:
Check /etc/default/grub on the F32 system, and make sure that all the
entries are correct for the F32 system. It needs to have
GRUB_ENABLE_BLSCFG=true
somewhere in there so that boot loader snippets will work.
G
On 2/6/20 12:10 am, Jonathan Billings wrote:
On Mon, Jun 01, 2020 at 11:20:31AM +0200, Patrick Dupre wrote:
with the -v option, I have
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0002,0001
Boot* fedora
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EF
On 2/6/20 3:44 am, stan via users wrote:
On Mon, 1 Jun 2020 15:23:26 +0200
"Patrick Dupre" wrote:
Thanks,
Actually, I am lost.
I am upgrading one of the systems on a multi-disks system.
1) I realized that one system is not efi, while the other ones are.
2) After I upgraded this system. I can
On Mon, 01 Jun 2020 14:28:46 -0400
Kevin Becker wrote:
> My system has two efi boot partitions on separate drives. I rarely
> boot to Windows and I wanted it on its own completely separate
> drive. I configured a default in the firmware settings and then for a
> while I would choose an alternat
My system has two efi boot partitions on separate drives. I rarely
boot to Windows and I wanted it on its own completely separate
drive. I configured a default in the firmware settings and then for a
while I would choose an alternate when I needed to by hitting a key to
bring up the efi boot menu
Hello,
I guess that very think is more or less, OK, I have just some difficulties
to understand the logic.
> How does the efi firmware decide which /boot/efi to use as the source when
> the computer is started
I realized that I have only one EFI System Partition on sda
By default, the system goe
On Mon, 1 Jun 2020 10:10:41 -0400
Jonathan Billings wrote:
> If you see in the Fedora entry, it has:
> HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800\
> ,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
>
> That means to look for a volume with the 3rd GPT partition, with the
> UUID of a5c3bc11-e8
On Mon, 1 Jun 2020 15:23:26 +0200
"Patrick Dupre" wrote:
> Thanks,
>
> Actually, I am lost.
> I am upgrading one of the systems on a multi-disks system.
> 1) I realized that one system is not efi, while the other ones are.
> 2) After I upgraded this system. I can boot it, but it is weird.
> a) T
On Mon, Jun 01, 2020 at 11:20:31AM +0200, Patrick Dupre wrote:
> with the -v option, I have
> BootCurrent:
> Timeout: 1 seconds
> BootOrder: ,0002,0001
> Boot* fedora
> HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
> [...]
> Howeve
20 at 2:55 PM
> From: "stan via users"
> To: users@lists.fedoraproject.org
> Cc: "stan"
> Subject: Re: boot/grub
>
> On Mon, 1 Jun 2020 11:20:31 +0200
> "Patrick Dupre" wrote:
>
> > If I run
> > grubby --info=ALL
> >
> >
On Mon, 1 Jun 2020 11:20:31 +0200
"Patrick Dupre" wrote:
> If I run
> grubby --info=ALL
>
> I get only the boot system available on the mounted system
>
> What bothers me also is the date of /boot/efi/EFI/fedora/grub.cfg
> -rwx--. 1 root root 15119 Jun 9 2019
>
> I can regenerate it and
Thank again,
with the -v option, I have
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0002,0001
Boot* fedora
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
Boot0001* Hard DriveBBS(HD,,0x0)..GO..NOo.I.N.T.E.L.
.S.S.D.S.
On 5/31/20 1:45 PM, Patrick Dupre wrote:
Thanks,
You are correct.
I also have Boot000F* Fedora
from this distribution (BootCurrent: 000F)
and
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0002,0001,0003,0004,0005
Boot* fedora
From another one.
I wanted to understand what this means.
T
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lis
This has become so complicated.
So if I want to change some of the kernel boot parameters in the grub
command line, on F32, how do I do it ?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedorap
===
Sent: Sunday, May 31, 2020 at 3:05 PM
From: "George N. White III"
To: "Community support for Fedora users"
Subject: Re: boot/grub
On Sun, 31 May 2020 at 05:41, Patrick Dupre <pdu...@gmx.com> wrote:
Hello,
On a multi-bo
y, May 31, 2020 at 8:54 PM
> From: "Jonathan Billings"
> To: "Community support for Fedora users"
> Subject: Re: boot/grub
>
> On May 31, 2020, at 04:41, Patrick Dupre wrote:
> > On a multi-boot PC, how grub is updated?
> > In the past /etc/grub2.cf
On May 31, 2020, at 04:41, Patrick Dupre wrote:
> On a multi-boot PC, how grub is updated?
> In the past /etc/grub2.cfg was updated.
Specifically, with the legacy bootloader, it was /boot/grub2/grub.cfg that was
updated, and the file in /etc was a symlink.
> and now?
If you use the legacy boot
Patrick Dupre writes:
Hello,
On a multi-boot PC, how grub is updated?
In the past /etc/grub2.cfg was updated.
and now?
It seems that there are 2 tools: bootctl, and efibootmgr
What are the files managed by these tools?
How to understand?
BootCurrent: 000F
Which tool is run after an update
On Sun, 31 May 2020 at 05:41, Patrick Dupre wrote:
> Hello,
>
> On a multi-boot PC, how grub is updated?
> In the past /etc/grub2.cfg was updated.
>
> and now?
>
> It seems that there are 2 tools: bootctl, and efibootmgr
>
> What are the files managed by these tools?
>
> How to understand?
> Boot
Hello,
On a multi-boot PC, how grub is updated?
In the past /etc/grub2.cfg was updated.
and now?
It seems that there are 2 tools: bootctl, and efibootmgr
What are the files managed by these tools?
How to understand?
BootCurrent: 000F
Which tool is run after an update of the kernel?
Thank.
=
29 matches
Mail list logo