On Tue, 2024-07-30 at 10:06 -0400, Go Canes wrote:
> On Tue, Jul 30, 2024 at 7:06 AM Patrick O'Callaghan
> wrote:
> > Attempting to run grub2-install, but I get:
> >
> > # grub2-install
> > grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't
> > exist. Please specify --target or --d
On Tue, Jul 30, 2024 at 7:06 AM Patrick O'Callaghan
wrote:
> Attempting to run grub2-install, but I get:
>
> # grub2-install
> grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.
> Please specify --target or --directory.
>
> I do have a modinfo.sh for i32, but not for x86_64.
On Tue, 2024-07-30 at 08:05 -0400, Jeffrey Walton wrote:
> On Tue, Jul 30, 2024 at 7:12 AM Patrick O'Callaghan
> wrote:
> >
> > On Tue, 2024-07-30 at 12:06 +0100, Patrick O'Callaghan wrote:
> > > Attempting to run grub2-install, but I get:
> > >
> > > # grub2-install
> > > grub2-install: error:
On Tue, Jul 30, 2024 at 7:12 AM Patrick O'Callaghan
wrote:
>
> On Tue, 2024-07-30 at 12:06 +0100, Patrick O'Callaghan wrote:
> > Attempting to run grub2-install, but I get:
> >
> > # grub2-install
> > grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't
> > exist. Please specify --tar
On Tue, 2024-07-30 at 12:06 +0100, Patrick O'Callaghan wrote:
> Attempting to run grub2-install, but I get:
>
> # grub2-install
> grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't
> exist. Please specify --target or --directory.
>
> I do have a modinfo.sh for i32, but not for x86
On Wed, 2024-06-05 at 13:37 +0200, Patrick Dupre via users wrote:
> Sorry for all this mail exchanges for a simple thing.
Multi-boot isn't a simple thing, there's a lot of hurdles. If you
needed to ask, you needed to ask. That's what the list is for.
--
NB: All unexpected mail to my mailbo
Thank for all these comments
>
> Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200):
>
> > Disklabel type: gpt
> > Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
> >
> > Device Start End Sectors Size Type
> > /dev/sda1 2048 6143 4096 2M BIOS boot
> >
Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200):
> Disklabel type: gpt
> Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
>
> Device Start End Sectors Size Type
> /dev/sda1 2048 6143 4096 2M BIOS boot
> /dev/sda2 6144 33560575 335544321
> On 6/5/24 1:04 AM, Patrick Dupre via users wrote:
> > Samuel S said
> >
> >> Number Start End Size Type File system Flags
> >> 2 1049kB 470MB 469MB primary ext4 boot
> >> 3 470MB 25.4GB 24.9GB primary ext4
> >> 4 25.4GB 82.0GB 56.6GB extended
> >> 5 25.4GB 82.0GB 56.6GB logical ext4
> >
> > You
On 6/5/24 1:04 AM, Patrick Dupre via users wrote:
Samuel S said
Number Start End Size Type File system Flags
2 1049kB 470MB 469MB primary ext4 boot
3 470MB 25.4GB 24.9GB primary ext4
4 25.4GB 82.0GB 56.6GB extended
5 25.4GB 82.0GB 56.6GB logical ext4
You don't have an EFI partition on this di
>
> On Tue, 4 Jun 2024 22:15:33 +0200, Patrick Dupre via users wrote:
>
> > I guess that when I run grub2-mkconfig there was a UBS key what connected
> > on the usb poer.
> >
> > I made some progresses, but not enough
> > I mounted the Fedora 40 / and
> > cp -a /mnt/fedrao40/boot/loader/entries/*
On Tue, 4 Jun 2024 22:15:33 +0200, Patrick Dupre via users wrote:
> I guess that when I run grub2-mkconfig there was a UBS key what connected on
> the usb poer.
>
> I made some progresses, but not enough
> I mounted the Fedora 40 / and
> cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/ent
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700):
> You don't have an EFI partition on this disk. It's not even a GPT
> partition table. So both installations will be fighting over the EFI
> partition on sda. And there's no easy way to add a boot entry for this
> installation.
A multiboo
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700):
> You don't have an EFI partition on this disk. It's not even a GPT >
> partition table. So both installations will be fighting over the EFI >
> partition on sda. And there's no easy way to add a boot entry for this >
> installation.
A mul
On 6/4/24 2:57 PM, Patrick Dupre via users wrote:
Model: ATA Maxtor 6Y080M0 (scsi)
Disk /dev/sdc: 82.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
2 1049kB 470MB 469MB primary ext4
Disklabel type: gpt
Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
Device Start End Sectors Size Type
/dev/sda1 2048 6143 4096 2M BIOS boot
/dev/sda2 6144 33560575 3355443216G Linux swap
/dev/sda3 33560576 34584575 1024000 500M EFI Sy
Samuel Sieb composed on 2024-06-04 13:49 (UTC-0700):
> Patrick Dupre via users wrote:
>> I am maintaining this machine for numerous years, it always passed the
>> updates,
>> but from 38 to 40, the same approach fails!
> You haven't given a full explanation of your disk layout,
If you provide
> On 6/4/24 1:39 PM, Patrick Dupre via users wrote:
> >>
> >> On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
> >>> I made some progresses, but not enough
> >>> I mounted the Fedora 40 / and
> >>> cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
> >>>
> >>> cat
> >>> /boot/loader/
> Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200):
>
> > I do not understand, because every thing seems OK
> > The file is at the right place as well as
> > System.map-6.8.11-300.fc40.x86_64
> > initramfs-6.8.11-300.fc40.x86_64.img
> > config-6.8.11-300.fc40.x86_64
> > symvers-6.8.1
Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200):
> I do not understand, because every thing seems OK
> The file is at the right place as well as
> System.map-6.8.11-300.fc40.x86_64
> initramfs-6.8.11-300.fc40.x86_64.img
> config-6.8.11-300.fc40.x86_64
> symvers-6.8.11-300.fc40.x86_
On 6/4/24 1:39 PM, Patrick Dupre via users wrote:
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough
I mounted the Fedora 40 / and
cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat
/boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8
>
> On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
> > I made some progresses, but not enough
> > I mounted the Fedora 40 / and
> > cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
> >
> > cat
> > /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
> >
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough
I mounted the Fedora 40 / and
cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat
/boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-
>
> On Tue, 4 Jun 2024 14:11:22 +0200, Patrick Dupre via users wrote:
>
> > > On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
> > >
> > > > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> > > > --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> > > > 0ab8c5a6-a
On Tue, 4 Jun 2024 14:11:22 +0200, Patrick Dupre via users wrote:
> > On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
> >
> > > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> > > --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> > > 0ab8c5a6-a344-48f8-afca-
On Tue, 2024-06-04 at 23:36 +0930, Tim via users wrote:
> You're supposed to reply to the bits you're responding to, and cut
> out
> the rest that isn't actually needed. Unfortunately people are
> forgetting this and trying to get an entire thread inside each and
> every message.
>
> If anyone ha
> On 4 Jun 2024, at 13:39, Patrick Dupre wrote:
>
>
>
>
> On 4 Jun 2024, at 13:11, Patrick Dupre via users
> wrote:
>
> Fedora 38 when I will be sure that I can have control on the full
> installation.
> The risk is that I lost more control, typically on the installation of sda4
>
On Mon, 2024-06-03 at 15:59 +0200, Patrick Dupre via users wrote:
> With your message we lost the thread.
The thread is there. You're not supposed to keep quoting every prior
reply when you respond to messages. Messages become huge and
unreadable messes.
You're supposed to reply to the bits you
On 4 Jun 2024, at 13:11, Patrick Dupre via users wrote:
Fedora 38 when I will be sure that I can have control on the full installation.
The risk is that I lost more control, typically on the installation of sda4
The way I test out new Fedora releases is to see if the live image w
> On 4 Jun 2024, at 13:11, Patrick Dupre via users
> wrote:
>
> Fedora 38 when I will be sure that I can have control on the full
> installation.
> The risk is that I lost more control, typically on the installation of sda4
The way I test out new Fedora releases is to see if the live image
>
> On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
>
> > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> > --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> > 0ab8c5a6-a344-48f8-afca-e6187c589cde
> > else
> > search --no-floppy --fs-uuid --set=root
> > 0ab8
On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
> search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> 0ab8c5a6-a344-48f8-afca-e6187c589cde
> else
> search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-
In my case
-rw-r--r--. 1 root root 160 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-0-memtest86+.conf
-rwxr-xr-x. 1 root root 417 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-0-rescue.conf
-rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.7-100.fc38.x86_64.conf
-rw
> On Tue, 4 Jun 2024 12:35:37 +0200, Patrick Dupre via users wrote:
>
> > but in the generated file (grub.cfg) there is no reference to Fedora 40
> > or sdc3
>
> What do you see in the grub2.cfg file section with the "10_linux" header?
### BEGIN /etc/grub.d/10_linux ###
insmod part_gpt
insmod ext
On Tue, 4 Jun 2024 12:35:37 +0200, Patrick Dupre via users wrote:
> but in the generated file (grub.cfg) there is no reference to Fedora 40
> or sdc3
What do you see in the grub2.cfg file section with the "10_linux" header?
--
___
users mailing list --
> On 4 Jun 2024, at 11:35, Patrick Dupre via users
> wrote:
>
> but in the generated file (grub.cfg) there is no reference to Fedora 40
> or sdc3
Fedora use BLS (boot loader specifcations) that are in /boot/loader/entries.
grub, by default, scans that folder and adds all the entries to the me
Hello,
With your message we lost the thread.
The Fedora 38 is installed on sda4 with /boot/efi on sda3 (fat16 EFI System
Partition)
The fedora 40 is installed on sdc3 I only have /boot installed on sdc2
I guess that I could run something like
grub-install /dev/sda --target=x86_64-efi --efi-direc
On Mon, Jun 3, 2024 at 3:11 AM Patrick Dupre via users
wrote:
> I updated a fedora 38 installation to 40 (on sdc3) as I used to do.
> But this installation is now not visible from the grub bot menu.
> I run grub2-mkconfig -o /boot/grub2/grub.cfg
> again, and again from both installation (40 and 38
On Mon, 2024-06-03 at 13:53 +0200, Patrick Dupre via users wrote:
> I wish to add that efibootmgr does not list the sdc3 installation.
By default, it'll only show the boot options that installations have
entered into it. If your install didn't do that, you can add entries,
yourself.
Have a look
I wish to add that
efibootmgr
does not list the sdc3 installation.
> Subject: Re: grub2-install
>
> Thank for the feedback,
>
> Thus, I am going to summarize the situation.
> I updated a fedora 38 installation to 40 (on sdc3) as I used to do.
> But this installation is now
Thank for the feedback,
Thus, I am going to summarize the situation.
I updated a fedora 38 installation to 40 (on sdc3) as I used to do.
But this installation is now not visible from the grub bot menu.
I run grub2-mkconfig -o /boot/grub2/grub.cfg
again, and again from both installation (40 and 38
On 2/6/24 23:00, Patrick Dupre via users wrote:
Hello,
There is bug reported about grub2-install
2240994
for a while
but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because
it does not support UEFI Secure Boot. If you really wish to procee
On 6/2/24 6:00 AM, Patrick Dupre via users wrote:
There is bug reported about grub2-install
2240994
for a while
but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because
it does not support UEFI Secure Boot. If you really wish to proceed, inv
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 almos
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 entr
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
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
did not see any error either.
I am going to
On Thu, Jun 15, 2023 at 8:03 PM Stephen Morris
wrote:
>
>
> On 12/6/23 05:24, George N. White III wrote:
>
> On Fri, Jun 9, 2023 at 9:54 PM Stephen Morris
> wrote:
>
>> 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
On 12/6/23 05:24, George N. White III wrote:
On Fri, Jun 9, 2023 at 9:54 PM Stephen Morris
wrote:
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 coupl
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
lik
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
On Fri, Jun 9, 2023 at 9:54 PM Stephen Morris
wrote:
> 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 u
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 d
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 egrep
"
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 reporting
> 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
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 reporting this.
For the most part this is just some attempt at reporting a "leaked"
file descriptor.I am not sure how o
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-mkconfig
> I have /boot/efi (UEFI
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 i
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/grub.cf
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 as the drive is GPT.
MBR is impli
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 not s
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 not su
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 Secure Boot.
> Sec
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
is my note fr
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
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 /home/pdupre/.serverauth.6
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 e
The big mistake is fixed.
Now, I am back to the previous situation where the boot does
not ask me for the paraphrase.
How can I fix this?
I though to make an additional installation with anaconda
However,
anaconda do see 2 installations
and a list of unknown partitions.
my /home encrypted partit
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 about what? If you use
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 list -- users@lists.fedoraproje
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 in VMware P
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 Player and for me
> that command d
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.
regards,
Steve
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 fastboot
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 Conduct:
https://d
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 men
On 8/28/20 2:15 PM, Samuel Sieb wrote:
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 roo
On Thu, 27 Aug 2020 at 19:02, Robert McBroom via users <
users@lists.fedoraproject.org> 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 o
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 mo
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: lset
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: (/boot/efi/EFI/fedora,
> sys
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 testing (5.5.15) and
On Mon, Apr 6, 2020 at 11:23 AM stan via users <
users@lists.fedoraproject.org> wrote:
> 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
>
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/entries.
I think
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
On Mon, 2020-04-06 at 18:24 +0930, Tim via users wrote:
> On Sun, 2020-04-05 at 20:57 -0500, Richard Shaw wrote:
> > I guess I'll have to wait for another kernel release to see if I can
> > figure out what's failing.
>
> If you didn't want to wait that long, you could temporarily enable the
> test
On Sun, 2020-04-05 at 20:57 -0500, Richard Shaw wrote:
> I guess I'll have to wait for another kernel release to see if I can
> figure out what's failing.
If you didn't want to wait that long, you could temporarily enable the
testing repos.
--
uname -rsvp
Linux 3.10.0-1062.18.1.el7.x86_64 #1 S
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/entries.
And even though I only have 3 kernels installed (all 5.5.x series) ther
On Sat, 2020-03-14 at 08:55 +1100, Philip Rhoades wrote:
> On 2020-03-14 05:12, Tom Horsley wrote:
> > On Sat, 14 Mar 2020 03:10:04 +1100
> > Philip Rhoades wrote:
> >
> > > In the olden days I used to just edit the grub conf file and delete
> > > these args manually - now I am supposed to use grub
On Sat, 14 Mar 2020 11:33:00 -0700 stan via users wrote:
> On Sat, 14 Mar 2020 22:23:41 +1100
> Philip Rhoades wrote:
>> GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d"
> Are you really trying to resume instead of booting from the installed
> system?
As far as I know this
On Sat, 14 Mar 2020 22:23:41 +1100
Philip Rhoades wrote:
> GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d"
Are you really trying to resume instead of booting from the installed
system?
As Francis already said, you are still booting using legacy grub, so
your grub.cfg will
Hi
On Sat, 14 Mar 2020 22:23:41 +1100 Philip Rhoades wrote:
> # cat /etc/default/grub
...
> GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d"
...
> GRUB_ENABLE_BLSCFG=true
With this, grub2-mkconfig will generate in /boot/grub2/grub.cfg (your
previous trace shows that your ma
sixpack13, Tom,
On 2020-03-14 10:48, sixpack13 wrote:
On 13.03.20 22:59, Philip Rhoades wrote:
...
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o
/boot/efi/EFI/fedora/grub.cfg || sudo grub2-mkconfig -o
/boot/grub2/grub.cfg
...
Did that but I still don't get the verbose boot .
On 13.03.20 23:03, Tom Horsley wrote:
On Sat, 14 Mar 2020 08:59:12 +1100
Philip Rhoades wrote:
Did that but I still don't get the verbose boot . .
Sounds an awful lot like you're booting something different
than you think you're booting. That's the only idea I have left.
...
+1
--
sixpack13
1 - 100 of 340 matches
Mail list logo
