FOG BIOS And EFI Coexistence
-
Well, 10.0.0.3 IS my home FOG server’s IP address. It’s a private address, not public, and it’s home so I don’t care about sharing here.
And my network’s address is 10.0.0.0 I set my house up like that for simplicity… it’s easier to type than that dumb 192.168.1 BS that most home DHCP is configured with.
-
The dhcp-range line, I recommend, being set to your fog server. It will automatically work on the network your fogserver is on. If you’re actually trying to use a range of IP’s for Proxy to hand out then you would have something like:
[code]dhcp-range=10.0.0.0,10.0.0.255,proxy,255.255.255.0[/code]However this is more than overkill. I think it highly unlikely you will be handing more than the network allowed (253 – e.g. gateway, network, broadcast) of your fog server’s possibilities.
If you know you’ll be hitting more than that at any time, just open the subnet to a higher range. Whatever the IP is set will be the same network the proxy hands out within.
-
[quote=“Junkhacker, post: 46793, member: 21583”]for windows server 2012 DHCP, it was as simple as the link Wayne Workman posted.
[url]http://www.syslinux.org/archives/2014-January/021404.html[/url] create vendor class that matches uefi systems ([I][COLOR=#000000]PXEClient:Arch:00007[/COLOR][/I]) and give those that match a different bootfile (in my case, ipxe.efi)[/quote]Did you got this up and running?
I created the Vendor Class, created the policy, downloaded ipxe.efi and updated the DHCP server settings in 2012R2Legacy Boot + undionly.kpxe ~ working
UEFI boot + ipxe.efi ~ [B]not working[/B][B]edit:[/B] typo ([I]ipxe.kpxe[/I] should have been[I] ipxe.efi[/I])
-
[quote=“Jeroen Brussich, post: 47054, member: 23215”]Did you got this up and running?
I created the Vendor Class, created the policy, downloaded ipxe.efi and updated the DHCP server settings in 2012R2Legacy Boot + undionly.kpxe ~ working
UEFI boot + ipxe.kpxe ~ [B]not working[/B][/quote]ipxe network boot is working for me. i set my uefi boot to ipxe.efi
uefi imaging isn’t working perfectly for me, but that has nothing to do with the network
i can schedule tasks, access the boot menu (without graphics), and load the fog kernel -
I did configure both bootfiles on the same tftpserver.
Maybe that’s what I did wrong?This is what i see on my boot screen:
[CODE]tftp://MY.IP/default.ipxe… ok
http://MY.IP/fog/service/ipxe/boot.php… ok
http://MY.IP/fog/service/ipxe/bg.png… okCould not use picture: Exec format error (htt://ipxe.org/2e008081)
Could not boot: Exec format error (htt://ipxe.org/2e008081)
Could not boot: Exec format error (htt://ipxe.org/2e008081)Failed to get IP, Booting back to bios
[/CODE]I downloaded ipxe.efi from [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url]
[B]edit:[/B] even if I don’t use the policy and make ipxe.efi the default BootFile Name of that scope, I get the same error. Maybe my ipxe.efi file is corrupt?
-
[quote=“Jeroen Brussich, post: 47057, member: 23215”]I did configure both bootfiles on the same tftpserver.
Maybe that’s what I did wrong?This is what i see on my boot screen:
[CODE]tftp://MY.IP/default.ipxe… ok
http://MY.IP/fog/service/ipxe/boot.php… ok
http://MY.IP/fog/service/ipxe/bg.png… okCould not use picture: Exec format error (htt://ipxe.org/2e008081)
Could not boot: Exec format error (htt://ipxe.org/2e008081)
Could not boot: Exec format error (htt://ipxe.org/2e008081)Failed to get IP, Booting back to bios
[/CODE]I downloaded ipxe.efi from [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url]
[B]edit:[/B] even if I don’t use the policy and make ipxe.efi the default BootFile Name of that scope, I get the same error. Maybe my ipxe.efi file is corrupt?[/quote]
It’s definitely working because the bootfile instructed your client to download default.ipxe and so on.
That being said, the problem now is with the bg.png picture. Maybe Tom will chime in with a fix for the bg.png…
-
There’s another guy that had this issue… he said he just commented out the code for the picture…
But then he ran into a ton of other issues too. He had built his own ROM for his NIC.
-
I can comment out the picturecode allright (if I would know in what file to comment
)But I don’t think I’m smart enough to build my own ROM for that NIC.
Especially since I have at least 5 different computertypes in my network and I would have to build one ROM to rule them all…That being said, do we really need uefi (now)?
I can install 8.1 with legacy boot enabled, right?Or am I missing the big picture again?
-
Newer computers are slowly ceasing even supporting BIOS.
-
Also UEFI can boot much faster, and has smarter support of the firmware interface.
-
Is there a way to find out what NIC’s are supported by ipxe.efi?
Or a manual to build my own ROM for the NIC?What’s the difference between:
[LIST]
[]intel.efi
[]intel.[B]kk[/B]pxe
[]intel.[B]k[/B]pxe
[]intel.pxe
[/LIST]
Can I failover between computers?
First try ipxe.efi
Then try intel.efi
Then try undionly.kpxe
…
I can test the hell out of FOG if you want me to
-
[url]http://fogproject.org/wiki/index.php/Filename_Information[/url]
.efi files are for UEFI, everything else is for BIOS.
There are ipxe.efi, snp.efi, and snponly.efi that you can try.
-
There’s also 32bit efi files in the i386-efi folder.
-
I am at home now and can only resume testing in 3 days.
I downloaded ipxe.efi twice and calculated the checksum for both files.
I compared the md5-hash with the file on in my tftpfolder and it was trice the same…
No errors there…I tested the ipxe.efi ROM on 2 different machines (intel NUC DC3217IYE and a Lenovo [SIZE=13px][FONT=Ubuntu][COLOR=#555555]ThinkPad Edge E540).[/COLOR][/FONT][/SIZE]Both time, the boot was interrupted as described above.
I will test snp.efi and snponly.efi in 3 days but I still got the feeling I’m doing something wrong.
Or is it a coincidence both machines refused to boot from the ipxe?Would it help to try a legacy boot from ipxe.kpxe to test the ROM in non-uefi mode?
-
Yeah, that could rule out other issues.
-
[quote=“need2, post: 47117, member: 21891”]There’s also 32bit efi files in the i386-efi folder.[/quote]
I never even thought of that…
-
we have it working here with Windows DHCP 2012 - as Junkhacker said really is simple process just create the vendor class then setup the DHCP policy and specify bootfile (option 67 and don’t need to specify option 66 in the policy as it will pick this up from already defined option in the scope)
-
I finally have all of our licenses in order, so I should be able to push forward with creating the new DHCP as early as next week. Thank you everyone for your input.
-
@need2
Documentation / screen shots please. -
Oh but of course.
