From: Leslie Rhorer <lesrhorer@siliconventures.net>
To: "linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>
Subject: module issues
Date: Thu, 10 Aug 2023 22:39:12 -0500 [thread overview]
Message-ID: <c6d34094-7363-a462-5043-768f688aef66@siliconventures.net> (raw)
Hello all,
About a yer or so ago, I upgraded one of my Debian servers to
Bullseye, and it killed the 10G NIC on the server due to issues with the
device driver in the Debian repository. I jumped through all sorts of
loops and hoops to try to get it working, but I finally had to give up
and resort to using the 1G interface. Recently, I tried upgrading
another server to the new Debian Bookworm, and it worked for that
server, so apparently the issue has been fixed in Bookworm.
With that in mind, I went ahead and upgraded the original server to
Bookworm, but the NIC remains dead. Unfortunately, I cannot find ny
notes on what I did originally to try to get the 10G interface working
and to shut it down in favor of a built-in port. I do recall I tried
compiling what was supposed to be the correct firmware driver and also
changing the udev rules, but I do not recall the exact details. I have
tried several things, including re-installing the firmware, but nothing
seems to work. The Ethernet interface does not appear on the system in
order to be able to specify it in /etc/network/interfaces. What can I
do in order to try to get the 10G card working?
The card is an Asus MCB-10G_PEB-10G NIC and uses the bnx2x.ko
driver. The system uses an Asus AMD-64 motherboard.
next reply other threads:[~2023-08-11 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 3:39 Leslie Rhorer [this message]
2023-08-11 18:45 ` module issues Luis Chamberlain
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=c6d34094-7363-a462-5043-768f688aef66@siliconventures.net \
--to=lesrhorer@siliconventures.net \
--cc=linux-modules@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).