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

    Lenovo N22 USB EFI boot

    Scheduled Pinned Locked Moved Solved
    Hardware Compatibility
    4
    9
    7.6k
    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.
    • M
      monasmith529
      last edited by

      Running Fog Trunk 7248

      I am trying to boot a lenovo N22 to get an image. This computer does not have a NIC, so I am using a usb 2.0 adapter.

      I used https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media to create the drive. It boots to the fog menu, however when I try to register the host, I receive the attached error. 0_1463153775680_IMG_9383.jpg

      The USB drive works if I efi boot from a machine with a built in nic.

      Anyone else experience this error?

      1 Reply Last reply Reply Quote 0
      • Scott AdamsS
        Scott Adams
        last edited by

        You could try a couple of different things here.

        1. In your kernel parameters under FOG Configuration -> FOG Settings -> General Settings, enter a value of “has_usb_nic=1”
          minus the quotes

        2. On your DCHP server, change your boot file to an efi file, which is compatible with the UEFI bios of the Lenovo. I typically use snponly.efi, but have had success with ipxe.efi as well.

        If everything is successful, you could then create a group for this model device and put in the kernel parameters in the group. Add these devices to the group, then they will always have the parameter applied.

        You don’t want to leave the parameter set (from option 1). This will cause other devices to not be able to image.

        1 Reply Last reply Reply Quote 0
        • Scott AdamsS
          Scott Adams
          last edited by

          Also, within the Lenovo BIOS, you may want to see if Secure Boot is enabled. If so, you want to disable it.

          S 1 Reply Last reply Reply Quote 2
          • george1421G
            george1421 Moderator
            last edited by

            Just thinking out loud here.

            You booted via uefi usb stick into iPXE.
            iPXE was able to pick up an IP address from dhcp on that usb 2.0 network adapter (assuming so since it downloaded bzImage).
            I see that bzImage (the kernel) transferred OK, but there isn’t any reference to the init.xz (the virtual hard drive) being transferred to the iPXE kernel.
            Now we see basically it couldn’t execute the bzImage.

            Right now you are at the stage where iPXE appears to transfer the images to iPXE but it can’t boot the FOS client OS (the software that deploys or uploads the images to the target computer).

            I the bzImage. I think Scott Adams is right you should check the secure boot setting. If you can switch that device into legacy mode you might be better off.

            If uefi is your only choice, I might recommend that you find a supported usb 3.0 network adapter that supports PXE booting on that Lenovo. The Lenovo uefi firmware must support the usb 3.0 device or pxe booting is not supported.

            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!

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

              @Scott-Adams said:

              Also, within the Lenovo BIOS, you may want to see if Secure Boot is enabled. If so, you want to disable it.

              Scott is absolutely right. But I guess what we have here is the Lenovo extra security chip issue. Read this (yes the whole lot!). I nearly ripped my hair out trying to find that… damn (sorry for that).

              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

              M 1 Reply Last reply Reply Quote 1
              • M
                monasmith529 @Sebastian Roth
                last edited by

                @Sebastian-Roth @Scott-Adams . Thanks for the reply and Sorry I am just not getting time to check and do some troubleshooting. I have disabled the security chip in the bios but that has not changed anything. I have not been able to try a usb3.0 pxe device, because my lenovo rep told me they will not work, hence the reason I bought the 2.0 device.

                Any other suggestions?

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

                  @monasmith529 Please take a picture of the BIOS setting for the security chip you disabled and a picture of the error you see (if it’s not exactly the same as in the original pic)!

                  I’ve put in a couple of days work to get this other thread solved. Talked to the iPXE devs, compiled debug enabled binaries, added signature enabled binaries and all that just to find out that this was not a software issue. So please understand that I am not very fond of digging into this from the FOG/iPXE side yet. The error is exactly the same as in the other post and I wonder if it’s just some kind of TPM/security chip issue again. Please double check all the settings and read through the other thread (the whole lot). Try the suggestions (e.g. debug enabled ipxe.efi binary) I posted there to see if you get all the same error messages.

                  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
                  • george1421G
                    george1421 Moderator
                    last edited by

                    [housekeepeing] Moving thread to the hardware section. This is not a windows issue (yet) [/housekeeping]

                    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!

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      monasmith529 @george1421
                      last edited by

                      @george1421 @Sebastian-Roth You can mark this as solved. Since this was a loaner unit from Lenovo, they locked down the bios so I could not fully disable the security chip. Once I changed the bios I was able to disable the chip and image the laptop 🙂

                      Thanks for you help

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

                      216

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project