On 5/2/25 15:45, Adam Williamson wrote:
On Fri, 2025-05-02 at 12:59 -0600, Leo Sandoval wrote:
Hi team,
My mistake: So I was trying to launch an official build for *f40* but I
did a wrong copy & paste from notes and still on the f40 working dir so I
launched the build with the *--release rawhi
On Fri, 2025-05-02 at 12:59 -0600, Leo Sandoval wrote:
> Hi team,
>
> My mistake: So I was trying to launch an official build for *f40* but I
> did a wrong copy & paste from notes and still on the f40 working dir so I
> launched the build with the *--release rawhide* parameter which is of
> cours
> wrote:
> >
> > On Thu, May 01, 2025 at 10:49:26AM -0400, Yaakov Selkowitz wrote:
> > > Yesterday there was a build of grub2 (2.12-17) from the f40 branch
> which was
> > > also built for rawhide/f43 and ELN. This was an NVR regression, as the
> > >
On Thu, May 01, 2025 at 10:49:26AM -0400, Yaakov Selkowitz wrote:
> Yesterday there was a build of grub2 (2.12-17) from the f40 branch which was
> also built for rawhide/f43 and ELN. This was an NVR regression, as the
> previous rawhide and ELN builds were 2.12-30 off the rawhide b
On Thu, May 1, 2025 at 11:04 AM Daniel P. Berrangé wrote:
>
> On Thu, May 01, 2025 at 10:49:26AM -0400, Yaakov Selkowitz wrote:
> > Yesterday there was a build of grub2 (2.12-17) from the f40 branch which was
> > also built for rawhide/f43 and ELN. This was an NVR regression, a
On Thu, 2025-05-01 at 10:49 -0400, Yaakov Selkowitz wrote:
> Yesterday there was a build of grub2 (2.12-17) from the f40 branch which
> was also built for rawhide/f43 and ELN. This was an NVR regression, as
> the previous rawhide and ELN builds were 2.12-30 off the rawhide bran
Yesterday there was a build of grub2 (2.12-17) from the f40 branch which
was also built for rawhide/f43 and ELN. This was an NVR regression, as
the previous rawhide and ELN builds were 2.12-30 off the rawhide branch
(as expected).
--
Yaakov Selkowitz
Principal Software Engineer, Emerging
Grr, sorry for the empty reply, that's what I get for emailing while
sick.
Once upon a time, Chris Adams said:
> > Netboot fixes are now integrated into rawhide, no official build yet just a
> > scratch one: https://koji.fedoraproject.org/koji/taskinfo?taskID=122703223
I can confirm that netboot
Once upon a time, Leo Sandoval said:
> On Fri, Aug 30, 2024 at 2:16 PM Leo Sandoval wrote:
>
> > Hi Adam / Team
> >
> > On Thu, Aug 1, 2024 at 10:01 AM Adam Williamson <
> > adamw...@fedoraproject.org> wrote:
> >
> >> On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
> >> > > >
> >> > > > A
On Fri, 2024-08-30 at 14:24 -0600, Leo Sandoval wrote:
> On Fri, Aug 30, 2024 at 2:16 PM Leo Sandoval wrote:
>
> > Hi Adam / Team
> >
> > On Thu, Aug 1, 2024 at 10:01 AM Adam Williamson <
> > adamw...@fedoraproject.org> wrote:
> >
> > > On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
> >
On Fri, Aug 30, 2024 at 2:16 PM Leo Sandoval wrote:
> Hi Adam / Team
>
> On Thu, Aug 1, 2024 at 10:01 AM Adam Williamson <
> adamw...@fedoraproject.org> wrote:
>
>> On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
>> > > >
>> > > > Again, once we have something solid, I will share relevant
Hi Adam / Team
On Thu, Aug 1, 2024 at 10:01 AM Adam Williamson
wrote:
> On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
> > > >
> > > > Again, once we have something solid, I will share relevant links for
> > > further community reviewing & testing.
> > > >
> > >
> > > Any progress on thi
Once upon a time, Leo Sandoval said:
> BTW, netbooting is not working on some configurations (we have four test
> variables: archs>, a few of them work..). Progress is tracked at
> https://bugzilla.redhat.com/show_bug.cgi?id=2303727
Hey, it's me! :) Despite my IPv6 early-adopter status, I don't
a.riscv.rocks:3000/rpms/grub2/commit/38415bc393864606b7b99be71dc30f3f519d06cb
The mcmodel in that PR is separate from the issue with these and
reported upstream.
https://savannah.gnu.org/bugs/?65909
On Fri, Aug 9, 2024 at 12:41 PM Adam Williamson
wrote:
>
> On Thu, 2024-08-01 at 07:46 -0600,
On Fri, Aug 9, 2024 at 10:41 AM Adam Williamson
wrote:
> On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
> > >
> > > Any progress on this? We're gearing up to Flock and branching will be
> > > the week after Flock...
> > >
> >
> > No progress since last email... Still in the testing phase.
On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
> >
> > Any progress on this? We're gearing up to Flock and branching will be
> > the week after Flock...
> >
>
> No progress since last email... Still in the testing phase.
There's progress now - the last build that was sent passed openQA
On Thu, 2024-08-01 at 07:46 -0600, Leo Sandoval wrote:
> > >
> > > Again, once we have something solid, I will share relevant links for
> > further community reviewing & testing.
> > >
> >
> > Any progress on this? We're gearing up to Flock and branching will be
> > the week after Flock...
> >
wrote:
> >> > On Tue, May 21, 2024 at 10:57:42AM GMT, Leo Sandoval wrote:
> >> > > Hi team,
> >> > >
> >> > > We (the Red Hat bootloader team) are completing the work of
> >> > > rebasing/reviewing/testing current rawhide
> > Hi team,
>> > >
>> > > We (the Red Hat bootloader team) are completing the work of
>> > > rebasing/reviewing/testing current rawhide patches, from GRUB2 2.06 to
>> > > 2.12, so at
>> > > some point in the near future these would la
mpleting the work of
> > > rebasing/reviewing/testing current rawhide patches, from GRUB2 2.06 to
> > > 2.12, so at
> > > some point in the near future these would land finally into rawhide.
> Once
> > > everything is in place, we would like your help to start testing
On Wed, Jun 19, 2024 at 11:02:57AM GMT, Andrea Bolognani wrote:
> On Tue, May 21, 2024 at 10:57:42AM GMT, Leo Sandoval wrote:
> > Hi team,
> >
> > We (the Red Hat bootloader team) are completing the work of
> > rebasing/reviewing/testing current rawhide patches, from GR
On Tue, May 21, 2024 at 10:57:42AM GMT, Leo Sandoval wrote:
> Hi team,
>
> We (the Red Hat bootloader team) are completing the work of
> rebasing/reviewing/testing current rawhide patches, from GRUB2 2.06 to
> 2.12, so at
> some point in the near future these would land finally
On Tue, May 21, 2024 at 12:58 PM Leo Sandoval wrote:
>
> Hi team,
>
> We (the Red Hat bootloader team) are completing the work of
> rebasing/reviewing/testing current rawhide patches, from GRUB2 2.06 to 2.12,
> so at
> some point in the near future these would land final
Hi team,
We (the Red Hat bootloader team) are completing the work of
rebasing/reviewing/testing current rawhide patches, from GRUB2 2.06 to
2.12, so at
some point in the near future these would land finally into rawhide. Once
everything is in place, we would like your help to start testing the
tation can be wrong
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/#sec-grub2-reinstall_on_UEFI-Based_Machines
> That’s really a challenge. You don’t describe what you did in detail.
I did some notes,
omplete new installation, but use ANACONDA from the live image to
replace btrfs by a LVM system reproducing your old LVM partitions as close as
possible and use grub2 (maybe you have to use the everything net install
medium). When the system boots, clone your LVM partitions (each partition
separat
that I need to
run one time
'grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg' . I think is wrong
use grub2-mkconfig -o /boot/grub2/grub.cfg , like it is wrote on grub2
on a uefi system [2], should we fix it ? and the advice of boot with
selinux=0 ?
Best regards,
rst partition starts at sector 63, as all installations of that
time did
My actual PC would be UEFI compatible, but it never got upgraded from
bios boot to efi.
(I tried before i downgraded, but that grub2-install complained about
missing secure boot for whatever reason)
== YESTERDAY ==
Bec
On Wed, Apr 26, 2023, at 12:26 AM, Philip Rhoades via devel wrote:
> People,
>
> LILO and SysLinux were simple and GRUB1 was straightforward - but by the
> time GRUB2 came around I was long past configuring my own kernels and
> hacking around at a lower level . . now I think,
People,
LILO and SysLinux were simple and GRUB1 was straightforward - but by the
time GRUB2 came around I was long past configuring my own kernels and
hacking around at a lower level . . now I think, finally, I need to know
more about how GRUB2 - works specifically with Fedoras 38+.
This
Hi,
another experiment proposal for Dominik 'Rathann' Mierzejewski:
Zeroize the GPT of a copy of boot-grub2-f36.iso and adjust MBR partition 1.
Do this in bash for the $'\x...' gestures:
# Create the playground
cp boot-grub2-f36.iso test.iso
# Zeroize the main GPT
Hi,
i wrote:
> > If test_oldlayout.iso does not boot, then i am quite clueless.
Dominik 'Rathann' Mierzejewski wrote:
> I'm afraid that this is the case.
What a naughty machine. :))
I'll think about making a BIOS-only GRUB ISO, just for testing.
(Am busy with finding out how to merge the two De
Hello, Thomas.
Thanks for your patience. I would've gotten the results sooner,
but life got in the way.
On Tuesday, 26 April 2022 at 23:18, Thomas Schmitt wrote:
> Hi,
> If test_oldlayout.iso does not boot, then i am quite clueless.
I'm afraid that this is the case. I'll try to re-do the ISO man
>
> > > == Summary ==
> > > Modify
> > > [https://github.com/weldr/lorax/tree/master/share/templates.d/99-generic
> > > lorax-generic-templates] to use GRUB2 when booting the boot.iso on
> > > BIOS systems, instead of syslinux. Upstream syslinux d
hare/templates.d/99-generic
> > lorax-generic-templates] to use GRUB2 when booting the boot.iso on
> > BIOS systems, instead of syslinux. Upstream syslinux development is
> > dead, and the Fedora maintainer would like to drop the package from
> > the distribution. GRU
oposals are publicly announced in order to receive
> > community feedback. This proposal will only be implemented if approved
> > by the Fedora Engineering Steering Committee.
> >
> > == Summary ==
> > Modify
> > [https://github.com/weldr/lorax/tree/master/shar
posal will only be implemented if approved
> by the Fedora Engineering Steering Committee.
>
> == Summary ==
> Modify
> [https://github.com/weldr/lorax/tree/master/share/templates.d/99-generic
> lorax-generic-templates] to use GRUB2 when booting the boot.iso on
> BIOS sy
f approved
> by the Fedora Engineering Steering Committee.
>
> == Summary ==
> Modify
> [https://github.com/weldr/lorax/tree/master/share/templates.d/99-generic
> lorax-generic-templates] to use GRUB2 when booting the boot.iso on
> BIOS systems, instead of syslinux. Upstream sys
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Modify [https://github.com/weldr/lorax/tree/master/share/templates.d/99-generic
lorax-generic-templates] to use GRUB2 when booting the boot.iso on
BIOS systems, instead of
Committee.
== Summary ==
Modify [https://github.com/weldr/lorax/tree/master/share/templates.d/99-generic
lorax-generic-templates] to use GRUB2 when booting the boot.iso on
BIOS systems, instead of syslinux. Upstream syslinux development is
dead, and the Fedora maintainer would like to drop the
" in the
specs protects it.
)
I am somewhat astonished that no BIOS machine was encountered yet in the
tests of boot-grub2-f36.iso which would refuse to boot with its pure
GPT-marking MBR table but would boot if the boot/active flag is set somwhere
in the MB
any machines around which suffer from the yet unknown
> particular demand of the Dell XPS 15 L502X.
>
> I am still pondering what to try next when the experiment results are in.
>
> If test_oldlayout.iso boots, then the next step would possibly to deface
> the GPT of boot-grub2-f3
ondering what to try next when the experiment results are in.
If test_oldlayout.iso boots, then the next step would possibly to deface
the GPT of boot-grub2-f36.iso by changing the type of MBR partition 1 from
0xEE to 0x83 or 0x00. If that does not boot, then i would ask for setting
the boot flag of pa
On Sat, Apr 23, 2022 at 10:43:39AM +0200, Thomas Schmitt wrote:
> Hi,
>
> i uploaded a new GNU xorriso development tarball for the next experiment
> with the Dell XPS 15 L502X of Dominik 'Rathann' Mierzejewski.
I followed your instructions and confirmed that this method still works
with qemu bios
t experiment:
# Extract the EFI partition
dd if=boot-grub2-f36.iso bs=512 skip=1313268 count=20288 of=test_efi.img
# Extract the MBR code
dd if=boot-grub2-f36.iso bs=1 count=446 of=test_mbr.img
# Pad MBR up to 32768 bytes, so that it overwrites the loaded system area
dd if=
On 4/20/22 17:25, Thomas Schmitt wrote:
> Hi,
>
Thanks Thomas for the reply. You've given us some good information to
consider/pursue.
Dusty
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fe
Hi,
i wrote:
> Whatever, if you want to try already now with the buggy result,
It comes to me that the MBR signature will be missing too. So it won't
be recognized by BIOS and its x86 code won't start.
The signature could be inserted by
echo $'\x55'$'\xAA' | dd of="$new_iso" conv=notrunc bs=1
Hi,
i wrote:
> > Does it boot with ubuntu-21.10-desktop-amd64.iso ?
Dominik 'Rathann' Mierzejewski wrote:
> It doesn't. Same error.
> [...]
> $ grub2-mkrescue -o output-mbr.iso --mbr-force-bootable minimal
> gives me the "Operation System not found"
hat does the trick.
>
> Building something nearer to the old ISO layout:
[...]
Unfortunately, that one doesn't boot.
> --
>
> If above boots on the Dell XPS 15 L502X, we should confirm that the MBR
> boot/active
Hi,
Dusty Mabe wrote:
> Currently we use isohybrid [1] (also from syslinux package) to modify the
> ISO to be able to be booted on a USB key. Would we be able to still get that
> functionality without isohybrid from the syslinux package?
Yes. The GRUB2 MBR code will get the equivalent
s=1 seek=446 count=1
>
> Dominik 'Rathann' Mierzejewski wrote:
> > No, it doesn't. Still getting "Operation System not found".
>
> A new firmware riddle.
>
> Does it boot with ubuntu-21.10-desktop-amd64.iso ?
> (That's supposed to be pure G
On 4/13/22 19:52, Brian C. Lane wrote:
> A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
>
> Here is a lorax PR switching to grub2 for BIOS and changing the layout
> of the iso as described in his post:
Hey Brian, thanks for sharing. Is this an effort to drop
https://postimg.cc/bD87J8tF
Tested on old Dell r720 with bios boot.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/p
https://postimg.cc/bD87J8tF
Booted on the old Dell r710 via classic bios.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/
ISO we know that the
problem can be avoided. The riddle is to find out what does the trick.
Building something nearer to the old ISO layout:
new_iso=test_mjgappended.iso
# Extract the EFI partition
dd if=boot-grub2-f36.iso bs=512 skip=1313268 count=20288 of=test_efi.img
# Extract the MBR
ootable may be added to the grub-mkrescue
> > > arguments. If we indeed face this bug, then a grub-mrescue ISO with EFI
> > > equipment should not boot on the affected machine, unless this extra
> > > option was given at production time.
> >
> > I'll try
r booting of the
stick on the affected BIOS machine until the dummy partition was recreated.
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308
especially
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/comments/60
)
> I'll try the grub2-mkrescue ISO next.
Once made with and once w
grub-mrescue ISO with EFI
> > equipment should not boot on the affected machine, unless this extra
> > option was given at production time.
>
> I'll try the grub2-mkrescue ISO next.
And indeed, it doesn't boot. Same "Operation System not found" message.
Regards,
option --mbr-force-bootable may be added to the grub-mkrescue
> arguments. If we indeed face this bug, then a grub-mrescue ISO with EFI
> equipment should not boot on the affected machine, unless this extra
> option was given at production time.
I'll try the grub2-mkrescue ISO next.
Re
On Monday, 18 April 2022 at 19:00, Brian C. Lane wrote:
> On Sun, Apr 17, 2022 at 03:12:59PM +0200, Dominik 'Rathann' Mierzejewski
> wrote:
> > I've tested your ISO with:
> >
> > - Dell XPS 15 L502X 8GB RAM (BIOS only) CD-R physical media
> >
> > Booted and started the installer reasonably fast
On Monday, 18 April 2022 at 04:41, John Reiser wrote:
> > - Dell XPS 15 L502X 8GB RAM (BIOS only) CD-R physical media
>
> It would be very nice to run /sbin/dmidecode, which is on the .iso,
> and report the "BIOS Information" section, such as:
Here's mine:
Handle 0x, DMI type 0, 24 bytes
BIO
On 4/15/22 5:06 PM, Thomas Schmitt wrote:
Hi,
Initial test with a CD-R and an HP Compaq 8510w are mixed.
It boots to GRUB, but it spins a long time blinking the HDD light displaying
nothing but "Welcome to GRUB". It eventually spits out "failure reading
sector 0x4f838 from 'hd31'."
'hd31' loo
tection against trouble.
>
>
> An alternative to --mbr-force-bootable could be to offer a 16-byte file
> for download together with the instructions to patch it into a pure and
> specs conformant ISO with GPT. Of course, only if a 10 year old laptop
> refuses to recognize the orig
0, 0 }
Assumed the file is named "dummy_mbr_part2.img" the patch instruction
would be
dd if=dummy_mbr_part2.img of=boot-grub2-f36.iso \
conv=notrunc bs=1 seek=462 count=16
-
Ubuntu is testing this for you
On Sun, Apr 17, 2022 at 03:12:59PM +0200, Dominik 'Rathann' Mierzejewski wrote:
> I've tested your ISO with:
>
> - Dell XPS 15 L502X 8GB RAM (BIOS only) CD-R physical media
>
> Booted and started the installer reasonably fast
>
> - same machine USB media (written to whole device using dd)
>
> B
On Mon, Apr 18, 2022 at 5:17 AM Thomas Schmitt wrote:
>
> Hi,
>
> Dominik 'Rathann' Mierzejewski wrote:
> > > > Dell XPS 15 L502X 8GB RAM (BIOS only)
>
> BIOS-only on a laptop might mean the firmware quirk which demands
> to see the "boot/active" flag at some MBR partition table slot.
>
> See a th
It would be very nice to run /sbin/dmidecode, which is on the .iso,
and report the "BIOS Information" section, such as:
Is the attached any use?
In the attachment I see these interesting lines (snipped):
=
SMBIOS 3.0.0 present.
BIOS Information
Vendor: American Megatrends Inc.
People,
On 2022-04-18 12:41, John Reiser wrote:
- Dell XPS 15 L502X 8GB RAM (BIOS only) CD-R physical media
It would be very nice to run /sbin/dmidecode, which is on the .iso,
and report the "BIOS Information" section, such as:
Is the attached any use?
Phil.
=
# dmidecode 3.3
Getti
Hi,
Dominik 'Rathann' Mierzejewski wrote:
> > > Dell XPS 15 L502X 8GB RAM (BIOS only)
BIOS-only on a laptop might mean the firmware quirk which demands
to see the "boot/active" flag at some MBR partition table slot.
See a thread of grub-bug (and later grub-devel) from 2015/16
https://marc.info
ism was somewhat premature.)
>
> I wonder from where this message comes. Was it really "Operation system"
> and not "Operating system" ?
Yes, that's the exact message. It might be coming from BIOS.
> In the cleartext strings of boot-grub2-f36.iso i find no
"Operation system"
and not "Operating system" ?
In the cleartext strings of boot-grub2-f36.iso i find no matches for
the two word string. Searching "peration" yields mostly lines with the
word "Microsoft" which i assume stem from the EFI secure boot equipment.
Searchi
- Dell XPS 15 L502X 8GB RAM (BIOS only) CD-R physical media
It would be very nice to run /sbin/dmidecode, which is on the .iso,
and report the "BIOS Information" section, such as:
=
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.5 present.
70 structures occupying 2511 bytes.
Table
Hello, Brian.
On Thursday, 14 April 2022 at 01:52, Brian C. Lane wrote:
> A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
>
> Here is a lorax PR switching to grub2 for BIOS and changing the layout
> of the iso as described in his post:
>
> https://github.co
7;hd31' looks strange for HDD as well as for CD-ROM. Do have that many ?
If it's about the CD drive:
0x4f838 = 325688 would be in 2048-byte-block range of boot-grub2-f36.iso
which has 333555 such blocks. The ISO 9660 filesystem data range ends at
328317. The rest is the appended EFI parti
On 4/13/22 6:52 PM, Brian C. Lane wrote:
A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
Here is a lorax PR switching to grub2 for BIOS and changing the layout
of the iso as described in his post:
https://github.com/weldr/lorax/pull/1226
And a Fedora 36 iso:
https
On Thu, Apr 14, 2022 at 08:59:28PM +0200, Hans de Goede wrote:
> Hi Brian,
>
> On 4/14/22 01:52, Brian C. Lane wrote:
> > A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
> >
> > Here is a lorax PR switching to grub2 for BIOS and changing the layout
https://bcl.fedorapeople.org/boot-grub2-f36.iso
I installed successfully using physical CD-R and physical DVD+R
on American Megatrends Inc version 1613 BIOS of 12/03/2008
running on Intel Core2 Duo (E8400, 3GHz, 8GB). The USB reade
was LG Slim Portable DVD Writer GP50NB40 (August 2014).
The
FWIW I've now added a commit that makes the same changes for
livemedia-creator created isos and tested it with QEMU.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
___
devel mailing list -- devel@lists.fedoraproject.org
To u
Hi Brian,
On 4/14/22 01:52, Brian C. Lane wrote:
> A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
>
> Here is a lorax PR switching to grub2 for BIOS and changing the layout
> of the iso as described in his post:
>
> https://github.com/weldr/lorax/pull/1226
On Wed, Apr 13, 2022 at 7:52 PM Brian C. Lane wrote:
>
> A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
>
> Here is a lorax PR switching to grub2 for BIOS and changing the layout
> of the iso as described in his post:
>
> https://github.com/weldr/lora
A huge thanks to Thomas Schmitt for posting xorrisofs arguments :)
Here is a lorax PR switching to grub2 for BIOS and changing the layout
of the iso as described in his post:
https://github.com/weldr/lorax/pull/1226
And a Fedora 36 iso:
https://bcl.fedorapeople.org/boot-grub2-f36.iso
I&#x
Heads up for anyone using Rawhide with Secure Boot enabled: *do not*
update to grub2 version 2.0.6-27! Due to a chain of unfortunate events,
it is in today's Rawhide compose, but is not signed with the official
Fedora SB keys and will not be trusted. If you update to it, your
system will not
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DKINRYGSNDNRSOY7KYLMJJXDGS4X45TU/
I understand that systemd.Boot is a great achievement and improvement.
But GRUB was great too! And we just cannot throw 70% of GRUB users under the
Fedora bus!
__
On Thu, May 27, 2021 at 02:05:08PM -0600, Chris Murphy wrote:
> This sort of analogy is not helpful at all. That's not what I'm doing.
> I'm just giving advice based on my own experience writing books and
> articles on super complicated material, and having a fairly good grasp
> of GRUB behavior in
it has
> > > to be maintained or it
> > > goes stale again. So when in doubt, just say no and don't document it"
> > >
> > > Then goes on to make a strong argument!
> > >
> > If you do not like it, don't use it. Campaign your rep
ocument it"
> >
> > Then goes on to make a strong argument!
> >
> If you do not like it, don't use it. Campaign your replacement
> of choice and see if you can make it get adopted and grub2 retired.
> Campaigning against it being documented is pushin
On Thu, May 27, 2021 at 7:02 AM e wrote:
>
> On Thu, 27 May 2021 12:54:31 +0200 astoundingly, Vitaly Zaitsev via devel
> wrote:
>
> > On 27.05.2021 12:30, Mauricio Tavares wrote:
> > > Support for other OS for those who like/need to dualboot?
> >
> > Yes. For example you can press "W" to start
On Thu, 27 May 2021 12:54:31 +0200 astoundingly, Vitaly Zaitsev via devel
wrote:
> On 27.05.2021 12:30, Mauricio Tavares wrote:
> > Support for other OS for those who like/need to dualboot?
>
> Yes. For example you can press "W" to start Windows directly.
>
> Also native UEFI Boot allows mul
On 27.05.2021 12:30, Mauricio Tavares wrote:
Support for other OS for those who like/need to dualboot?
Yes. For example you can press "W" to start Windows directly.
Also native UEFI Boot allows multiple bootloaders.
Cutting date for hardware that supports it?
All hardware with UEFI support
On Thu, May 27, 2021 at 6:27 AM Vitaly Zaitsev via devel
wrote:
>
> On 27.05.2021 12:13, Sérgio Basto wrote:
> > why systemd-boot is better ?
>
> 1. Not a bootloader.
> 2. Very simple and clean.
> 3. Starts Linux kernel directly with EFIStub without any bootloaders.
> 4. Can be used with XBOOTLDR[
On 27.05.2021 12:13, Sérgio Basto wrote:
why systemd-boot is better ?
1. Not a bootloader.
2. Very simple and clean.
3. Starts Linux kernel directly with EFIStub without any bootloaders.
4. Can be used with XBOOTLDR[1] on any FS, supported by your hardware[2].
5. Has full BLS support.
Links:
[
On Thu, 2021-05-27 at 11:49 +0200, e wrote:
> sounds unintuitive, but he just speaks truth to power:
>
> https://pagure.io/fedora-docs/quick-docs/issue/352#comment-734630
>
> "I think the GRUB stuff is so esoteric, so conditional and overly
> complicated, that we shouldn't
> explain it. Explainin
it. Campaign your replacement
of choice and see if you can make it get adopted and grub2 retired.
Campaigning against it being documented is pushing to have it cancel
cultured. There is nobody putting a gun on the head of those
documenting it; it is open source maintained by volunteers.
___
On 27.05.2021 11:49, e wrote:
"I think the GRUB stuff is so esoteric, so conditional and overly complicated,
that we shouldn't
explain it. Explaining it will take a lot of resources, and then it has to be
maintained or it
goes stale again. So when in doubt, just say no and don't document it"
sounds unintuitive, but he just speaks truth to power:
https://pagure.io/fedora-docs/quick-docs/issue/352#comment-734630
"I think the GRUB stuff is so esoteric, so conditional and overly complicated,
that we shouldn't
explain it. Explaining it will take a lot of resources, and then it has to be
Am 05.02.21 um 15:03 schrieb Marek Marczykowski-Górecki:
I know it's problematic when you run Fedora VM on non-fedora Xen host if you
use
pvgrub/pygrub - in that case it uses host's grub to parse guest grub.cfg
and load the actual kernel. But I'm pretty sure there are other
problematic cases t
> What is the vision for grub2 package in Fedora versus upstream grub? The
> huge amount of patches in Fedora's grub (279 at this time) makes it
> basically a fork. And indeed many parts are incompatible with upstream
> grub, like "increment" module, or BLS, just
Hi,
What is the vision for grub2 package in Fedora versus upstream grub? The
huge amount of patches in Fedora's grub (279 at this time) makes it
basically a fork. And indeed many parts are incompatible with upstream
grub, like "increment" module, or BLS, just to name a f
Hi,
as there is a small problem with pinephones and grub2-efi, heres how to
fix it:
https://bugzilla.redhat.com/show_bug.cgi?id=1919907
Problem:
[root@fedorapine boot]# rpm -U
/var/cache/dnf/rawhide-135a69fc59e3201d/packages/grub2-efi-aa64-2.04-34.fc34.aarch64.rpm
Fehler: Entpacken des
c32.x86_64
xen-libs-4.13.1-4.fc32.x86_64
xen-licenses-4.13.1-4.fc32.x86_64
xen-runtime-4.13.1-4.fc32.x86_64
rpm -qa | grep grub
grub2-common-2.04-21.fc32.noarch
grub2-efi-x64-2.04-21.fc32.x86_64
grub2-efi-x
1 - 100 of 449 matches
Mail list logo
