You are not logged in.

#1 2025-02-03 23:45:45

boredhero
Member
Registered: 2020-10-14
Posts: 24

broadcom-wl-dkms failing after 6.13.1 kernel upgrade

Hello all, I was doing a system upgrade and noticed that the broadcom-wl-dkms package fails to compile for the 6.13.1 kernel (also upon further investigation, it appears the broadcom-wl package is no longer available in the repo).

This is my network controller (I also have ethernet which I am using for now)

21:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter [14e4:43a0] (rev 03)
        DeviceName: Broadcom 5762
        Subsystem: Broadcom Inc. and subsidiaries Device [14e4:0619]
        Kernel modules: bcma
==> dkms install --no-depmod broadcom-wl/6.30.223.271 -k 6.13.1-arch1-1

Error! Bad return status for module build on kernel: 6.13.1-arch1-1 (x86_64)
Consult /var/lib/dkms/broadcom-wl/6.30.223.271/build/make.log for more information.
==> WARNING: `dkms install --no-depmod broadcom-wl/6.30.223.271 -k 6.13.1-arch1-1' exited 10

Upon inspecting the build log:

 \cat /var/lib/dkms/broadcom-wl/6.30.223.271/build/make.log
DKMS (dkms-3.1.5) make.log for broadcom-wl/6.30.223.271 for kernel 6.13.1-arch1-1 (x86_64)
Mon Feb  3 06:31:17 PM EST 2025
Applying patch 001-null-pointer-fix.patch
# command: patch -p1 < ./patches/001-null-pointer-fix.patch
patching file src/wl/sys/wl_linux.c
Hunk #1 succeeded at 2165 (offset 8 lines).

# exit code: 0
# elapsed time: 00:00:00
Applying patch 002-rdtscl.patch
# command: patch -p1 < ./patches/002-rdtscl.patch
patching file src/shared/linux_osl.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 003-linux47.patch
# command: patch -p1 < ./patches/003-linux47.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 004-linux48.patch
# command: patch -p1 < ./patches/004-linux48.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 2386 (offset -2 lines).
Hunk #2 succeeded at 2496 (offset -2 lines).
Hunk #3 succeeded at 2928 (offset 4 lines).

# exit code: 0
# elapsed time: 00:00:00
Applying patch 005-debian-fix-kernel-warnings.patch
# command: patch -p1 < ./patches/005-debian-fix-kernel-warnings.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 006-linux411.patch
# command: patch -p1 < ./patches/006-linux411.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c
patching file src/wl/sys/wl_linux.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 007-linux412.patch
# command: patch -p1 < ./patches/007-linux412.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 54 (offset 1 line).
Hunk #2 succeeded at 471 (offset 1 line).
Hunk #3 succeeded at 2395 (offset 1 line).
Hunk #4 succeeded at 2418 (offset 1 line).

# exit code: 0
# elapsed time: 00:00:00
Applying patch 008-linux415.patch
# command: patch -p1 < ./patches/008-linux415.patch
patching file src/wl/sys/wl_linux.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 010-linux56.patch
# command: patch -p1 < ./patches/010-linux56.patch
patching file src/shared/linux_osl.c
Hunk #1 succeeded at 946 (offset 4 lines).
patching file src/wl/sys/wl_linux.c
Hunk #1 succeeded at 586 (offset 4 lines).
Hunk #2 succeeded at 776 (offset 4 lines).
Hunk #3 succeeded at 3352 (offset 17 lines).

# exit code: 0
# elapsed time: 00:00:00
Applying patch 011-linux59.patch
# command: patch -p1 < ./patches/011-linux59.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 38 with fuzz 2.
Hunk #2 succeeded at 444 (offset 8 lines).
patching file src/wl/sys/wl_iw.c
patching file src/wl/sys/wl_linux.c
Hunk #1 succeeded at 1647 (offset 4 lines).
Hunk #2 succeeded at 1668 (offset 4 lines).
Hunk #3 succeeded at 1681 (offset 4 lines).
patching file src/wl/sys/wl_linux.h
patching file src/wl/sys/wlc_pub.h

# exit code: 0
# elapsed time: 00:00:00
Applying patch 012-linux517.patch
# command: patch -p1 < ./patches/012-linux517.patch
patching file src/wl/sys/wl_linux.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 013-linux518.patch
# command: patch -p1 < ./patches/013-linux518.patch
patching file src/shared/linux_osl.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 014-linux414.patch
# command: patch -p1 < ./patches/014-linux414.patch
patching file src/shared/linux_osl.c
Hunk #1 succeeded at 1097 (offset 21 lines).

# exit code: 0
# elapsed time: 00:00:00
Applying patch 015-linux600.patch
# command: patch -p1 < ./patches/015-linux600.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 2375 (offset -37 lines).

# exit code: 0
# elapsed time: 00:00:00
Applying patch 016-linux601.patch
# command: patch -p1 < ./patches/016-linux601.patch
patching file src/wl/sys/wl_cfg80211_hybrid.c

# exit code: 0
# elapsed time: 00:00:00
Applying patch 017-linux612.patch
# command: patch -p1 < ./patches/017-linux612.patch
patching file src/wl/sys/wl_linux.c

# exit code: 0
# elapsed time: 00:00:00
Cleaning build area
# command: make -C /usr/lib/modules/6.13.1-arch1-1/build M=/var/lib/dkms/broadcom-wl/6.30.223.271/build clean
make: Entering directory '/usr/lib/modules/6.13.1-arch1-1/build'
make[1]: Entering directory '/var/lib/dkms/broadcom-wl/6.30.223.271/build'
CFG80211 API is prefered for this kernel version
Makefile:85: Neither CFG80211 nor Wireless Extension is enabled in kernel
make[1]: Leaving directory '/var/lib/dkms/broadcom-wl/6.30.223.271/build'
make: Leaving directory '/usr/lib/modules/6.13.1-arch1-1/build'

# exit code: 0
# elapsed time: 00:00:00
Building module(s)
# command: make -j16 KERNELRELEASE=6.13.1-arch1-1 -C /usr/lib/modules/6.13.1-arch1-1/build M=/var/lib/dkms/broadcom-wl/6.30.223.271/build
make: Entering directory '/usr/lib/modules/6.13.1-arch1-1/build'
make[1]: Entering directory '/var/lib/dkms/broadcom-wl/6.30.223.271/build'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  CC [M]  src/shared/linux_osl.o
  CC [M]  src/wl/sys/wl_linux.o
  CC [M]  src/wl/sys/wl_iw.o
  CC [M]  src/wl/sys/wl_cfg80211_hybrid.o
In file included from src/shared/linux_osl.c:25:
././src/include/linuxver.h:151:10: fatal error: net/lib80211.h: No such file or directory
  151 | #include <net/lib80211.h>
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
In file included from src/wl/sys/wl_cfg80211_hybrid.c:26:
././src/include/linuxver.h:151:10: fatal error: net/lib80211.h: No such file or directory
  151 | #include <net/lib80211.h>
      |          ^~~~~~~~~~~~~~~~
In file included from src/wl/sys/wl_linux.c:27:
././src/include/linuxver.h:151:10: fatal error: net/lib80211.h: No such file or directory
  151 | #include <net/lib80211.h>
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
compilation terminated.
make[3]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: src/shared/linux_osl.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: src/wl/sys/wl_cfg80211_hybrid.o] Error 1
make[3]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: src/wl/sys/wl_linux.o] Error 1
make[2]: *** [/usr/lib/modules/6.13.1-arch1-1/build/Makefile:1989: .] Error 2
make[1]: *** [/usr/lib/modules/6.13.1-arch1-1/build/Makefile:251: __sub-make] Error 2
make[1]: Leaving directory '/var/lib/dkms/broadcom-wl/6.30.223.271/build'
make: *** [Makefile:251: __sub-make] Error 2
make: Leaving directory '/usr/lib/modules/6.13.1-arch1-1/build'

# exit code: 2
# elapsed time: 00:00:01

It seems like the kernel module lib80211 is missing. When I try to modprobe it, sure enough.

modprobe lib80211
modprobe: FATAL: Module lib80211 not found in directory /lib/modules/6.13.1-arch1-1

Anyone know what's up here or what is the recommended solution other than just waiting for maintainers to update broadcom-wl-dkms or downgrading kernel?

Offline

#2 2025-02-03 23:55:42

loqs
Member
Registered: 2014-03-06
Posts: 18,277

Re: broadcom-wl-dkms failing after 6.13.1 kernel upgrade

You need broadcom-wl-dkms 6.30.223.271-39.  Did you do a partial update?

Offline

#3 2025-02-04 00:02:50

mackin_cheese
Member
Registered: 2025-01-07
Posts: 188

Re: broadcom-wl-dkms failing after 6.13.1 kernel upgrade

This was patched just today. go ahead and run a full system update again while installing this package

Offline

#4 2025-02-04 00:19:02

hegstal
Member
Registered: 2025-02-04
Posts: 1

Re: broadcom-wl-dkms failing after 6.13.1 kernel upgrade

All the needed patches are in the -39 release (https://gitlab.archlinux.org/archlinux/ … f59954d425) but they weren't being applied on dkms install when I ran pacman/dkms.
To fix I added the 018-linux613.patch patch to /var/lib/dkms/broadcom-wl/6.30.223.271/source/dkms.conf, and then manually re-ran dkms: sudo dkms install --no-depmod broadcom-wl/6.30.223.271 -k 6.13.1-arch1-1

Offline

#5 2025-02-04 01:47:03

loqs
Member
Registered: 2014-03-06
Posts: 18,277

Re: broadcom-wl-dkms failing after 6.13.1 kernel upgrade

hegstal wrote:

All the needed patches are in the -39 release (https://gitlab.archlinux.org/archlinux/ … f59954d425) but they weren't being applied on dkms install when I ran pacman/dkms.

Thank you for the explanation I have reopened https://gitlab.archlinux.org/archlinux/ … -/issues/2

Offline

#6 2025-02-04 05:39:02

bth
Member
Registered: 2025-02-04
Posts: 1

Re: broadcom-wl-dkms failing after 6.13.1 kernel upgrade

Confirmed that this works. For anyone else experiencing this today, this means manually adding the last patch to the list of patches, so that /var/lib/dkms/broadcom-wl/6.30.223.271/source/dkms.conf looks like this:

PACKAGE_NAME="broadcom-wl"
PACKAGE_VERSION="6.30.223.271"
BUILT_MODULE_NAME[0]="wl"
DEST_MODULE_LOCATION[0]="/kernel/drivers/net/wireless"
PATCH[0]="001-null-pointer-fix.patch"
PATCH[1]="002-rdtscl.patch"
PATCH[2]="003-linux47.patch"
PATCH[3]="004-linux48.patch"
PATCH[4]="005-debian-fix-kernel-warnings.patch"
PATCH[5]="006-linux411.patch"
PATCH[6]="007-linux412.patch"
PATCH[7]="008-linux415.patch"
PATCH[8]="010-linux56.patch"
PATCH[9]="011-linux59.patch"
PATCH[10]="012-linux517.patch"
PATCH[11]="013-linux518.patch"
PATCH[12]="014-linux414.patch"
PATCH[13]="015-linux600.patch"
PATCH[14]="016-linux601.patch"
PATCH[15]="017-linux612.patch"
PATCH[16]="018-linux613.patch"
AUTOINSTALL="yes"

And running:

source /usr/share/bash-completion/completions/dkms
dkms autoinstall

And now my stupid question is, do I need to revert this before next update? It'll just be overwritten, right?

Offline

Board footer

Powered by FluxBB