Go here: [url]https://rom-o-matic.eu/[/url]

Click Advanced, at the bottom choose “EFI PXE Bootstrap 32-bit (.efi)”

These are the options I always check:

[SIZE=12px][FONT=Arial][COLOR=#000000]CPUID_SETTINGS[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]DOWNLOAD_PROTO_NFS[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]IMAGE_PNG[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]PARAM_CMD[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Arial][COLOR=#000000]CONSOLE_CMD[/COLOR][/FONT][/SIZE]

Finally, plop this script in the iPXE script box (remember to change the last line to match your FOG server’s IP or hostname:
(the colour and cpair lines are optional, I use these for my menu colors. Simply remove them if desired.)

#!ipxe

colour --basic 2 7
cpair --foreground 7 --background 9 1
cpair --foreground 0 --background 9 2
dhcp
set arch i386 ||
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain [url]http://x.x.x.x/fog/service/ipxe/boot.php##params[/url]

Note: With the 32-bit tablets I UEFI PXE boot with, I have to manually set the arch to i386 in this script because they are technically 64-bit capable and FOG detects this and gives them bzImage/init.xz, but they only work with bzImage32/init_32.xz.

Webmaster should add fog version details as a field to be displayed on the user Icon to the left at the forums posts.

i am happy with the answers i have , thanks.

The purpose in any OS (as they all have a kernel).

The Kernel loads all the relevant drivers and hardware for the system. That’s the basic construct of the kernel is to be the “middleman” between the interface(s) and the rest of the computer.

The Kernel’s job, essentially, is to pass the information to and from the relevant needed components whether it be Sound, RAM, HDD, CPU, or otherwise.

It’s what get’s loaded to RAM as the system is booting.

The way linux handles devices is during load up of the kernel it’s detecting the systems components and making the relevant connections between those devices on how to interpret and work with those items.

Once the OS is loaded, it already knows about the rest of the system because it was detected at load out. Those connections (in the linux world) are created as nodes or devices in /proc, /sys, and/or /dev. These items are linked (in a different manner but similar) to as “files” as everything in a *nix system is related to as a file object.

Windows operates similarly. Except everything is done, usually, from the registry and RAM. The “devices” and “registers” are loaded into the Registry. In the case of SYSPREP, it removes all the non-relevant and possibly changing aspects of the registry and places it in a point where the first boot loads all the devices and items into the Registry during the bootup process.

This is where Windows and Linux varies (I think) in the most dramatic of ways.

While a linux system can have the hdd moved around from one system to a another, and typically still operate with little to no issues, a Windows system cannot do this because the components recognized vs. the components actually available may not match.

Having the drivers embedded in a Windows system can help, but won’t work 100% of the time. This is kind of the point behind sysprep though. Clean out the registry and system so it can readily receive new item.

Hopefully this will help clarify things.

Am I 100% correct? Probably not, this is just a means to express the simple differences.

There is likely a seperate option in the BIOS for “PXE Boot after WOL”. I’ve seen it on a few of my machines but not all of them have it. If the option doesn’t exist then you are going to have to change the boot order.

Why so old? 1.2.0 is the latest and it’s far more stable than 1.1.2 was.

I don’t have your router or dhcp server. But you need to set the next-server or option 66 and the filename or option 67 items.

Click on the host to edit it.

In the Host Kernel Arguments, place the arguments you need.

Hello Tom,

I get to the ipxe menu, and the hosts keeps saying it’s not registered. I can run the registration process, the hosts gets added to the web interface, too, but after reboot the ipxe menu still reports “Host is NOT registered”.

It’s just the sony vaios that have this problem, other systems (Dell Latitudes, Workstations, …) are running fine, so I guess it’s a problem of the sony pxe boot options…

Here are the other details you requested:
[SIZE=12px]FOG Version: 1.2.0[/SIZE]
[SIZE=12px]OS Version: [/SIZE][SIZE=12px]CentOS release 6.4 (Final)[/SIZE]
[SIZE=12px]The foginstall.log is attached. I couldn’t find an error in the apache logs, is there anything I explicitly need to look for?[/SIZE]

[SIZE=12px]Regards[/SIZE]
[SIZE=12px]Christoph[/SIZE]

[url=“/_imported_xf_attachments/1/1357_foginstall.log.txt?:”]foginstall.log.txt[/url]

sry i have a mistake…
change the default config of apache root

That’s part of why I’ve included fixparts in the init.xz/init_32.xz files. If something doesn’t seem to work properly, boot into a debug task, preferably upload, and run fixparts. It should find and fix any partition data that is supposed to be mbr but still has residue of GPT within it. This has been a common issue and I just don’t have a better means to fix this. I don’t know if you’re intending to maintain GPT or go pure MBR and if I start trying to make guesses as to what you’re attempting to do, it may cause more problems down the road.

FOG Configuration->PXE Settings->Timeout

Yes, I did comment out the --picture line and that got me working for this issue. Thanks for the explanation. That makes sense.

[U][B]Regarding 1.1.2:[/B][/U]
I would suggest upgrading 1.1.2 to 1.2 and then making sure your DHCP is pointed towards undionly.kpxe for that server. With the 6400 model I noticed undionly.kkpxe doesn’t work. The default kernel should work in 1.2 if not go to fog settings>update kernel>unpublished kernels and install the 3.16*

Another issue I found was the M73 would load the Fog menu but than would hang on booting from Hard drive but if I switched the boot order back to hard drive first that would fix the issue and it would boot right up after imaging, now this was on a fog server running 0.32 not sure about the newer versions of fog.

updated Working Devices to include

[FONT=sans-serif][COLOR=#000000][SIZE=13px]HP ProBook 6450b ✓ Defualt bzImage undionly.kpxe 2014-06-13
HP Probook 645 ✓ Defualt bzImage undionly.kkpxe 2014-06-13 Disable UEFI-Bootdodus in BIOS. undionly.kkpxe is not a typo you need to use this file to boot properly.[/SIZE][/COLOR][/FONT]

Ahaha! I renamed undionly.kkpxe to undionly.kpxe (I don’t have permission to access the DHCP server. 😕 ) and everything works! It’s also quite a bit faster than .kpxe. Many thanks!

I think it’s time to run a donate task. 🙂

No problem. I’ve seen this errors many times before, it’s the only reason I give the suggestions I do.

Thanks for reporting back.

Yep tried all of them, same issue it just sits there with a blinking dos style dash and hangs.

That’s ok, I was just wondering if the issue was in the NIC firmware having a problem loading the png file. Is there an easy way for me to pretty up the menu to a simple white text on black background? I haven’t worked with php before, but thought I’d ask before researching the ‘colour’ and ‘cpair’ parameters of the print statements.

On my server I only have PXE boot menu. I had it set to grub. I tried the other options with no help

As for our computers, most of our older ones are dx2450’s, the 3500’s are the newest (this year), the 5150’s are a few years old and then we do have a mix of other PCs but those 3 are they main ones used for work stations

Oh and I’m running version 1.1.2 on a Ubuntu computer and it just happens it is one of the older dx2450’s that that could be anything

I understand. FWIW, switching to the old bzImage and 32bit init file appears to make my Hyper-V server work again. I’m uploading a new image right now.