Posts made by jbsclm

I apologise in advance if you have tried some of the following.
This may be a basic question but, if you put your 1.2.0 server on its own isolated LAN and enable DHCP does it work.
We need to prove your 1.2.0 is good.
I’m not sure what tells it to load default.ipxe, presumably the dhcp server.
is there anything in the apache log on 10.2.6.40 for boot.php

What happens if you build a boot CD or pendrive as per the following.
[url]http://fogproject.org/forum/threads/physical-boot-disk-for-imaging.12142/#post-40540[/url]
just burn the iso to disk or pendrive and try booting from it.

No, the reason i said to disable it as you shouldn’t have 2 dhcp servers on the same network.if neither of your fog servers provide dhcp then the comment doesn’t apply.
I suspect having a seperate dhcp server may be the problem, ipxe will be getting an address from that, which will point to the 0.32 server, i don’t know whether that would affect it.

I’ll have a think.

there is a recent thread on booting from a cd or pendrive, you could try that, not what you asked i know, but it may achieve what you want to do.

Here is what I did to get 0.33 to boot from a 0.32 menu item.
[url]http://fogproject.org/forum/threads/chain-booting-0-33-beta-from-0-32.10156/[/url]
Worth a try.

My bug on [url]https://rom-o-matic.eu/[/url] has been fixed, so you should be able to build your own iso, just edit the ipxeask_33.txt (the name is not important)
change
#set fog-server 192.168.3.11
echo enter the ip address of the fog server
read fog-server

to

set fog-server 192.168.3.11
#echo enter the ip address of the fog server
#read fog-server

Changing the address above to that of your fog server.

Paste contents of the file into the "paste yours script box.

Most odd.

They used to be under
Customize image configuration options:
There were a load of tick boxes, they seem to have changed the website to take them away, which seems to be an error, or so I think
All I can think is try again later.
My guess is that the options is populated by a javascript which they have omitted to include.
I’ve raised an issue on the website
[url]https://github.com/xbgmsharp/ipxe-buildweb/issues/19[/url]

You can try the iso in the zip file it should fine.
It attempts to get a dhcp address, if not you enter ip, mask and gateway.
It then asks for the IP address of the fog server, it is this bit you can omit by building your own.

