Log Files Boot Operation
it’s possible enable a Log Files when Boot from LAN Start ?
I need to solve the “Hang” on different hardware …
IPXE Boot write the operation on Files ? ( for example when initialize devices … )
@ZINGARO1972 Sure you can move files around in /tftpboot. That’s one way of doing it. Or you can use symbolic links. Or change the filename in your DHCP configuration. Moving files or using symbolic links you might overwrite files if you don’t pay full attention. So I’d prefer to change DHCP config.
I guess you installed FOG with DHCP. Then edit /etc/dhcp/dhcpd.conf and simply change the filename there. After saving the file you only need to restart the DHCP service:
service isc-dhcp-server restart
I have the last version (1.2 ) of Fog
Thanks for your information:
now are these files in tftpboot directory:
-rw-r–r-- 1 fog root 840 mar 12 2015 boot.txt
-rw-r–r-- 1 fog root 389009 mar 12 2015 ipxe.kkpxe
-rw-r–r-- 1 fog root 389057 mar 12 2015 ipxe.kpxe
-rw-r–r-- 1 fog root 388044 mar 12 2015 ipxe.krn
-rw-r–r-- 1 fog root 389073 mar 12 2015 ipxe.pxe
-rw-r–r-- 1 fog root 25340 mar 12 2015 memdisk
-rw-r–r-- 1 fog root 16794 mar 12 2015 pxelinux.0.old
-rw-r–r-- 1 fog root 165088 mar 12 2015 snponly.efi
-rw-r–r-- 1 fog root 101989 mar 12 2015 undionly.kkpxe
-rw-r–r-- 1 fog root 102037 mar 12 2015 undionly.kpxe.SAV
-rw-r–r-- 1 fog root 382650 mar 12 2015 undionly.kpxe
-rw-r–r-- 1 fog root 102053 mar 12 2015 undionly.pxe
-rw-r–r-- 1 fog root 147728 mar 12 2015 vesamenu.c32
-rw-r–r-- 1 root root 295 mar 12 2015 default.ipxe
lrwxrwxrwx 1 root root 13 mar 12 2015 undionly.0 -> undionly.kpxe
for test I have saved the original undionly.kpxe in undionly.kpxe.SAV ,
and rename undionly.INTEL to undioly.kpxe
for try undionly.kkpxe I can rename the actual undionly.kpxe into undionly.INTEL (original name )
and move undionly.kkpxe into undionly.kpxe
It’s correct ??
And to answer your question about log files. There aren’t any in this early stage of (network) booting! To find out what exactly goes wrong you need to compile your own iPXE binaries with DEBUG enabled. If you are keen enough to get into this, let us know and we can point you a way on how to do this.
Tom is absolutely right about you should try undionly.kkpxe and see if it works on those machines!
First, and always, what version of FOG are you hitting into the issues with? I can’t help if I don’t know. Even that said, there are multiple files in the /tftpboot directory that you could use.
Hanging is usually indicative of the client harder having some issue or other, most often, dealing with the firmware of the BIOS. For those cases, I’d recommend using the undionly.kkpxe file over the undionly.kpxe file. What’s great about that approach, is anything that works perfectly with undionly.kpxe will typically work the same with undionly.kkpxe and then some.