Bluetooth stops working after updates of broadcom modules -- includes solution

[Sauerland]

Search for:

kernel-default

Mark the entry and go to the version TAB…

[tckosvic]

After purging,

(base) tom@mydesktop: ~ $ zypper se -si broadcom
Loading repository data...
Reading installed packages...

S  | Name                    | Type    | Version                                | Arch   | Repository
---+-------------------------+---------+----------------------------------------+--------+-------------------
i+ | broadcom-wl             | package | 6.30.223.271-1699.27.pm.190            | x86_64 | Packman Repository
i  | broadcom-wl-kmp-default | package | 6.30.223.271_k6.19.11_1-1699.27.pm.186 | x86_64 | (System Packages)
i  | broadcom-wl-kmp-default | package | 6.30.223.271_k6.19.10_1-1699.27.pm.180 | x86_64 | (System Packages)
i  | broadcom-wl-kmp-default | package | 6.30.223.271_k6.19.12_1-1699.27.pm.190 | x86_64 | Packman Repository
i  | broadcom-wl-ueficert    | package | 6.30.223.271-1699.27.pm.190            | x86_64 | Packman Repository

    Note: For an extended search including not yet activated remote resources please use 'zypper
    search-packages'.
(base) tom@mydesktop: ~ $ 

(base) tom@mydesktop: ~ $ zypper se -si kernel-default
Loading repository data...
Reading installed packages...

S  | Name                 | Type    | Version           | Arch   | Repository
---+----------------------+---------+-------------------+--------+----------------------
i+ | kernel-default       | package | 6.19.11-1.1       | x86_64 | (System Packages)
i+ | kernel-default       | package | 6.19.10-1.2       | x86_64 | (System Packages)
i+ | kernel-default       | package | 6.19.12-1.1       | x86_64 | Main Repository (OSS)
i+ | kernel-default       | package | 6.19.12-1.1       | x86_64 | repo-oss
i  | kernel-default-devel | package | 6.19.11-1.1       | x86_64 | (System Packages)
i  | kernel-default-devel | package | 6.19.10-1.2       | x86_64 | (System Packages)
i  | kernel-default-devel | package | 6.4.0-150600.21.3 | x86_64 | (System Packages)
i  | kernel-default-devel | package | 6.19.12-1.1       | x86_64 | Main Repository (OSS)
i  | kernel-default-devel | package | 6.19.12-1.1       | x86_64 | repo-oss

    Note: For an extended search including not yet activated remote resources please use 'zypper
    search-packages'.
(base) tom@mydesktop: ~ $ 

I’ll remove remaining 6.4.0 module. Anything more to do?

thanks guys, tom kosvic

[tckosvic]

@tckosvic

(base) tom@mydesktop: ~ $

ok, I missed version tab

[Sauerland]

@tckosvic

i | kernel-default-devel | package | 6.4.0-150600.21.3 | x86_64 | (System Packages)

This is also kernel 6.4 from Leap.
Delete it.

I would do also as root:
dracut --regenerate-all --force
and
update-bootloader --config

Now restart

[tckosvic]

thanks all is back to normal. I feel like I just had an oil change and all the fluids topped off.

tom kosvic

[Sauerland]

But do not forget:

@Sauerland

But think of this:
broadcom-wl is an old software and it is more and more difficult to get it build for newer kernels.

So it might be a good solution, to buy a new USB-Wlan Stick.

Manfred and me are patching broadcom-wl and it is more and more difficult to patch.

[tckosvic]

I looked up some USB-Wlan for linux. It doesn’t look too bad to change from mb lan module to usb.

thanks, tom kosvic

[tckosvic]

I think that, if broadcom has not really been updated for a long time and zypper keeps updating the same file, that I will “taboo” the broadcom modules and potentially avoid my bluetooth getting corrupted each update.

If I get into a problem, I will got to a usb wifi adapter.

thanks, tom kosvic