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

Surface Pro 3 - ipxe issues

Scheduled Pinned Locked Moved Solved
Hardware Compatibility
6
32
11.7k
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 @xerxes2985
    last edited by Nov 16, 2016, 7:59 PM

    @xerxes2985 You have the proper setup now. Adding filters (if you need them) is just a short walk from there. There is two ways you can go with the config file, easy and a little harder. But the little harder gives you many more options.

    The wiki page you referenced is based on my working document here: https://forums.fogproject.org/topic/8726/advanced-dnsmasq-techniques

    which goes into the details a bit more.

    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 @xerxes2985
      last edited by Nov 17, 2016, 12:18 AM

      @xerxes2985 is it possible it’s looping back because it’s looking for snponly.efi.0?

      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
      • W
        Wayne Workman @george1421
        last edited by Wayne Workman Nov 16, 2016, 6:22 PM Nov 17, 2016, 12:21 AM

        @george1421

        PXEClient:Arch:00007:UNDI:003016

        Either one of two things here…

        Either this is not a Surface 3 but is actually a Surface 4, or, all Surface Pros have the exact same vendor class identifier.

        Why do I say this? That vendor class identifier is exactly what we found for a Surface Pro 4 and integrated into FOG’s built-in DHCP configuration:
        https://github.com/FOGProject/fogproject/blob/dev-branch/lib/common/functions.sh#L2020

        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!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        T G 2 Replies Last reply Nov 17, 2016, 12:25 AM Reply Quote 0
        • T
          Tom Elliott @Wayne Workman
          last edited by Nov 17, 2016, 12:25 AM

          @Wayne-Workman I only say that because he’s using Dnsmasq (.0). I’m not sure if Dnsmasq still looks for .0 regardless of what the filename actually is.

          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

          W 1 Reply Last reply Nov 17, 2016, 12:27 AM Reply Quote 0
          • W
            Wayne Workman @Tom Elliott
            last edited by Nov 17, 2016, 12:27 AM

            @Tom-Elliott Simon Kelly did away with the .0 thing in the version we instruct people to build I believe, mostly because it made .0 sense

            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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • T
              Tom Elliott
              last edited by Nov 17, 2016, 12:30 AM

              So now that you have a working system, is it safe to solve this thread?

              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
              • G
                george1421 Moderator @Wayne Workman
                last edited by george1421 Nov 16, 2016, 6:36 PM Nov 17, 2016, 12:34 AM

                @Wayne-Workman said in Surface Pro 3 - ipxe issues:

                PXEClient:Arch:00007:UNDI:003016

                This really doesn’t tell you anything useful in regards to uniqueness.
                There is actually 4 parts there in that option 60 value. Those values are also present in other dhcp options like 93, 94, and I think 97 (as said from a faulty memory).
                the undi part on the end is the undi version 003 and I forget what the 016 is but its not unique. But in the case of this surface pro the uuid file is unique. That just needs to have a filter created for the uuid part and to exclude the sid part.

                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!

                W 1 Reply Last reply Nov 17, 2016, 12:40 AM Reply Quote 0
                • W
                  Wayne Workman @george1421
                  last edited by Nov 17, 2016, 12:40 AM

                  @george1421 the UUID is unique per device though. We were trying to find something unique to the surface pro because FOG’s latest boot files won’t work with them for whatever reason, and none of us have a Surface Pro to even begin to figure out what’s wrong.

                  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!
                  Daily Clean Installation Results:
                  https://fogtesting.fogproject.us/
                  FOG Reporting:
                  https://fog-external-reporting-results.fogproject.us/

                  G 1 Reply Last reply Nov 17, 2016, 12:47 AM Reply Quote 0
                  • G
                    george1421 Moderator @Wayne Workman
                    last edited by george1421 Nov 16, 2016, 6:47 PM Nov 17, 2016, 12:47 AM

                    @Wayne-Workman The issue/trouble is the UUID entry is up to the device manufacturer to populate. Dell does it, Microsoft must do it, Lenovo and ASUS not so much (at least with the testing I’ve see so far).

                    In the case of the dells there are two parts to the UUID the system ID that identifies the hardware and the right part that is the mac address of the computer (computer unique part). For the surface pro it doesn’t look like MS followed that when creating the UUID. What we would need to do is capture 2 discover packets from two different surface pros of the same model and compare the uuid part to see where the unique system ID is. I would expect the left part of the UUID to be system model consistent and the right part to be device unique part. But I’m only guessing here. MS may have done something totally different.

                    That is why we need the support of the people who have surface pros to collect this data for use so we can make the FOG system even better that it is today. As I posted before I’m sure the developers would gladly accept a donated surface pro 4 to help clean up a bit of theses still unknowns.

                    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 1
                    • S
                      Scott Adams @george1421
                      last edited by Nov 17, 2016, 1:43 PM

                      @george1421 I will work on getting something together and post it once complete.

                      In the meantime, I use Windows DHCP service (not FOG’s DHCP). I simply set my 66 and 67 scope options to my fog server and to snponly.efi ( I still have to manually change this setting as my DHCP server is 2008).

                      I use the actual Microsoft Surface USB Ethernet adapter. I used to have to add has_usb_nic=1, but that was not needed after a particular RC (I can’t remember which one).

                      Also as part of the imaging, I do have an issue with using the Type Cover. I can use it in the FOG menu, but when it wants me to disconnect the NIC, plug it back in, and hit Enter, it will not recognize any input from the Type Cover. I simple plug in a USB keyboard, hit enter, then plug my Ethernet adapter back in.

                      1 Reply Last reply Reply Quote 1
                      • X
                        xerxes2985
                        last edited by Nov 17, 2016, 2:29 PM

                        @Tom-Elliott @george1421 @Wayne-Workman @Scott-Adams

                        First, I can assure you its a Surface Pro 3. Unfortunately, its the only one I have at the moment so I cannot verify whether multiple SP3 share the same vendor class. (although I am guessing they may)

                        PXEClient:Arch:00007:UNDI:003016

                        The other question in regards to changing to snponly.efi, it could have been I wasn’t pointing the BC_EFI entry.

                        Correct entry

                        pxe-service=BC_EFI, "Boot UEFI PXE-BC", ipxe7156.efi
                        

                        Wrong architecture entry

                        pxe-service=X86-64_EFI, "Boot Surface UEFI" snponly.efi
                        

                        Tom, to answer your question, yes I believe you can mark this as solved.

                        Thanks for all your help.

                        G 1 Reply Last reply Nov 17, 2016, 2:42 PM Reply Quote 0
                        • G
                          george1421 Moderator @xerxes2985
                          last edited by Nov 17, 2016, 2:42 PM

                          @xerxes2985 just for reference I’ve started documenting this solution here: https://forums.fogproject.org/topic/8971/pxe-booting-surface-pro-3-to-fog-menu

                          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
                          • 1
                          • 2
                          • 2 / 2
                          2 / 2
                          • First post
                            32/32
                            Last post

                          220

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project