Posts made by oneblot

Hi,
Have a look at editing the default file. /tftpboot/pxelinux.cfg/default
There is a line there [COLOR=#ff0000]TIMEOUT XX[/COLOR] this is the time such that 120secs will be written as 1200.
You can also change what the default selection is on the menu within this file.

Hi,
I have a similar problem to this whenever the Fog server is shutdown and restarted. I run it on ubuntu 12.04. to restart the services open up a terminal window and type the following:

[COLOR=#ff0000]sudo service isc-dhcp-server start[/COLOR] - this starts the dhcp

[COLOR=#ff0000]sudo service tftpd-hpa start[/COLOR] - this starts the tftp

sometimes you may need to stop and then start the service other times you can just restart. Give it a go and see if it works it, if not then the service names may be different in 11.04 but it will give you a starting point.

Have alook at this thread [url]http://fogproject.org/forum/posts/8960/[/url]

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.

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]

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.

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]

Cheers for the information.
I have tried that config file today and it worked I will just have to experiment know to get rid of the drivers that aren’t needed to stop the various errors. But at least it can see the HDD’s after compiling a new bzImage file.

Thanks for the pointer. unfortunately I tried that kernel with the kitchensink.config file from fog0.33 to form the bzImage file but it still didn’t work. For some reason it still does not see the hard drive. Went back to the original bzImage file and that can see the HDD.
Any suggestions?

Thanks for the reply. I am still learning linux and fog setup.

Do you know what kernel the bzImage file is based on as this is what i recompiled to work with 0.32 without problems. When trying to use this recompiled kernel with 0.33 it doesn’t see the HDD.

The bzImage file that comes with version 0.33 can see the HDD without problem but throws up other errors that although dont effect the running are just annoying. The screen resolution is also finer than in 0.32.

Thanks again for any advice / help

I am testing the latest version of fog0.33 for use with intel atom based tablets. I am looking to compile a custom kernel but the versions i have tried never seem to be able to see the HDD.
I have tried versions:
2.6.34.13
3.3 - this worked with fog0.32
3.5.4

Can anyone tell me which kernel version fog uses?

Hi still learning to use FOG 0.32 in my workplace. I am also new to using linux so any help please take it easy with me.

Basically i have installed trunk 890 on ubuntu 10.01.04 to test any new features. I just have a few problems.

1 - I cannot upload any images wes7e, Win7 and xp images in either single partiton or multi partition both fail with the same error:-
[I]cannot open /proc/partition[/I]

[I]Fatal error: Unable to locate hard disk[/I]

2 - In version 0.32 i use capone all the time in this beta version of 0.33 i cannot get capone to install. When i click on installed plugin I get a red box at the top of the screen:-

[I]FOG DEBUG: FOGPageManager: Class: PlugInManagementPage, Method: installe, Error: Method not found in class, defaulting to index()[/I]

It might just be a case of something i have done and simply missed any help is appreciated.

Managed to get the imageing working by going back to the original kernel and not using my custom kernel for Atom processors that works in 0.32. Still cannot get capone to work.

Hi Im new to using the forums but found this post.
I work with intel Atom based tablets and had similar errors. I managed to get rid of the errors by recompiling the kernel used.
I cant remember the finer details and am still new to Linux but when you recompile the kernel you can select the processor archetecture and use the option for Atom.
Switch your newly compiled kernel with that used in bzImage and the error messages go.

Hope it helps