[Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta

John Anderson 2120508 at bugs.launchpad.net
Tue Feb 17 14:22:45 UTC 2026


Hello,

I was on Ubuntu 24.04. The solution failed for me. So I failed forward 
to Ubuntu 24.10 still had the issue. At this point I should advise this 
was installed over 24.04 so you need to back up every thing. Get 
yourself an an iso image

https://www.releases.ubuntu.com/questing/

build a bootable USB and ensure your UEFI is in order

once you have built and updated follow these steps

dkms

Reconnect to wifi and rebuild your computer from your saves.

Many thanks

JohnnieA

On 2/17/26 09:13, Davi wrote:
> Hi Daniel,
> Thanks for the package; I have installed it on noble-proposed. Unfortunately I am still on the 6.14.0-37-generic kernel. So the fix does not work on noble.
>

** Attachment added: "Screenshot From 2026-02-17
 14-18-08.png"
   https://bugs.launchpad.net/bugs/2120508/+attachment/5946701/+files/Screenshot%20From%202026-02-17%0A%2014-18-08.png

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to a duplicate bug report (2111898).
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




More information about the Ubuntu-sponsors mailing list