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 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
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
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
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
On 28/5/19 3:17 am, ja wrote:
On Mon, 2019-05-27 at 19:10 +0200, Tom H wrote:
On 23/5/19 9:07 pm, Tom H wrote:
I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
"/etc/default/grub" _should_ (given the variable's name) allow
"grub2-mkconfig" give you an upstream-style "grub.cfg".
Thanks
On Mon, May 27, 2019 at 10:37 PM Chris Murphy wrote:
>
> On Thu, May 23, 2019 at 5:08 AM Tom H wrote:
> >
> > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > "/etc/default/grub" _should_ (given the variable's name) allow
> > "grub2-mkconfig" give you an upstream-style "grub.cfg".
>
On Thu, May 23, 2019 at 5:08 AM Tom H wrote:
>
> I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> "/etc/default/grub" _should_ (given the variable's name) allow
> "grub2-mkconfig" give you an upstream-style "grub.cfg".
It is also necessary to
# dnf install grubby-deprecated
I'm not s
On Mon, 2019-05-27 at 19:10 +0200, Tom H wrote:
> > On 23/5/19 9:07 pm, Tom H wrote:
> > > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > > "/etc/default/grub" _should_ (given the variable's name) allow
> > > "grub2-mkconfig" give you an upstream-style "grub.cfg".
> >
> > Thanks Tom
> On 23/5/19 9:07 pm, Tom H wrote:
>>
>> I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
>> "/etc/default/grub" _should_ (given the variable's name) allow
>> "grub2-mkconfig" give you an upstream-style "grub.cfg".
>
> Thanks Tom, "/etc/default/grub" had a setting of
> "GRUB_ENABLE_BLSCFG=
. Grub2-mkconfig
and grub2-install no longer seem to generate the grub menu as
they did under F29, the menu seems to be that generated by grubby
(it could be that turning off the suppression of sub-menu
creation is now being ignored). Looking at /boot/grub2/grub.cfg I
cannot see any references in
n a vm under vmware player. Grub2-mkconfig
>>> and grub2-install no longer seem to generate the grub menu as
>>> they did under F29, the menu seems to be that generated by grubby
>>> (it could be that turning off the suppression of sub-menu
>>> creation is now bein
On 23/5/19 3:49 pm, Tom H wrote:
On Thu, May 23, 2019 at 12:55 AM Stephen Morris
wrote:
I have upgraded from F29 to F30 via the recommenced dnf method. I
have Fedora running in a vm under vmware player. Grub2-mkconfig and
grub2-install no longer seem to generate the grub menu as they did
under
On Thu, May 23, 2019 at 12:55 AM Stephen Morris
wrote:
>
> I have upgraded from F29 to F30 via the recommenced dnf method. I
> have Fedora running in a vm under vmware player. Grub2-mkconfig and
> grub2-install no longer seem to generate the grub menu as they did
> under F29, the m
Hi,
I have upgraded from F29 to F30 via the recommenced dnf method. I
have Fedora running in a vm under vmware player. Grub2-mkconfig and
grub2-install no longer seem to generate the grub menu as they did under
F29, the menu seems to be that generated by grubby (it could be that
turning
On Sun, Aug 30, 2015 at 4:15 PM, Gordon Messmer
wrote:
> On 08/30/2015 05:27 AM, Tom H wrote:
>>
>> Crippling an upstream tool is beyond anything other distros patch.
>
>
> It's not crippled. The efi modules are packaged separately. If you know
> that you wan
On 08/30/2015 05:27 AM, Tom H wrote:
Crippling an upstream tool is beyond anything other distros patch.
It's not crippled. The efi modules are packaged separately. If you
know that you want to run grub2-install, then you need to install the
"grub2-efi-modules" package. Whe
On Sun, Aug 30, 2015 at 6:27 AM, Tom H wrote:
> On Sat, Aug 29, 2015 at 4:41 PM, Gordon Messmer
> wrote:
>> On 08/29/2015 01:03 PM, Tom H wrote:
>>>
>>> https://fedoraproject.org/wiki/GRUB_2
>>>
>>> I hadn't read that page. I stand corrected.
>>>
>>> How nice that Fedora diverges from upstream.
>
On 08/30/2015 01:35 PM, Chris Murphy wrote:
> I've already hinted at this, because those entries are either wrong or
> suboptimal. Each distro has its own /etc/default/grub which contains
> its own unique GRUB_CMDLINE_LINUX= which really only applies to that
> distro. The Ubuntu GRUB menu entries f
On Sun, Aug 30, 2015 at 4:19 AM, Paul Cartwright wrote:
> On 08/29/2015 11:12 PM, Chris Murphy wrote:
>>> > grub2-mkconfig will add entries for other operating systems it can find.
>>> > That will be done based on the output of the os-prober tool.
>> This is why one of my first modifications post-
On Sat, Aug 29, 2015 at 4:41 PM, Gordon Messmer
wrote:
> On 08/29/2015 01:03 PM, Tom H wrote:
>>
>> https://fedoraproject.org/wiki/GRUB_2
>>
>> I hadn't read that page. I stand corrected.
>>
>> How nice that Fedora diverges from upstream.
>
> It does, considerably:
> http://pkgs.fedoraproject.org/
On 08/29/2015 11:12 PM, Chris Murphy wrote:
>> > grub2-mkconfig will add entries for other operating systems it can find.
>> > That will be done based on the output of the os-prober tool.
> This is why one of my first modifications post-install is to
> /etc/default/grub to add
>
> GRUB_DISABLE_OS_P
On Sat, Aug 29, 2015 at 1:48 PM, Paul Cartwright wrote:
> grub2-mkconfig will add entries for other operating systems it can find.
> That will be done based on the output of the os-prober tool.
This is why one of my first modifications post-install is to
/etc/default/grub to add
GRUB_DISABLE_OS
On 08/29/2015 04:31 PM, Gordon Messmer wrote:
>>> >
>>> >https://fedoraproject.org/wiki/GRUB_2
>> so grub2-efi installs it, but how do you modify/maintain it??
>
> You don't. If you modify the grub2 binary, the signature is invalid
> and the system won't boot (under Secure Boot). There is almost
On 08/29/2015 01:03 PM, Tom H wrote:
the grub2-install command
>creates a custom grubx64.efi, deletes the original installed one, and looks
>for grub.cfg in /boot/grub2/."
>https://fedoraproject.org/wiki/GRUB_2
I hadn't read that page. I stand corrected.
How nice that F
On 08/29/2015 12:51 PM, Paul Cartwright wrote:
Not according to the documentation, which indicates that:
>"grub2-install shouldn't be used on EFI systems. The grub2-efi package
>installs a prebaked grubx64.efi on the EFI System partition, which
>looks for grub.cfg on th
On Sat, Aug 29, 2015 at 2:59 PM, Gordon Messmer
wrote:
> On 08/29/2015 03:20 AM, Tom H wrote:
>>
>> grub2-install works on non-SB systems.
>> And there's no reason that it shouldn't work on SB systems. Aren't the
>> grub and shim executables simply copie
On 08/29/2015 02:59 PM, Gordon Messmer wrote:
>> grub2-install works on non-SB systems.
>> And there's no reason that it shouldn't work on SB systems. Aren't the
>> grub and shim executables simply copied from "/usr/something"? So they
>> should b
On 08/29/2015 03:00 PM, Gordon Messmer
wrote:
it
would really be nice if there was some HOW-TO or documentation
on all
this new UEFI/shim packages...
There is.
https://fedoraproject.or
On 08/29/2015 04:15 AM, Paul Cartwright wrote:
it would really be nice if there was some HOW-TO or documentation on all
this new UEFI/shim packages...
There is.
https://fedoraproject.org/wiki/GRUB_2
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription optio
On 08/29/2015 03:20 AM, Tom H wrote:
grub2-install works on non-SB systems.
And there's no reason that it shouldn't work on SB systems. Aren't the
grub and shim executables simply copied from "/usr/something"? So they
should be signed.
Not according to the documentat
On 08/29/2015 02:17 AM, Chris Murphy wrote:
>> > https://fedoraproject.org/wiki/GRUB_2
>> >
>> > yum install grub2-efi grub2-efi-modules shim
> grub2-efi-modules is not necessary unless you plan on going off the
> rails with GRUB modules that aren't baked into the signed Fedora GRUB
> EFI OS Loader
On 08/29/2015 06:20 AM, Tom H wrote:
>> > grub2-install does not apply on UEFI systems at all, it should not be
>> > used. Instead you reinstall shim and grub2-efi packages.
> grub2-install works on non-SB systems.
SB-systems?
>
> And there's no reason that it shou
On Fri, Aug 28, 2015 at 12:02 PM, Chris Murphy wrote:
> On Wed, Aug 26, 2015 at 10:33 AM, Paul Cartwright
> wrote:
>>
>> I installed my new drive, and everything was fine. I added another OS,
>> and now I can't do the grub2-install anymore. What am I missing??
&
On Fri, Aug 28, 2015 at 11:06 AM, Paul Cartwright
wrote:
> On 08/28/2015 12:02 PM, Chris Murphy wrote:
>> grub2-install does not apply on UEFI systems at all, it should not be
>> used. Instead you reinstall shim and grub2-efi packages.
>>
> ok, I wasn't aware of thi
On 08/28/2015 12:02 PM, Chris Murphy wrote:
> grub2-install does not apply on UEFI systems at all, it should not be
> used. Instead you reinstall shim and grub2-efi packages.
>
ok, I wasn't aware of this shim package, but I see how that works now...
https://fedoraproject.org/wi
On 08/28/2015 12:02 PM, Chris Murphy wrote:
> grub2-install does not apply on UEFI systems at all, it should not be
> used. Instead you reinstall shim and grub2-efi packages.
>
thanks, I got some other replies that mentioned efibootmgr, and that did
the trick.
my default grub was ubun
On Wed, Aug 26, 2015 at 10:33 AM, Paul Cartwright
wrote:
> I installed my new drive, and everything was fine. I added another OS,
> and now I can't do the grub2-install anymore. What am I missing??
>
> # grub2-install /dev/sda
> grub2-install: error: /usr/lib/grub/x86_64-ef
I installed my new drive, and everything was fine. I added another OS,
and now I can't do the grub2-install anymore. What am I missing??
# grub2-install /dev/sda
grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.
Please specify --target or --directory.
boot
On 04/21/2014 06:52 AM, Edward M wrote:
On 4/20/2014 12:13 PM, Jim wrote:
fedora 20
I installed Fedora 20 on /dev/sdb1 and after installation was
completed it didn't select /dev/sdb1 and bootup .
I have Windows on sda1 so i put a sdb in computer for Linux.
Is the command, grub2-in
On 04/21/2014 06:52 AM, Edward M wrote:
On 4/20/2014 12:13 PM, Jim wrote:
fedora 20
I installed Fedora 20 on /dev/sdb1 and after installation was
completed it didn't select /dev/sdb1 and bootup .
I have Windows on sda1 so i put a sdb in computer for Linux.
Is the command, grub2-in
On 4/20/2014 12:13 PM, Jim wrote:
fedora 20
I installed Fedora 20 on /dev/sdb1 and after installation was
completed it didn't select /dev/sdb1 and bootup .
I have Windows on sda1 so i put a sdb in computer for Linux.
Is the command, grub2-install /dev/sdb1 the correct command for
bo
fedora 20
I installed Fedora 20 on /dev/sdb1 and after installation was completed
it didn't select /dev/sdb1 and bootup .
I have Windows on sda1 so i put a sdb in computer for Linux.
Is the command, grub2-install /dev/sdb1 the correct command for booting
Fedora 20 on sdb1 ?
--
63 matches
Mail list logo
