From: Leslie Rhorer <lesrhorer@att.net>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>
Subject: Re: Module failure on new install of Debian Bullseye
Date: Mon, 30 May 2022 01:50:49 -0500 [thread overview]
Message-ID: <486038c1-bac9-c66c-826f-32fa41aa85e4@att.net> (raw)
In-Reply-To: <22c909ae-1bd5-731e-53e7-ff6e0b47c7bb@csgroup.eu>
On 5/30/2022 1:11 AM, Christophe Leroy wrote:
>
>
> Le 30/05/2022 à 01:45, Leslie Rhorer a écrit :
>> If this is the wrong list, please let me know the correct one so I
>> can subscribe and post there.
>>
>> Two of my servers are having bizarre problems after upgrading to
>> Debian Bullseye. After attempting numerous fixes, I decided to wipe the
>> systems and do a fresh install. I did a fresh install of he first from
>> a netinst thumb drive, but the .iso does not contain the bnx2c drivers
>> needed for the ASUS PEB-10G/57811-1S 10GbE SFP+ Network Adapters used by
>> both systems. I tried adding what I thought to be the correct non-free
>> drivers, but I still got errors about the bnx2x drivers and the
>> interface shows no carrier. Since no carrier is detected on the
>> interface, no LAN or internet access is possible. The system is
>> effectively dead, although it boots up and of course I have local
>> console access.
>>
>> After several different approaches, I changed from the netinst
>> image to a full non-free image. It still would not properly load the
>> bnx2x drivers. I tried downloading all six bnx2x e1, e1h, and e2
>> release 7.13.15.0 and 7.13.21.0 firmware files and adding them to the
>> initram image. It no longer complains about missing files, but it
>> doesn't activate the NIC, either. These servers are both essentially
>> dead in the water until I can get this fixed.
>>
>> The only thing I spot from dmesg that seems possibly related is:
>>
>> ...
>> [ 12.976323] r8169 0000:0b:00.0: firmware: failed to load
>> rtl_nic/rtl8168f-1.fw (-2)
>> [ 12.976478] firmware_class: See https://wiki.debian.org/Firmware for
>> information about missing firmware
>> [ 12.976632] r8169 0000:0b:00.0: Direct firmware load for
>> rtl_nic/rtl8168f-1.fw failed with error -2
>> [ 12.976636] r8169 0000:0b:00.0: Unable to load firmware
>> rtl_nic/rtl8168f-1.fw (-2)
>
> Do you have that file rtl8168f-1.fw in your setup ? Is it at the correct
> place ?
I will check. Without remote LAN support, it isn't very easy.
>
> By the way, this seems to be more a Debian problem than a kernel
> problem. Have you asked your question to Debian support ?
They and I do not get along. More importantly, while at first glance
this might seem to be the case, I don't think it is. The github
repository at
git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/bnx2x/
Is not a Debian thing. It is a kernel module thing for all distros.
It is from there I downloaded the firmware (after it failed to load
during install), and it is that which is failing. As I said, it could
possibly be the realtek drivers also need to be loaded, and they are
not, but I really would not expect it to be the case.
prev parent reply other threads:[~2022-05-30 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd7e69ce-41a4-cc5e-5a15-0ae9fc52aad0.ref@att.net>
2022-05-29 11:35 ` Modules list Leslie Rhorer
2022-05-29 15:21 ` Christophe Leroy
2022-05-29 15:41 ` Randy Dunlap
2022-05-29 23:42 ` Leslie Rhorer
2022-05-29 23:45 ` Module failure on new install of Debian Bullseye Leslie Rhorer
2022-05-29 23:46 ` Leslie Rhorer
2022-05-30 6:08 ` Christophe Leroy
2022-05-30 6:43 ` Leslie Rhorer
2022-05-30 9:50 ` Leslie Rhorer
2022-06-03 4:00 ` Leslie Rhorer
2022-06-03 15:09 ` Luis Chamberlain
2022-06-04 6:14 ` Leslie Rhorer
2022-05-30 6:11 ` Christophe Leroy
2022-05-30 6:50 ` Leslie Rhorer [this message]
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=486038c1-bac9-c66c-826f-32fa41aa85e4@att.net \
--to=lesrhorer@att.net \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=rdunlap@infradead.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 NNTP newsgroup(s).