• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. usb-to-ethernet
    Log in to post
    • All categories
    • T

      Microsoft Surface Go - USB-C to Ethernet Adapter Compatibility

      Hardware Compatibility
      • microsoft surface go usb-to-ethernet usb-c usb 3.0 • • ttrammell
      13
      0
      Votes
      13
      Posts
      2.8k
      Views

      T

      @george1421 said in Microsoft Surface Go - USB-C to Ethernet Adapter Compatibility:

      Just be aware I only gave you the 64 bit kernel. So the step you did above will break a 32 bit computer.

      Gotcha.

      If everything works OK with bzImage4186 you can leave it in the bzImage place. The only thing that is different is I added the microsoft nic. With the next release of the official FOG kernel they will add in the new Microsoft NIC.

      I’ll leave it under bzImage4186 until the next release. We don’t have any other machine right now that uses a USB-C NIC Adapter, so it should be fine.

    • T

      Solved Asus ZenBook Flip UX360U - PXE Assistance Needed

      Hardware Compatibility
      • asus zenbook pxe ux360u usb-to-ethernet • • ttrammell
      11
      0
      Votes
      11
      Posts
      3.8k
      Views

      george1421G

      @ttrammell said in Asus ZenBook Flip UX360U - PXE Assistance Needed:

      UEFI BIOS on the Zenbook still doesn’t recognize the USB-to-Ethernet adapter,

      FWIW: To get this to work, you need network adapters supported by your hardwares UEFI firmware. Think of uefi as a very limited operating system. If it doesn’t have the drivers built in, then it can’t initialize the device. So if you want to pxe boot on that zenbook you need to contact the manufacturer to find out what usb network adapters are supported by the firmware … or … just boot fos from the usb stick and move on to the next problem.

    • F

      Acer travelmate b usb to ethernet

      FOG Problems
      • usb-to-ethernet acer dhcp • • fox134
      14
      0
      Votes
      14
      Posts
      2.1k
      Views

      george1421G

      @fox134 Well lets hope you don’t have an ipxe.exe in there…

      The client gets its booting information from (the) dhcp responsible for assigning an ip address to the target computer. So if you want the target computer to use a different boot file then you might update dhcp options 67.

      Now with that said, from your OP you say that FOG is giving out the IP addresses on a dedicated imaging network. So if you want to change the boot file, you will need to edit the dhcp config file on your FOG server.

      To see what you config file looks like, you can review this example: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1

      You will see for arch 7 and 9 it calls out ipxe.efi. You can replace that with maybe snponly.efi or any of the other efi files. Then you must restart your dns server. On ubuntu you would issue the command sudo systemctl restart isc-dhcp-server to restart the service.

    • JJ FullmerJ

      USB ethernet adapter mac(s) for imaging multiple hosts. (Universal Imaging Nics) (Wired Nic for All Wireless Devices)

      Feature Request
      • usb-to-ethernet image wireless • • JJ Fullmer
      25
      0
      Votes
      25
      Posts
      6.4k
      Views

      Wayne WorkmanW

      @jj-fullmer said in USB ethernet adapter mac(s) for imaging multiple hosts. (Universal Imaging Nics) (Wired Nic for All Wireless Devices):

      current host or get a host by a given uuid, mac, or hostname.

      You should fork the fog-community-scripts repository and add this stuff to it. Just label it the powershell cli or something, give it some snazzy name.

      For the Python project, I’m calling it fog-cli.

    • 1 / 1