You have to either download and rebuild the .src.rpm yourself, or wait until the package in Packman is updated.
If you are lucky, we’ll get another kernel update tomorrow (but it might be on Monday too), then broadcom-wl should work again shortly afterwards.
Then run “rpmbuild --rebuild broadcom-wl-22.214.171.124-2.3.src.rpm” and it should work if you have the necessary development packages installed (it will tell you what’s missing otherwise). And no, this does not need a specific kernel.
I’m waiting until tomorrow to see if something is going to happen.
Probably the better idea if you can wait.
It was said that the kernel update will be re-released on Monday, an updated broadcom-wl package should be available on Packman soon after (it can take a few hours until it is available from the mirrors though).
Nearly forgot to mention it:
the kernel update has been released a few days ago, and Packman has updated braodcom-wl packages for that kernel meanwhile.
So you should have no problems any more to install them.
Where did you get Kernel 4.0.0 from?
Remove that (use YaST’s “Versions” tab for that), and the corresponding repo, that’s rather counter-productive if you need/want to use the proprietary broadcom-wl driver (which by itself doesn’t even support kernel 3.16.7, but Packman added patches for it to work)…
If in doubt, please post your repo list:
zypper lr -d
I have installed broadcom-wl
from YaST2 however the latter has the following requirements:
I have booted to the 3.16.7-21-default kernel, but with sudo ifconfig I still cannot see my card. Also in kernels4.xxxx I get the same.
What am I doing wrong?
Are you really using kernel-default? Apparently not, otherwise you shouldn’t have a problem with the requirements.
The default is kernel-desktop, and that’s what you rather should be using anyway (for that you need broadcom-wl-kmp-desktop though). Although kernel-default should work too.
Please post also a list of all installed kernel and broadcom packages:
rpm -qa | egrep "kernel|broadcom"
And again, the broadcom-wl-kmp package has to match your kernel, so there’s no way to get this to work with kernel 4.x. (unless you rebuild the package for that kernel yourself)