Latest Development FOG
-
The bios on the computers are set in UEFI they cant be set to legacy. All I did to make it work was switch the boofiles on the dhcp server, am I suppose to do something else ?
-
I don’t know.
I don’t have any pure UEFI systems, so I don’t know what to do. I’m sorry. I’m a failure
-
[quote=“Ray Zuchowski, post: 39508, member: 24449”]Tom,
Just tried imaging one of the Dell Venu Pro 11 5130 and tried all the .efi files and none of them work. Any suggestions ?[/quote]
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’][COLOR=#737373]http://x.x.x.x/fog/service/ipxe/boot.php##params[/COLOR][/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.
-
This can actually be updated with the new default.ipxe script, I don’t have access to it ATM, though…
Simply hand out that 32-bit ipxe.efi bootfile via DHCP and that should do the trick.
-
Drk3
Thanks bro for this hookup. Im going to try it out today. I just setup WDS on a Windows server to get me through this imaging but if FOG works with this… This will be sick!
-
[quote=“Ray Zuchowski, post: 39585, member: 24449”]Drk3
Thanks bro for this hookup. Im going to try it out today. I just setup WDS on a Windows server to get me through this imaging but if FOG works with this… This will be sick![/quote]
No problem brother. At the very least you should be able to register them/send inventory. I hope you’re able to get them to image, though!
-
Drk3,
It worked like a champ but when I go to register the PC, it comes back that the Hard Drive isn’t found. Tom… LOL you are needed here !
-
What’s the drive?
-
SVN 2759 released.
With this comes a slight change to how the apache web server operates.
It will download the kernels and inits as needed rather than having them stored in the svn repo.
What’s bound to happen, some delay (sometimes seemingly a long time) during the Setting up and starting Apache Web Server phase. This delay is the download occurring.
What this means, for the kernel’s, it will always have the most current one on the published kernels, even if you use older SVN revisions back to 2759.
Hopefully you all understand.
-
Sounds great, always updated and only a minor delay on boot (which doesn’t happen very often).
Does it download updates/new kernels at regular intervals or only on boot.
Possibly once a week or once a month would be good to update them and put the older ones in a backup folder for roll back if needed.
-
Ummm, What?
It only installs/updates kernels/inits at install, not at boot.
If you want a “rotation” schedule I leave that on you to create the necessary scheduled tasks.
-
Tom,
Does the latest SVN work with the latest Ubuntu Server 14 ?
-
I don’t know what you mean.
-
Will Fog run/install on Ubuntu Server 14.04.1 LTS ?
-
There are examples in the Tutorials section ( [url]http://fogproject.org/forum/forums/tutorials.13/[/url] ).
-
[url]http://fogproject.org/wiki/index.php/Installation[/url]
To be clear. TFTP is a bit buggy in Ubuntu 14.xx but some have corrected this by editing a start up script.
[url]http://fogproject.org/wiki/index.php/Ubuntu_14.04[/url] (includes 14.04.1 & 14.10) -
[quote=“Ray Zuchowski, post: 39830, member: 24449”]Will Fog run/install on Ubuntu Server 14.04.1 LTS ?[/quote]
What Wolfbane Said!!!
But, Yes Fog will run on Ubuntu 14.04, 14.10 and Kubuntu 14.04, 14.10
We do not recommend using the latest version, stuff tends to get changed, or broken (such as moving the Apache root dir, and TFTP) If you find issues during installation, please document them and how you solve them so we can help the community.
I set up a 14.10 Kubuntu server this morning. The only issue I ran into is the common issue with ANY Ubuntu revision as of 12.04.4 and requiring users to specify their nameserver in resolv.conf so that you have internet connectivity.
-
[quote=“Ray Zuchowski, post: 39700, member: 24449”]Drk3,
It worked like a champ but when I go to register the PC, it comes back that the Hard Drive isn’t found. Tom… LOL you are needed here ![/quote]
Welcome to my world, that’s where I’m at with my Asus T100TA’s.
Try setting the Host Primary Disk to:
/dev/mmcblk0
I can’t pull inventory until I do this…
-
Can you try updating again?
-
SVN 2787 released.
With this release comes some sad, but hopefully better news. The sad is that We’ve decided to remove clamav from our package sources. This is two fold, we no longer build clamav as a part of the init’s, for the simple fact init’s don’t change too often, and therefor the packages tend to be outdated, especially when there’s a new release of clamav just far too frequently. We moved the clamav and made an effort to get clamav as a static binary set. This worked, but the binaries only worked with 64 bit, and inflated the size of the installer from (before inits and kernels where installed during installer) about 70MB to a whopping 200MB. It is because of the size of this and the fact that the files are far to vast in changes consistently, that keeping clamav on the installer or integrated in the init is just too much.
That all said, I am working on getting the [url]http://fogproject.org/wiki/index.php/Clamav[/url] wiki article updated with how to build and place the built binaries in the /opt/fog/clamav folder so that those of you who use clamav can still get it operational for your environments.
I know some are going to love this, and others are going to hate it. This is not to make anybody’s lives rougher or anything. It’s simply a practical (I think) decision that needed to happen probably long ago.
