This yielded no luck on my system and just made things worse. I'm now running my display at a lower resolution so something happened to my nvidia drivers. The iBus process also crashed immediately when i tried seeing if i had any other options than a wired connection.
****Hardware**** Cpu: 4770k Mb: asus maximus vi impact z87 On Sat, 21 Mar 2026, 17:15 Matias Larsson, <[email protected]> wrote: > Hello, > > This bug has been affecting me, so I tested the following on my PC > running Ubuntu 24.04. Version info etc. at the end of the message. > > - Enabled 'proposed' source (pocket) via Updates settings GUI, developer > options > - $ sudo apt update > - $ sudo apt install broadcom-sta-dkms/noble-proposed > - I was able to confirm that the kernel modules for this package built > successfully. > > Due to another bug > (https://bugs.launchpad.net/ubuntu/noble/+source/virtualbox/+bug/2136499), > I was unable to test further for a long time. But today I was able to > get that fix from -proposed as well. > > So now I can confirm that wifi connectivity works on 6.17.0-19-generic > using broadcom-sta-dkms from noble-proposed. I have noticed an odd issue > of unexpected prompts to "log in to network" and the wifi icon showing > the '?' symbol. But I have no idea if this is related to the kernel > modules. In any case, connectivity seems to work OK and I can now use > 6.17 kernel which solves the problem for me. > > Thank you for the fix and information! > > Version info: > > $ apt policy broadcom-sta-dkms > broadcom-sta-dkms: > Installed: 6.30.223.271-23ubuntu1.2 > Candidate: 6.30.223.271-23ubuntu1.2 > Version table: > *** 6.30.223.271-23ubuntu1.2 100 > 100 http://se.archive.ubuntu.com/ubuntu noble-proposed/restricted > amd64 Packages > 100 http://se.archive.ubuntu.com/ubuntu noble-proposed/restricted > i386 Packages > 100 /var/lib/dpkg/status > 6.30.223.271-23ubuntu1.1 500 > 500 http://se.archive.ubuntu.com/ubuntu noble-updates/restricted > amd64 Packages > 500 http://se.archive.ubuntu.com/ubuntu noble-updates/restricted > i386 Packages > 6.30.223.271-23ubuntu1 500 > 500 http://se.archive.ubuntu.com/ubuntu noble/restricted amd64 > Packages > 500 http://se.archive.ubuntu.com/ubuntu noble/restricted i386 > Packages > > # (Reduced) System Details Report > --- > > ## Hardware Information: > - **Processor:** Intel® Core™ i5-7600K × 4 > > ## Software Information: > - **OS Name:** Ubuntu 24.04.4 LTS > - **OS Build:** (null) > - **OS Type:** 64-bit > - **GNOME Version:** 46 > - **Windowing System:** X11 > - **Kernel Version:** Linux 6.17.0-19-generic > > -- > 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120508 Title: [SRU] Kernel 6.17 support in broadcom-sta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
