On 9 Sep 2021 at 22:51, Samuel Sieb wrote:
Subject: Re: Failure in gsetting up a UEFI USB
Flash with Fedora 33??
To: Community support for Fedora users
<users@xxxxxxxxxxxxxxxxxxxxxxx>
From: Samuel Sieb <samuel@xxxxxxxx>
Date sent: Thu, 9 Sep 2021 22:51:43 -0700
Send reply to: Community support for Fedora
users <users@xxxxxxxxxxxxxxxxxxxxxxx>
> On 9/9/21 10:21 PM, Michael D. Setzer II wrote:
> > On 9 Sep 2021 at 19:16, Samuel Sieb wrote:
> >> Is there a reason you can't use the Fedora kernel? That would give you
> >> full secure boot support. What different options are you using for your
> >> kernel?
> > I have done a test.
> > I can boot from the Fedora 34 live cd I have setup in
> > Virtual box. 2G boot file.
> > I've found that there are 23 packages that are not
> > included in the live cd setup, so have to install them.
>
> [snip]
>
> > So, going from a simple boot with a 10M kernel and 30M
> > filesystem running in ram versus booting to a 2G
> > filesystem and having to add stuff requiring the internet.
>
> I don't think you're getting my point and aren't actually answering my
> questions.
>
> What is special about the kernel you're compiling that the Fedora kernel
> won't work? Don't say anything about EFI.
Not sure? The Fedora Kernels are built to use Systemd
and Selinux, so not sure how they would interact with the
g4l's ramdisk.lzma file. With the G4L kernel, it includes
almost all available disk and nic devices the kernel offers
since it is meant to boot and support whatever the
hardware has, and haven't had issues from users about
not supporting things very often, and have resolved the
few issues. The g4l ramdisk.lzma has no gnome or other
desktop environment. Is just a text based system using
dialog interface..
Guess I could setup a option in 40_custom, that used the
rescue kernel, since it would be the only one that would
come close to supporting more hardware. Once change a
machine from an old IDE hard disk to a new SATA hard
disk. Imaged the IDE to the SATA and everything was
identical, but it would not boot from the SATA drive..
Turned out the default kernel didn't include the SATA
support, since the machine didn't have an SATA drive at
the time. Don't know if there was a resue kernel on disk
at time, but ended up booting back from the old IDE
drive, and went thru a complex process to build a new
initrd that include the SATA controller. Was then able to
copy it to the SATA disk, and it booted just fine. I could
boot from the Fedora CD, and could see the SATA drive,
since it had all the different hard disk support, but the
current one did not.
As an example this notebooks current rescue initramfs is
over twice the since the current booting initramfs.
106180650 May 7 23:45
initramfs-0-rescue-189711f94e78436d9618b891a8fce70e
.img
48724393 Sep 9 17:42
initramfs-5.13.14-100.fc33.x86_64.img
The g4l current ramdisk.lzma
28244926 Sep 9 17:35 ramdisk.lzma
Comparing kernel files.
10596624 May 7 23:44
vmlinuz-0-rescue-189711f94e78436d9618b891a8fce70e
10865648 Aug 13 07:42 vmlinuz-5.13.10-100.fc33.x86_64
G4l kernel file
9818816 Sep 9 17:35 bz5x13.15
>
> You have an initramfs already. Why can't you keep that, but replace the
> kernel modules with the ones from Fedora?
The G4L has all the modules built into the kernel, versus
have them as loadable one. The CD version has multiple
kernels include in case default one doesn't work with
hardware, hopefully one of the others will. Since the
kernels contain all the modules built in, doesn't require
created different directories for each kernel.
Current CD version has the following kernel options.
LABEL bz5x4.144
MENU LABEL ^A: bz5x4.144 x86 09-03-2021
TEXT HELP
Kernel 5x4.144 from Kernel.org
ENDTEXT
LINUX bz5x4.144
APPEND initrd=ramdisk.lzma root=/dev/ram0
LABEL bz5x10.63
MENU LABEL ^B: bz5x10.63 x86 09-08-2021
TEXT HELP
Kernel 5x10.63 from Kernel.org
ENDTEXT
LINUX bz5x10.63
APPEND initrd=ramdisk.lzma root=/dev/ram0
LABEL bz5x12.19
MENU LABEL ^C: bz5x12.19 x86 07-20-2021
TEXT HELP
Kernel 5x12.19 from Kernel.org
ENDTEXT
LINUX bz5x12.19
APPEND initrd=ramdisk.lzma root=/dev/ram0
LABEL bz5x13.15
MENU LABEL ^D: bz5x13.15 x86 09-08-2021
MENU DEFAULT
TEXT HELP
Kernel 5x13.15 from Kernel.org
ENDTEXT
LINUX bz5x13.15
APPEND initrd=ramdisk.lzma root=/dev/ram0
LABEL Failsafe
MENU LABEL ^J: Failsafe Menu
TEXT HELP
Switch between menu with/without failsafe options
ENDTEXT
CONFIG failsafe.cfg
APPEND initrd=ramdisk.lzma root=/dev/ram0
LABEL bz5x14.1
MENU LABEL ^K: bz5x14.1 x86 09-08-2021
TEXT HELP
Kernel 5x14.1 from Kernel.org
ENDTEXT
LINUX bz5x14.1
APPEND initrd=ramdisk.lzma root=/dev/ram0
The flash if created by copying the iso to flash would have
all these kernels.
If the g4l-lite file is used to create a flash using grub4dos
it only has the default kernel as an option, and is thus
much smaller.
Adding it directly as a boot option on the regular grub2
just requires putting the bzxxx kernel file and the
ramdisk.lzma file in the boot directory.
Then have the following lines in 40_custom
menuentry G4L {
linux /bz5x13.15 root=/dev/ram0 telnetd=yes
initrd /ramdisk.lzma
}
and using grub2-mkconfig command.
>
> This would get you a fully functional EFI boot that would even work with
> secure boot enabled.
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
