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 0D29B60798 for ; Tue, 11 Jan 2022 02:51:04 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F046F18410 for ; Tue, 11 Jan 2022 02:50:33 +0100 (CET) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 75D19183FB for ; Tue, 11 Jan 2022 02:50:32 +0100 (CET) Received: by mail-yb1-xb35.google.com with SMTP id i3so43117738ybh.11 for ; Mon, 10 Jan 2022 17:50:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=NgCu3fe/516ZUVDbchG3LKtW08cnD7npTM2skhnB2ao=; b=blRhthEERU+sqGVFJmJ2fPjRuAeTy3IsCWpx1BVaLuNwYnjBM7EinJ9CvSgrWh8oBc chsNHUe0ikqLw+1WbpxkSNJw8QQTLyeT+5Am9cF8D6P5eWETTBF3cWxbIHl7CLOosq3I 0WD6oFiTbIqNmOIGRVRAdHVanj3PmLlm1yGFuZMc6Awdnvrc7yf0kpXQA0bdrcwzKyMc qjXPKXUroOgOSpSwof4ZxXr+Viwly6A+iAxakmbLYLKPOViwikwHQT2xWuzVqY6kZifi 7NGLnfOd1lqIC3SNPzMIUxjOZYi9nDr/g4cqU1le421/+iQ6cdhbBnesG68g7PDlYTGn AKkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NgCu3fe/516ZUVDbchG3LKtW08cnD7npTM2skhnB2ao=; b=BhSQ0S/aQvw1Cc1DuBRyuDg3+9xydcsm2KsM5tag24YuCyDFvGSWqBVxL3O1finH5L gd4dB/EZEWrrh9evJShH4XmOH+SRCYJsU3igfsHbnsD7lzSaOfM6llY2lyOtkjaAMK+x 1lHfikrEcAfNaGM1eepxyecXPD6ZS8KU4kwvU5mzAC1loIJuKByFKrJyd+etloIDyWnA 0JK+SViXR6TCqNLR8/gtk6rFOPvkHCjRHXmNlh8cc2h9pqhPHkwCkqPlFHBsJ3LYJ+vX i9nBZBFBVm8tsb7ENlIvun8NZ4ZRjWwD+jv+7gdU4cFdAZgLZK5pqZD/Xa7q6VOf2ODm Z9Qg== X-Gm-Message-State: AOAM530kOrkEskyyOeqEubcTmu0E6PItZVJIrQrTPKjHS5sydi9dfG/d r9Fz2UDZj9qMRvy3hjZtD1bjq4oOxcaAii3bM5k4fc5r X-Google-Smtp-Source: ABdhPJxkwg0SmOxnotEMtJKaIRdnsQK5xo1UlWKWV3F1N9ngkZUeBBthfvBMFvao4a0iH1PxqFHRd3i799AdNzZ8lU4= X-Received: by 2002:a25:8b85:: with SMTP id j5mr3472195ybl.698.1641865824724; Mon, 10 Jan 2022 17:50:24 -0800 (PST) MIME-Version: 1.0 From: Patrick Buryk Date: Mon, 10 Jan 2022 20:50:14 -0500 Message-ID: To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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] Proxmox VE 7.1-2 Installation question - SOLVED, I think... 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: Tue, 11 Jan 2022 01:51:04 -0000 As a follow-up to my recent posts regarding Network interfaces not coming UP after a successful Proxmox 7.1-2 Installation - I think I've resolved the problem. Many previous (related) posts here (and in the Proxmox Release Notes and Bug Reports) spoke about a known bug in the Intel e1000e driver and suggested some work-arounds, implemented as commands issued at the Linux Command level. Before I tried these I thought I might visit the Dell Support site just to see if there was any news there about this. What I found (to my surprise!) was a recent BIOS update (A26) for the M6800 class machine. This was put out since I updated all my drivers and BIOS for Windows 10 Pro, last year. The description of the A26 BIOS update listed a fix to the e1000e LAN interface. I reattached my Win10Pro system disk and upgraded the BIOS to A26. After removing Win10Pro, re-inserting my Proxmox system SSD and booting up ther corresponding indicator lights on my switch illuminated. I was then able to ping my network gateway from the Proxmox host and login to the Proxmox host via remote browser. A brief "tour" of the various parts of the Proxmox GUI suggest that my network issue has been resolved and I can move forward with intended undertakings. Thanks, once again, for all of the suggestions, both from the mailing-list posts and via private email. I will end in reiterating (2) basic rules of computer administration: 1) RTFM 2) Keep drivers and BIOS levels - up to date!!! VBR, Patrick Buryk