Hello Sergio,
> I found the following approach to test kmods on any Fedora or RHEL
> version.
>
> Since broadcom-wl is in nonfree, the mock root can be
> epel+rpmfusion_nonfree-10-x86_64. My /etc/mock/epel-10-x86_64.cfg
> symlink points to centos-stream+epel-10-x86_64.cfg, but it can be
> changed to /etc/mock/alma+epel-10-x86_64.cfg if needed.
>
> After that, just install kernel, broadcom-wl, and also dnf to prevent
> failures at the end of the script when it tries to install it. On
> F43+,
> pam may also be required to allow su - to work properly.
>
> mock -r epel+rpmfusion_nonfree-10-x86_64 --install kernel pam dnf
> broadcom-wl
> mock -r epel+rpmfusion_nonfree-10-x86_64 --shell
>
> Inside the mock chroot, since akmods is currently not working and
> still
> needs investigation:
>
> kernel=$(basename /usr/src/kernels/6.12.0-210.el10.x86_64/)
> /usr/sbin/akmods --kernels $kernel
Thank you very much for the explanation of this approach. Very
instructive.
I had to use another approach. Maybe I should have been more explicit
about it. Here it is. My every day and only available working laptop is
old (2011) and uses an old CPU (core i3 first generation - Intel(R)
Core(TM) i3 CPU U 330 @ 1.20GHz) which is only compatible with x86-64-
v2 glibc compiled for this hardware capabilities. When using mock with
the correct configuration files provided by rpmfusion sibling *epel*10,
the build of the package always fails because of the x86-64-v3 glibc
provided after Redhat mandated it in rhel10 and therefore in all its
derivatives. This version (x86-64-v3) doesn't work on old CPUs and quit
quickly after its usage with an explicit message about the hardware
capabilities requirements. So, I had to find an alternative. The only
easy one that I could set-up quickly was to create a VM with one of the
only rhel10 derivative that provides glibc for x86-64-v2 CPUs, e.g.
almalinux 10.1. Here is the complete explanation that leads me to this
process to workaround using mock as well as the problems that result.
> This results in:
>
> /usr/sbin/akmods: line 258: /run/akmods/akmods.lock: No such file or
> directory
> flock: 99: Bad file descriptor
> Checking kmods exist for 6.12.0-210.el10.x86_64 [ OK ]
> Building and installing wl-kmod [FAILED]
> Building rpms failed; see /var/cache/akmods/wl/6.30.223.271-59-for-
> 6.12.0-210.el10.x86_64.failed.log for details
>
> You can then inspect:
>
> cat /var/cache/akmods/wl/6.30.223.271-59-for-6.12.0-
> 210.el10.x86_64.failed.log
>
>
> 2026/02/24 02:20:34 akmodsbuild: /tmp/akmodsbuild.nyXj67sl/BUILD/wl-
> kmod-6.30.223.271/_kmod_build_6.12.0-
> 210.el10.x86_64/src/wl/sys/wl_cfg80211_hybrid.c:1930:25: error:
> initialization of ‘int (*)(struct wiphy *, struct wireless_dev *,
> int, unsigned int, int *)’ from incompatible pointer type ‘s32
> (*)(struct wiphy *, struct wireless_dev *, s32 *)’ {aka ‘int
> (*)(struct wiphy *, struct wireless_dev *, int *)’} [-Wincompatible-
> pointer-types]
> 2026/02/24 02:20:34 akmodsbuild: 1930 | .get_tx_power =
> wl_cfg80211_get_tx_power,
> 2026/02/24 02:20:34 akmodsbuild: |
> ^~~~~~~~~~~~~~~~~~~~~~~~
> 2026/02/24 02:20:34 akmodsbuild: /tmp/akmodsbuild.nyXj67sl/BUILD/wl-
> kmod-6.30.223.271/_kmod_build_6.12.0-
> 210.el10.x86_64/src/wl/sys/wl_cfg80211_hybrid.c:1930:25: note: (near
> initialization for ‘wl_cfg80211_ops.get_tx_power’)
Thank you again for your very detailed explanation.
I should have mention in my first message that I also encountered this
exact failing output and that I have a fix for it and that I used it to
go through the build process of the wl-kmod package. Unfortunately, I
didn't already pushed it to the rhel10 branch of the wl-kmod package of
the rpmfusion source repository, nor the rawhide branch. But the fix
allows to go further in the build process, and leads to the problem at
link time (LD) explained in my previous message:
~/rpmbuild/BUILD/wl-kmod-6.30.223.271/_kmod_build_6.12.0-
124.8.1.el10_1.x86_64_v2/wl.o: error: objtool: aes_cbc_encrypt_pad+0x4c:
unannotated intra-function call
make[2]: *** [scripts/Makefile.build:425: ~/rpmbuild/BUILD/wl-kmod-
6.30.223.271/_kmod_build_6.12.0-124.8.1.el10_1.x86_64_v2/wl.o] Error 255
I'll try to "git push" the fix as soon as possible in order to allow
you, and everyone who wants to help, to be able to reproduce the failing
process. I should have done early. Sorry for that.
Thank you very much for your response, your great explanations and your
help.
Hope we can delve deeper into the analysis of this problem.
Cordially,
--
NVieville
_______________________________________________
rpmfusion-developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
