And you've ensured that UEFI has been turned off in the BIOS?...what about switching from Compatibility to "ACHI"?....I've noticed that sometimes? that simple switch can work wonders....just a suggestion. Cheers EGO II On 9/9/21 8:04 AM, Michael D. Setzer II via users wrote:

I couldn't remember which key it was...so I found this...maybe one of these might help?... https://www.4winkey.com/windows-tips/how-to-access-enter-bios-on-dell.html EGO II On 9/9/21 8:35 AM, Michael D. Setzer II wrote: > On 9 Sep 2021 at 8:21, Eddie G. O'Connor Jr. wrote: > > From: "Eddie G. O'Connor Jr." <eoconnor25(a)gmail.com&gt; > Subject: Re: Failure in gsetting up a UEFI USB Flash with Fedora 33?? > To: "Michael D. Setzer II via users" <users(a)lists.fedoraproject.org&gt; > Date sent: Thu, 9 Sep 2021 08:21:23 -0400 > Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; > >> And you've ensured that UEFI has been turned off in the BIOS?...what about >> switching from Compatibility to "ACHI"?....I've noticed that sometimes? that simple >> switch can work wonders....just a suggestion. > From my understanding from one of the Users. They just > got 140 of these new Dell 3080 machines, and they have > no options for other than UEFI boot. The 3070 versions of > the machines had the option to do regular boots. Could be > a more complex process to enable it, but I'm sure he tried > lots of things. Got a message about Lenova doing the > same, but no specifics from that user. Went to Dell site, > but there site seems to have no options unless you > provide a code number from an actual machine?? > Right now, the user is having to physically remove drives > from 3080 machine, and connect them to a 3070 machine > to do image, and then can put the drive back?? > > >> >> >> Cheers >> >> >> EGO II >> On 9/9/21 8:04 AM, Michael D. Setzer II via users wrote: >> I've found 6 web sites so far that had instructions on >> setting up a UEFI USB flash to boot, but all have failed. >> Some actually create a UEFI Flash that my test usb is >> seen as being a UEFI flash, but the boot fails? >> >> The last one I fully documented the steps from page, but >> the resulting flash doesn't even show up as an UEFI >> Flash. Probable due to the failure of the grub2-install >> option?? >> grub2-install: error: this utility cannot be used for EFI >> platforms because it does not support UEFI Secure Boot. >> >> So, it seems it worked on some system before, but fails >> with Fedora 33 at least?? Don't want to create a UEFI >> Secure Boot, but just a UEFI Boot?? >> >> >> #https://linuxconfig.org/how-to-create-multiboot-usb-with-linux >> parted -s /dev/sdb mklabel msdos >> parted -s /dev/sdb mkpart primary 1MiB 551Mib >> parted -s /dev/sdb set 1 esp on >> parted -s /dev/sdb set 1 boot on >> mkfs.fat -F32 /dev/sdb1 >> parted -s /dev/sdb mkpart primary 551Mib 100% >> mkfs.ext4 /dev/sdb2 >> mkdir /media/{efi,data} >> mount /dev/sdb1 /media/efi >> mount /dev/sdb2 /media/data >> # Installing legacy grub2 >> grub2-install \ >> --target=i386-pc \ >> --recheck \ >> --boot-directory="/media/data/boot" /dev/sdb >> >> # Installing grub for efi >> grub2-install \ >> --target=x86_64-efi \ >> --recheck \ >> --force \ >> --removable \ >> --efi-directory="/media/efi" \ >> --boot-directory="/media/data/boot" >> ## grub2-install: error: this utility cannot be used for EFI >> platforms because it does not support UEFI Secure Boot. >> mkdir /media/data/boot/iso >> chown 1000:1000 /media/data/boot/iso >> cd /media/data/boot/iso/ >> cp /home/msetzerii/g4l0.60alpha/g4l-v0.60.iso . >> cd /media/data/boot/grub2 >> #create grub.cfg with these lines. >> #menuentry "G4L" { >> # isofile="/boot/iso/g4l-v0.60.iso" >> # loopback loop "${isofile}" >> # linux (loop)/isolinux/bz5x13.14 iso-scan/filename="${isofile}" >> root=/dev/ram0 >> # initrd (loop)/isolinux/ramdisk.lzma >> #} >> >> Have just got had email chat with Clonezilla developer to see >> what they have done. Seems they gave up on trying to make a >> UEFI boot, and have created a live-cd boot of a distro to get >> around issue. >> >> Seems going from boot loaders link syslinux, grub4dos, and >> regular grub2 with a 10M kernel and 30M ramdisk. >> With Fedora, it would require the 2G live CD image, and then the >> downloading of a number of packages that are not included on >> the live-cd. So, 40M to 2000+M and a bunch of steps. >> >> Does anyone know of a process to make a UEFI USB Boot that >> actual works using Fedora?? >> >> Very Frustrated... >> >> >> >> _______________________________________________ >> users mailing list -- users(a)lists.fedoraproject.org >> To unsubscribe send an email to users-leave(a)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 Thu, 9 Sept 2021 at 09:35, Michael D. Setzer II via users < users(a)lists.fedoraproject.org&gt; wrote: [...] It is not surprising that legacy boot is going away -- vendors want to minimize support issues and removing "features" that few customers use gives users one less way to break systems and allows them to simplify the BIOS code. You might look at Knoppix UEFI support < https://www.knopper.net/knoppix/knoppix-uefi-en.html> It looks like they have automated the process of creating a "machine owner key" (MOK) when booting. -- George N. White III

