what can i put in boot options on a custom ipxe menu

[robertkwild]

hi all,

i have noticed when i go to

fog configuration > ipxe new menu entry

i have noticed “boot options”

can i add this as a boot option

modprobe.blacklist=nouveau

thanks,
rob

[Sebastian Roth]

@robertkwild Adding such a kernel parameter is better done per host. Check the host’s settings in the web UI and use the field called “Host Kernel Arguments”.

[robertkwild]

@Sebastian-Roth thanks, do you think i could add it in the parameters ie -

kernel http://172.17.1.1/listing/centos7_1804/iso/images/pxeboot/vmlinuz ks=http://172.17.1.1/listing/centos7_1804/ks2.cfg
initrd http://172.17.1.1/listing/centos7_1804/iso/images/pxeboot/initrd.img
modprobe.blacklist=bochs_drm
boot || goto MENU

[Sebastian Roth]

@robertkwild Add, now I see what you mean. Then use:

kernel http://172.17.1.1/listing/centos7_1804/iso/images/pxeboot/vmlinuz modprobe.blacklist=bochs_drm ks=http://172.17.1.1/listing/centos7_1804/ks2.cfg
initrd http://172.17.1.1/listing/centos7_1804/iso/images/pxeboot/initrd.img
boot || goto MENU

That should do what you want (untested).

[robertkwild]

@Sebastian-Roth this is exactly what i mean thanks, i will test it out and get back to you!!!

it works!!!

when i do a “lsmod | grep bochs_drm” i see nothing

[dvorak]

A lot has changed since then. We now use “Parameters” instead of “Boot options”.

My questions is, is it possible to add (or maybe in a future update) commands to the “boot options” that run AFTER pxe finishes loading the iso/files?

The goal is, instead of editing the ISO (everytime I use DISM to edit wimboot, remake the ISO using imgburn it get sanboot errors, but the original unaltered ISO works fine), I could just run 3 simple commands (.bat script) via FOG (boot options?) that run after it boots. For instance, adding the below to be ran after a WinPE iso loads and you get to a desktop:

net use Z: yada yada; Explorer Z:\test.iso;“X:\StartScript.exe”

[Tom Elliott]

@dvorak You’d need it in the ISO.

PXE is before the system is loaded, and as such cannot trigger actions at the HDD level beyond loading a Disk, Boot Rom, or whatever.