12.04 Ubuntu + FOG .32 - isolated network

[foggybottom]

I got FOG .32. working with Ubuntu 12.04 in an isolated network setup to work. My issue is that when I reboot, I can no longer PXE boot and image without reinstalling fog (installfog.sh).

I have already tried:
sudo stop tftpd-hpa
sudo start tftpd-hpa

I also did: "Edit etc/rc.local and add the line one up from exit 0: /bin/sleep 30 && /etc/init.d/tftpd-hpa restart

It should look like this:

/bin/sleep 30 && /etc/init.d/tftpd-hpa restart"

It didn’t work. Can suggestions?
Thanks.

[JakeS]

[quote=“oneblot, post: 8904, member: 1063”]I have a similar setup and there are a couple of things to try.

1, find the file called /etc/default/isc-dhcp-server
Change the line [I][COLOR=#ff0000]INTERFACES"“[/COLOR][/I] to [I][COLOR=#ff0000]INTERFACES"eth0”[/COLOR][/I]
[COLOR=#000000] Edit the connection setting of eth0. Under IPv4 settings tick connect Automatically and set it to manual[/COLOR]
[COLOR=#000000] Enter IP address and netmask of the fog server[/COLOR]
[COLOR=#000000]2, From a terminal type[/COLOR]
[I][COLOR=#000000] sudo service isc-dhcp-server restart[/COLOR][/I][COLOR=#000000] - this will restart the dhcp server[/COLOR]

[I][COLOR=#000000] sudo service tftpd-hpa restart - this will restart the tftp service[/COLOR][/I]

[COLOR=#000000]I find that these two commands both need to be run when the fog server is switched on especially if there is nothing connected to it via ethernet cable.[/COLOR]

[COLOR=#000000]Give it a go and see it it works it did for me.[/COLOR][/quote]
I had the exact same issue and this helped a bundle. Thanks for the posts guys! Saved me alotta time!

[oneblot]

Sorry not replied sooner but busy at work.

The differnece between kitchensink.config and core.config as far as know is the number of drivers added. the kitchensink version having the most to try and cover anything.
Compiling the kernel to actually work is trial and error. The finer points of exactly what each setting in the kernel editor does is beyond me I am still learning myself and have it easier than you as all my systems are identical. When I first compiled a new kernel all i had to do was swap the processor type to atom and this got rid of the error messages. I still struggle with some images, making them resizeable images but i think that is more to do with the image im starting with.

[foggybottom]

So I resolved to use different kernels for different machines. I was hoping to use one universal kernel but that doesn’t look like it’s going to happen. I am trying to image a 740 but it will start and then it hangs (10%). I am using 2.6.33.3 PS kernel because FOG Rookie had an Optiplex 740 and it worked with that kernel. Any ideas on what would cause hanging? Thanks.

[foggybottom]

[IMG]http://i.imgur.com/fb5Fi.jpg[/IMG]
Here is the error message I get. Any suggestions from anyone would be greatly appreciated.

[foggybottom]

Update, I got it to compile . My new one didn’t work. Is it more or less trial and error?

[foggybottom]

Thanks man. What is the difference between kitchensink and core.config?
I don’t see the folder that is being referenced in the copy command:
[COLOR=#ff0000][I][U]cp /opt/fog-setup/fog_0.32/kernel/kitchensink.config[/U] /usr/src/linux-3.3.3/.config [/I][/COLOR]

The fog-setup directory or the .config in the new kernel download.

[oneblot]

The page i used from the wiki has now disappeared, so I have listed the steps.

1. install the required packages to build the kernel.
   Connect to the internet and from a terminal:
   [COLOR=#ff0000][I] sudo apt-get install qt3-dev-tools libqt3-mt-dev[/I][/COLOR]
   [COLOR=#000000]2) Download the kernel you want to use and put the tar file in /usr/src (i’ll use linux-3.3.3 as an example)[/COLOR]
   [COLOR=#000000]3) move to the folder and Extract the tar file[/COLOR]
   [COLOR=#ff0000][I] tar -zxvf linux-3.3.3.tar.gz [/I][COLOR=#000000]for gz file[/COLOR][/COLOR]
   [COLOR=#ff0000][I] tar -xjvf linux-3.3.3.tar.bz2 [/I][COLOR=#000000]for bz2 file replacing the stars with the kernel version.[/COLOR][/COLOR]
   [COLOR=#ff0000][COLOR=#000000]4)copy the config file from fog either the kitchensink.config or core.config[/COLOR][/COLOR]
   [COLOR=#ff0000][I] cp /opt/fog-setup/fog_0.32/kernel/kitchensink.config /usr/src/linux-3.3.3/.config [/I][/COLOR]
   [COLOR=#000000]5) change directory to /usr/src/linux-3.3.3 and type[/COLOR]
   [COLOR=#ff0000][I] make xconfig [/I][/COLOR]
   [COLOR=#000000]6) this will open the editor allowing you to make all sorts of changes only change things you know about. A hint might be to change the processor type to 586 instead of 486???[/COLOR]

[COLOR=#000000]7) when finished save the file and then exit.[/COLOR]

[COLOR=#000000]8) type [COLOR=#ff0000][I]make bzImage [/I][COLOR=#000000]and walk away for the best part of an hour. when finished back up your existing bzImage file and copy your new bzImage file to its place.[/COLOR][/COLOR][/COLOR]
[COLOR=#000000][COLOR=#ff0000][COLOR=#000000]the original bzImage is in /tftpboot/fog/kernel/[/COLOR][/COLOR][/COLOR]
[COLOR=#000000][COLOR=#ff0000][COLOR=#000000]your newly compiled bzImage will be in /usr/src/linux-3.3.3/arch/x86/boot/[/COLOR][/COLOR][/COLOR]

[COLOR=#000000][COLOR=#ff0000][COLOR=#000000]test it and then keep adjusting until you get the results you want. If you get it wrong you still have the original stored safely.[/COLOR][/COLOR][/COLOR]
[COLOR=#000000][COLOR=#ff0000][COLOR=#000000]Have fun and other people might be able to help with finer points, but this has worked for myself.[/COLOR][/COLOR][/COLOR]

[foggybottom]

Thanks for the info.

The crazy part is that they are all Dells. Do you have any information about compiling a new kernel?

[oneblot]

I am glad it worked.

I have found that I usually need to run those two commands if the server is shutdown and restarted.

As for the kernel I am lucky that all the machines i use fog to image are of almost identical hardware. This meant I had to tweak the kernel a few times to remove error messages from unneeded drivers etc. I think if you have machines from different manufacturers the chances are that you will need a greater spread of drivers or other things selected when you compile a new kernel. You could also try to use the core.config file instaed of the kitchensink.config file that solved my problem of getting a working kernel in fog0.33B.
I am by far no expert on doing this as my linux knowledge only started about April of this year when i was tasked with setting up a FOG server at work. Trial and error and a lot of googling to get some features working.

May be someone else could point you in the right direction.

[foggybottom]

This worked. Thank you!

Anyway to do this at startup?:
[I][COLOR=#000000]sudo service isc-dhcp-server restart[/COLOR][/I]

[I][COLOR=#000000] sudo service tftpd-hpa restart[/COLOR][/I]

Fog is beautiful when it works. My issue is the kernel that is included with FOG .32 didn’t image Optiplex 790. I thought the latest kernel version would do the trick 3.3.3.3. This didn’t work. I ended up downloading a customized kernel that did work. Then I went to image a Latitude E6520 with the customized [COLOR=#000000]kernel and it no longer imaged them.[/COLOR][COLOR=#000000]When you use FOG do you have to constantly tweak the kernel?[/COLOR]
Thanks![I][COLOR=#000000][/COLOR][/I]

[oneblot]

I have a similar setup and there are a couple of things to try.

1, find the file called /etc/default/isc-dhcp-server
Change the line [I][COLOR=#ff0000]INTERFACES"“[/COLOR][/I] to [I][COLOR=#ff0000]INTERFACES"eth0”[/COLOR][/I]
[COLOR=#000000] Edit the connection setting of eth0. Under IPv4 settings tick connect Automatically and set it to manual[/COLOR]
[COLOR=#000000] Enter IP address and netmask of the fog server[/COLOR]
[COLOR=#000000]2, From a terminal type[/COLOR]
[I][COLOR=#000000] sudo service isc-dhcp-server restart[/COLOR][/I][COLOR=#000000] - this will restart the dhcp server[/COLOR]

[I][COLOR=#000000] sudo service tftpd-hpa restart - this will restart the tftp service[/COLOR][/I]

[COLOR=#000000]I find that these two commands both need to be run when the fog server is switched on especially if there is nothing connected to it via ethernet cable.[/COLOR]

[COLOR=#000000]Give it a go and see it it works it did for me.[/COLOR]