[quote=“Junkhacker, post: 34899, member: 21583”]compression on 0.32 was hard coded to 3
if you’re uploading an image off of a slower computer, it will make a very big difference.
download speeds are typically faster then they were with 0.32, and isn’t that more important?[/quote]
Oh btw! We just tested it on the download and holy hell, you were not kidding about the improved download speeds. Excellent work!
Funny enough, 3 is just what I set it to before reading your response.
And yeah, I don’t mind slower than previous uploads, but I was a bit more concerned about the downloads. I wont have a chance to test that out until tomorrow, but something tells me we’re probably going to be fine. Thanks for the quick response time!
[quote=“2cool4me4, post: 34891, member: 25120”]
It’s probably something in the compression. Go to FOG Configuration -> FOG Settings -> FOG Boot Settings and turn down [FONT=Ubuntu][COLOR=#555555]FOG_PIGZ_COMP[/COLOR][/FONT]. It will decrease image upload time but will increase image size on your server.
[/quote]
Thanks. I’ll check that out when I get a chance, although it doesn’t seem like it’s compressing the images any smaller than before. On the other hand, the PIGZ compression setting IS set to 9, so that’s probably it. I’ll try it out, and post back if that doesn’t seem to fix my issue.
Hi folks,
We have been using Fog 0.32 on Ubuntu 12.04 for a little over a year now. We’ve just upgraded to 1.2
When we were using 0.32, we liked the speed; uploading a 25-30 gig image took about half an hour or so, with throughput speeds hovering around 900 Megs to 1.02 Gigs a second. Similar results achieved for downloads by and large.
On 1.2, that same image, on the same network, with the same switches et al, appears to take about an hour and a half. It looks like maybe it’s trying to do a sector by sector copy, even though we haven’t selected that option in the images we’ve been creating with 1.2. I would say throughput is about 300-350 megs a minute now.
Is there some new setting we are missing, some vital tweak we need to adjust, or is it just that 1.2 is really that much slower than before? I find that hard to believe though. We haven’t tried downloading an image onto equipment from FOG, so maybe thats much quicker?
I’d hate to roll back; I only just got it working a couple days ago after a somewhat bumpy upgrade, and I’m liking the GPT support a lot.
Thanks in advance!
-RR
EDIT/UPDATE: This article: [url]http://fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0[/url]
got things working at long last, at least as far as booting into the FOG Environment, and running the diagnostics mode. I haven’t tried actually imaging or uploading from any of our PC’s yet.
I WILL note that FOG now seems touchier than ever about switch equipment; on the other hand, I keep telling the PTB our switches are desperately in need of replacement, so maybe this will give them an extra kick in the butt 
ORIGINAL POST:
Hi there,
I have been banging my head against this same problem. I just upgraded today from FOG 0.32 to 1.2.0 in Ubuntu 12.04
The DNSMasq trick worked like a charm…but now whenever we try to PXE boot, it craps out at this error:
/default.ipxe…Connection timed out ([url]http://ipxe.org/4c126035[/url])
We boot mostly Panasonic Toughbooks and HP Compaq Pro Elite workstations. We had NO problem in the past with PXE booting, not until this upgrade.
The chain http statement in that file is pointing to the correct IP address of the FOG server, and when we run the URL through, we get an output that appears as expected.
Any ideas?