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

    Surface Pro 4 with new Dock, no PXE boot

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    4
    530
    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.
    • S
      svalding
      last edited by

      So I’ve got a weird one. It seems that FOS doesn’t see the NIC on a Surface Pro 4 using:
      Fog Server Version 1.5.4
      bzImage details:

      file bzImage
      bzImage: Linux kernel x86 boot executable bzImage, version 4.10.10 (root@debian64) #1 SMP Sat Apr 15 13:21:35 EDT 2017, RO-rootFS, swap_dev 0x7, Normal VGA
      

      SP4 updated to latest firmware.

      Any suggestions?

      Running udhcpc from within FOS just kinda sits there sending discovers, eventually gives up. Where are the logs located that would help track down this issue? I didn’t see anything interesting in /var/log while booted into FOS

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • Wayne WorkmanW
        Wayne Workman @svalding
        last edited by

        @svalding Read through these: 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
        • S
          svalding
          last edited by

          I tried with a different dock, and everything worked without any issues whatsoever. It was the same “style” of dock (the new brick style ones). Not sure if a chipset changed inside them or what, but that did the trick for this issue.

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

            @svalding What would be interesting to know is what is different between the two docks.

            Please do the following

            1. Schedule a debug deploy/capture (tick the check box for debug before you submit the task) for the nic of the working dock. It doesn’t matter if its a capture or deploy because we are not going to do either.
            2. PXE boot the target computer, after FOS boots you should see several screens of text press enter a few times until you get to the linux command prompt.
            3. Key in
              lspci -nn | grep etwork
            4. Record what you see there for the network adapter. The hex codes are important.
            5. Repeat the same process with the non-working dock. You may get warning messages about not able to access the network, but it still should allow you to get to the linux command prompt.
            6. Collect the output of the lspci command from above.
            7. Please post the output of those two systems in 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!

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

            210

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project