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

USB Boot UEFI client into FOG menu (harder way)

Scheduled Pinned Locked Moved
Tutorials
5
35
18.9k
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.
  • G
    george1421 Moderator @Psycholiquid
    last edited by Jan 20, 2016, 4:15 PM

    @Psycholiquid said:

    What I am trying to do is boot from USB pxe because the laptop has no NIC or UEFI is not cooperating like it should.and Wireless wont boot from network. So basically trying to make a live USB drive so I can boot to FOG on machine where there is no nic or the docking station wont show up.

    While this is the intended purpose of the usb boot, dealing with wireless nics is a bit of a pain since the number of models is staggering. I don’t think I included the wireless management code in my how to script. The preference would be to use a usb ethernet nic.

    The issue I see is some how you need to tell the client what SSID to connect to and any security keys required to connect. Unless you create a fully open wireless network just for imaging.

    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
    • T
      Tom Elliott @george1421
      last edited by Jan 20, 2016, 4:17 PM

      @george1421 I don’t think you’re doing anything wrong, but at this point you’re already in ipxe. so why not just use the file with the modified embedded script? you’re already in there. ipxe.efi or ipxe.pxe already have ALL the same drivers ours do. Only difference is the embedded script at that point.

      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

      G 1 Reply Last reply Jan 20, 2016, 4:19 PM Reply Quote 0
      • G
        george1421 Moderator @Tom Elliott
        last edited by Jan 20, 2016, 4:19 PM

        @Tom-Elliott OK great. I just wanted to give the usb booted device just enough to get into the official FOG ipxe.efi kernel. That way if you guys developed new or additional tests this external boot would not have to stay in lock step with your updates.

        BUT, with that said, if there is an easier/better/preferred way to do this, just let me know and I’ll update this document.

        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!

        T 1 Reply Last reply Jan 20, 2016, 4:27 PM Reply Quote 0
        • T
          Tom Elliott @george1421
          last edited by Jan 20, 2016, 4:27 PM

          @george1421 Best way to keep up with updates in that regard, would be, (for your setup at least), instead of booting to ipxe.efi, or some other filename, goto: tftp://FOGIP/default.ipxe.

          THe problem with this approach (though) is it assumes the fogip in the file will always have tftp running. That’s why I recommend using a combination of your scripts and the ipxescript from the src as a part of the embedded script.

          It leads you away from the need to have tftp running, and all the DB style checks can still be made.

          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
          • C
            cnkpadobi
            last edited by Mar 1, 2017, 5:12 PM

            Step Number 6 does not appear under the San boot protocols but under the Http Extension. Is this correct?

            SAN boot protocols:
            SANBOOT_PROTO_ISCSI, iSCSI protocol

            SANBOOT_PROTO_AOE, AoE protocol

            SANBOOT_PROTO_IB_SRP, Infiniband SCSI RDMA protocol

            SANBOOT_PROTO_FCP, Fibre Channel protocol

            SANBOOT_PROTO_HTTP, HTTP SAN protocol

            HTTP extensions:
            HTTP_AUTH_BASIC, Basic authentication

            HTTP_AUTH_DIGEST, Digest authentication

            HTTP_ENC_PEERDIST, PeerDist content encoding

            HTTP_HACK_GCE, Google Compute Engine hacks

            G C 2 Replies Last reply Mar 1, 2017, 5:15 PM Reply Quote 0
            • G
              george1421 Moderator @cnkpadobi
              last edited by Mar 1, 2017, 5:15 PM

              @cnkpadobi Just be aware that this document was created over a year ago so some of the menu/values on the rom-o-matic site may have moved. But from memory I would say that the HTTP Extensions is the right location now.

              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
              • C
                cnkpadobi
                last edited by Mar 1, 2017, 5:35 PM

                Thank you, was wondering why I am getting this message.

                Thanks0_1488389723743_rsz_20170301_092141.jpg

                G 1 Reply Last reply Mar 1, 2017, 5:37 PM Reply Quote 0
                • G
                  george1421 Moderator @cnkpadobi
                  last edited by george1421 Mar 1, 2017, 11:51 AM Mar 1, 2017, 5:37 PM

                  @cnkpadobi This may not be an issue with the iPXE kernel settings specifically. I would test this pxe boot stick on a computer that does work with pxe booting today. The idea here is that there is a potential that the iPXE kernel may not have the required driver for this usb network adapter.

                  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!

                  C 1 Reply Last reply Mar 1, 2017, 8:49 PM Reply Quote 0
                  • C
                    cnkpadobi @george1421
                    last edited by Mar 1, 2017, 8:49 PM

                    @george1421 Hmm that make sense is there a way to get a list of compatible USB adapter

                    1 Reply Last reply Reply Quote 0
                    • C
                      cnkpadobi @cnkpadobi
                      last edited by Mar 1, 2017, 11:18 PM

                      @george1421 0_1488410321600_rsz_pic3.jpg Here is the pic from the FOS USB

                      G 1 Reply Last reply Mar 1, 2017, 11:20 PM Reply Quote 0
                      • G
                        george1421 Moderator @cnkpadobi
                        last edited by Mar 1, 2017, 11:20 PM

                        @cnkpadobi I just rebuilt that image file and will test it tonight to see if something changed.

                        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!

                        C 1 Reply Last reply Mar 2, 2017, 6:15 PM Reply Quote 0
                        • C
                          cnkpadobi @george1421
                          last edited by Mar 2, 2017, 6:15 PM

                          @george1421 Thank you

                          C 1 Reply Last reply Mar 2, 2017, 8:15 PM Reply Quote 0
                          • C
                            cnkpadobi @cnkpadobi
                            last edited by Mar 2, 2017, 8:15 PM

                            @cnkpadobi Here is the new error0_1488485699885_rsz_20170302_111551.jpg

                            1 Reply Last reply Reply Quote 0
                            • C
                              cnkpadobi
                              last edited by Mar 8, 2017, 12:41 AM

                              @george1421 here is the error2_1488933685695_rsz_20170307_163040.jpg 1_1488933685695_rsz_20170307_163050.jpg 0_1488933685693_rsz_20170307_163106.jpg

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

                              205

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project