Boot menu and Kernel panic

[Tom Elliott]

I didn’t even see that, but I have now added the init=/sbin/init to the kernel args list for kernel bootup in an attempt to hopefully ensure we always use the proper file.

[ch3i]

@Sebastian-Roth OK it’s solved my problem for the kernel panic. Menu always bugged

[Tom Elliott]

@ch3i Do you have anything in the apache error logs when you try to load the boot menu?

[ch3i]

@Tom-Elliott Hi Tom, I’ve nothing in error.log

[Sebastian Roth]

@ch3i Please try accessing the bootmenu URL from a browser and see what you get: http://ip.or.fog.srv/fog/service/ipxe/boot.php

[ch3i]

@Sebastian-Roth said:

http://ip.or.fog.srv/fog/service/ipxe/boot.php

#!ipxe
set fog-ip 172.20.0.4
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 && colour --rgb 0x00567a 2 && colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 && cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://172.20.0.4/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.quickimage Quick Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.20.0.4/fog/ consoleblank=0 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.20.0.4/fog/ consoleblank=0 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.quickimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.20.0.4/fog/ consoleblank=0 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://172.20.0.4/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

[Sebastian Roth]

Interesting as :fog.reginput and :fog.reg are available but not listed as an item in the menu section… Are you sure you don’t have any related messages in your apache error log??

[ch3i]

@Sebastian-Roth

No error, but can’t post the log >> Antispam xD

[Sebastian Roth]

Looking at the source code I think I found the “issue”. Didn’t know that there is a new option called FOG_REGISTRATION_ENABLED in FOG Settings… Check the settings in your web interface…

[ch3i]

@Sebastian-Roth said:

Looking at the source code I think I found the “issue”. Didn’t know that there is a new option called FOG_REGISTRATION_ENABLED in FOG Settings… Check the settings in your web interface…

\o/ Solved ! Thx

[Tom Elliott]

@ch3i Believe it or not, this option isn’t really new. It’s been there for a while.

It’s what enables registering or not, so you have control over whether or not you want to allow systems to register. It’s kind of a security feature.

[ch3i]

@Tom-Elliott Hi Tom, I’ve updated my old server during few month, and never seen that option. I’m on a fresh install, and I’ve not checked that