From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 74C126A505 for ; Mon, 15 Mar 2021 03:06:36 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 667CE1ABF6 for ; Mon, 15 Mar 2021 03:06:36 +0100 (CET) Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 94F6B1ABDF for ; Mon, 15 Mar 2021 03:06:34 +0100 (CET) Received: by mail-il1-x12f.google.com with SMTP id z9so7973721iln.1 for ; Sun, 14 Mar 2021 19:06:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=x0j0psSCGwPPQczw7szVeXPU4LtkywW9VRNfQ4giccY=; b=gRi64lqyCUGMG6i/ewjTeDl0nMpu3+DgoapxrsLWaAzqff86SzO2cg01kqikO/qJ4h T7nhRRmFOPmSk+eYtCwlTw6X1JxlNSc/TNsJuB690OudMrvTetDcIeuaxnci0Jw9n3vo feFxBIL0Qc9OxXi9UcOPFLFKhqJD/fPmHUo9Cmkpz1JAnpqhlh9BgzJq1oD6gcn44VaR wD44rgpgh6+Lyf6ddPykSGE/c2Bckk7MUR7abpSKlbNT/bQOXS55IWVKSgt7aVYdMqkt 2T0NdmLc/J/KcOHmZEqt2VyqgaSYWVWP5RwcvT66rtWYfx2lm5RN9cIF2CEuB+DfwOZa riZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=x0j0psSCGwPPQczw7szVeXPU4LtkywW9VRNfQ4giccY=; b=eulGHVFP+i5aduEKzgZDpIoNv6RVgvT1tszMLgbFaSCQ2Sd2qFWWq7fuzeezMUWvR+ SbzvsJaU1IjZKnipyeY4V6Ac0hG1D1O+2wLW37Io0iQ45ptxXq0subLHeTwK84OWLex+ YA7G3Sw9T6RqZxuUjWAiUJsNhIXkQXhRZ8CUa609pTkR2HNo1wjs5S3mJQUSo7By81nE V8debJDQMslzmwwLb24nLJWjGdCQuAC9ATvB4aJzdLGraA7KjyiWR/RotQnJrkPla6SQ AIOVmsyGyRGfsVvX6YKXI+vguWgWnGAdV8k1kX+A/ZUHtpUnSn+kTuJdWvaacyiu9skr gWdw== X-Gm-Message-State: AOAM533u7S0WgqGV+Ey8BzoLgN2rCnNyrQc+2qcS/E6AD59L6iG3gGiA JnQ55y3DqzQjS68k825/bYFIEE+13uPMVNSBgLdGExefkSmfAg== X-Google-Smtp-Source: ABdhPJywuBuTtezmFhpuYVl7VJT1nvij6pPN9m2trbVgaSGwtMO6SPvfntFTDt6EkUdSBmJwBmhAsO+d4+ml/lgru7I= X-Received: by 2002:a92:444b:: with SMTP id a11mr9794780ilm.291.1615773987020; Sun, 14 Mar 2021 19:06:27 -0700 (PDT) MIME-Version: 1.0 From: Kyle Schmitt Date: Sun, 14 Mar 2021 21:06:16 -0500 Message-ID: To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [PVE-User] tn40xx network driver issue X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2021 02:06:36 -0000 Just an FYI in case this helps anyone: The tn40xx driver included with 5.4.101-1-pve wasn't built with the firmware needed to use the Tehuti Networks TN9710P 10GBase NIC. Identified like this in lspci: 05:00.0 Ethernet controller: Tehuti Networks Ltd. TN9710P 10GBase-T/NBASE-T Ethernet Adapter With this kernel, if you manually modprobe tn40xx, you will see something like Tehuti Network Driver from https://github.com/acooks/tn40xx-driver, 004 Supported phys : QT2025 TLK10232 AQR105 MUSTANG The driver needs build-time firmware for each phy the chip can support, and the one my NIC needs shows as MV88X3310 in the "Supported phys" list. Temporary work around: There may be cleaner methods than this but as a stopgap if you get one of these: Grab a version of the linux driver from someplace relatively safe: https://sgcdn.startech.com/005329/media/sets/tn4010_linux_esxi_drivers/tehuti_tn4010_linux_pcie_10_gigabit_network_card.zip, and extract the firmware. In this case the firmware was x3310fw_0_2_8_0_8850.hdr. Grab the source for the DKMS module (older since the driver has been moved in kernel, but still works). https://github.com/acooks/tn40xx-driver.git. It makes it easy if you put this into /usr/src/tn40xx-004 via: git clone -b release/tn40xx-004 https://github.com/acooks/tn40xx-driver.git /usr/src/tn40xx-004 In the Readme it says you need x3310fw_0_3_4_0_9445.hdr for NICs with this chip. Symlinking or renaming x3310fw_0_2_8_0_8850.hdr works just fine. The firmware you snagged in the first step goes in the /usr/src/tn40xx-004/ directory. Note: you can build this as a DKMS driver, but understand that since it's older than what's there, dkms install will complain, and it might not load automatically. In my case I had to run: dkms install tn40xx/004 --force and it still ended up not putting the right module in place, but a simple: cp /usr/src/tn40xx-004/tn40xx.ko /lib/modules/5.4.101-1-pve/updates/dkms worked. After modprobe tn40xx, this shows in dmesg. Tehuti Network Driver from https://github.com/acooks/tn40xx-driver, 004 Supported phys : MV88X3120 MV88X3310 QT2025 TLK10232 AQR105 MUSTANG And the interface works. Hopes this helps if anyone else runs into this. --Kyle