BCM4360 802.11ac

English Hardware
1

Hello gents,

So i have Archer T6E V2

description: Network controller
       product: BCM4360 802.11ac Dual Band Wireless Network Adapter
       vendor: Broadcom Inc. and subsidiaries
       physical id: 0
       bus info: pci@0000:07:00.0
       version: 03
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=bcma-pci-bridge latency=0
       resources: irq:31 memory:fc600000-fc607fff memory:fc400000-fc5fffff

Using the broadcom-wl, I get that this is a rolling release, but once in a month my wifi stops working, so I just wait it out until its gets all the dependencies

 #### YaST2 conflicts list - generated 2024-04-17 21:15:13 ####

nothing provides 'ksym(default:netif_tx_wake_queue) = 61fa19d3' needed by the to be installed broadcom-wl-kmp-default-6.30.223.271_k6.8.5_1-1699.19.pm.103.x86_64

    [ ] break broadcom-wl-kmp-default-6.30.223.271_k6.8.5_1-1699.19.pm.103.x86_64 by ignoring some of its dependencies

    [ ] do not install broadcom-wl-6.30.223.271-1699.19.pm.103.x86_64




#### YaST2 conflicts list END ###

My question is: is there another driver that wont change so i can freeze the version and just have my wifi reliable after an update?

2

Post:
zypper se -si kernel broad
and
uname -a

3

I think there is a problem on Packman, build for kernel 6.8.6 but in the Repos is kernel 6.8.5…

Or maybe the kernel 6.8.6 is too new?
Because I have triggered a build in my Tumbleweed Repo and now all kmps are on rebuilding.

So wait until tomorrow?

4

Build is done, here we are.

My Repo for broadcom-wl, the same as in Packman:
https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Tumbleweed

2 Likes
5

Thank you for building it for me, shame I never learned the skill to do so myself. It works now ofc.
I wouldn’t complain from the first sign of problems. Im aware packman has a delay, this happens every once in a while and can last for a week util resolved.
So it was a versioning mistake?

6

No, it’s a delay of the server.

The Packman server does not or to late know when a new Kernel is build.
But that is also for my Repo.
But I can rebuild the drivers in my Repo, not on Packman.

7

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