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

    Kernel Build that supports USB-C NIC

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    2
    4
    643
    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.
    • H
      himem
      last edited by

      Got the system up and running great and then got new Dell laptops with BIOS 1.5.0. Previous 1.3.0 builds were able to image through USB 3.0 dongle, Thunderbolt dock and USB-C dongle. With the revision no longer working through USB-C and I had to add the kernel argument has_usb_nic=1 to get USB 3 to start working (wonky at best usually needs a couple of tries). The Device iD is
      USB\VID_0BDA&PID_8153&REV_3000
      USB\VID_0BDA&PID_8153
      …should I be seeing support for that in kernel 4.19.1? It’s not a game ender. I just purchased several of the USB-C dongles to support the roll out and wonder if I should return them.

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

        @himem said in Kernel Build that supports USB-C NIC:

        PID_8153

        That appears to be a realtek nic. If you setup a debug deploy/capture (doesn’t matter which) then pxe boot the target computer. After a few enter key presses you will be dropped to a linux command prompt.

        It would be interested in seeing what
        ip addr show
        and
        lsusb
        produces.

        One final bit, is this network adapter in a usb-c dock/port replicator, or is it a usb-c to ethernet adapter?

        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
        • H
          himem
          last edited by

          Thanks for your help…I actually think I found the issue in the BIOS settings. Under Secure Boot settings there are 2 modes Deployment and Audit. Deployment fully vets boot security and audit just logs it, so I believe it was blocking the NIC after the initial PXE boot. Thanks for the quick response.

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

            @himem If you find this is the case; could you provide the hardware info an a clear screen shot of the setting changes to make it work taken with a mobile phone? If you have a problem, I’m sure someone else will in the near future.

            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

            131

            Online

            12.1k

            Users

            17.3k

            Topics

            155.3k

            Posts
            Copyright © 2012-2024 FOG Project