[help] how to make blank undionly.kpxe - Printable Version +- iPXE discussion forum (https://forum.ipxe.org) +-- Forum: iPXE user forums (/forumdisplay.php?fid=1) +--- Forum: General (/forumdisplay.php?fid=2) +--- Thread: [help] how to make blank undionly.kpxe (/showthread.php?tid=6892) |
[help] how to make blank undionly.kpxe - biatche - 2013-04-30 20:13 is it possible to remove all the verbose info ipxe does after pxe loads? RE: [help] how to make blank undionly.kpxe - mcb30 - 2013-04-30 20:16 (2013-04-30 20:13)biatche Wrote: is it possible to remove all the verbose info ipxe does after pxe loads? Not without modifying the code. You could include an embedded script which clears the screen before attempting to boot; see http://ipxe.org/cmd/set#notes for instructions on clearing the screen and http://ipxe.org/embed for information about embedding scripts. Michael RE: [help] how to make blank undionly.kpxe - biatche - 2013-04-30 22:44 ###1### After embedding, will i still require this (it's in my embedded script now) on my dhcp server: dhcp-boot=http://192.168.0.xx/xxxxxx/bootstrap.ipxe if in the case the chain link in the embedded script is broken, what happens? will the above line serve in dnsmasq serve as backup? ###2### your link also brought me to notice: make bin-x86_64-efi/808610de.efirom # 64-bit driver ROM that got me interested in building UEFI pxe. Do I just type: " make bin-x86_64-efi/808610de.efirom " and that it would automatically know it has to build a 64bit efi rom based on filename? ###3### zlib and binutils header files (only needed for EFI builds) [ebuild R ] sys-devel/binutils-2.21 USE="nls -multislot -multitarget -test -vanilla" [ebuild R ] sys-libs/zlib-1.2.5-r2 I have an old linux box, which i dont intend to update, will those versions suffice for EFI? RE: [help] how to make blank undionly.kpxe - mcb30 - 2013-04-30 23:07 (2013-04-30 22:44)biatche Wrote: After embedding, will i still require this (it's in my embedded script now) on my dhcp server: If you have an embedded script, then the control flow (including what to do in the case of failure) is entirely under the control of that script. For example, you could create a script that retries indefinitely: Code: #!ipxe Quote:Do I just type: "make bin-x86_64-efi/808610de.efirom " Yes. Quote:[ebuild R ] sys-devel/binutils-2.21 USE="nls -multislot -multitarget -test -vanilla" Probably. Try it and see if it builds. Michael RE: [help] how to make blank undionly.kpxe - biatche - 2013-04-30 23:18 Code: #!ipxe Sorry I'm a little slow, please tell me if i got the program flow wrong scenarios: dhcp -> gets ip -> boots ${filename} -> out of myscript.ipxe dhcp -> gets ip -> boots ${filename} but fails to find filename -> infinite 1 sec loop attempting to boot ${filename}? dhcp -> doesn't get ip -> infinite loop till it does? and filename = http://192.........../bootmenu.ipxe right? RE: [help] how to make blank undionly.kpxe - mcb30 - 2013-04-30 23:22 (2013-04-30 23:18)biatche Wrote: scenarios: Yes, pretty much. You can find documentation for flow control in scripts at http://ipxe.org/scripting#flow_control. Michael RE: [help] how to make blank undionly.kpxe - biatche - 2013-04-30 23:27 You are the best. Such fast replies here and @ reboot pro Thank you great lead developer. |