Another way to chainload iPXE from iPXE
|
2017-11-10, 13:20
Post: #1
|
|||
|
|||
Another way to chainload iPXE from iPXE
Hello all!
I tried to use iPXE with DHCP Server that not support classes (MikroTik ROS) with following config: make bin/undionly.kpxe EMBED=loadlkrn.ipxe loadlkrn.ipxe contents: Code: #!ipxe Then booting using "undionly.kpxe" as boot file name I got this error: If I boot using pxelinux.0 with this config: Code: menu title PXE Boot Menu All files (undionly.kpxe, ipxe.lkrn, boot.ipxe) are in the Boot TFTP root. What do I do incorrectly in the first option of loading and what decision will be true to use only iPXE? |
|||
2017-11-10, 18:55
Post: #2
|
|||
|
|||
RE: Another way to chainload iPXE from iPXE
https://image.prntscr.com/image/6r9Wp5ul...6517eA.png
Reading that image you have "Could not start download: Operation not supported (http://ipxe.org/3c092003)" To break down what you do: You have an ipxe binary with embeded script that downloads ipxe and runs a downloaded script? Why do you do this in the first place? your line: kernel ipxe.lkrn initrd=boot.ipxe will start ipxe.lkrn with initrd=boot.ipxe as argument and I'm skeptical to what it does in this case, just skip the "initrd=boot.ipxe" part instead to load the script that you put into memory on the separate initrd line Use GitHub Discussions VRAM bin |
|||
2017-11-10, 21:57
Post: #3
|
|||
|
|||
RE: Another way to chainload iPXE from iPXE
(2017-11-10 18:55)NiKiZe Wrote: https://image.prntscr.com/image/6r9Wp5ul...6517eA.png I have removed initrd=boot.ipxe parameter, but the behavior of ipxe.lkrn hasn't changed - Operation not supported |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)