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

[Ludvig Aleman]

This is what i got the from the first set of instructions.(image
below/above)

So when im back after a clean install i guess i'll dig around some more.

On Wed, 18 Feb 2026, 16:42 Davi, <2120508 at bugs.launchpad.net> wrote:

> Hi all,
>
> Someone gave me de next advice to do. And it works for me! I have back
> the 6.17.0-14-generic kernel on noble!
>
> Commands under root user:
>
> sudo apt install --install-recommends linux-generic-hwe-24.04
> sudo update-grub
> reboot
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2141975).
> 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
>
>

-- 
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