Bug#1012859: #1012859installation-reports: Ethernet firmware module failure - no LAN / internet access during or after install

[Holger Wansing <hwansing@mailbox.org>]

Hi all,

Am 2. Juni 2025 01:11:26 MESZ schrieb Nicholas D Steeves <sten@debian.org>:
>reopen 1012859
>thanks
>
>Leslie, please retain me in CC for your replies.
>
>Holger Wansing <hwansing@mailbox.org> writes:
>
>> Leslie Rhorer <lesrhorer@siliconventures.net> wrote:
>>> OK, I went ahead and did a fresh install of Bookworm and the 10G NIC works. 
>>
>
>Yes, that's the "crippled system".  The above quote is truncated, and
>there is a second server that Leslie Rhorer previously described as
>"dead".  In the last email to this bug, the reporter's second sentence,
>about the second system was:
>
>>> I went ahead and upgraded the [second] Bullseye system to bookworm,
>>> and everything seems to work as well as ever, but I still don't have
>>> the 10G NIC working on that system.  The driver for the card is
>>> bnx2x, but the card currently does not even show up on the system.
>
>So there are two affected systems.  For the record, the specific NIC
>that uses bnx2x but that isn't working is this one:
>
>>>>> Asus PEB-10G/57811-1S 10GbE SFP+ Network Adapter which employs a
>>>>> BCM 57811S controller
>
>Leslie, does your server with this NIC work with up-to-date firmware
>from bookworm?  How about bookworm-backports?  And in combination with
>the kernel from bookworm-backports?
>
>Alternatively, would you please test with a TESTING image for the
>upcoming Debian 13 (trixie) release?
>
>  https://www.debian.org/CD/live/

Leslie already confirmed, that in a fresh Bookworm install all is fine.
Testing with a Trixie ISO might be good, yes.

So the only issue is on a Buster system, which was upgraded to Bullseye, and is then broken.
That's an issue with oldoldstable and oldstable, which I think is unlikely to be fixed.

Did I miss something in my summary?


>
>> So I close this bug.
>>
>> Apparently there was an issue with the firmware in Bullseye, but since the issue is already fixed in Bookworm, there is nothing more to do here.
>>
>
>Holger, do you have another source of information that shows that this
>was fixed for the reporter's second server?  In the absence of this,
>this bug should not be closed.

No, no further information apart from this bug.
Sorry, if I closed that too early.


Holger