Posts made by Junkhacker

the PXE boot menu configuration page allows you to choose how long the menu shows up

Tom, do you think it would be a good idea to change that line from [CODE]sanboot --no-describe --drive 0x80 || goto MENU[/CODE] to [CODE]sanboot --no-describe --drive 0x80 || exit[/CODE] or would that not work, since it sounds like it may lock up on the first bit

a bit of research says that this is likely a hardware/firmware specific bug that occurs a lot on HP machines

i’m not sure why it is failing to boot to the hard drive of the computer after ipxe loads, but fog appears to be working properly. I would actually be willing to bet that if you took an image of the computer, then imaged it again with fog, it would work fine when not pxe booting. fog is typically used on windows clients, but many people have it working on linux as well.

i mean on the client that is pxe booting, not the server

SAN device 0x80 is the local hard disk. is there a valid OS on the drive?

i recommend setting 66=10.0.1.40 on your DHCP server, so there isn’t any question if it’s resolving the hostname

I think it would be a very handy to have additional information available in the “hosts” list view and search. Additional information about hosts is saved in the “inventory” table that could be very useful. my suggestion is to have a checklist of these fields available on the configuration page that would enable their listing in the “hosts” listing and search results pages.

i found a tutorial for ipxe with DNSMasq [url]http://www.heath-bar.com/blog/?p=326[/url]
looks like it could give you some ideas on what’s wrong

UPS systems are very efficient. 99.9% of the time all they’re doing is monitoring power and keeping the batteries topped off, so they don’t take much power. they shouldn’t affect your energy bill, really. the best thing about them is that you can have your systems go into a proper shutdown sequence when the power goes out, instead of just dying. they’re also great for stabilizing your power if you live in an area subject to brownouts or quick drops in power caused by high wind or everyone turning on their AC at the same time.

The tftp command is not available by default in Windows 7 but can be enabled by turning on the [I]TFTP Client[/I] Windows feature from Programs and Features in Control Panel.
tftp will also be blocked by default by the windows firewall

the undionly.kpxe is made to automatically look for the file default.ipxe in the same directory as itself. for some reason i don’t think it could find it, and that’s why it wasn’t working for you.

well, i know that i’ve had chainloading working from pxelinux.0 with the ipxe.krn one with the following in the pxelinux.cfg/default file
[CODE]DEFAULT vesamenu.c32
LABEL fog
MENU DEFAULT
kernel ipxe.krn dhcp && chain http://(fog-server-ip-address)/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 01
[/CODE]

i don’t have any experience with DNSMasq but i’ll help with what i can. when you tried chainloading from pxelinux.0, what ipxe file did you direct it to. ipxe.krn or undionly.kpxe?

a quick search of the ipxe org website says that DNSMasq needs special configuration to work directly with ipxe. have you tried the advice on this thread? [url]http://forum.ipxe[/url] .org/showthread.php?tid=6077

makes sense to me. thanks

advanced menu stopped working. looks like it happened when code was moved from base.inc.php to BootMenuClass.php
changing advanced.php code from
[CODE]<?php
header(“Content-type: text/plain”);
require_once(‘…/…/commons/base.inc.php’);
print “#!ipxe\n”;
print $advanced;
?>
[/CODE] to
[CODE]<?php
header(“Content-type: text/plain”);
require_once(‘…/…/commons/base.inc.php’);
$advanced = $FOGCore->getSetting(‘FOG_PXE_ADVANCED’);
print “#!ipxe\n”;
print $advanced;
?>
[/CODE] makes it work again

not just “look” how you want it to. act how you want it to as well. with a proper hooking system, plugins will be able to modify core functionality without being hard-coded into the files.

depending on what exactly you’re doing with those manually created pxelinux config files and how much they interact with fog, at this point there is nothing stopping you from keeping doing what you’re currently doing. just keep using pxelinux and your 01-XX-XX-XX-XX-XX-XX files, but in your default file chainload to undionly.kpxe