Hello satmandu, or anyone else affected, Accepted broadcom-sta into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/broadcom- sta/6.30.223.271-23ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: broadcom-sta (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2120508 Title: [SRU] Kernel 6.17 support in broadcom-sta Status in broadcom-sta package in Ubuntu: Fix Released Status in broadcom-sta source package in Noble: Fix Committed Status in broadcom-sta source package in Plucky: Invalid Status in broadcom-sta source package in Questing: Fix Released Bug description: [SRU Justification] [ Impact ] Failed to build against kernel v6.17-rc1. [ Test Plan ] 1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available: $ sudo apt-get install --no-install-recommends --yes \ linux-oem-6.17 2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup: $ sudo apt-get install --no-install-recommends --yes \ linux-generic 3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with: $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r) # With Questing $ dkms status broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed # With Noble $ dkms status broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed 4. Reboot to load the kernel module 5. The wl module should be loaded automatically and wireless lan should be usable as before. 6. There should not be any UBSAN warning in dmesg, e.g.: ``` [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4 ``` [ Where problems could occur ] This doesn't affect the rest part of the system, and it doesn't introduce functional changes. [ Other Info ] This affects series with kernels >= 6.17. Nominate Questing and Noble for fixing. Kernel 6.17 will not be introduced in Plucky ========== original bug report ========== A patch to fix building for kernel 6.17-rc1 is at https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
