Bug#1010240: broadcom-sta-dkms: cannot build module, it fails after upgrade kernel to 5.17.3-1

[manel vallès]

Package: broadcom-sta-dkms
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages broadcom-sta-dkms depends on:
ii dkms 2.8.7-2

Versions of packages broadcom-sta-dkms recommends:
ii wireless-tools 30~pre9-13.1

broadcom-sta-dkms suggests no packages.

[brokers...@icloud.com]

Package: broadcom-sta-dkms

Version: 6.30.233.271-17

Severity: important

Dear Mr. Bloch,

I upgraded my kernel to 5.17.3-1 (I'm on AMD64), and, as reported before, the module fails to build. I have dkms version 2.8.7-2 and wireless-tools version 30~pre9-13.1. I'm using bash and am on Debian Testing. The driver runs totally fine with 5.16.18-1. All packages required and recommened are there.  Here is the output when installing the driver.

sudo apt install ./broadcom*

[sudo] password for dexcube:

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

Note, selecting 'broadcom-sta-dkms' instead of './broadcom-sta-dkms_6.30.223.271-17_all.deb'

broadcom-sta-dkms is already the newest version (6.30.223.271-17).

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

1 not fully installed or removed.

After this operation, 0 B of additional disk space will be used.

Do you want to continue? [Y/n] y

Setting up broadcom-sta-dkms (6.30.223.271-17) ...

Removing old broadcom-sta-6.30.223.271 DKMS files...

Deleting module broadcom-sta-6.30.223.271 completely from the DKMS tree.

Loading new broadcom-sta-6.30.223.271 DKMS files...

Building for 5.16.0-6-amd64 5.17.0-1-amd64

Building initial module for 5.16.0-6-amd64

Done.

wl.ko:

Running module version sanity check.

- Original module

   - No original module exists within this kernel

- Installation

   - Installing to /lib/modules/5.16.0-6-amd64/updates/dkms/

depmod...

Backing up initrd.img-5.16.0-6-amd64 to /boot/initrd.img-5.16.0-6-amd64.old-dkms

Making new initrd.img-5.16.0-6-amd64

(If next boot fails, revert to initrd.img-5.16.0-6-amd64.old-dkms image)

update-initramfs.......

Building initial module for 5.17.0-1-amd64

Error! Bad return status for module build on kernel: 5.17.0-1-amd64 (x86_64)

Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more informat

ion.

dpkg: error processing package broadcom-sta-dkms (--configure):

installed broadcom-sta-dkms package post-installation script subprocess returne

d error exit status 10

Errors were encountered while processing:

broadcom-sta-dkms

E: Sub-process /usr/bin/dpkg returned an error code (1)

As shown, the dkms build is successful for 5.16, but not 5.17. Note that the local file being used was a .deb of the latest version in testing, due to the fact that I had to reinstall it for diagnostic purposes on an offline system.

[Lars Kindermann]

I'm affected, too.

For Slackware there seems to be already a patch for this:

https://www.linuxquestions.org/questions/slackware-14/fix-for-broadcom-sta-not-building-in-kernel-5-17-a-4175710375/