Have a project that I've maintained since 2004. Have a simple process to add it to the regular grub boot list using the 40_custom with the following lines.
menuentry G4L { linux /bz5x13.14 root=/dev/ram0 initrd /ramdisk.lzma }
Just copy the kernel and ramdisk.lzma to /boot and it becomes an option in the grub menu.
Just had a use that got 140 new Dell machines, and they seem to no longer support any bios boot?? So, EFI is the only option.
Have the EFI kernel options set, but haven't found info on how to make an efi boot. I've looked, but I've not seen anything. Did find one page that talks about just copying kernel files to the efi direct with a minor rename and including System.map file, but doesn't say anything about the filesystem?
Anyone know of a web page. Currently, the user is pulling drive out, and connecting it to an older machine to make images.
Thanks.
On 9/3/21 10:37 PM, Michael D. Setzer II via users wrote:
Have a project that I've maintained since 2004. Have a simple process to add it to the regular grub boot list using the 40_custom with the following lines.
menuentry G4L { linux /bz5x13.14 root=/dev/ram0 initrd /ramdisk.lzma }
Just copy the kernel and ramdisk.lzma to /boot and it becomes an option in the grub menu.
Just had a use that got 140 new Dell machines, and they seem to no longer support any bios boot?? So, EFI is the only option.
Have the EFI kernel options set, but haven't found info on how to make an efi boot. I've looked, but I've not seen anything. Did find one page that talks about just copying kernel files to the efi direct with a minor rename and including System.map file, but doesn't say anything about the filesystem?
Anyone know of a web page. Currently, the user is pulling drive out, and connecting it to an older machine to make images.
I'm going to assume that you're saying you work on Ghost for Linux which can BIOS boot and you want to have it work with EFI, but don't know how to set it up.
What do you mean that you have "the EFI kernel options set"? Are you referring to the kernel compile options? If you have that, then it should be ready. You don't need any specific filename and I don't think you need the System.map file. If you are booting in EFI mode, grub will automatically do an efi boot of the kernel. However, unless you're signing the kernel and have added the keys, you will need to disable secure boot.
Do an EFI install of Fedora to see how it's all laid out.
On 3 Sep 2021 at 22:51, Samuel Sieb wrote:
Subject: Re: OT: How to load kernels in EFI setup. To: users@lists.fedoraproject.org From: Samuel Sieb samuel@sieb.net Date sent: Fri, 3 Sep 2021 22:51:57 -0700 Send reply to: Community support for Fedora users users@lists.fedoraproject.org
On 9/3/21 10:37 PM, Michael D. Setzer II via users wrote:
Have a project that I've maintained since 2004. Have a simple process to add it to the regular grub boot list using the 40_custom with the following lines.
menuentry G4L { linux /bz5x13.14 root=/dev/ram0 initrd /ramdisk.lzma }
Just copy the kernel and ramdisk.lzma to /boot and it becomes an option in the grub menu.
Just had a use that got 140 new Dell machines, and they seem to no longer support any bios boot?? So, EFI is the only option.
Have the EFI kernel options set, but haven't found info on how to make an efi boot. I've looked, but I've not seen anything. Did find one page that talks about just copying kernel files to the efi direct with a minor rename and including System.map file, but doesn't say anything about the filesystem?
Anyone know of a web page. Currently, the user is pulling drive out, and connecting it to an older machine to make images.
I'm going to assume that you're saying you work on Ghost for Linux which can BIOS boot and you want to have it work with EFI, but don't know how to set it up.
What do you mean that you have "the EFI kernel options set"? Are you referring to the kernel compile options? If you have that, then it should be ready. You don't need any specific filename and I don't think you need the System.map file. If you are booting in EFI mode, grub will automatically do an efi boot of the kernel. However, unless you're signing the kernel and have added the keys, you will need to disable secure boot.
Do an EFI install of Fedora to see how it's all laid out.
Thanks for the quick response. Yes, the kernel EFI options are built into the kernels build from the kernel.org source code, but don't have signatures, since that seems to be a very expensive and long process, as I've seen on the memtest page about there looking into it.
I've currently got 5 running machines at home, all with Fedora 33, but none are setup with EFI boot. All where setup before, and have just had Fedora updated to next versions as releases came out, so setup wasn't changed. There is the efi directories, but they don't seem to have any kernel files installed.
I'm not even clear what OS the user has on machines. Many use the G4L to make images of windows machines. If I was still teaching, would have access to machines to test with, but retired, so just have my working machines.
Process was so easy with the 40_custom setup, or booting to CD or USB, but now with systems not offering legacy options seems to be a major issue.
Thanks again.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 9/4/21 4:21 AM, Michael D. Setzer II wrote:
Thanks for the quick response. Yes, the kernel EFI options are built into the kernels build from the kernel.org source code, but don't have signatures, since that seems to be a very expensive and long process, as I've seen on the memtest page about there looking into it.
As an individual, you aren't going to go through the official process. If it's your own machine, you can create your own key and register it with the BIOS. But that doesn't scale for many users.
The alternative is to disable secure boot which is supposed to be possible.
I've currently got 5 running machines at home, all with Fedora 33, but none are setup with EFI boot. All where setup before, and have just had Fedora updated to next versions as releases came out, so setup wasn't changed. There is the efi directories, but they don't seem to have any kernel files installed.
I don't know what efi directories you are referring to, but if it's not an EFI boot, then they won't be used.
I'm not even clear what OS the user has on machines. Many use the G4L to make images of windows machines. If I was still teaching, would have access to machines to test with, but retired, so just have my working machines.
You can use virt-manager to create VMs using UEFI if you want to test things.
Process was so easy with the 40_custom setup, or booting to CD or USB, but now with systems not offering legacy options seems to be a major issue.
It's probably just as easy with EFI, but I'm still not clear on what exactly you're asking.
On 6 Sep 2021 at 1:02, Samuel Sieb wrote:
Subject: Re: OT: How to load kernels in EFI setup. To: Community support for Fedora users users@lists.fedoraproject.org From: Samuel Sieb samuel@sieb.net Date sent: Mon, 6 Sep 2021 01:02:18 -0700 Send reply to: Community support for Fedora users users@lists.fedoraproject.org
On 9/4/21 4:21 AM, Michael D. Setzer II wrote:
Thanks for the quick response. Yes, the kernel EFI options are built into the kernels build from the kernel.org source code, but don't have signatures, since that seems to be a very expensive and long process, as I've seen on the memtest page about there looking into it.
As an individual, you aren't going to go through the official process. If it's your own machine, you can create your own key and register it with the BIOS. But that doesn't scale for many users.
Basically, I want to be able to let people run the g4l program with as little extra work as possible. Originally, it was run only from a bootable regular CD with the syslinux boot process. Have been watching there pages, but it still seems the EFI boot is a working issue. Has been fixed at 6.03 for a long long time. Then added the ability of booting from a Flash by either using they syslinux hybrid option on the iso, and then just copying it to a flash. A second option was to use grub4dos to make a bootable flash as well. Then adding it directly to the grub menu using the 40_custom, and just putting the kernel and ramdisk file in /boot.
Did use isomaster to look at the Fedora 34 iso image, and see that it does have a similar grub.cfg file under the efi directory, on my machines, they have the efi directory under boot, but guess it is just support files with no grub.cfg listed. So, might be the 40_custom option would work with the files in /image?
For most users, it has been an option to just enable the legacy boot for running the g4l, and then turning it back off if necessary, but now seems some machines no longer have legacy at all, or it might be a multi-step process they haven't discovered to enable it?
In past, it was something as easy as putting in a flash, and using F12 (or other key) to boot from it.
Perhaps I'll have to setup a machine with EFI to do some more testing.. Thanks again for all your replies and time.
Use to have an option on my grub menu in classrooms that would restore the windows 10 partition in about 10 minues from an image on an extra partition, so that any one could reset image to know set. Worked great, and used the udpcast option to image 19 other machines in about 45 minutes after creating a new multi-boot setup.
The alternative is to disable secure boot which is supposed to be possible.
I've currently got 5 running machines at home, all with Fedora 33, but none are setup with EFI boot. All where setup before, and have just had Fedora updated to next versions as releases came out, so setup wasn't changed. There is the efi directories, but they don't seem to have any kernel files installed.
I don't know what efi directories you are referring to, but if it's not an EFI boot, then they won't be used.
I'm not even clear what OS the user has on machines. Many use the G4L to make images of windows machines. If I was still teaching, would have access to machines to test with, but retired, so just have my working machines.
You can use virt-manager to create VMs using UEFI if you want to test things.
Process was so easy with the 40_custom setup, or booting to CD or USB, but now with systems not offering legacy options seems to be a major issue.
It's probably just as easy with EFI, but I'm still not clear on what exactly you're asking. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-
Michael D. Setzer II -
Samuel Sieb