by the way, you now have demonstrated the ease with which you can exploit uefi.
drop any random DXE in there, and it runs. Harder on newer hardware, as it has protections against this sort of thing, but ... not as hard as might seem. note, also, you can build a linux kernel, with an embedded initramfs, as a UEFI DXI, and UEFI will happily run that as it will the UEFI shell. On Tue, Feb 18, 2025 at 9:39 AM <tlaro...@kergis.com> wrote: > (I will make documentation about this later, but here is a quick > tip.) > > Since on the hardware I'm testing (AM08PRO), Windows 11Pro comes > pre-installed, I used it to edit the plan9.ini. > > This is easy in either configurations: > - If it is in the FAT32 EFI System Partition (esp for 9front), > the partition is recognized hence a volume is created, and you > just have to assign a letter in diskpart to be able to > manipulate the contents; > > - If the files are in the 9fat partition of the 9front slice, > the 9fat partition starts at the beginning of the slice. > Hence, under Windows, I make acrobatics by assigning the ID of an > ESP to the 9front slice (under diskpart: set id=the_guuid_of_efi > see the help for what is it---I haven't tested to see if the > hexadecimal byte value would suffice); then Windows will > recognize this as a FAT and allow to assign a letter. But you > have to reassign correctly the GUUID to the 9front one, since > 9front uses this to recognize one of its possible realms. > > But in fact, there is more simple and more efficient. > > The BIOS coming with the hardware is an AMI Bios (Del key to access > BIOS config) that implements UEFI 2.80. But it comes without an UEFI > shell. > > Just grab the amd64 variant of the shell: > > https://github.com/pbatard/UEFI-Shell/releases/download/24H2/shellx64.efi > > Put it at the root of the EFI partition on the disk and then, from the > BIOS (under last menu entry: Save and Exit, that allows to override > the booting order) run "Try to run an UEFI shell found on one > filesystem". > > The UEFI shell allows you to edit a file (if it is ASCII, it remains > ASCII; a created file will generally be UCS-2 so has to be converted > afterwards). > > So navigating to the one of the recognized filesystems (this is a > Windows like syntax, with volumes and backslash for directory > components separator): > > Shell> fs4: # This the start of the embedded (initial) 9fat > Shell> edit plan9.ini # CTL-E to see help; CTL-S to save; CTL-Q to quit > Shell> boot efi\boot\bootx64.efi > > But the UEFI shell lets you explore the hardware (it comes with an > hexedit editor too, allowing to see blocks---blocks devices being > distinct from filesystems devices). > > In particular, you can list the devices at disposal, and the whole > smbios informations (smbios -a)---and you can redirect the output to > a file, letting spaces between the '>' redirection). > > You can find almost the whole story of the hardware here: > > http://notes.kergis.com/nix-os/AM08PRO/devices.txt > > and > > http://notes.kergis.com/nix-os/AM08PRO/smbios.txt > > -- > Thierry Laronde <tlaronde +AT+ kergis +dot+ com> > http://www.kergis.com/ > http://kertex.kergis.com/ > Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T4560932587002aaa-M910282006c794ffb9ac17b48 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
