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

    Host EFI Exit Type - Refind EFI

    FOG Problems
    2
    6
    239
    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.
    • F
      Florent last edited by

      Hi,
      What “Host EFI Exit Type - Refind EFI” exactly doing ?
      I have a weird behavior here. If computers boot on pxe with no fog image task and with “Host EFI Exit Type - Refind EFI”, Bitlocker always ask me the recovery key.
      My problem is the other options of “Host EFI Exit Type” does’nt work for me because show error chainloading and reboot after 10 seconds.

      Have you an idea ?

      Florent
      Bretagne, FRANCE

      george1421 1 Reply Last reply Reply Quote 0
      • F
        Florent @george1421 last edited by Florent

        @george1421 Yes i already try this. Works fine but already my problem with Bitlocker.
        Actually my problem is our computers are configure to boot on pxe when receive wake on lan.
        And Bitlocker ask recovery key if order boot has changed.
        But i notice if i reboot “normally” even after that, Bitlocker don’t ask recovery key Bitlocker.
        My problem is for our computers “Refind EFI” is the only mode who work with pxe. If i use other option, i have an error like “Chainloading failed”.
        This is why i was thinking to have a “reboot” mode, because i don’t find how to make it work the “Exit” mode

        Florent
        Bretagne, FRANCE

        1 Reply Last reply Reply Quote 0
        • george1421
          george1421 Moderator @Florent last edited by

          @florent Is it possible to add a Reboot exit mode? Yes. You will need to make some adjustments to the FOG php code to add this feature.

          Before you do that I want you to try something. I see that refind has updated its program. I think the last version that ships with FOG is 0.11.4, I see that refind has 0.13.3.1. I would like to see you try a later version of refind, maybe it has fixes to in it to resolve your problem.

          https://sourceforge.net/projects/refind/files/0.13.3.1/

          download refind-bin-0.13.3.1.zip In the zip file in this directory refind-bin-0.13.3.1.zip extract refind_x64.efi and refind_ia32.efi

          Move these to the FOG server in /var/www/html/fog/service/ipxe directory. But before you move them rename the original files in case the new files do something that breaks exit modes with FOG. Lets see how / if the new version of refind manages the new hardware.

          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!

          F 1 Reply Last reply Reply Quote 0
          • F
            Florent @george1421 last edited by

            @george1421 Do you think it’s possible to have an option “Reboot” ? Where i can set this to try ?

            Florent
            Bretagne, FRANCE

            george1421 1 Reply Last reply Reply Quote 0
            • F
              Florent @george1421 last edited by

              @george1421 Yes if i change boot order and set hard drive first it’s okay.
              Do the problems for many models HP & Dell.
              On a model I try to set exit type to “Exit” it works, but do you think it will work same on all ?
              On other model with “Exit” option if i have not active tasks it stay on “chainloading failed” and reboot after 10 seconds.

              Florent
              Bretagne, FRANCE

              1 Reply Last reply Reply Quote 0
              • george1421
                george1421 Moderator @Florent last edited by

                @florent rEFInd should not mess with bitlocker at all (at least what I’ve seen). I have seen computers trigger bitlocker on themselves for no apparent reason.

                So if you change the boot order to hard drive first does the device function normally?

                Is it just one model of computer doing this or all models of computers that boot through FOG?

                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!

                F 2 Replies Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post

                197
                Online

                10.4k
                Users

                16.4k
                Topics

                150.5k
                Posts

                Copyright © 2012-2023 FOG Project