On Thu, 09 Sep 2021 22:04:04 +1000 Michael D. Setzer II via users wrote: I've always used: https://wiki.archlinux.org/index.php/Multiboot_USB_drive I created a big utility USB stick with it than can boot the giant collection of ISO images I put on the stick. It can boot either "normal" MSDOS or UEFI, but I've found a lot of computers that don't like one or the other for some reason. I just boot whichever version I can get to work. Here's my notes for setting up the initial stick: If starting from scratch, use gparted to erase all partitions from the usb stick. Create a 4 GB fat32 partition labeled BOOTUSB Create an ext4 partition labeled DATAUSB in remainder of space. Using /dev/sdc as the example name of the usb stick device, run these commands to install grub on the BOOTUSB partition (taken from the web page at https://wiki.archlinux.org/index.php/Multiboot_USB_drive). mount /dev/sdc1 /mnt mkdir /mnt/boot grub2-install --target=i386-pc --recheck --boot-directory=/mnt/boot /dev/sdc grub2-install --target x86_64-efi --removable --boot-directory=/mnt/boot --efi-directory=/mnt Now copy in the grub.cfg file (gets very specific to my case after this).

On 9/9/21 6:27 AM, Eddie G. O'Connor Jr. wrote: I think you're misunderstanding the goal here. He's trying to create a UEFI bootable flash drive, not boot off the hard drive. Wiping the hard drive would be the complete opposite of the objective which is make a drive image of the existing hard drive by booting from a flash drive.

On Fri, 10 Sep 2021 00:39:27 +1000 Michael D. Setzer II via users wrote: I've never gotten that error. Are use sure it is an error rather than just an information message that the efi boot won't work on a secure boot system? Grub barely make any distinction between errors and simple messages. There is also a --force option for grub2-install which might make it go ahead and do the install anyway if it really was an error.

On Sep 9, 2021, at 10:40, Michael D. Setzer II via users <users(a)lists.fedoraproject.org&gt; wrote: The basic answer is: Don’t use grub2-install on Fedora UEFI systems. https://bugzilla.redhat.com/show_bug.cgi?id=1917213 You will have to boot into another OS to create a UEFI boot using grub-install. However, you can use the files from the Fedora grub2-efi-x64 and shim-x64 packages, and just copy them into the /EFI/BOOT directory of the fat32 partition, which should work for the Secure Boot systems, although the expect to find grub2 EFI executables in /EFI/fedora. If you can’t disable Secure Boot, that’s what I suggest. — Jonathan Billings

On Fri, Sep 10, 2021 at 03:21:48PM +1000, Michael D. Setzer II via users wrote: I build and boot upstream kernels quite often, and I do this on Fedora systems with UEFI and Secure Boot turned off. But I typically am just rebuilding the rawhide kernel and adding my patches to the patch list in the spec, building the kernel and installing the package (if it succeeds to build). It's so much easier to just add kernels to a working UEFI build than try to generate a base UEFI boot structure from scratch -- and anyway, what's the point of having a booting kernel without a known good base OS to run under it? -- Jonathan Billings <billings(a)negate.org&gt;

On Fri, Sep 10, 2021 at 11:49:38PM +1000, Michael D. Setzer II via users wrote: I used Ghost4Linux before, although it was years ago before I ever touched a UEFI system. I think that if you are required to run some kernel provided by a project, then they need to provide a kernel that works with the initial ramdisk, and that includes kernel modules needed to load network devices and storage systems. If the Ghost4Linux project doesn't have a UEFI-capable boot image, then building some random kernel isn't going to help you. You need the kernel that is the exact same version as the kmods in the initrd that loads g4l. You could probably just any UEFI-capable boot image and just move the kernel and initrd into there, but it still won't be able to be used on a Secure Boot system because the kernel isn't signed. -- Jonathan Billings <billings(a)negate.org&gt;

On Sat, Sep 11, 2021 at 01:11:38AM +1000, Michael D. Setzer II via users wrote: So, that makes sense, and if this is a heavily customized, boot-from-ram system, then it would work fine with all the drivers compiled into the kernel and not as modules, although it would make the kernel rather large. Wait, I'm confused, now you are talking about dnf, I thought this was an all-in-one initrd system, what is using dnf? Where are you putting these kernels on the EFI volume? For example, if you have the msdos-formatted volume mounted as /boot/efi, the EFI firmware looks for this: /boot/efi/EFI/BOOT/BOOTX64.EFI ... by default. You can make that be your kernel, a GRUB2 EFI executable or the shimx64.efi, which is what Fedora systems uses. The shimx64.efi executable is a signed UEFI executable that launches GRUB2. But if you want to disable Secure Boot, you could just put it in EFI/BOOT/BOOTX64.EFI and it should detect it by default. The UEFI spec says that on x86_64 systems you should be able to disable secure boot. Dell most likely has that option, because they have a lot of customers who need it. (for example, if you use nvidia and CUDA, you'll need to disable secure boot or manually install your own signing keys) libvirtd lets you set up UEFI VMs, even on systems that don't have UEFI boot, which is something I have. In virt-manager, just click to configure the VM before starting the install, and go over into Overview, you can change the Firmware from BIOS to UEFI. I believe there's a secboot firmware option, even, although I've not tested it. Then you can test to your heart's content. -- Jonathan Billings <billings(a)negate.org&gt;

