From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Leslie Rhorer <lesrhorer@att.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Ariel Elior <aelior@marvell.com>
Subject: Re: Failing network hardware
Date: Tue, 15 Aug 2023 08:20:00 +0700 [thread overview]
Message-ID: <ZNrSwBqP1vPW8OKz@debian.me> (raw)
In-Reply-To: <ddbed5c6-4ded-df22-fae0-bd256e40d6b3@att.net>
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
(fixing up netdev address)
On Sun, Aug 13, 2023 at 01:53:58PM -0500, Leslie Rhorer wrote:
> Hello all,
>
> About a year 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 (it was missing). 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 a new install on a
> different server to the new Debian Bookworm, and it worked for that server,
> so apparently the issue has been fixed in Bookworm. I reported a bug
> against the Buster distribution, but it was never fixed.
>
> With that in mind, I went ahead and upgraded the original server to
> Bookworm, but the NIC remains dead. Unfortunately, I cannot find my 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. The bnx2x.ko driver is installed,
> and lspci shows the card in the system, but ifconfig does not see the
> interface.
>
Too many moving parts here, hence allow me to rule things out:
If there is any of your system haven't been dist-upgraded to bookworm, can you
confirm this issue on vanilla v6.1 kernel? And also, can you check latest
mainline? If all have been upgraded, though, you need to reinstall bullseye
first.
As a side note, when you reply to mailing lists, please don't top-post;
reply inline with appropriate context instead.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-15 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ddbed5c6-4ded-df22-fae0-bd256e40d6b3.ref@att.net>
2023-08-13 18:53 ` Failing network hardware Leslie Rhorer
2023-08-15 1:20 ` Bagas Sanjaya [this message]
2023-08-15 1:50 ` Leslie Rhorer
2023-08-20 16:38 ` Leslie Rhorer
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=ZNrSwBqP1vPW8OKz@debian.me \
--to=bagasdotme@gmail.com \
--cc=aelior@marvell.com \
--cc=lesrhorer@att.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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