More interesting things in testing.
I can boot from the flash, and it loads my kernel and your
g4l.img file with no problem, except of course have a
blank screen...
How do I know it works.
First thing I tried was after waiting a while, pressed enter
a number of times that will eventual bring it to a
command prompt. At that point, nothing but a blank
screen with the echo messages I added.
Type eject on the keyboard, and the cd rom ejects, so
assumed it was working.
Then modified the menu option to add the telnet=y
option. That has it automatically load the telnetd program
as start of the boot process. Booted from a regular g4l
usb, and found system gets ip 192.168.16.105.
Rebooted with the UEFI flash, and again tried the eject,
and it worked. Then took my notebook, and
telnet 192.168.16.105 gets me into the machine?
Looked at dmesg, but it didn't have info on video.
G4L didn't include lshw, so I had to use ncftp to connect
to my notebook, and download the lshw program.
lshw -c video reports this?
*-display UNCLAIMED
description: VGA compatible controller
product: 4th Generation Core Processor Family Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list
configuration: latency=0
resources: memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64)
memory:c0000-dffff
-bash-5.0#
Looked at lshw | more and don't find any other video info??
The only reference to efi was this line, and another line had word Definition in it.
capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720
int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification
netboot uefi
So, one could boot from the UEFI Flash, but then would need to telnet into it from another machine.
Did this in the past when access machine remotely, could change default boot to the g4l option in
grub, then telnet in, and make image..
Added some kernel option about graphics for EFI, but even with that still get a blank screen??
These where the changes to the .config file.
< CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
< CONFIG_FB_CMDLINE=y
< CONFIG_FB_NOTIFY=y
< CONFIG_FB=y
< CONFIG_FIRMWARE_EDID=y
< CONFIG_FB_BOOT_VESA_SUPPORT=y
< CONFIG_FB_CFB_FILLRECT=y
< CONFIG_FB_CFB_COPYAREA=y
< CONFIG_FB_CFB_IMAGEBLIT=y
< CONFIG_FB_MODE_HELPERS=y
<
< CONFIG_FB_VESA=y
< CONFIG_FB_EFI=y
So, must need something else??
Thanks again. Always more to learn.
On 12 Sep 2021 at 0:54, Samuel Sieb wrote:
From: Samuel Sieb <samuel@sieb.net>
Subject: Re: Failure in gsetting up a UEFI USB
Flash with Fedora 33??
To: users@lists.fedoraproject.org
Date sent: Sun, 12 Sep 2021 00:54:09 -0700
Send reply to: Community support for Fedora
users <users@lists.fedoraproject.org>
> On 2021-09-09 5:04 a.m., Michael D. Setzer II via users wrote:
> > Does anyone know of a process to make a UEFI USB Boot that actual works
> > using Fedora??
>
> 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.
> _______________________________________________
> 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