We used rufus ( [url]https://rufus.akeo.ie/[/url] ) to burn the iso to a usb stick, which is less wasteful that using a cd.

Yes, I’ve done this.
Try the attached.
I did this in March 2014, but it should still work.
There are instructions in there as to how to build it.

[url=“/_imported_xf_attachments/1/1585_ipxe_ask33.zip?:”]ipxe_ask33.zip[/url]

Make sure your network card type is set to Intel in virtual box, other types, eg realtek, can give this problem.
It only happens on the Virtual box emulated ones, the real hardware ones are OK.
See the attached screenshot for a working example
The name doesn’t matter, just the adapter type.[ATTACH=full]1583[/ATTACH]

[url=“/_imported_xf_attachments/1/1583_Capture.PNG?:”]Capture.PNG[/url]

I had a go on my failing system today, when I rename run.php to something else I get the problem back, i.e. no options for capone.
I’ve tried clearing the browser cache, on both Firefox on the server and ie8 on xp, and it makes no difference.
My home system is fine, I’ll try building a new one and see if I can reproduce the problem.

My home system was fine.
My work system had the problem, I can’t remember whether I was on the server (firefox) or my PC (ie8).
I’ll have a try tomorrow, renaming run.php and clearing the cache and see if I can get some more details.

I too have seen this.
My fix, dirty and should not be necessary was to find the capone instance of run.php. which did exist at an earlier revision, and copy it into
lib/plugins/capone/html
It used to exist there in an earlier revision, but shouldn’t be necessary now, but for some strange reason it is, but only on some installation.
Most odd.

before you do that just try change the value of FOG_UPLOADRESIZEPCT to 15
It is in the general settings.

I seem to remember we had the same problem, a couple of years ago.

Do any of the others, ie Latitude E5430 work, I realise you may not have had the opportunity to try any others.
could you post the response from both wmic calls please, just for confirmation.

thanks

Can you post the following please.

1. A screenshot of the capone gui page, showing the dmi field and the associations.
   2 output from the following dos commands from a similar device running windows
   wmic bios get serialnumber
   wmic computersystem get manufacturer,model

thanks

The log location is os dependent,

Debian based Location (normally)
/var/log/apache2
Redhat based Location (normally)
/var/log/httpd

there are 2 logs, access.log and error.log.

The messages you need will probably be in the access log, search for WindowsAIO.iso starting at the end, you should see a status 404, which says not found
You can test by typing the following in to your browser

[URL=‘http://$%7Bfog-ip%7D/$%7Bfog-webroot%7D/service/ipxe/boot.php?mac=$%7Bnet0/mac%7D’]http://<fog_ip_address>/fog[/URL]/Win7AIO/WindowsAIO.iso
replacing <fog_ip_address> with your fog server ip.

eg
[URL=‘http://$%7Bfog-ip%7D/$%7Bfog-webroot%7D/service/ipxe/boot.php?mac=$%7Bnet0/mac%7D’]http://192.168.3.11/fog[/URL]/Win7AIO/WindowsAIO.iso

[url]http://sourceforge.net/p/freeghost/code/HEAD/tree/[/url]

take the “download snapshot” link at the top

unzip it to a folder

cd to the bin folder

run ./installfog.sh

Please be aware that this is development code, although it is tested it may contain bugs.

The client doesn’t understand paths on the fog server, only http paths.

:WIN7PE64BIT
initrd var/www/fog/Win7AIO/WindowsAIO.iso
chain memdisk iso raw ||
goto MENU

Needs to be

:WIN7PE64BIT
initrd [URL=‘http://$%7Bfog-ip%7D/$%7Bfog-webroot%7D/service/ipxe/boot.php?mac=$%7Bnet0/mac%7D’]http://${fog-ip}/${fog-webroot}[/URL]/Win7AIO/WindowsAIO.iso
chain memdisk iso raw ||
goto MENU

OR

:WIN7PE64BIT
initrd [URL=‘http://$%7Bfog-ip%7D/$%7Bfog-webroot%7D/service/ipxe/boot.php?mac=$%7Bnet0/mac%7D’]http://${fog-ip}/fog[/URL]/Win7AIO/WindowsAIO.iso
chain memdisk iso raw ||
goto MENU

Both should tell the client to look in the same place, although the first form is preferable.

If this fails check your apache log, it will tell you where i is looking for the iso.

Tom has fixed this at R1750, it should now work as before, ie 1234 will match anything starting with 123.
Can you give it a try and report back.

I take it you can log in to the gui OK.
A couple of things to try.
point your browser at [url]http://<myip>/fog/service/ipxe/boot.php[/url] you should see an ipxe menu.
if this fails check your apache log, on ubuntu 12.04 the above should go to /var/log/www/fog/service/ipxe/boot.php if my memory serves me right.
There should be an entry in the log saying what it can’t find.

If you were interested in using the capone plug in, I think the following would probably work, assuming that the usb ethernet adaptor is supported by the fog kernel.
Create a bootable cd or usb drive containing ipxe, and the fog kernel and bzimage.
boot from this, it would then load kernel and bzimage from there, connect to the fog server, lookup the configured image for the particular dmi field, and then image the client. From what you say the I would suggest model for the capone dmi field.
Let me know if this might work for you, and I will see if my idea works.

I’ve tested on r1717, and can confirm that you associate more than one image to a dmi criteria, and will get a message to that effect on the client, and asked to choose which one.

see attached screen shot, for info I have the dmi field set to serial number.

[ATTACH=full]828[/ATTACH]

[url=“/_imported_xf_attachments/0/828_capone_multi.png?:”]capone_multi.png[/url]