summaryrefslogtreecommitdiff
path: root/rootfs/samizdat-deps.yaml
diff options
context:
space:
mode:
authorAndrew Cady <d@jerkface.net>2023-06-17 16:10:18 -0400
committerAndrew Cady <d@jerkface.net>2023-06-17 16:21:51 -0400
commit297d9046b61e9d6695f4f06da260635123f3e3f5 (patch)
tree438e7fe72f45eb7f788b3fb4b30df000296df472 /rootfs/samizdat-deps.yaml
parent0b4c41d1fb932246463e253b93ab312794d7179f (diff)
"fix" efi booting with disgusting hack and out-of-repo binary
it turns out all that we need to do to make EFI booting work is to replace the BOOTX64.EFI file that is produced by GRUB's "grub-install" command with the version of that file from Ventoy's upstream source of the same file: <https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk/>. Ventoy claims that to be their source here: <https://github.com/ventoy/Ventoy/blob/master/DOC/BuildVentoyFromSource.txt> """ 5.10 UEFIinSecureBoot https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk/releases Super-UEFIinSecureBoot-Disk_minimal_v3.zip unzip it and get Super-UEFIinSecureBoot-Disk_minimal.img, extract the img by 7zip. INSTALL/EFI/BOOT/BOOTX64.EFI --> EFI/BOOT/BOOTX64.EFI SHA-256: 475552c7476ad45e42344eee8b30d44c264d200ac2468428aa86fc8795fb6e34 """ That SHA-256 matches what we have downloaded and are using. I have created a separate repo containing the code that pulls down the .zip file and extract the BOOTX64.EFI file from it. That code verifies the SHA-256 hash. It can be added as a sami.git submodule. This code is not usable without that file generated by that code. This commit should be amended with a git submodule added with that code too.
Diffstat (limited to 'rootfs/samizdat-deps.yaml')
0 files changed, 0 insertions, 0 deletions