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'
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
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:
> > >
&g
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/modi
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
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.
poc
--
___
an older version.
We have an issue in that the kernels appear to require the command
line option "rd.auto" for the older systems to boot with the rootfs
using software raid. When we use grub2-mkconfig (or update a kernel
which I guess also uses this) the produced /boot/grub2/gru
that the kernels appear to require the command line
option "rd.auto" for the older systems to boot with the rootfs using
software raid. When we use grub2-mkconfig (or update a kernel which I
guess also uses this) the produced /boot/grub2/grub.cfg file does not
have "rd.auto
command line
option "rd.auto" for the older systems to boot with the rootfs using
software raid. When we use grub2-mkconfig (or update a kernel which I
guess also uses this) the produced /boot/grub2/grub.cfg file does not
have "rd.auto" in the kernel command line and so the old
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
booting.
> The most recently installed Fedora bootloader will be the one whose ESP entry
> in
> /boot/efi/EFI/fedora/ is in control of UEFI booting.
>
> Please boot in UEFI mode, then gather and provide here output from:
OK, I see
By default, I was not using UEFI to boot.
It means that I us
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
>
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/entr
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-
> You can run e.g. blkid -U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find
> > > out.
> > > Or run "blkid" and skim over the output.
> > This is sda4 where Fedora 38 is installed (sda4)
>
> There are two entries! What about the second entry with
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
-80F4
>
> What partitions do these two UUIDs refer to?
> You can run e.g. blkid -U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find out.
> Or run "blkid" and skim over the output.
This is sda4 where Fedora 38 is installed (sda4)
>
>
> > This is the fedora 38
-U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find out.
Or run "blkid" and skim over the output.
> This is the fedora 38
Do you mean you're running F38 and trying to reconfigure Grub2?
Or what scenario is it exactly?
--
___
-rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.8-100.fc38.x86_64.conf
-rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.9-100.fc38.x86_64.conf
As anticipate no Fedora 40 while grub2-mkconfig
says
Found Fedora Linux 40 (Forty) on /dev
> 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/1
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?
--
___
us
> 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,
I am still stuck with my installation.
Question
Why
grub2-mkconfig
says
Found Fedora Linux 36 (Workstation Edition) on /dev/sdb11
Found Fedora Linux 40 (Forty) on /dev/sdc3
Found Fedora Linux 36 (Workstation Edition) on /dev/mapper/VolSys_2-root
Adding boot menu entry for UEFI Firmware
-directory=/boot/efi/
but this provide an error as indicated in my previous message.
sda1 is BIOS boot partition grub2 core.img (I cannot mount it)
efibootmgr -v
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0006,0004,0005,0002,0001
Boot* fedora
HD(3,GPT,01dd38df-fda0-487b-add4
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 installa
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
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
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 proceed, invoke the
--force option.
Make sure Secure
root 2960704 Mar 8 01:00 grubia32.efi
-rwx--. 1 root root 3968320 Mar 8 01:00 grubx64.efi
-rwx--. 1 root root 148 Jun 13 2021 grub.cfg
-rwx--. 1 root root1024 Jun 13 2021 grubenv.rpmsave
-rwx--. 1 root root 10306 Jul 2 2020 grub.cfg.rpmsave
When I run
grub2-mkconfig
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
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 --
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 usi
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? I'm
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 wi
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 recollectio
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 ago
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 to
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
disk, 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 recoll
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
38, 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
>> l
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
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
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 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
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 the
"
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
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 this
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)' --
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
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/
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 ma
rk. I guess
the entire internal 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
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
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
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
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
1 - 100 of 812 matches
Mail list logo
