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

Surface Pro 4

Scheduled Pinned Locked Moved
FOG Problems
4
13
3.5k
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
    fry_p Moderator
    last edited by Apr 10, 2017, 5:24 PM

    Hi Everyone,
    I am unable to get a Surface pro 4 to quick image. I have the UEFI co-existence set up on my DHCP server. I am running 1.3.5. I am using a Microsoft model 1663 usb to ethernet dongle to connect. I have used a powered USB hub as well to no avail. Please see the below picture. I am able to get to the fog menu but it fails at this point.
    0_1491844992340_unnamed.jpg

    Note: I have successfully imaged surfaces in the past with the same setup. Kernel is latest

    Thanks

    Like open source community computing? Why not do it for a good cause?
    Use your computer/server for humanitarian projects when it is idle!
    https://join.worldcommunitygrid.org?recruiterId=1026912

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Apr 10, 2017, 5:57 PM

      What boot file are you using? Are you using ipxe7156.efi? This is the only file, that I’m aware of, that consistently works with these Surface machines. As far as network not working, I don’t know about that. Maybe, if you can, try another usb port? Also would you mind telling the VERSION of the kernel? “The latest” is in regards to what’s currently available? I just pushed up 4.10.9 so I’m “assuming” this is the version you’re referring to. I might also ask if you can try the RC versions of FOG. The fact that “Failed to get an IP via DHCP! Tried on interface(s):” shows that the system isn’t detecting a single nic to use. It also appears to show that there is NO nic to use. You pair that with the error message (Cannot enable. Maybe the USB cable is bad?) (This is not my message btw), seems to point to the device being unrecognized.

      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

      F 2 Replies Last reply Apr 10, 2017, 6:00 PM Reply Quote 0
      • F
        fry_p Moderator @Tom Elliott
        last edited by Apr 10, 2017, 6:00 PM

        @Tom-Elliott Sorry the kernel is 4.10.1. In my DHCP policy, the 7156 is the file it points to. I can move to RC and try. I have an different upload running so I’ll try the RC in a bit.

        Like open source community computing? Why not do it for a good cause?
        Use your computer/server for humanitarian projects when it is idle!
        https://join.worldcommunitygrid.org?recruiterId=1026912

        T 1 Reply Last reply Apr 10, 2017, 6:01 PM Reply Quote 0
        • T
          Tom Elliott @fry_p
          last edited by Apr 10, 2017, 6:01 PM

          @fry_p Roger, thank you.

          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

          F 2 Replies Last reply Apr 10, 2017, 6:01 PM Reply Quote 0
          • F
            fry_p Moderator @Tom Elliott
            last edited by Apr 10, 2017, 6:01 PM

            @Tom-Elliott oops i mean 4.10.9

            Like open source community computing? Why not do it for a good cause?
            Use your computer/server for humanitarian projects when it is idle!
            https://join.worldcommunitygrid.org?recruiterId=1026912

            1 Reply Last reply Reply Quote 0
            • F
              fry_p Moderator @Tom Elliott
              last edited by Apr 10, 2017, 6:42 PM

              @Tom-Elliott Just got to 1.4.0 RC4, still no luck. I tested the USB nic on an already imaged surface for plain connectivity and it worked for that. I tried to image a Pro 3 with the dongle and the same issue. Please let me know what info you need from me.

              Like open source community computing? Why not do it for a good cause?
              Use your computer/server for humanitarian projects when it is idle!
              https://join.worldcommunitygrid.org?recruiterId=1026912

              1 Reply Last reply Reply Quote 0
              • F
                fry_p Moderator @Tom Elliott
                last edited by fry_p Apr 11, 2017, 7:24 AM Apr 11, 2017, 1:20 PM

                @Tom-Elliott I followed the exact steps in the highlighted in the solution post on this thread to no avail: https://forums.fogproject.org/topic/9704/surface-3-unable-to-obtain-dhcp/22

                It almost appears that it is looking at the wrong interface. Is there a way to specify the interface in fog? It is looking at USB0 but when I unplug the dongle, it states USB2-port1 is the one being pulled.

                EDIT: Just noticed i triple posted, sorry. I am just eager to get this working. It is the superintendent’s surface that needs an image, go figure.

                Like open source community computing? Why not do it for a good cause?
                Use your computer/server for humanitarian projects when it is idle!
                https://join.worldcommunitygrid.org?recruiterId=1026912

                W 1 Reply Last reply Apr 11, 2017, 10:43 PM Reply Quote 0
                • W
                  Wayne Workman @fry_p
                  last edited by Wayne Workman Apr 11, 2017, 4:43 PM Apr 11, 2017, 10:43 PM

                  @fry_p Here are the better threads on the Surface Pro topic: https://wiki.fogproject.org/wiki/index.php?title=Surface_Pro

                  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
                  • D
                    dylan123
                    last edited by Apr 11, 2017, 11:16 PM

                    Out of interest Fry, looking at the image you’ve attached in the OP, is your surface still attached to the docking station as the charger looks like the fat one for the docking station rather then just the power lead which is much thinner? Just curious as to whether having that disconnected makes any difference as it might be trying to read the docking station USB interfaces instead o the one directly connected to the surface?

                    F 1 Reply Last reply Apr 12, 2017, 11:36 AM Reply Quote 1
                    • F
                      fry_p Moderator @dylan123
                      last edited by fry_p Apr 12, 2017, 8:00 AM Apr 12, 2017, 11:36 AM

                      @dylan123 Brilliant suggestion, I didn’t think of that. Unfortunately, with the dock disconnected, we have the same result. I have also tried using the nic on the dock. I have tried a powered usb hub as well. I get the “Failed to get an IP via DHCP” message immediately if I have the usb nic directly connected. In the hub, it waits 35 seconds before the message pops up.

                      EDIT: I think I figured it out. I failed to realize that my powered USB hub has its own nic. I gather that it is switching the interface to that once it gets to the screen I am having trouble with. My first test, I let it pxe boot and when it got to the “Sleeping for 5 seconds” part, I quickly swapped the ethernet from the microsoft dongle to the USB hub port. It imaged perfectly. My second test is to hook up network to both the USB hub and the dongle going into the USB hub, and I had no trouble. I guess it is “switching” from the microsoft dongle MAC to the USB hub MAC when it hits this stage. I will try to get a powered usb hub (tried non powered to no avail) sans the nic. I am just curious why the stupid dongle by itself can’t pull an ip at that stage.

                      Like open source community computing? Why not do it for a good cause?
                      Use your computer/server for humanitarian projects when it is idle!
                      https://join.worldcommunitygrid.org?recruiterId=1026912

                      D 1 Reply Last reply Apr 12, 2017, 10:48 PM Reply Quote 0
                      • D
                        dylan123 @fry_p
                        last edited by Apr 12, 2017, 10:48 PM

                        @fry_p So if I’m understanding correctly, you’ve got your Surface with a USB hub directly connected to that. From that you’ve plugged in your surface adapter to one of those ports? Kind of makes sense with it struggling given it’s trying to get the IP from the other adapter.

                        I think to get this working together you’d want turn your surface on with the USB hub connected. CMD > getmac to figure out the mac address for both the HUB ethernet and the surface adapter. Then you can open up the fog dashboard, create a new host, manually add both mac addresses (making the surface adapter the primary one). Then under the FOG_KERNEL_ARGS section, add has_usb_nic=1. I imagine the next time you try to image it with all of that connected it should work.

                        With all of that said, do you really need to use the USB hub? Can you not just plug the surface usb > Ethernet adapter in directly? I haven’t done a full test with my 4 yet, but I know with the 3, the surface keyboard worked fine plugged in so I didn’t really have any need for the usb hub.

                        W F 2 Replies Last reply Apr 13, 2017, 12:02 AM Reply Quote 1
                        • W
                          Wayne Workman @dylan123
                          last edited by Apr 13, 2017, 12:02 AM

                          @dylan123 said in Surface Pro 4:

                          the surface keyboard worked fine plugged in so I didn’t really have any need for the usb hub.

                          The keyboard working for the surface 3 is a new thing in Linux, a year ago I don’t think the kernel supported it. A lot of people just don’t know it is working 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!
                          Daily Clean Installation Results:
                          https://fogtesting.fogproject.us/
                          FOG Reporting:
                          https://fog-external-reporting-results.fogproject.us/

                          1 Reply Last reply Reply Quote 0
                          • F
                            fry_p Moderator @dylan123
                            last edited by Apr 13, 2017, 2:07 PM

                            @dylan123 As stated earlier, I got an instant “Failed to get IP via DHCP” error when I had just the dongle plugged directly in. I also am already using the “has_usb_nic=1” argument. Lastly. I have both the dongle MAC and the USB hub MAC listed in the host.

                            Like open source community computing? Why not do it for a good cause?
                            Use your computer/server for humanitarian projects when it is idle!
                            https://join.worldcommunitygrid.org?recruiterId=1026912

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

                            191

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project