I just updated my kernel to the latest gentoo-sources, 2.6.16-r9 and find I cannot re-emerge bcm43xx. package.mask claims it is obsolete because it is in kernel 2.6.17, but that has not been released yet. Surely it would make sense to at least wait until a kernel containing this has been released before masking it?
The ebuild is extremely out of date and contains many bugs that would prevent it from working. Please use a 2.6.17_rc kernel instead or unmask locally if you want to keep using the ebuild.
There isn't a 2.6.17 release of gentoo-sources. It's worked for me for months. It may not be perfect, but there is no alternative as yet.
There are vanilla 2.6.17_rc releases, you should be using these if you're using bcm43xx. If you won't use a vanilla kernel and if you insist on using the ebuilds, feel free to unmask it locally, but I don't want to unmask them since they really are obsolete and have issues.
Resolving as WONTFIX. I won't bother extracting bcm43xx and necessary softmac out of 2.6.17(_rc). Neil: Please use package.unmask as long as there is no gentoo-sources-2.6.17. Joseph: Thanks for taking care :-)
Sure. Let's hope 2.6.17 won't be long now.
*** Bug 166234 has been marked as a duplicate of this bug. ***
I don't think this package is obsolete. It would be nice to have again a special (more up-to-date) ebuild for compiling the bcm43xx driver as a module like we have it for alsa (there, it is also not obsolete). This makes it also not neccesary to install a new kernel and you don't need to reboot your machine.
I won't resurrect this package simply because upstream only works in the regular kernel tree. I'm sorry, but I don't have the time to continuously backport changes and make sure that they work with older kernels. Sorry.
(In reply to comment #7) > > This makes it also not neccesary to install a new kernel and you don't need to > reboot your machine. > What's wrong with compiling bcm43xx as a module via the normal kernel configuration? No need for reboots there either.
