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

Tablet with WINDOWS 10 and USB-LAN SMC 7500 adapter

Scheduled Pinned Locked Moved
Hardware Compatibility
3
53
9.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.
  • A
    AndrewG78
    last edited by Aug 21, 2018, 1:44 PM

    I have some not standard tablet(WINDOWS 10).
    It supports both USB and PXE.
    I have docking station with USB -LAN SMC 7500, but it is recognized as network card in BIOS and I can select it to boot through the PXE.
    It even connects to FOG server, but then I got EFI PXe boot error.
    I was trying a few different efi kernels, and even downloaded
    http://ww1.microchip.com/downloads/en//softwarelibrary/obj-lan95xx-uefi/lan95xx_7500_uefi_driver_0.10.zip
    to test SmscUsbNetDriver.efi

    logs:
    I put dots(…) in the places whre MAC address was shown
    "
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 available DHCP subnet: 172.18.147.206/255.255.255.0
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 vendor class: PXEClient:Arch:00006:UNDI:003001
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 PXE(ens160) 70… proxy
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 tags: UEFI32, ens160
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 bootfile name: i386-efi/ipxe.efi
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 next server: 172.18.147.206
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 broadcast response
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 sent size: 1 option: 53 message-type 2
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 sent size: 4 option: 54 server-identifier 172.18.147.206
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
    Aug 20 10:55:28 localhost dnsmasq-dhcp[9463]: 2705516733 sent size: 17 option: 97 client-machine-id 00…
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 2705516733 available DHCP subnet: 172.18.147.206/255.255.255.0
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 2705516733 vendor class: PXEClient:Arch:00006:UNDI:003001
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 available DHCP subnet: 172.18.147.206/255.255.255.0
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 vendor class: PXEClient:Arch:00006:UNDI:003001
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 PXE(ens160) 70… proxy
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 tags: UEFI32, ens160
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 bootfile name: i386-efi/ipxe.efi
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 next server: 172.18.147.206
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 sent size: 1 option: 53 message-type 5
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 sent size: 4 option: 54 server-identifier 172.18.147.206
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 sent size: 17 option: 97 client-machine-id 00…
    Aug 20 10:55:31 localhost dnsmasq-dhcp[9463]: 109533102 sent size: 25 option: 43 vendor-encap 06…
    "
    First screen: I have to make a short movie to catch this. It is displayed for about 0.5s in top left corner
    0_1534853053882_3bb8f259-b722-48d4-8141-bb8164e197b3-image.png
    This short message is displayed on the center of the screen.
    I just blurred my MAC address
    0_1534853066656_0f2e072d-2a7c-404d-8a9c-dba93592e99e-image.png

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Aug 21, 2018, 3:20 PM

      @andrewg78 said in Tablet with WINDOWS 10 and USB-LAN SMC 7500 adapter:

      It even connects to FOG server, but then I got EFI PXe boot error.

      Don’t see an error in the pictures. Can you please post a picture showing the actual error?

      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
      • A
        AndrewG78
        last edited by Aug 21, 2018, 3:24 PM

        The blue one(from my post) says ‘boot failed’ but there is some communication to dnsmasq as I understand from logs…

        G 1 Reply Last reply Aug 21, 2018, 6:16 PM Reply Quote 0
        • G
          george1421 Moderator @AndrewG78
          last edited by Aug 21, 2018, 6:16 PM

          @andrewg78 OK a couple of things here.

          1. I see that your tablet is a 32 bit efi system.
          2. Why are you using dnsmasq in this case? (there are reasons to use dnsmasq, I’m just making sure you have the proper use case).

          Can you post the contents of your dnsmasq config file?

          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!

          A 1 Reply Last reply Aug 22, 2018, 8:58 AM Reply Quote 0
          • A
            AndrewG78 @george1421
            last edited by Aug 22, 2018, 8:58 AM

            @george1421
            I use dnsmasq since a year or so, without any issues on regular Windows machines in the network with DHCP server.
            My config

            port=0
            
            # Log lots of extra information about DHCP transactions.
            log-dhcp
            
            # Set the root directory for files available via FTP.
            tftp-root=/tftpboot
            
            # The boot filename, Server name, Server Ip Address
            dhcp-boot=undionly.kpxe,,172.18.147.206
            dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,172.18.147.206
            dhcp-boot=net:UEFI64,ipxe.efi,,172.18.147.206
            dhcp-boot=net:UEFI,ipxe.efi,,172.18.147.206
            
            # Disable re-use of the DHCP servername and filename fields as extra
            # option space. That's to avoid confusing some old or broken DHCP clients.
            dhcp-no-override
            
            dhcp-vendorclass=BIOS,PXEClient:Arch:00000
            dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
            dhcp-vendorclass=UEFI,PXEClient:Arch:00007
            dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
            
            # PXE menu.  The first part is the text displayed to the user.  The second is t$
            pxe-prompt="Booting FOG Client", 1
            
            # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
            # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
            # This option is first and will be the default if there is no input from the us$
            #pxe-service=X86PC, "Boot to FOG", undionly
            #pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe
            #pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe
            
            dhcp-range=172.18.147.206,proxy
            
            G 1 Reply Last reply Aug 22, 2018, 10:00 AM Reply Quote 0
            • G
              george1421 Moderator @AndrewG78
              last edited by george1421 Aug 22, 2018, 4:00 AM Aug 22, 2018, 10:00 AM

              @AndrewG78 said in Tablet with WINDOWS 10 and USB-LAN SMC 7500 adapter:
              Lets tweak your config file a bit. I’m not sure if order is important but lets change it up this way. Plus we’ll enable the pxeservice function (since we see it stopping just past “Booting FOG Client (1)”

              port=0
              
              # Log lots of extra information about DHCP transactions.
              log-dhcp
              
              # Set the root directory for files available via FTP.
              tftp-root=/tftpboot
              
              # Disable re-use of the DHCP servername and filename fields as extra
              # option space. That's to avoid confusing some old or broken DHCP clients.
              dhcp-no-override
              
              dhcp-vendorclass=BIOS,PXEClient:Arch:00000
              dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
              dhcp-vendorclass=UEFI,PXEClient:Arch:00007
              dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
              
              # The boot filename, Server name, Server Ip Address
              dhcp-boot=undionly.kpxe,,172.18.147.206
              dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,172.18.147.206
              dhcp-boot=net:UEFI64,ipxe.efi,,172.18.147.206
              dhcp-boot=net:UEFI,ipxe.efi,,172.18.147.206
              
              # PXE menu.  The first part is the text displayed to the user.  The second is t$
              pxe-prompt="Booting FOG Client", 1
              
              # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
              # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
              # This option is first and will be the default if there is no input from the us$
              pxe-service=X86PC, "Boot to FOG", undionly
              pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe
              pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe
              pxe-service=IA32_EFI, "Boot to FOG UEFI IA32_EFI", i386-efi/ipxe.efi
              
              dhcp-range=172.18.147.206,proxy
              

              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!

              A 1 Reply Last reply Aug 22, 2018, 12:47 PM Reply Quote 0
              • A
                AndrewG78 @george1421
                last edited by Aug 22, 2018, 12:47 PM

                @george1421
                Thx. There is something new. We have progress and regress at the same time.
                Looks like adding pxe-service did the job.
                I got FOG menu.
                0_1534941669815_dcf7fa02-3c14-408b-b790-0b19848ef48e-image.png
                When I select host registration I got:
                0_1534941730069_e76843b5-0af7-47a4-8e18-e39c44c40e0c-image.png
                And after (3) seconds
                0_1534941785699_765702a6-05be-4f4b-b71f-54ade08005f9-image.png
                When I select bot from disk
                0_1534941844936_6016403c-761c-4177-ab32-db68b43de13a-image.png
                And the regression
                I’m unable to load FOG from PXE on my old regular BIOS machines.
                They were working fine before I enabled these pxe-service lines

                G 1 Reply Last reply Aug 22, 2018, 1:11 PM Reply Quote 0
                • G
                  george1421 Moderator @AndrewG78
                  last edited by Aug 22, 2018, 1:11 PM

                  @AndrewG78 Just to be clear, you only change the dnsmasq configuration and you get this error?

                  It almost looks like for the exit mode for bios systems, you have REFIND configured and not SANBOOT. But again without know what was changed, its only a weak guess.

                  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!

                  A 1 Reply Last reply Aug 22, 2018, 1:19 PM Reply Quote 0
                  • A
                    AndrewG78 @george1421
                    last edited by Aug 22, 2018, 1:19 PM

                    @george1421
                    Editing /etc/dnsmasq.d/ltsp.conf was my only change.

                    G 2 Replies Last reply Aug 22, 2018, 1:23 PM Reply Quote 0
                    • G
                      george1421 Moderator @AndrewG78
                      last edited by Aug 22, 2018, 1:23 PM

                      @AndrewG78 OK so lets be clear here then.

                      The fix to dnsmasq only allowed this system to boot, by delivering the proper boot file to the target computer.

                      This issue is different. The dnsmasq configuration sent the right ipxe boot kernel to the target computer. After ipxe boots, then dnsmasq is not used.

                      So now you need to look at the fog configuration for the default exit modes for both bios and uefi system. According to the picture it appears to be sending refind.conf and refind.efi to the target computer, but the target computer could not boot them. If the target computer is bios mode, I can understand why it can’t boot. If the target computer is EFI-32 then… I might suspect that refind.efi is a 64 bit kernel…

                      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
                      • G
                        george1421 Moderator @AndrewG78
                        last edited by Aug 22, 2018, 1:31 PM

                        @AndrewG78 OK I just checked and it appears that FOG does not distinguish between 64 bit and 32 bit systems in regards to which boot kernel it sends for refind. I checked with refind and there are two different boot kernels for refind, that may explain why we have that boot error.

                        @Developers for FOG 1.5.5 would it be possible to add a new exit mode like rEFInd-32 for those that have 32 bit uefi systems, plus include refind_ia32.efi into the fog/service/ipxe directory?

                        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!

                        A 1 Reply Last reply Aug 22, 2018, 3:49 PM Reply Quote 0
                        • A
                          AndrewG78 @george1421
                          last edited by Aug 22, 2018, 3:49 PM

                          @george1421
                          Thx for this finding.
                          What is strange to me is my old BIOS behavior. I did not change BIOS exit mode - I have GRUB_FIRST_HDD here but I got this error on my old BIOS machines
                          0_1534952754068_4b810ca7-0fdf-4afa-b946-53e92dce56ba-image.png
                          What should I do in dnsmasq config to setup just this tablet, and remove BIOS machines temporarily?

                          G 2 Replies Last reply Aug 22, 2018, 3:53 PM Reply Quote 0
                          • G
                            george1421 Moderator @AndrewG78
                            last edited by george1421 Aug 22, 2018, 9:53 AM Aug 22, 2018, 3:53 PM

                            @AndrewG78 Ok lets backtrack a bit. I had you change a setting for consistency sake, but lets remove all but what we need. Go back and edit your ltsp.conf file and comment out out the pxe-service settings like this, leaving just the EFI 32 bit entry.

                            # pxe-service=X86PC, "Boot to FOG", undionly
                            # pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe
                            # pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe
                            pxe-service=IA32_EFI, "Boot to FOG UEFI IA32_EFI", i386-efi/ipxe.efi
                            

                            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!

                            A 1 Reply Last reply Aug 22, 2018, 5:44 PM Reply Quote 0
                            • G
                              george1421 Moderator @AndrewG78
                              last edited by Aug 22, 2018, 3:55 PM

                              @AndrewG78 The one thing I didn’t ask you was what version of dnsmasq are you using? You can find out by opening a command shell on your dnsmasq server and key in dnsmasq -v to get the version number. Hopefully you are using 2.76 or later.

                              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!

                              A 1 Reply Last reply Aug 22, 2018, 4:18 PM Reply Quote 0
                              • A
                                AndrewG78 @george1421
                                last edited by Aug 22, 2018, 4:18 PM

                                @george1421
                                yes it is 2.76

                                1 Reply Last reply Reply Quote 0
                                • A
                                  AndrewG78 @george1421
                                  last edited by Aug 22, 2018, 5:44 PM

                                  @george1421
                                  OK. Now, old BIOS machines boot to FOG properly.

                                  G 1 Reply Last reply Aug 22, 2018, 5:45 PM Reply Quote 0
                                  • G
                                    george1421 Moderator @AndrewG78
                                    last edited by george1421 Aug 22, 2018, 11:46 AM Aug 22, 2018, 5:45 PM

                                    @AndrewG78 OK so now the only thing we need to work on is getting the EFI-32 systems to boot through to the hard drive?

                                    of the other option is to not have the target computers booting through pxe to the hard drive. Once imaged, have them boot locally then there is no immediate need for the 32 bit refind option.

                                    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!

                                    A 1 Reply Last reply Aug 22, 2018, 7:25 PM Reply Quote 0
                                    • A
                                      AndrewG78 @george1421
                                      last edited by Aug 22, 2018, 7:25 PM

                                      @george1421
                                      Well, this is fully autonomous system, so it must boot through the pxe all the time.
                                      Regarding EFI-32:
                                      1 system is not booting from hardrive
                                      2 fog is not loading when selected from the menu (e.g. host registration)

                                      G 1 Reply Last reply Aug 22, 2018, 7:34 PM Reply Quote 0
                                      • G
                                        george1421 Moderator @AndrewG78
                                        last edited by Aug 22, 2018, 7:34 PM

                                        @AndrewG78 Well in regards to #1, this is a current limitation in fog. I’m going to look tonight to see how hard it is to add another exit mode to fog. In the end this may be up to the developers to figure out if its not a quick fix for someone at my pay grade.

                                        As for #2, what do you see when “not loading” happens? Is there a specific error message? We’ll need a bit more to go on than, “its not working”.

                                        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!

                                        A 1 Reply Last reply Aug 22, 2018, 8:18 PM Reply Quote 0
                                        • A
                                          AndrewG78 @george1421
                                          last edited by Aug 22, 2018, 8:18 PM

                                          @george1421
                                          Thx
                                          #2
                                          I actually described this specific case in this post
                                          https://forums.fogproject.org/topic/12373/tablet-with-windows-10-and-usb-lan-smc-7500-adapter/7
                                          This is the post with 4 screen shots.

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 1 / 3
                                          1 / 3
                                          • First post
                                            15/53
                                            Last post

                                          137

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project