From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Leslie Rhorer <lesrhorer@att.net>,
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 06:08:11 +0000 [thread overview]
Message-ID: <13529cf4-a00d-5e59-2e1c-cb1daf24bf71@csgroup.eu> (raw)
In-Reply-To: <8de4e4b7-f741-eb4d-9e11-9b23ba65c21a@att.net>
Le 30/05/2022 à 01:46, Leslie Rhorer a écrit :
>
> Below is the output of dmesg after removing quite a few of what I
> am certain are unrelated lines:
>
> [ 0.000000] Linux version 5.10.0-13-amd64
> (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1
> 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian
> 5.10.106-1 (2022-03-17)
> [ 1.465675] bnx2x: disagrees about version of symbol module_layout
> [ 12.075903] bnx2x: disagrees about version of symbol module_layout
Those two messages means that you are trying to use modules that were
built for a different kernel version.
As far as I can see you are using kernel 5.10
You have to use bnx2 modules for that exact kernel.
Christophe
next prev parent reply other threads:[~2022-05-30 6:08 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 [this message]
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
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=13529cf4-a00d-5e59-2e1c-cb1daf24bf71@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=lesrhorer@att.net \
--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).