why did kernel wimboot gui fix my issue ? - Printable Version +- iPXE discussion forum (https://forum.ipxe.org) +-- Forum: iPXE user forums (/forumdisplay.php?fid=1) +--- Forum: General (/forumdisplay.php?fid=2) +--- Thread: why did kernel wimboot gui fix my issue ? (/showthread.php?tid=9578) |
why did kernel wimboot gui fix my issue ? - bain19 - 2017-05-04 16:47 I had been using wimboot for quite some time, my chain loading pxe server looks a bit like this Code: lpxelinux.0 --> ipxe.krn --> wimboot -->boot.ipxe My boot.ipxe was working with all our workstations models boot.ipxe Code: #!ipxe then at some point we got new hardware and my boot.ipxe stopped working HP 820 G3 Dell 5040 I did a couple things to try and resolve the issue but in the end adding "gui" to my kernel command resolved the issue. boot.ipxe Code: #!ipxe Could someone tell me why gui command resolved the issue when everything was working without it before ? RE: why did kernel wimboot gui fix my issue ? - NiKiZe - 2017-05-04 21:18 In my experience gui is always good, the only time you don't want it is when something does not boot. I have been thinking that win10 boot.wim needs gui to work. If we look at what wimboot does without gui it disables all VESA modes, which more or less forces text mode and lowest resolution. this might not work with never versions of windows or maybe it is new bios/firmware that is the cause. |