⇤ ← Revision 1 as of 2019-12-16 01:23:46
577
Comment: PXE boot an ISO
|
2125
new PXE stuff and initrds
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
= New in 2020 = Well I forgot I had this page, but I've been wanting it again because I tried to install Pop OS and had no luck with local USB. :/ It get somewhat more complex with UEFI, I think, but here are some notes. * How it can work: https://unix.stackexchange.com/questions/218379/boot-iso-file-through-uefi-by-calling-efi-executable-inside-the-iso * Live CD to netbootable: https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 * Ubuntu hardware enablement notes: https://wiki.ubuntu.com/Kernel/LTSEnablementStack Maybe can PXE this with a pxelinux.cfg/default entry: {{{ # taken from grub.conf on the iso menuentry "Try or Install Pop_OS" --class pop-os { set gfxpayload=keep linux /casper_pop-os_20.10_amd64_nvidia_debug_22/vmlinuz.efi boot=casper live-media-path=/casper_pop-os_20.10_amd64_nvidia_debug_22 hostname=pop-os username=pop-os noprompt modules_load=nvidia --- initrd /casper_pop-os_20.10_amd64_nvidia_debug_22/initrd.gz } }}} How to run tftp server on suomi: * /home/furinkan/Documents/tftp_root/uefi * sudo py3tftp -p 69 * Unifi DHCP points to x.x.x.175 and looks for syslinux.efi I found that Pop's initrd doesn't have support for a ramdisk, so copying Ubuntu's config didn't work with it. Here's some tricky stuff with initrds: * Mangling your initrd: https://wiki.ubuntu.com/CustomizeLiveInitrd * Modern initrds are whack: https://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel |
Working with ISOs
Let's say you've got a CD ISO, but you want to boot that from the network, because using virtual media over an iDRAC sucks.
And you wanna jam it into Foreman: https://projects.theforeman.org/projects/foreman/wiki/Fetch_boot_files_via_http_instead_of_TFTP
Looks like memdisk is involved in "chaining" the ISO along: https://wiki.syslinux.org/wiki/index.php?title=MEMDISK
New in 2020
Well I forgot I had this page, but I've been wanting it again because I tried to install Pop OS and had no luck with local USB. :/
It get somewhat more complex with UEFI, I think, but here are some notes.
How it can work: https://unix.stackexchange.com/questions/218379/boot-iso-file-through-uefi-by-calling-efi-executable-inside-the-iso
Live CD to netbootable: https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
Ubuntu hardware enablement notes: https://wiki.ubuntu.com/Kernel/LTSEnablementStack
Maybe can PXE this with a pxelinux.cfg/default entry:
# taken from grub.conf on the iso menuentry "Try or Install Pop_OS" --class pop-os { set gfxpayload=keep linux /casper_pop-os_20.10_amd64_nvidia_debug_22/vmlinuz.efi boot=casper live-media-path=/casper_pop-os_20.10_amd64_nvidia_debug_22 hostname=pop-os username=pop-os noprompt modules_load=nvidia --- initrd /casper_pop-os_20.10_amd64_nvidia_debug_22/initrd.gz }
How to run tftp server on suomi:
- /home/furinkan/Documents/tftp_root/uefi
- sudo py3tftp -p 69
- Unifi DHCP points to x.x.x.175 and looks for syslinux.efi
I found that Pop's initrd doesn't have support for a ramdisk, so copying Ubuntu's config didn't work with it. Here's some tricky stuff with initrds:
Mangling your initrd: https://wiki.ubuntu.com/CustomizeLiveInitrd
Modern initrds are whack: https://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel