On 28/10/14 22:43, Floris Bos wrote:
I am having problems getting a Windows 2012 iSCSI installation to work
with recent iPXE versions,
while it does work with an older iPXE version.
Have you tried performing a bisection (http://ipxe.org/howto/bisect) to
identify the commit causing the problem?
set keep-san 1
set skip-san-boot 1
sanboot
iscsi:192.168.178.99::3260::iqn.2000-01.com.synology:DiskStation.diskless
kernel http://192.168.178.100/wimboot
initrd http://192.168.178.100/bootmgr bootmgr
initrd http://192.168.178.100/bcd bcd
initrd http://192.168.178.100/boot.sdi boot.sdi
initrd http://192.168.178.100/segmono_boot.ttf segmono_boot.ttf
initrd http://192.168.178.100/segoe_slboot.ttf segoe_slboot.ttf
initrd http://192.168.178.100/wgl4_boot.ttf wgl4_boot.ttf
initrd http://192.168.178.100/boot.wim boot.wim
boot
For what it's worth: in the current iPXE and wimboot builds this script
should probably be:
#ipxe
sanhook
iscsi:192.168.178.99::3260::iqn.2000-01.com.synology:DiskStation.diskless
kernel http://192.168.178.100/wimboot
initrd http://192.168.178.100/bcd bcd
initrd http://192.168.178.100/boot.sdi boot.sdi
initrd http://192.168.178.100/boot.wim boot.wim
boot
i.e. use "sanhook" instead of the "skip-san-boot" hack, and there's no
longer any need to provide bootmgr or the font files.
With undionly.kkpxe compiled today from git sources:
Another possibility is that a small increase in code or data size has
pushed the iBFT below the 512kB boundary. Try with undionly.kpxe
instead (which should reclaim more base memory); this may work.
Michael
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
