After Tumbleweed `dup` Broadcom wi-fi no longer works

English Network/Internet
1

Tumbleweed VERSION_ID=“20240405”
wi-fi adapter: BCM4360 802.11ac [14e4:43a0] (rev 03)

I installed ‘broadcom-wl’ and ‘broadcom-wl-kmp-default’.

Before the last dup, my wi-fi was working fine, once I ran zypper dup and rebooted, I can no longer see available networks, nor can I turn on/off ‘Airplane’ mode. I can run lspci -vnn | grep Network and my adapter is shown. I can access the internet through my phone’s usb connection. I don’t have ethernet so I can’t test that.

Running iwconfig gives:

“lo no wireless extensions.
eno1 no wireless extensions.
enp7s0u2c4i2 no wireless extensions.
nordlynx no wireless extensions.”

Running uname -a gives:

“Linux localhost.localdomain 6.8.4-rc1-1-default #1 SMP PREEMPT_DYNAMIC Thu Apr 4 07:22:28 UTC 2024 (1089550) x86_64 x86_64 x86_64 GNU/Linux”

I’m at a loss what to try next. Should I wait and see if the next dup fixes the issue or is there something else I can try? I can get by with just my phone but it’s pretty slow.

Thank you.

2

You should be able to boot with the previous kernel. Try the “Advanced options” line in the grub menu.

With the previous kernel, WiFi will probably still work. In that case, continue using the previous kernel until “broadcom-wl-kmp-default” is updated to match the current kernel.

3

@nrickert If it came from Packman, then it’s built for the new kernel…

4

It came from packman:

Information for package broadcom-wl-kmp-default:

Repository : packman
Name : broadcom-wl-kmp-default
Version : 6.30.223.271_k6.8.2_1-1699.19.pm.99
Arch : x86_64
Vendor : http://packman.links2linux.de
Installed Size : 1.4 MiB
Installed : Yes
Status : up-to-date
Source package : broadcom-wl-6.30.223.271-1699.19.pm.99.src

edit: I reverted to the previous kernal (6.8.2-1-default) and the Wi-Fi is working again.

5

Hi use your usb connection and force a refresh and zypper dup again it should be on the mirrors now

6

So, reverting to kernal 6.8.2-1-default fixes the issue.

Rebooting into the most recent kernal (6.8.4-rc1-1-default) then running sudo zypper refresh --force && sudo zypper dup returns “…Nothing to do.”

7

I’m glad to hear that.

The latest kernel is 6.8.4, but your “kmp” is for the 6.8.2 kernel.

This mismatch may happen again in the future. So now you have experience in dealing with it.

1 Like
8

@EmptyBucket It built an hour ago http://packman.links2linux.org/package/broadcom-wl/1072819 and should be there https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials/x86_64/

If you run zypper se -s broadcom-wl what is the output?

9

zypper se -s broadcom-wl gives:

S  | Name                              | Type       | Version                             | Arch   | Repository
---+-----------------------------------+------------+-------------------------------------+--------+-----------
i+ | broadcom-wl                       | package    | 6.30.223.271-1699.19.pm.99          | x86_64 | packman
v  | broadcom-wl                       | package    | 6.30.223.271-1699.19.pm.99          | i586   | packman
   | broadcom-wl                       | srcpackage | 6.30.223.271-1699.19.pm.99          | noarch | packman
   | broadcom-wl-debugsource           | package    | 6.30.223.271-1699.19.pm.99          | x86_64 | packman
   | broadcom-wl-debugsource           | package    | 6.30.223.271-1699.19.pm.99          | i586   | packman
i+ | broadcom-wl-kmp-default           | package    | 6.30.223.271_k6.8.2_1-1699.19.pm.99 | x86_64 | packman
v  | broadcom-wl-kmp-default           | package    | 6.30.223.271_k6.7.7_1-1699.19.pm.99 | i586   | packman
   | broadcom-wl-kmp-default-debuginfo | package    | 6.30.223.271_k6.8.2_1-1699.19.pm.99 | x86_64 | packman
   | broadcom-wl-kmp-default-debuginfo | package    | 6.30.223.271_k6.7.7_1-1699.19.pm.99 | i586   | packman
   | broadcom-wl-kmp-pae               | package    | 6.30.223.271_k6.7.7_1-1699.19.pm.99 | i586   | packman
   | broadcom-wl-kmp-pae-debuginfo     | package    | 6.30.223.271_k6.7.7_1-1699.19.pm.99 | i586   | packman
i  | broadcom-wl-ueficert              | package    | 6.30.223.271-1699.19.pm.99          | x86_64 | packman
v  | broadcom-wl-ueficert              | package    | 6.30.223.271-1699.19.pm.99          | i586   | packman

Just to be sure, I reran sudo zypper refresh --force && sudo zypper dup then zypper se -s broadcom-wl.

edit: I don’t know if it’s anything but every time I run any kind of zypper search ... I get:

Repository 'repo-non-free' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'openSUSE:Tumbleweed' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'openSUSE:Tumbleweed' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'nordvpn' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'repo-non-oss' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'repo-openh264' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'repo-oss' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'update-tumbleweed' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'packman' is out-of-date. You can run 'zypper refresh' as root to update it.

Even if it’s immediately after a refresh.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.