Summary: | net-wireless/broadcom-sta-5.100.82.112-r2 fails to build against kernel 3.10.7-gentoo | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ken Rose <rose> |
Component: | New packages | Assignee: | M. B. <tomboy64> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
emerge -pqv output |
Description
Ken Rose
2013-09-10 23:15:09 UTC
Created attachment 358444 [details]
emerge -pqv output
Please provide: - your kernel .config - output of `lsmod` - output of `lspci -kn` are you sure you followed the advice in the warnings emerge gives you? (in particular, have you disabled bss in your kernel?) apart from that, broadcom-sta-5* is deprecated by upstream and there are no fixes known to me that make it work on kernels later than 3.9.x. So please, try 6.30.223.30-r2 (tree) or 6.30.223.141 (from my overlay, tbc, or here: https://bugs.gentoo.org/show_bug.cgi?id=484676 ) Also, when and how does the kernel crash? @Pinkbyte: Considering that broadcom-sta-5 is deprecated by upstream in favor of v6 ("This is a rollup release. It includes and deprecates all previous releases and patches." - http://www.broadcom.com/docs/linux_sta/README.txt) it is unlikely there will come anything in terms of fixes for it. -r2 does not work with reasonably current kernels. -> please at least hardmask it - i would even argue for dropping it from the tree. It's superseded by -r3 and won't work with anything later than 3.4. -r3 should probably stay ~, but in time it will have to get hardmasked as well. It will eventually stop working with current kernels, if it didn't already, and new users should move on to v6. I'm pretty sure I followed all the directions. But I checked my current configuration, and confirmed, in particular, that bss is not configured. Then I rebuilt broadcom-sta-6.whatever. This produced a .ko that differed from the older one, and that, at least for the moment, seems to be OK. It is working (indeed, I'm posting over it), and so far the kernel hasn't crashed. I'll close this if the system lets me, and should the crash reappear, I'll file a new bug on that. Thank you. (In reply to M. B. from comment #3) > @Pinkbyte: > Considering that broadcom-sta-5 is deprecated by upstream in favor of v6 > ("This is a rollup release. It includes and deprecates all previous > releases and patches." - http://www.broadcom.com/docs/linux_sta/README.txt) > it is unlikely there will come anything in terms of fixes for it. > > > -r2 does not work with reasonably current kernels. -> please at least > hardmask it - i would even argue for dropping it from the tree. It's > superseded by -r3 and won't work with anything later than 3.4. > > -r3 should probably stay ~, but in time it will have to get hardmasked as > well. It will eventually stop working with current kernels, if it didn't > already, and new users should move on to v6. I have just dropped broadcom-sta-5.100.82.112 entirely, leaving only unstable versions in tree. I know that's not good, but this is last resort thing. I think this due to package's binary nature, breakages and slow upstream, it would be better to leave it permanently in unstable state. And i think we should drop -r3 too when bug #484676 would be resolved |