On Thu, Aug 10, 2023 at 10:39:12PM -0500, Leslie Rhorer wrote: > 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. Sounds like a networking driver issue, not a modules issue. So report this to your driver maintainer and you can remove linux-modules from the email. ./scripts/get_maintainer.pl drivers/net/ethernet/broadcom/bnx2x/ Ariel Elior <aelior@xxxxxxxxxxx> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER) Sudarsana Kalluru <skalluru@xxxxxxxxxxx> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER) Manish Chopra <manishc@xxxxxxxxxxx> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER) <I'm skipping the generic networking maintainer list here> netdev@xxxxxxxxxxxxxxx (open list:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER) linux-kernel@xxxxxxxxxxxxxxx (open list) So email these folks, and you should be more specific about your kernel version, and what the issue was. If its not an issue today, then you need to be more specific about if its a regression present only in older kernels. Luis
