03:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:43c3] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:86fb]
Flags: fast devsel, IRQ 19
Memory at f7000000 (64-bit, non-prefetchable) [size=32]
Memory at f6800000 (64-bit, non-prefetchable) [size=8]
Memory at f2400000 (64-bit, prefetchable) [size=4]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/32 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 <?>
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 00-00-00-ff-ff-00-00-00
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [220] #15
Kernel modules: brcmfmac, wl
Hi everybody I have a problem with my new wireless card, I see it has brcmfmac and wl module, how do I make kernel use one of them? I know for other devices there is line: kernel driver in use.
But the package broadcom-wl blocks (blacklists) other kernel modules, to prevent them from being loaded automatically.
I would suggest to uninstall it, that wireless card should be supported by kernel 4.4+ (by the included brcmfmac module, which should then be used automatically).
It probably would have been easier to do that in the graphical session…
And I didn’t want to see the full output, but rather the new one when running “sudo modprobe -v brcmfmac”.
Did you run that? And nothing changed?
so this might be my only option upgrade to kernel v4.12 (or other LTR) it seems. have been googling for hours and kernel firmware for broadcom newest chip is not in 4.4
Sorry guys have been having issues with GUI (part of nVidia problems everyone is having here), finally got GUI going so now I will be posting from my PC not from laptop or from cellphone.
Ok, so there seems indeed to be a problem with loading the firmware.
I’m wondering why it tries to load brcmfmac4366b-pcie.txt .
This does not exist in openSUSE’s kernel-firmware package.
I’m not sure whether this is critical though.
Have you actually tried whether the device works or not?
You should switch to NetworkManager in YaST->System->Network Settings, otherwise you’d need to configure the connection in YaST.
But I found this: https://ubuntuforums.org/showthread.php?t=2337200
Apparently that device is misidentified by the kernel, seems it’s rather a 4366c not 4366b. No idea whether that fix is in Leap’s 4.4 kernel already, but try to install the latest one from the repo I posted.
Apparently you also need to get the proper firmware manually, that thread mentions how to do that.
One more question how comes this comes out as USB not as PCI?
Hm? lspci only shows PCI devices…
Or do you mean the mention of “usbcore”?
Well, I suppose the card has internally an USB bus and that’s how the actual wireless chip is connected.
I.e. the card is some kind of USB->PCIe adapter.
Just guessing though.
That was about Ubuntu 16.04 though which is over a year older than Leap 42.3.
Maybe that didn’t contain the necessary firmware file yet (it was released in April 2016, and that firmware file was added in January 2016).
The comments indicate that it works fine in Ubuntu 17.04 and 17.10 though.
According to the page firmware version in there is 1.164 :S IDK!!!
Where do you see any firmware version?
There have been no changes to the firmware in kernel-firmware git since that initial commit.
No, I mean have you actually tried whether it works on this PC?
I.e. does it show up in NetworkManager/ifconfig, have you tried to establish a connection?
So far, the only “problem” mentioned here is that there is no line “Kernel driver in use” in the lspci output…
AIUI, you 'd need a newer version of brcmfmac, that knows about brcmfmac4366c-pcie.bin.
IOW, install a newer kernel.
But note that you’d need to reinstall the nvidia driver for the new kernel as well.
I was tired when I wrote this message.