Hey Tom. I am using my Windows DHCP server services. Do I need to change the name of the iPXR file there too? Currently set to the default kpxe file

After the BIOS update the Intel Bootagent version was upgraded from 1.4.10 to 1.5.50. With Intel Boot agent 1.5.50 I can succesfully boot to the FOG menu.

I used 1.1.2 fog version it’s done I reinstall the system again but do not migrate the old images
and select the image resize able single disk
thanks again

Many Thanks its work!

[quote=“Tom Elliott, post: 31637, member: 7271”]The IMAGE_TRUST_CMD is not referring to “images” in the sense of FOG, but rather literal “images” such as Pictures. So having it or not having it shouldn’t really matter.[/quote]
Ah OK. That’s all good then.
[quote=“Tom Elliott, post: 31637, member: 7271”]They are rebuilt in SVN Trunk:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url][/quote]

That’s awesome, Tom. We love FOG here at our School (and so does my brother at his School) and I’m glad I’ve been able to contribute.

[quote=“Tom Elliott, post: 30601, member: 7271”]Moving to iPXE isn’t necessarily causing issues, rather, it’s showing issues that you haven’t seen quite yet. PXE was old and slow, and probably didn’t care about many things as much as iPXE does. While I understand this is unexpected, I would go out on a limb and say the PRO’s completely outweigh the CON’s of this change.[/quote]

Ok, thanks for the follow-up. I guess we either do further testing or possibly move to another switch.

am running on Ubuntu 12.04 and I am currently on Fog version 1.1.1

What kind of hard drive is this? It is Seagate 500gb sata drive

Has this system worked before? No it has not worked before. I have been trying to get it to work since we had Version .32 of fog.

