Modifying Boot Menu
-
@mbarker Yeah, I would review my config file when you have a chance, but this line jumped out at me right way.
dhcp-boot=undionly.kpxe,,<fog_server_IP>The fog server IP address should appear twice in your config file, you missed this one.
-
I was literally just adding that into my config right now
hold tight (it probably will solve the TFTP server IP prompt too :)) -
Still Kernel panic but no more prompt for a TFTP Server IP
so one thing fixed lolWhen the system loads past the menu I get
bzImage…ok
init.xz…okand then this is where the Kernel Panic happens…it just makes no sense to me
I have my dnsmasq almost identical to your .conf file (I’m on CentOS 6.8…)
Think I should try copying the known working bzimage and xint.xz files and see if that helps?
-
@mbarker Ok the next step is to ensure that we have the proper boot kernels.
https://fogproject.org/inits/init.xz
https://fogproject.org/inits/init_32.xz
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32These links will download the latest (current) kernel and inits. They go in /var/www/html/fog/service/ipxe
Also when ipxe loads there is a version number and a hex number in parentheses, what is that hex number.
Just for clarity what device are you trying to pxe boot into fog? Is it configured for uefi or bios (legacy) mode?
I feel you have the dnsmasq part setup right now so we can rule that out as long as you have your links correct as I have defined them in the tutorial.
-
@george1421
Hey I didn’t run away, just had a conference call to do…the device is a Lenovo T420 laptop with an Intel Series Ethernet Controller (I can’t recall the exact info on it).When i re-loaded the images that you linked now I’m getting a kernel panic before the menu loads…same panic, earlier in the boot sequence.
Since I didn’t change anything for the “mode” I’m assuming it’s Legacy mode…
The TFTP service serves out the boot.php file but then it hangs, tries to get init.xz and bzImage, then throws a Kernel Panic at me -_-
-
@mbarker where is it loading the init from?
Where is it loading the kernel from? Is something passing pxelimux instead of the ipxe files?
-
@Tom-Elliott
It’s loading them from /var/www/html/fog/service/ipxe/Now what’s weird is unregistered hosts get to the menu OK but a registered host doesn’t …however still have the same Kernel Panic I did before…so frustrating lol
edit: figured this out by renaming init.xz, now when I try to get to anything from the menu it fails chainloading that file instead of the Kernel Panic (init.xz IS in my /tftpboot/ folder, but isn’t referenced in any config files to boot from there
-
That’s the issue.
The init’s and kernels should NOT be loading from tftpboot at all.
-
@mbarker Even before Tom posted, my intuition is telling me your FOG install is botched/been tweaked a little too much. I can’t explain why I feel this, but I can’t escape the thought you shouldn’t be having this level of difficulty getting this to work.
My recommendation would be to rename /var/www/html/fog to fog.old and /tftpboot to /tftpboot.old and then go back to the files you downloaded for FOG in the /bin directory and rerun the fog installer. That will put everything back to a known configuration. Once the installer is done then create the two links as I mentioned in my tutorial. Then reboot your fog server. Dnsmasq will still be setup so that part (that works) should be OK.
-
Here’s the process I did with Fog 1.3:
Installed FRESH Centos, updated, installed git, wget, nano, and disabled selinux
Downloaded and installed Fog 1.3
Upgraded PHP from 5.3.3 to PHP 5.5
Created 2 Usernames
Installed and configured dnsmasq
hid a couple of menu items
created an image for the host to image to
booted into the menu, and then ran into kernel panic problems
It is NOT loading from tftpboot at all, as I mentioned it’s loading from /var/www/html/fog/service/ipxe/
Something just tells me this isn’t worth the effort at this point. I really don’t know what to say, I don’t have another full day to waste messing about with this, re-installing Fog just isn’t an option since this will be the 4th time in the last week I’ve done and always ran into problems, so sounds as though I’m looking for another solution
-
@mbarker I understand your logic and decision to look elsewhere. If you decide to circle back to the FOG Project we will be here to help.
Just for my knowledge what hardware are you running the FOG server on. It has no bearing on your results other than I’m interested in the hardware setup.
-
@mbarker
in a normal fog install, there is no init.xz in /tftpboot.
I think that maybe your install is very modified and this is causing some issues…
I know that it would be your thousandth installation, but when you got fog up and running, your effort will have been worthwhile.I was looking for other tools, they exist but are not as productive as this.
