• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved
    General
    4
    7
    764
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      robertkwild
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @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”.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        R 1 Reply Last reply Reply Quote 1
        • R
          robertkwild @Sebastian Roth
          last edited by

          @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

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @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).

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            R 1 Reply Last reply Reply Quote 1
            • R
              robertkwild @Sebastian Roth
              last edited by 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

              1 Reply Last reply Reply Quote 0
              • D
                dvorak
                last edited by

                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 ElliottT 1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott @dvorak
                  last edited by

                  @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.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • First post
                    Last post

                  189

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project