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
>
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 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 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-
-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
Spec files that use this variable work
correctly even
# without a grubenv file, define a fallback kernelopts variable if this has not
been set.
#
# The kernelopts variable in the grubenv file can be modified using the grubby
tool or by
# executing the grub2-mkconfig tool. For t
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,
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
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
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?
> >
> > In addition,
> >
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
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&qu
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
>
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
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
> > > "gr
> 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"
. 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
On Thu, May 23, 2019 at 11:12 AM Stephen Morris
wrote:
> 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 i
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 Tue, 2018-11-27 at 16:17 -0700, linux guy wrote:
> Interesting. /boot/efi/EFI/fedora/grub.cfg didn't exist on my
> workstation. But /etc/grub2-efi.cfg points to it ! /boot/efi
> existed, but it was empty.
This means that either /boot/efi/ isn't mounted after you reboot (check
/etc/fstab)
On 11/27/18 3:17 PM, linux guy wrote:
Interesting. /boot/efi/EFI/fedora/grub.cfg didn't exist on my
workstation. But /etc/grub2-efi.cfg points to it ! /boot/efi existed,
but it was empty.
How are you booting into it right now to do this?
Btw, both grub.cfg symlinks are always created whet
Interesting. /boot/efi/EFI/fedora/grub.cfg didn't exist on my
workstation. But /etc/grub2-efi.cfg points to it ! /boot/efi existed,
but it was empty.
I created /boot/efi/EFI/fedora/.
I ran grub2-mkconfig -o/boot/grub2/grub.cfg It ran without error.
I rebooted using shutdown -r n
Thank you.
On Mon, Nov 26, 2018 at 11:12 PM Samuel Sieb wrote:
> On 11/26/18 7:56 PM, linux guy wrote:
> > It still boots to the grub prompt, even when I use -o
> /boot/grub2/grub.cfg
>
> That is still the wrong file. You need either
> /boot/efi/EFI/fedora/grub.cfg
> or
> /etc/grub2-efi.cfg whi
On 11/26/18 7:56 PM, linux guy wrote:
It still boots to the grub prompt, even when I use -o /boot/grub2/grub.cfg
That is still the wrong file. You need either
/boot/efi/EFI/fedora/grub.cfg
or
/etc/grub2-efi.cfg which is a symlink to the first one.
__
)/initramfs-0-rescueimg
> > grub>boot
> >
> > I can get networking working
> > #ls /sys/call/net <- find Ethernet device is enp3s0
> > # ifup enp3s0
> > # ping www.google.com
> >
> > Now update it
> > # dnf update
>
> Does dnf
It still boots to the grub prompt, even when I use -o /boot/grub2/grub.cfg
On Thu, Nov 1, 2018 at 1:33 PM linux guy wrote:
> I was running grub2-mkconfig. I did not use -o.
>
> I never even thought of that. I was running it from the wrong directory
> ! Good catch. Thanks
I was running grub2-mkconfig. I did not use -o.
I never even thought of that. I was running it from the wrong directory
! Good catch. Thanks for replying.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users
s0
> # ifup enp3s0
> # ping www.google.com
>
> Now update it
> # dnf update
>
> Regenerate the grub2 config file
> # grub2-mkconfig
Are you running this exact command? Or are you running "grub2-mkconfig
-o /boot/grub2/grub.cfg"?
> Reboot
> # shutdown -r no
net device is enp3s0
> # ifup enp3s0
> # ping www.google.com
>
> Now update it
> # dnf update
Does dnf give any errors because of the interrupted update?
>
> Regenerate the grub2 config file
> # grub2-mkconfig
>
> Reboot
> # shutdown -r now
>
> It still b
. root=/dev/mapper/fedora-root
grub>initrdefi (hd0,gpt2)/initramfs-0-rescueimg
grub>boot
I can get networking working
#ls /sys/call/net <- find Ethernet device is enp3s0
# ifup enp3s0
# ping www.google.com
Now update it
# dnf update
Regenerate the grub2 config file
# grub2-m
On 07/27/2018 11:44 AM, Patrick Dupre wrote:
On 07/27/2018 11:19 AM, Patrick Dupre wrote:
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/gru
> On 07/27/2018 11:19 AM, Patrick Dupre wrote:
> >>
> >> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> >>> If I run a system on VolSys1-root, and if I run grub2-mkconfig
> >>> with
> >>> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/roo
On 07/27/2018 11:19 AM, Patrick Dupre wrote:
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.1
>
> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> > If I run a system on VolSys1-root, and if I run grub2-mkconfig
> > with
> > GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> > in /etc/default/grub
> > I get in grub.cfg
> >
&g
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSy
Hello,
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
rd.lvm.lv=VolSys0/root nouveau
On 02/26/18 07:48, Celso Viana wrote:
> Is there no more "grub2-mkconfig" in Fedora 27?
dnf is your friend
egreshko@meimei system]$ dnf whatprovides *bin/grub2-mkconfig
Last metadata expiration check: 0:56:28 ago on Mon 26 Feb 2018 06:54:20 AM CST.
grub2-tools-1:2.02-2
Hi all,
Is there no more "grub2-mkconfig" in Fedora 27?
Thanks
--
Celso Vianna
BSD User: 51318
http://www.bsdcounter.org
Palmas/TO
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email t
On Sat, Jan 20, 2018 at 10:47 AM, Tom Horsley wrote:
> On Sat, 20 Jan 2018 10:24:26 -0500
> Sam Varshavchik wrote:
>>
>> Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and then
>> subsequently installed kernels new without grubby causing any issues?
>
doesn't know anything about it.
"/etc/default/grub" is used by "grub2-mkconfig" and not by "grubby".
> If I run grub2-mkconfig, it generates something completely different
> from the existing grub.cfg. I have not analyzed the differences, but
>
On 21/1/18 12:50 pm, stan wrote:
On Sun, 21 Jan 2018 11:30:46 +1100
Stephen Morris wrote:
I have always used grub2-mkconfig and the old grub equivalent as I
have never liked the boot menus that grubby generates. The one thing
I don't like about this process is that I also boot Ubunt
On Sun, 21 Jan 2018 11:30:46 +1100
Stephen Morris wrote:
> I have always used grub2-mkconfig and the old grub equivalent as I
> have never liked the boot menus that grubby generates. The one thing
> I don't like about this process is that I also boot Ubuntu and
> Windows from
On 21/1/18 4:58 am, stan wrote:
On Sat, 20 Jan 2018 10:24:26 -0500
Sam Varshavchik wrote:
Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and
then subsequently installed kernels new without grubby causing any
issues?
Yes, I've done this without any problems. Grubby
On Sat, 20 Jan 2018 10:24:26 -0500
Sam Varshavchik wrote:
> Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and
> then subsequently installed kernels new without grubby causing any
> issues?
Yes, I've done this without any problems. Grubby puts the latest en
On Sat, 20 Jan 2018 10:24:26 -0500
Sam Varshavchik wrote:
> Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and then
> subsequently installed kernels new without grubby causing any issues?
I never use /etc/default/grub, I always edit the grub.cfg file by hand.
The whole
appears to be responsible for updating grub.cfg, and it does that,
apparently (not 100% sure) by cloning existing kernel entries; and the
/etc/default/grub file comes from the grub2-tool package, and grubby doesn't
know anything about it.
If I run grub2-mkconfig, it generates something compl
On 13/07/16 04:24, Tom H wrote:
On Mon, Jul 11, 2016 at 3:55 PM, Chris Murphy wrote:
The built-in method to discover and create menu entries for other
Linux's is suboptimal. If you update the kernel on any of those
distros, it's not reflected in the GRUB menu because each distro only
updates it
On Mon, Jul 11, 2016 at 3:55 PM, Chris Murphy wrote:
>
> The built-in method to discover and create menu entries for other
> Linux's is suboptimal. If you update the kernel on any of those
> distros, it's not reflected in the GRUB menu because each distro only
> updates its own grub.cfg; and the G
On 07/11/2016 01:19 PM, stan wrote:
In the old grub, there used to be a command to switch immediately to
the configuration file for another installation. I looked for how I
used to do that, but I haven't got any installations with old grub
left. It's been years since fedora switched to grub2.
On Mon, 11 Jul 2016 16:45:55 +0300
Kevin Wilson wrote:
> Hi,
> Thanks Todd.
> The thing is that now CentOS is installed and it is the current
> control and it indeed uses an older grub. So what do you suggest ?
In the old grub, there used to be a command to switch immediately to
the configuratio
of the Fedora 24 net installs or server DVD, go
> to Troubleshooting in the boot menu, then choose to rescue a fedora
> system, and that will help assemble Fedora from fstab at /mnt/sysimage
> and then just 'chroot /mnt/sysimage' rather than assembling it by
> hand.
>
>
4 net installs or server DVD, go
to Troubleshooting in the boot menu, then choose to rescue a fedora
system, and that will help assemble Fedora from fstab at /mnt/sysimage
and then just 'chroot /mnt/sysimage' rather than assembling it by
hand.
grub2-install
grub2-mkconfig -o /boot/gr
dev/sdX
Try including the patch in this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1353026
And then run
grub2-mkconfig -o /boot/grub2/grub.cfg
> That I will reinstall Ubuntu on Fedora on the current machine so they
> will the "current control"? It is quite a hassle as ther
If you have a Fedora live disk you can boot to that and use the chroot
method to install grub from your Fedora install on your disk. A bit more
complicated but good tutorials out there.
Things are always complicated when you do several distros on a single
disk. A bit easier if separate disks. Y
Ok, I meant to say "Google is our friend". I consider myself your friend
but the time to put together tutorials on procedures where many already
exist is not what I plan to do today.
On Mon, Jul 11, 2016 at 10:36 AM, Tod Merley wrote:
> It sounds like your "most recent" distro is Fedora - so -
It sounds like your "most recent" distro is Fedora - so - re-install grub
from Fedora. Google is your friend.
On Mon, Jul 11, 2016 at 6:45 AM, Kevin Wilson wrote:
> Hi,
> Thanks Todd.
> The thing is that now CentOS is installed and it is the current
> control and it indeed uses an older grub. S
Hi,
Thanks Todd.
The thing is that now CentOS is installed and it is the current
control and it indeed uses an older grub. So what do you suggest ?
That I will reinstall Ubuntu on Fedora on the current machine so they
will the "current control"? It is quite a hassle as there is no free
partition fo
I mean run "update-grub" from the Ubuntu distribution. It is the control.
On Sun, Jul 10, 2016 at 11:38 AM, Tod Merley wrote:
> On a multi-boot machine the big question is “who controls the boot
> process”.
>
>
> My “big box” has two SSD (Ubuntu, CentOS) a 1T HDD (eight Linux partitions
> if me
On a multi-boot machine the big question is “who controls the boot process”.
My “big box” has two SSD (Ubuntu, CentOS) a 1T HDD (eight Linux partitions
if memory serves) and a small clunky HDD with W7.
In this case I choose Ubuntu to control the boot process and understand
that if I update the
Hello,
On a machine with Fedora 23 grub2, I use "grub2-mkconfig -o
/boot/grub2/grub.cfg" in order to update
/boot/grub2/grub.cfg if there are changes in /etc/default/grub.
Running this command also
sees to it that if there are other installations of Linux on the
machine, and if the
And even *better* would be to disable 30_os-prober, and instead of
copy pasting corrected grub2-mkconfig output into
/etc/grub.d/40_custom, would be to create menuentries using the
configfile command that point to the real grub.cfg for each distro on
your system. That way you use that distro&#
run grub2-mkconfig. This will cause it to use the statically generated
/etc/grub.d/40_custom corrected contents, and not run
/etc/grub.d/30_os-prober.
You can disable 30_os-prober by editing /etc/default/grub and adding
GRUB_DISABLE_OS_PROBE="true"
The next time you run grub2-mkconfi
ue, France
===
> Sent: Sunday, February 08, 2015 at 5:41 PM
> From: "Chris Murphy"
> To: "Community support for Fedora users"
> Subject: Re: grub2-mkconfig
>
> On S
n16
> rd.lvm.lv=VolGrpSys0/root LANG=en_US.UTF-8
What the hell? Every Fedora 20 entry says VolGrpSys2-root in the
description, but the kernel parameter line uses VolGrpSys0-root. This
is why I hate multibooting and find it fundamentally flawed and
perilous. Better to use VMs.
Anyway, you might get
x27; x = x ']'
+ pkgdatadir=/usr/share/grub
+ grub_cfg=
+ grub_mkconfig_dir=/etc/grub.d
++ basename grub2-mkconfig
+ self=grub2-mkconfig
+ grub_probe=/usr/sbin/grub2-probe
+ grub_file=/usr/bin/grub2-file
+ grub_editenv=/usr/bin/grub2-editenv
+ grub_script_check=/usr/bin/grub2-script-check
+ ex
1 - 100 of 153 matches
Mail list logo