[COLOR=#888888] Multi-part single disk[/COLOR],

[url=“/_imported_xf_attachments/1/1006_Apache log.txt?:”]Apache log.txt[/url]

Used some info that has been thrown around about these files and checked on a few other sites and threw this together. This should cover most questions on PXE and iPXE along with the different file types.
[U][url]http://fogproject.org/wiki/index.php/IPXE[/url][/U]

Rather than break a working FOG server just for this one batch of PC’s I have built another and all is now working.

Thanks for your help

So, after spending two days trying to figure it out, I came up with a solution that works best for my situation for the moment until I can figure out how to use syslinux with uefi boot. The USB NIC works after loading bzImage which is great.

I forgot to mention but this has been something I’ve been trying to figure out with the Surface Pro 1 from Microsoft since I don’t have the funds to purchase a crapload of $40 Microsoft Ethernet to USB adapters which are the only ones that support PXE boot natively.

I used this [B][URL=‘http://www.fogproject.org/wiki/index.php/Bootable_Media’]guide [/URL][/B]as proof of concept to see if I could hit the FOG 0.32 running in a VM, and it seems like I can but unless I replace syslinux.cfg every time I create a task for a new host since the MAC address changes. I could use the capone plug-in I guess, but that doesn’t solve my problem of booting with UEFI and syslinux and bzImage/init.gz. I was able to run everything in the boot menu, but anything that required a reboot (hence an imaging task) required me to overwrite syslinux.cfg manually. At least if I could get an EFI bootable stick to hit the FOG server (1.1.0) then I could do a hardware inventory on it instead of having to manually add the MAC address of all the devices.

My solution for the time being seems to be using CloneZilla and DRBL using samba to individually image or multicast image, or, use an ISO that I created with Win8.1SE on a USB which will load a ramimage of Win 8.1 as a live OS that even allows for wireless imaging since I have a licensed version of Ghost 11.5 copied into the image.

Lastly, I still want to use FOG to pick these up and join them to the domain / printer management / snap in management so once they reboot and sysprep, they should connect and do these once they boot into the OS.

In a perfect world, I’d be able to use an EFI bootable USB like the guide describes using a bios bootable version of syslinux with bzImage to hit the FOG server, register so I can create an imaging task, then reboot and hit the FOG server again without having to replace syslinux.cfg to customize the mac for the over 100 tablets that I plan on imaging :).

I have no problems rehosting that, but all of the kernel’s I’ve been building have the “ALLNET” identifier by default now.

Just wanted to add clarity for you all.

I will try with R61 i have one here.

The reason the kernel takes a while is because of all the drivers it has to load.

Basic kernel 101 here:

Kernel’s are the foot print that communicates system devices with the software layer of the OS.

With this, especially so in Linux, some systems don’t care what has to be loaded to boot, others care very much, as is the case with your laptops here.

The reason it takes a while is because it’s loading the kernel and loading all the drivers in the system. Then the kernel checks the system for what it needs. If you where to have debug displayed, you’d likely see things failing all over the place as the driver being loaded doesn’t exist or is unusable on a particular system.

I can’t tell you WHY it’s fast on some and slow on the others. Just understand this is the case.

I’m wondering if the issues we are having are being caused by the kernel like OP. We can create an image but can’t push it out to machines. Our original FOG server was ver.29 and it would seem to create an image and when pushed out to the machines the process would run. When finished we would get the Windows 7 splash screen and after that a black screen with mouse cursor. We decided to do a fresh install of FOG 1.0.1 on Ubuntu Server 14.04 LTS. The problem we have run into now is once the image is created we can push out the image but once we PXE boot the EliteBook that is to receive the image, the process starts we get the FOG graphic and through to “starting image push”. At this point we get a message that says “Task is complete, computer will restart.”
Thank you for any insight you can give this frustrated intern.

ah yes, version 1.0.1

Searched the forums, most of what I found did not apply the rest did not help. Also tried loading old kernels, result was different error messages (thus my suspicion that its the bzImage file) but still no fog screen. Even tried creating the host manually and assigning an upload task.

If I’m wrong hopefully I can get pointed in the right direction. the host is a Windows Server 2008 R2
[ATTACH=full]819[/ATTACH]

[url=“/_imported_xf_attachments/0/819_fogerror.png?:”]fogerror.png[/url]

Thank you and I hope more success.

personally, i would recommend using Ubuntu 12.04 LTS. haven’t had many people report problems with that. Ubuntu 14.04 LTS is too new, we haven’t had a chance to fix all the issues with it.

Thanks for the info.

[quote=“Sivasubramaniam.T, post: 25002, member: 22852”]Hi Tom,

I have tried the kernel with few others models. Its working absolutely fine with some new models.

[B]Good Working with below Models :[/B]
Dell Latitude 5420
Dell Latitude 6420
Dell Latitude 5440
Lenovo L440

[SIZE=3][B]Delay in loading kernel with below models :[/B][/SIZE]
Dell Vostro 3400
Dell Vostro 3460
Dell Vostro 3450 (i3)

[SIZE=3][B][I]Problem :[/I][/B][/SIZE] Its taking 4 to 5 minutes to load the kernel to perform any tasks.
[COLOR=#ff6600]esas2r : driver will not be loaded because no ATTO esas2r devices were found [/COLOR]
[COLOR=#ff6600]i2c-parport-light: adapter type unspecified [/COLOR]
After 5 minutes its performing the tasks in a normal way.
[ATTACH]640[/ATTACH]

[B]Problematic Model :[/B]
Dell Vostro 3450 (i5)

Kernel have stopped at this line once the kernel is loaded
[COLOR=#ff6600]esas2r : driver will not be loaded because no ATTO esas2r devices were found [/COLOR]
[COLOR=#ff6600]i2c-parport-light: adapter type unspecified [/COLOR]
[COLOR=#ff6600]IP-Config:Reopening network devices.[/COLOR]…
No Process after this.
[ATTACH]638[/ATTACH]

Sorry for long description. Please help in solving this issue.[/quote]

AN EMERGENCY ON YOUR PART DOES NOT CONSTITUTE ONE ON MINE!

I realize you want help, but I can’t possibly tell you why or what is wrong. The esas2r message doesn’t mean anything, but it’s telling you that the kernel has not found that driver and can’t load it. same with the i2c-parport-light.

What the kernel’s doing after that I don’t know. It’s fast on some, slow on others, and yet others it doesn’t work at all. I don’t know what to say to help.

The best I can do is recompile and try different things.

But I don’t have the systems to build against.

I’m sorry that my kernels have failed you thus far!

Awesome Tom It works!

And one more thing, the pxe boot is much faster than earlyer 🙂