I usually keep the old version. From time to time I do a diff check to see
if there is something new and research the change.
On Sat, May 4, 2024 at 8:06 PM Jeffrey Walton wrote:
>
>
> On Sat, May 4, 2024 at 8:11 PM Javier Perez wrote:
>
>> Don' know. I have been dnf upgrading this system
On Sat, May 4, 2024 at 8:11 PM Javier Perez wrote:
> Don' know. I have been dnf upgrading this system almost since Fedora was
> simple digits. .樂
> I am planning a new build for F40 and definitely clean install it.
>
There are post-upgrade tasks that should be performed to keep the system
tidy.
Don' know. I have been dnf upgrading this system almost since Fedora was
simple digits. .樂
I am planning a new build for F40 and definitely clean install it.
On Sat, May 4, 2024, 19:00 Samuel Sieb wrote:
> On 5/4/24 1:26 AM, Javier Perez wrote:
> > Ok, I think I solved it.
> > I created the
On 5/4/24 1:26 AM, Javier Perez wrote:
Ok, I think I solved it.
I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted.
Once in this kernel, I dnf reinstalled it and everything seems to have
worked fine.
dnf did not show any error and I had journalctl -f on another terminal
and
see this error:
>
> Running scriptlet: kernel-modules-core-6.8.8-200.fc39.x86_64
>
> 49/49
> Running scriptlet: kernel-core-6.8.8-200.fc39.x86_64
>
> 49/49
> /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev
> mounted?).
> grub2-probe: error
/usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?).
grub2-probe: error: cannot find a device for / (is /dev mounted?).
No path or device is specified.
Usage: grub2-probe [OPTION...] [OPTION]... [PATH|DEVICE]
Try 'grub2-probe --help' or 'grub2-probe --usage' for more
On 22/3/24 09:10, Samuel Sieb wrote:
On 3/21/24 15:06, Stephen Morris wrote:
On 21/3/24 09:38, Samuel Sieb wrote:
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid
environment and hence have Fedora installed on raid, I'm assuming
you are
On 3/21/24 15:06, Stephen Morris wrote:
On 21/3/24 09:38, Samuel Sieb wrote:
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid
environment and hence have Fedora installed on raid, I'm assuming you
are using Fedora server, is that correct?
On 21/3/24 09:38, Samuel Sieb wrote:
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid
environment and hence have Fedora installed on raid, I'm assuming you
are using Fedora server, is that correct? I'm just curious because I
played around
On Mar 20, 2024, at 20:10, Sam Varshavchik wrote:
>
> Stephen Morris writes:.
>>
>> If I can ask a silly question, given that on UEFI systems grub2-install is
>> redundant, and the initial messages you were getting were indicating you are
>> booting in a
Stephen Morris writes:
resynced all RAID partitions, I ran grub2-install and I'm fairly certain
there was a definitive change in grub's behavior, afterwards. Originally
three periods were initially shown, for a few seconds, before the grub menu
opened. I have a recollection
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid
environment and hence have Fedora installed on raid, I'm assuming you
are using Fedora server, is that correct? I'm just curious because I
played around with using Raid 10 a couple of years
On 20/3/24 11:28, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run
grub2-install
On 3/19/24 17:29, Tom Horsley wrote:
On Tue, 19 Mar 2024 19:05:51 -0400
Sam Varshavchik wrote:
[root@jack ~]# grub2-install /dev/sda
That is the way you install grub for old MSDOS partitions.
To install grub with GPT and use EFI, it needs different
arguments. Something like:
grub2-install
, recently – after I reassembled
and resynced all RAID partitions, I ran grub2-install and I'm fairly
certain there was a definitive change in grub's behavior, afterwards.
Originally three periods were initially shown, for a few seconds, before
the grub menu opened. I have a recollection that
On Tue, 19 Mar 2024 19:05:51 -0400
Sam Varshavchik wrote:
> [root@jack ~]# grub2-install /dev/sda
That is the way you install grub for old MSDOS partitions.
To install grub with GPT and use EFI, it needs different
arguments. Something like:
grub2-install --target x86_64-efi --removable --b
Samuel Sieb writes:
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install
to actually update the bootloader. Additionally I
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run
grub2-install to actually update the bootloader. Additionally I run
mdraid, so I need
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install
to actually update the bootloader. Additionally I run mdraid, so I need the
bootloader on both /dev/sda and /dev
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run
grub2-install to actually update the bootloader. Additionally I run
mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to
actually update the bootloader. Additionally I run mdraid, so I need the
bootloader on both /dev/sda and /dev/sdb.
But:
[root@jack ~]# grub2-install /dev/sda
grub2-install
; F38, having not put any on for a week or so, after upgrading from F37 via
>> dnf system-upgrade a couple of weeks ago.
>> After putting on the maintenance I used grub2-mkconfig to build the
>> grub.cfg file and got the message below after it notified of finding the
&
a couple of weeks ago.
After putting on the maintenance I used grub2-mkconfig to
build the grub.cfg file and got the message below after it
notified of finding the linux kernels, does anyone know what this
means and why they are being produced from the released version of
grub2
On 10/6/23 11:11, Tom Horsley wrote:
On Sat, 10 Jun 2023 10:53:58 +1000
Stephen Morris wrote:
fgrep: warning: fgrep is obsolescent; using grep -F
It means OCD linux geeks have decided they ought to remove an option used
for decades in uncounted thousands of shell scripts because they don't
On 11 Jun 2023 at 16:24, George N. White III wrote:
From: "George N. White III"
Date sent: Sun, 11 Jun 2023 16:24:45 -0300
Subject: Re: grub2-mkconfig Strange Message
To: Community support for Fedora users
Send reply to: Community support for Fedora users
>
&g
e maintenance I used grub2-mkconfig to build the
> grub.cfg file and got the message below after it notified of finding the
> linux kernels, does anyone know what this means and why they are being
> produced from the released version of grub2-mkconfig, the process I ran
> after the mainte
On Sat, 10 Jun 2023 19:41:34 +0200
Ralf Corsépius wrote:
> You mean, after a 15 years period of deprecation
Yes, I always examine ever single shell script I have and google
for any potential deprecations for every command I use every time
there is an update.
Am 10.06.23 um 03:11 schrieb Tom Horsley:
On Sat, 10 Jun 2023 10:53:58 +1000
Stephen Morris wrote:
fgrep: warning: fgrep is obsolescent; using grep -F
It means OCD linux geeks have decided they ought to remove an option used
for decades in uncounted thousands of shell scripts because they
On Sat, 10 Jun 2023 10:53:58 +1000
Stephen Morris wrote:
> fgrep: warning: fgrep is obsolescent; using grep -F
It means OCD linux geeks have decided they ought to remove an option used
for decades in uncounted thousands of shell scripts because they don't
like it. They've done the same with
Hi,
I have just used dnf to put on the currently available maintenance
in F38, having not put any on for a week or so, after upgrading from F37
via dnf system-upgrade a couple of weeks ago.
After putting on the maintenance I used grub2-mkconfig to build the
grub.cfg file and got
flin"
To: "Community support for Fedora users"
Cc: "stan"
Subject: Re: grub2-mkconfig
try typing vgs/lvs/pvs and see if that also gets the warning.
Some prior centos version did also have this error for a while, I
never noticed any real issue with the programs report
> Sent: Saturday, June 03, 2023 at 8:11 PM
> From: "Roger Heflin"
> To: "Community support for Fedora users"
> Cc: "stan"
> Subject: Re: grub2-mkconfig
>
> try typing vgs/lvs/pvs and see if that also gets the warning.
> Some prior centos
at, Jun 3, 2023 at 9:09 AM stan via users
wrote:
>
> On Fri, 2 Jun 2023 13:18:47 +0200
> Patrick Dupre wrote:
>
> > Hello,
> >
> > On a machine with a triple boot (an 3 HD, all fedora), I get a
> > bunches of
> >
> > File descriptor 3 (pipe:[
On Fri, 2 Jun 2023 13:18:47 +0200
Patrick Dupre wrote:
> Hello,
>
> On a machine with a triple boot (an 3 HD, all fedora), I get a
> bunches of
>
> File descriptor 3 (pipe:[240388]) leaked on vgs invocation. Parent
> PID 75317: grub2-probe
>
> when I run grub2-
Hello,
On a machine with a triple boot (an 3 HD, all fedora), I get a bunches of
File descriptor 3 (pipe:[240388]) leaked on vgs invocation. Parent PID 75317:
grub2-probe
when I run grub2-mkconfig
I have /boot/efi (UEFI) on /dev/sda3 (in fat16)
and
grub2 core.img on /dev/sda1
Can I fix
Francis,
On 2023-04-22 17:18, francis.montag...@inria.fr wrote:
Hi.
On Sat, 22 Apr 2023 16:37:53 +1000 Philip Rhoades via users wrote:
- but why is there is not a line like this in /boot/grub2/grub.conf
for
Fedora 38 Sway?
I can see that the appropriate other Sway files are in the /boot
Hi.
On Sat, 22 Apr 2023 16:37:53 +1000 Philip Rhoades via users wrote:
> - but why is there is not a line like this in /boot/grub2/grub.conf for
> Fedora 38 Sway?
> I can see that the appropriate other Sway files are in the /boot tree so
> I am guessing that grub2 somehow know
PRETTY_NAME="Fedora Linux 38 (Sway)"
ANSI_COLOR="0;38;2;60;110;180"
.
VARIANT="Sway"
VARIANT_ID=sway
- The install picked up old Fedora boot setups which show up in
/boot/grub2/grub.conf like this:
menuentry 'Fedora Linux 37 (KDE Plasma) (on /dev/sde3)' --class
gnu
On 27/11/22 17:03, Samuel Sieb wrote:
On 11/26/22 21:10, Stephen Morris wrote:
Hi,
With the install of grub2 2.06.67 in F37 and playing around with
trying to eliminate the unicode font signing issue highlighted in
another thread, I've now found that grub2 when displaying its boot
menus
On 11/26/22 21:10, Stephen Morris wrote:
Hi,
With the install of grub2 2.06.67 in F37 and playing around with
trying to eliminate the unicode font signing issue highlighted in
another thread, I've now found that grub2 when displaying its boot menus
is no longer reading /boot/grub2
Hi,
With the install of grub2 2.06.67 in F37 and playing around with
trying to eliminate the unicode font signing issue highlighted in
another thread, I've now found that grub2 when displaying its boot menus
is no longer reading /boot/grub2/grub.cfg, which I believe was
introduced
On Sun, 20 Nov 2022 10:47:22 -0500
Tom Horsley wrote:
> If I try the same thing with the Fedora 37 iso image file (looking up
> the CDLABEL to use via the isoinfo tool), it doesn't work.
Figured it out. I loop mounted the iso file and found a grub.cfg file
and interpolated the info in there to
ternal structure of the iso image is now different?
(Something to do with getting rid of syslinux maybe?)
Anyone know the proper incantation to boot the iso image directly
via grub2?
___
users mailing list -- users@lists.fedoraproject.org
Robert McBroom via users composed on 2022-11-01 17:37 (UTC-0400):
>> Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):
>>> ~]# grub2-install /dev/sdc
>>> grub2-install: error: this utility cannot be used for EFI platforms
...
> No mention of MBR
On 11/1/22 14:37, Robert McBroom via users wrote:
No mention of MBR as the drive is GPT. Totally UEFI system, four drives
three OS. I was suspecting a problem with the boot sector, but on
removal of all drives but the one, it boots. Adding the drives one by
one to see the point of digression.
On 10/31/22 17:26, Felix Miata wrote:
Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):
Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does
On 1/11/22 08:26, Felix Miata wrote:
Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):
Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does
Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):
> Running Fedora 35 and trying to fix installed boot files on a third drive.
> ~]# grub2-install /dev/sdc
> grub2-install: error: this utility cannot be used for EFI platforms
> because it does not support UEFI
On Mon, 31 Oct 2022 17:17:35 -0400
Robert McBroom via users wrote:
> ~]# grub2-install /dev/sdc
> grub2-install: error: this utility cannot be used for EFI platforms
> because it does not support UEFI Secure Boot.
An efi install of grub2 needs more info than just a disk drive. Here
i
On 10/31/22 14:17, Robert McBroom via users wrote:
Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does not support UEFI Secure Boot.
Secure Boot is turned off
Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does not support UEFI Secure Boot.
Secure Boot is turned off in the bios. The boot is from UEFI
On 1/9/22 09:45, Roger Heflin wrote:
On Wed, Aug 31, 2022 at 6:02 PM Stephen Morris wrote:
On 30/8/22 01:16, Roger Heflin wrote:
sudo/root is required to access the grub subdirectory because the
permissions are locked down.
I would guess since there can be encrypted grub passwords (and
On Wed, Aug 31, 2022 at 6:02 PM Stephen Morris wrote:
>
> On 30/8/22 01:16, Roger Heflin wrote:
> > sudo/root is required to access the grub subdirectory because the
> > permissions are locked down.
> >
> > I would guess since there can be encrypted grub passwords (and
> > possibly other similar
?
regards,
Steve
On Sun, Aug 28, 2022 at 6:38 PM Stephen Morris wrote:
Hi,
/etc/extlinux.conf is flagged as missing, the file is displayed in
red and the link is shown in white text on a red background. As
mentioned in another thread on this list that file actually is missing.
/etc/grub2
On 30/8/22 01:10, Chris Murphy wrote:
On Sun, Aug 28, 2022, at 7:38 PM, Stephen Morris wrote:
Hi,
/etc/extlinux.conf is flagged as missing
flagged as missing by what? This file is normally not created on any Fedora
variant I'm aware of. It could be a legacy file.
/etc/grub2
gt; Hi,
> /etc/extlinux.conf is flagged as missing, the file is displayed in
> red and the link is shown in white text on a red background. As
> mentioned in another thread on this list that file actually is missing.
> /etc/grub2.cfg and /etc/grub2-efi.cfg both of which point to th
On Sun, Aug 28, 2022, at 7:38 PM, Stephen Morris wrote:
> Hi,
> /etc/extlinux.conf is flagged as missing
flagged as missing by what? This file is normally not created on any Fedora
variant I'm aware of. It could be a legacy file.
> /etc/grub2.cfg and /etc/grub2-efi
Hi,
/etc/extlinux.conf is flagged as missing, the file is displayed in
red and the link is shown in white text on a red background. As
mentioned in another thread on this list that file actually is missing.
/etc/grub2.cfg and /etc/grub2-efi.cfg both of which point to the
same file also
OK,
I should have say passphrase !
Anyway, I made a touch /.autorelabel
ans now, the passphrase is asked.
Both partition are mount correctly.
Here are the new issues.
I cannot login th graphics mode as a user.
Login in text mode and loading startx I get
xauth: file
On Sat, 2022-07-23 at 10:29 +0200, Patrick Dupre wrote:
> Now, I am back to the previous situation where the boot does
> not ask me for the paraphrase.
>
> How can I fix this?
Not really enough information provided. e.g. Show us your fstab files.
Generally speaking, if all your partitions are
Cedex FRANCE
Tel: +33 (0)380395988| | Room# D114A
===
> Sent: Friday, July 22, 2022 at 11:16 PM
> From: "Patrick Dupre"
> To: "fedora"
> Subject: grub2 Big mistake
>
Hello,
I have not been able to provide my paraphrase at boot.
I mount the encrypted partition manually after removing it from
/etc/fstab
Then I run
grub2-mkconfig -o /boot/grub2/grub.cfg
(there was almost no diffrence with the previous grub.cfg that I saved).
Then I run grub2-install /dev/sda
On Wed, Jan 26, 2022 at 8:50 PM Tom Horsley wrote:
>
> I haven't noticed this one either...
I noticed this change.
It turns out that
/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the entry saved_entry=
which refers to /boot/loader/entries/.conf
which co
On Wed, 26 Jan 2022 12:36:00 -0700
stan via users wrote:
> I don't recall seeing any discussion of a change like this, but I could
> have missed it.
I haven't noticed this one either, but I do find a lot of the "helpful"
stuff grub2 desperately tries to do for me annoying, so
On Tue, 25 Jan 2022 16:04:57 -0600
Dave Ulrick wrote:
> Every so often I have to boot Linux into single-user mode. I do this
> by waiting for the Grub2 menu, selecting the desired kernel, and
> pressing 'e'. Then I select the 'linux' statement, add '1' to
> the end of the li
Every so often I have to boot Linux into single-user mode. I do this by
waiting for the Grub2 menu, selecting the desired kernel, and pressing
'e'. Then I select the 'linux' statement, add '1' to the end of
the line, and boot with .
This still works fine, but since upgrading to Fedora 34 I've
On Mon, Mar 29, 2021 at 02:02:58PM -0600, Chris Murphy wrote:
> On Mon, Mar 29, 2021 at 1:55 AM Richard W.M. Jones wrote:
> >
> >
> > I have a weird problem on an old Asus Zenbook UX305C where new kernels
> > cannot be installed by grub. Specifically what happens is they appear
> > in the boot
On Mon, Mar 29, 2021 at 1:55 AM Richard W.M. Jones wrote:
>
>
> I have a weird problem on an old Asus Zenbook UX305C where new kernels
> cannot be installed by grub. Specifically what happens is they appear
> in the boot menu fine, but if you try to boot them then the machine
> hangs hard with a
I have a weird problem on an old Asus Zenbook UX305C where new kernels
cannot be installed by grub. Specifically what happens is they appear
in the boot menu fine, but if you try to boot them then the machine
hangs hard with a completely black screen.
Oddly the kernel installed by Anaconda can
On 9 Dec 2020 at 8:28, stan via users wrote:
Date sent: Wed, 9 Dec 2020 08:28:19 -0700
To: users@lists.fedoraproject.org
Subject:Re: Questions on grub2 kernel options.
Organization: zohofree
Send reply to: Community support
n you run grub2-mkconfig which handled the
details.
Fedora 29 and older the menu entries are is grub.cfg.
Fedora 30-32 they are in grubenv and picked up via a macro in each BLS
snippet. Those are in /boot/loader/entries
Fedora 33 the are in each BLS snippet. And BLS snippets are simple enough
and s
On 9 Dec 2020 at 8:28, stan via users wrote:
Date sent: Wed, 9 Dec 2020 08:28:19 -0700
To: users@lists.fedoraproject.org
Subject:Re: Questions on grub2 kernel options.
Organization: zohofree
Send reply to: Community support
On Wed, Dec 9, 2020 at 9:32 AM Michael D. Setzer II wrote:
>
>
>
> Sometimes have the rescue kernel around is handy. Had people
> sometime move a hard disk to a different system with a diskcontroller
> that wasn't included by the standard kernel. The rescue kernel generally
> has the support for
On 9 Dec 2020 at 9:44, Jorge Fábregas wrote:
Subject:Re: Questions on grub2 kernel options.
To: Community support for Fedora users
From: Jorge Fábregas
Date sent: Wed, 9 Dec 2020 09:44:16 -0400
Send reply to: Community
On Wed, 09 Dec 2020 17:42:32 +1000
"Michael D. Setzer II" wrote:
> Noticed that my rescue kernels on one machine were actually a couple
> years old. Machine had been upgraded a couple times using dnf.
>
> Moved the rescue files to another locations, and thought the system
> was suppose to
I didn't understand what you mean
On Wed, Dec 9, 2020, 2:44 PM Jorge Fábregas
wrote:
> On 12/9/20 3:42 AM, Michael D. Setzer II wrote:
> > In previous configurations the grub.cfg file contained the kernel
> > lines, now it doesn't seem to have them included.
>
> The entries are in
On 12/9/20 3:42 AM, Michael D. Setzer II wrote:
> In previous configurations the grub.cfg file contained the kernel
> lines, now it doesn't seem to have them included.
The entries are in /boot/loader/entries/See the new darling:
See
In previous configurations the grub.cfg file contained the kernel lines,
now it doesn't seem to have them included.
Is there a place where they are listed, or does grub dynamically create
them at boot time? The other lines for windows, memtest and custom are
still listed??
Noticed that
On Mon, 2020-11-16 at 13:23 +, Andre Robatino wrote:
> Sorry about that, the command I was actually using was "grub2-editenv - unset
> menu_auto_hide" (from https://fedoraproject.org/wiki/Changes/HiddenGrubMenu
> ), I always have to look that up before using it.
Sorry abo
Sorry about that, the command I was actually using was "grub2-editenv - unset
menu_auto_hide" (from https://fedoraproject.org/wiki/Changes/HiddenGrubMenu ),
I always have to look that up before using it.
___
users mailing lis
On 16/11/20 10:38 am, Chris Murphy wrote:
On Sun, Nov 15, 2020 at 5:14 AM Stephen Morris wrote:
On 15/11/20 12:26 pm, Andre Robatino wrote:
I have a BIOS Fedora 33-only laptop, and "grub2-editenv - unset auto_hide_menu"
worked on that.
That's interesting. I am running F33 in a VM
On Sun, Nov 15, 2020 at 5:14 AM Stephen Morris wrote:
>
> On 15/11/20 12:26 pm, Andre Robatino wrote:
> > I have a BIOS Fedora 33-only laptop, and "grub2-editenv - unset
> > auto_hide_menu" worked on that.
> That's interesting. I am running F33 in a VM in VMware P
On 15/11/20 12:26 pm, Andre Robatino wrote:
I have a BIOS Fedora 33-only laptop, and "grub2-editenv - unset auto_hide_menu"
worked on that.
That's interesting. I am running F33 in a VM in VMware Player and for me
that command did nothing, whereas it worked fine in F32.
rega
On 15/11/20 1:20 am, Tom Horsley wrote:
On Sat, 14 Nov 2020 16:00:38 +1100
Stephen Morris wrote:
In Fedora 33 is the only way to get the menu to permanently display to
edit /etc/grub.d/12_menu_auto_hide and change the timeout_style and
timeout settings within the else condition for the
I have a BIOS Fedora 33-only laptop, and "grub2-editenv - unset auto_hide_menu"
worked on that.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Condu
On Sat, 14 Nov 2020 16:00:38 +1100
Stephen Morris wrote:
> In Fedora 33 is the only way to get the menu to permanently display to
> edit /etc/grub.d/12_menu_auto_hide and change the timeout_style and
> timeout settings within the else condition for the fastboot check? I
> currently have the
In Fedora 32 issuing the command sudo grub2-editenv - unset
auto_hide_menu would enable the display of the grub boot menu.
This does not work in Fedora 33. I did find some details on the net on
how to get the menu to display on the next boot, but that was not a
permanent solution.
In Fedora
UEFI.?? With either boot method you should be
able to add an entry that loads the config file from the other GRUB.
___
Pre UEFI bios systems. Used chainload with grub for a long time but
missing something to do it with grub2. The configurations in
/boot
ot. Seems to be an issue on boot in the root versus boot in
> a boot partition.
>
There are boot managers for UEFI, https://rodsbooks.com/refind/ is one
example that I have used (but not with the latest incarnation of grub2).
--
George N. White III
On 8/27/20 3:01 PM, Robert McBroom via users wrote:
Second system has f32 on sda and f31 on sdb. The f32 system is the only
one that will boot. There are entries in /boot/loader for both. but only
f32 will boot. Seems to be an issue on boot in the root versus boot in
a boot partition.
UEFI
On 8/27/20 5:01 PM, Robert McBroom via users wrote:
What does one do in the new environment to run different versions of
linux on different drives of a system. One system has f31 on sda and
centos7 on sdb. With legacy grub I could call the boot of one system
from the other and vice versa. No
What does one do in the new environment to run different versions of
linux on different drives of a system. One system has f31 on sda and
centos7 on sdb. With legacy grub I could call the boot of one system
from the other and vice versa. No more. Switching drives in the bios no
longer works. I
antonio montagnani writes:
After an update from F31 to F32, the next update sent these warnings, but
upgrade was completed:
Upgrading: grub2-common-1:2.04-13.fc32.noarch 4/299
errore: lsetfilecon: (/boot/efi/EFI/fedora, system_u:object_r:boot_t:s0)
This is a known bug
stan via users ha scritto il 25/04/20 alle 18:17:
On Sat, 25 Apr 2020 17:55:42 +0200
antonio montagnani wrote:
After an update from F31 to F32, the next update sent these warnings,
but upgrade was completed:
Upgrading: grub2-common-1:2.04-13.fc32.noarch
4/299
errore
On Sat, 25 Apr 2020 17:55:42 +0200
antonio montagnani wrote:
> After an update from F31 to F32, the next update sent these warnings,
> but upgrade was completed:
>
>
> Upgrading : grub2-common-1:2.04-13.fc32.noarch
> 4/299
> errore: lsetfilecon:
After an update from F31 to F32, the next update sent these warnings,
but upgrade was completed:
Upgrading: grub2-common-1:2.04-13.fc32.noarch
4/299
errore: lsetfilecon: (/boot/efi/EFI/fedora, system_u:object_r:boot_t:s0)
Operazione non supportata
Upgrading
On Mon, 6 Apr 2020 11:32:18 -0500
Richard Shaw wrote:
> I updated grub2/grub.cfg but I did it to a temporary file first and
> diff'ed the differences not finding anything significant. I deleted
> the extraneous entries in /boot/loader/entries and installed a new
> kernel in tes
nger generated and inserted into
> > grub.cfg during grub2-mkconfig, but are individual files now in
> > /boot/loader/entries.
>
> I think this was introduced in F30, and it became the default in F31.
> Called snippets. It is no longer necessary to update the grub.cfg file
> with
On Sun, 5 Apr 2020 20:57:48 -0500
Richard Shaw wrote:
> Well I figured out PART of it... I'm not sure when it changed but the
> individual boot load entries are no longer generated and inserted into
> grub.cfg during grub2-mkconfig, but are individual files now in
> /boot/loader
On Sun, 5 Apr 2020 20:44:35 -0500
Richard Shaw wrote:
> I recently updated one of my F31 machines and rebooted it remotely. I was
> wondering why I couldn't get to it after a couple of minutes so I went out
> and switch the input to the PC (It's the multimedia machine) to be greeted
> by a rescue
1 - 100 of 748 matches
Mail list logo