On Sep 10, 2021, at 17:32, Michael D. Setzer II <mikes(a)guam.net&gt; wrote: Give up trying to use grub2-install, it doesn’t do what you need it to do. UEFI boots off EFI executables on a fat32 volume, you don’t need to install special sectors on the beginning of the disk, so you don’t really need to run fancy commands, just ‘cp’. According to the manual: Make sure you have USB boot enabled: https://www.dell.com/support/manuals/en-us/optiplex-3080-desktop/optiplex... Under “USB configuration. Also, according to this: https://www.dell.com/support/manuals/en-us/optiplex-3080-desktop/optiplex... Hitting F12 will list all *valid* boot options. Most likely your boot disk isn’t valid if you have USB boot enabled. — Jonathan Billings

On 9/10/21 10:32 PM, Michael D. Setzer II via users wrote: A lot of the problem is that you are being very unclear about what you're doing and it's very hard to follow. Now what you're saying is that a non-EFI flash drive doesn't boot on an EFI system. Why do you need to point that out? Unless you can enable legacy or CSM mode, it's obviously not going to work. And newer systems don't have that option any more. Also, you apparently ignored the part where he told you that there is no point in trying to use grub-install. It's not useful for EFI. You just need to copy a few files into the right directories.

On Sat, Sep 11, 2021 at 06:51:47PM +1000, Michael D. Setzer II via users wrote: Newer machines == no longer supports legacy boot. Maybe you should look at some of the other suggestions on your project's forums, such as using Refind? It might be easier to create a bootable disk using refind than trying to build your own image? If you are curious, here is the patch Fedora adds: https://src.fedoraproject.org/rpms/grub2/blob/f34/f/0169-grub-install-dis... This is where it's disabled. GRUB2 has the capability, but it is patched to not work because it doesn't make sense for *Fedora*. Intel and motherboard vendors have been saying they're going to drop legacy bootloader support. Honestly, I expected it sooner. It looks like you're seeing some Dells that don't support the legacy bootloader. Since you appear to be one of the people supporting G4L (I found the thread that must be related to this: https://sourceforge.net/p/g4l/discussion/408763/thread/24d7652d5f/?limit=... ) then I am sorry that Fedora isn't useful for creating your project's boot images. But the grub2 package for Fedora is built for booting Fedora, and since it has signed EFI executables that can only be used for booting signed Fedora kernels, that makes sense. If you want to mess around with building your own UEFI capable boot image with your own kernel and initrd, I suggest going to the GRUB2 web site and compiling it. I think part of the confusion here was that many people didn't realize you were basically a proxy for supporting someone else in another forum. -- Jonathan Billings <billings(a)negate.org&gt;

You do not need to do anything fancy at all with a Fedora USB install media.  Fedora comes with both UEFI and legacy boot mechanisms, so it just works on all machines.  Instead, you have a BIOS setting problem, that is preventing you from seeing the USB key.  Fix that, and everything should just work. On 2021-09-09 8:04 a.m., Michael D. Setzer II via users wrote:

On Thu, Sep 09, 2021 at 10:04:04PM +1000, Michael D. Setzer II via users wrote: Any reason why you're using an msdos disk label? I think that most UEFI systems require GPT for booting UEFI-only disks. -- Jonathan Billings <billings(a)negate.org&gt;

On Thu, Sep 09, 2021 at 10:04:04PM +1000, Michael D. Setzer II via users wrote: In the six things, have you tried Fedora Media Writer? This is the official thing we use and test, and it definitely successfully creates UEFI-bootable flash drives. It's not as full-featured as some of the other tools, but it's meant to do that one thing very successfully. -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, 10 Sep 2021 05:22:34 +1000 Michael D. Setzer II via users wrote: Before I figured out how to use grub2-install directly, I would sometimes get grub installed by installing fedora on the disk, then remove all the fedora bits and modify the config to boot what I wanted. Round-a-bout way to do it, but it did work. Never tried that with UEFI though.

On 9 Sep 2021 at 19:16, Samuel Sieb wrote: Subject: Re: Failure in gsetting up a UEFI USB Flash with Fedora 33?? To: users(a)lists.fedoraproject.org From: Samuel Sieb <samuel(a)sieb.net&gt; Date sent: Thu, 9 Sep 2021 19:16:51 -0700 Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; 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. dnf install ncftp nano dialog fsarchiver aespipe bwm-ng dd_rescue ddrescue f3 hexedit iperf fuse-sshfs strace testdisk hdparm dmidecode nvme-cli gpm rpcbind partclone udpcast Then there is the g4l script plus a copy little programs and scripts. Did a comparison of the /bin and /sbin directories to see what wasn't there. Might be some of those packages that are not needed by main script, but the main script is 2460 lines long, so would have to go thru it. Found files from 2006 where I had some systems that wouldn't boot from the G4L kernels, but booted fine with Knoppix live cd. Had created a simpler setup that worked with that. Booting the knoppix, and then just extacting the missing programs. But a lot had been added since 2006. 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. Not clear why the grub2-install fails with the efi message about not supporting secure boot, since I am not looking for efi secure boot?? I've looked at the /boot efi files on the Fedora 34 live CD, but they seem to be locked for the secure boot enabled Fedora kernels, and wouldn't work with my kernels, since they don't have the signature.. Will keep looking, but the answer may be it is beyond my abilities. But guess if memtest can't create a setup for EFI, it can't be easy.

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(a)lists.fedoraproject.org&gt; From: Samuel Sieb <samuel(a)sieb.net&gt; Date sent: Thu, 9 Sep 2021 22:51:43 -0700 Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; 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 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.

Well, tired it and get a kernel panic... Booted a notebook that has fully updated fedora 33, and went to the 3rd kernel on the list and used edit option. Changed the initrd line to use the g4l ramdisk.lzma as the initrd and it comes up with a kernel panic.. Could just be that Fedora kernel doesn't include support for the lzma compression, but the panic message didn't give much detail, and it didn't even go thru a whole screen of line. I went with lzma compression, since it greatly reduces the size of ramdisk, and my kernels have no issues since they have the support built in. Did try using xz compression onces, but kernel got an error with the uncompression, so assumed the kernels xz support didn't include something?? Did note the size difference between the lzma compressed ramdisk and xz compressed was small. So, at least for a simple change of the initrd results in kernel panic. On 10 Sep 2021 at 0:02, Samuel Sieb wrote: Subject: Re: Failure in gsetting up a UEFI USB Flash with Fedora 33?? To: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; From: Samuel Sieb <samuel(a)sieb.net&gt; Date sent: Fri, 10 Sep 2021 00:02:55 -0700 Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt;

This may be a totally useless experience from another Dell computer, but ... I was running an older Fedora on both a non-Dell desktop and a Dell Vostro laptop. I decided to do a fresh reinstall on the laptop. First, used the desktop to create an install flash drive (F34). Forget if I used mediawriter or dd, but should not matter. The flash mounted fine on the desktop. Took it to the laptop, again mounted fine under the old Fedora. Tried to boot from the flash and could not see it at all no matter what bios boot options I tried. Returned to the desktop and there was no problem booting from the flash drive. But no success on the laptop until... I recalled a brief message "Press F12 to ..." So brief I had to <ctrl><alt><del> several times to get the rest that said something like "select boot device". When I next rebooted and pressed F12, it gave a menu that included USB legacy boot, USB secure boot, and my hard drive. Maybe the new Dell bios at your client needs something like that to USB boot. -- Jon H. LaBadie jonfu(a)jgcomp.com

On 2021-09-09 5:04 a.m., Michael D. Setzer II via users wrote: 1. Format your flash drive with a GPT partition table and a FAT32 partition. 2. Extract the tarball at https://bit.ly/3npBP0r into that partition. (Sorry, I can't give the real link or an upstream spam filter will block the email. The file is at filebin.) 3. Boot it. It uses the Fedora kernel and I included the modules. However, because you have no process to load the modules when necessary, networking won't work automatically. You can either try using your static kernel or else include something like udev to automatically load modules as needed. I didn't want to share a file from any personal servers. That link will expire in 6 days. It's very simple though. I just used the F34 installer image and removed almost everything. I kept the EFI directory and added the kernel and repacked the g4l initramfs with the kernel modules added to it.

Good news Bad News.. Download and tested and have a mixed set of results. Yes, your setup does boot you kernel and the g4l.img file. Not sure if your g4l.img file is just an uncompressed version of the ramdisk.lzma. 62469461 Sep 12 16:40 g4l.img 28325385 Sep 11 20:19 ramdisk.lzma If something else, please let me know. As you said, it comes up with no network support, so the problem would be how to get all the ethernet support added, and don't know what all hardware for disk is included. You grub.cfg file had some options the other ones I tried didn't. The did just use linux and initrd without the efi options. I tried some other things, but leads to more questions. Created a menuentry to try loading my kernel file, but still using your g4l.img file. But ended with just getting a blank screen. Just to fun, I added echo lines before and after the commands to see if it was actually doing anything. Results - I got all the echos. Echo before loading /bz5x13.15 Echo before loading /g4l.img and echo done after it?? So, it seems to be loading the kernel and g4l.img, but doesn't display any output. Perhaps the efi puts the video in some mode the standard kernel doesn't support?? Found a page that talked about efi not supporting vga? Tried adding debug option to kernel lines, but neither with your kernel or mine did it produce any additional output?? So, Problem of getting network support for the vmlinuz or getting my kernels to work with the efi video mode?? Thanks again. One step forward, One step back. On 12 Sep 2021 at 0:54, Samuel Sieb wrote: From: Samuel Sieb <samuel(a)sieb.net&gt; Subject: Re: Failure in gsetting up a UEFI USB Flash with Fedora 33?? To: users(a)lists.fedoraproject.org Date sent: Sun, 12 Sep 2021 00:54:09 -0700 Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt;

Short update. I know have the g4l booting via UEFI with my bz5x14.2d kernel and ramdisk.lzma. Had to basically add 100 lines to the .config file to load most of the framebuffer drivers and to setup the fbconsole.. But it now boots with video output, and even has the default linux penguins logo show up. Screen is at a higher resolution that needs, but think that is OK. Makes kernel a little larger. 9795552 Sep 9 17:09 bz5x14.2 10172032 Sep 13 10:11 bz5x14.2d So, increased kernel 376480 bytes. Need to check if the bz5x14.2d kernel will work with regular non-efi setup boot. Guess it just could be a simple process.