Posts made by Junkhacker

did the exact same error show up on the boot screen?

i would check bios settings, make sure anything regarding uefi or secureboot are disabled. also check for any bios updates.

is this happening only on one client, or on multiple models of computers?

i just tried changing the setting on my server. the setting does not appear to change on the settings page, but it does change in the database, where it counts. please set it to exit and see if it works for you.

[url]http://fogproject.org/forum/threads/requests-for-wiki-access-ask-here.3811/[/url]
if you feel you can help with the documentation, feel free to help

i’m sure you can get fog to work on the desktop version, but i prefer to use the low-overhead gui-less versions of linux for servers. there’s nothing about installing and configuring fog that you can’t do from the command line, or from the browser of another computer.

nothing is required beyond the standard server installation and running updates before installing fog on ubuntu 12.04 server

if you want to re-install and if you feel more comfortable with ubuntu, 12 and 13 work fine.
that said, those who have had this problem in the past have said that the problem either went away on it’s on, leading me to believe it was a network issue, or it went away after performing a reinstall/upgrade in place.

i never noticed that video section before, lol.
i’ve never installed fog on centos, so you may want to seek out the advice from others on the subject.
I personally use Ubuntu server installs without a gui
the fog install script will most likely install everything you need

there isn’t any reason not to use 64bit, and i don’t know what video you’re talking about but Tom has some of the best driver support possible included in the default kernel.

the fog 1.0.1 interface is still written in php, so there’s nothing stopping you from manually editing the files like you did before.

there was a line in the install script telling you that you would need to edit the config.php file if you had a password
you had to hit enter to proceed past that message

btw, the pxe files used for 1.0.1 and 1.1.0 are identical in functionality, they just use slightly different code to do it. if one works for you and another doesn’t, there is no need to do any kind of “downgrade,” just swap the file for the one that works. that said, i recommend you try the undionly.kpxe file currently in the svn trunk release if you are having issues.

Ubuntu 12 and 13 are fine. I recommend that you do not use ubuntu 14. any of the modern Centos’s should be fine as well.
SVN is the development “bleeding edge” release. It contains some bug fixes that have not been put into the official release, but it also changes daily, and contains code that is less tested and, on rare occasions, it can be incomplete with half implemented features/fixes.
“downgrading” is not really supported at all. you are expected to backup your server before any upgrades so that you can revert to backup if something goes wrong.

image replication for storage servers already exists, though it is designed to replicate all images and is not customizable

unfortunately, any failure in pxe booting typically means no way of logging anything to file or even to screen. often, the best you can hope for is hitting the “pause/break” key at the right moment.

this should not be a problem when you upgrade to the latest svn

here’s a tip to tracking down what line kills it
put a “prompt” after each line, and it will make you hit a key before continuing

the tftp issues with 12.04 are easily worked around with a startup script that makes the tftp service start after a delay on startup.
that said, i run a 12.04 ubuntu server, and have not had to make that modification.

[FONT=Consolas]set boot_url [url]http://${fog-ip}/var/www/html/fog/service/ipxe/[/url][/FONT]
should be
[FONT=Consolas]set boot_url [url]http://${fog-ip}/fog/service/ipxe/[/url][/FONT]
because http://[FONT=Consolas]${fog-ip} resolves to the root of your web server[/FONT]

[FONT=Consolas]your menu doesn’t have a choose statement to tell ipxe to let you choose something[/FONT]

[FONT=Consolas]try this[/FONT]

[CODE]
set boot_url http://${fog-ip}/fog/service/ipxe/
set boot_nfs ${fog-ip}:/images/

:MENU
menu
item Ubuntu12 Ubuntu 12.04 x64 Live
item Ubuntu14 Ubuntu 14.04 x64 Live
item return return to previous menu
choose target && goto ${target}

:Ubuntu12
kernel http://xxx.xxx.xxx.xxx/fog/service/ipxe/ubuntu12/casper/vmlinuz.efi
initrd http://xxx.xxx.xxx.xxx/fog/service/ipxe/ubuntu12/casper/initrd.lz
imgargs boot=casper netboot=nfs nfsroot=xxx.xxx.xxx.xxx:/images/ubuntu12.04/
shell
boot

:Ubuntu14
kernel ${boot_url}/ubuntu/casper/vmlinuz.efi
initrd ${boot_url}/ubuntu/casper/initrd.lz
imgargs boot=casper netboot=nfs nfsroot=xxx.xxx.xxx.xxx:/images/ubuntu14.04/
boot

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

autoboot[/CODE]