From: Patrick Buryk <pburyk@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Proxmox VE 7.1-2 Installation question - SOLVED, I think...
Date: Mon, 10 Jan 2022 20:50:14 -0500 [thread overview]
Message-ID: <CAEJyo+tyRnTAuEMWvFasngweUNxceMrq0=aNiL-j=RTLUmDKbQ@mail.gmail.com> (raw)
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
reply other threads:[~2022-01-11 1:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEJyo+tyRnTAuEMWvFasngweUNxceMrq0=aNiL-j=RTLUmDKbQ@mail.gmail.com' \
--to=pburyk@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.