emerge net-wireless/broadcom-sta fails [solved]

ImAmMe · n00b Joined: 10 Feb 2006 Posts: 61

I'm trying to install the drivers for my wireless a card. I'm using this guide. but i can not patch to emerge. I know that the my wireless card is untested but shouldnt still emerge the patch, right? Any suggestions

lspci -vv
03:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: Dell Wireless 1370 WLAN Mini-PCI Card
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 10
Region 0: Memory at dfbfe000 (32-bit, non-prefetchable) [size=8K]

emerge -av net-wireless/broadcom-sta

d2_racing · Posted: Sat Jan 09, 2010 3:50 am Post subject:

Hi, can you post this :

d2_racing · Posted: Sat Jan 09, 2010 3:52 am Post subject:

Make sure that you have this :

cach0rr0 · Posted: Sat Jan 09, 2010 4:34 am Post subject:

ImAmMe · n00b Joined: 10 Feb 2006 Posts: 61

cach0rr0 · Posted: Sat Jan 09, 2010 5:18 am Post subject:

ImAmMe · n00b Joined: 10 Feb 2006 Posts: 61

i was missing a couple of kernel options and installed just fine. i didnt change the CONFIG_SSB_POSSIBLE, thought i might be wise ask first.

thanks for help

pappy_mcfae · Posted: Sat Jan 09, 2010 6:19 am Post subject:

You want the ssb module off. That will slow down the broadcom-sta driver, if it operates at all. cach0rr0 is definitely right about the kernel settings. Any more than that can cause issues, especially if you turn on the mac80211 stack.

Once you have your kernel fixed, then set the your kernel symlink to that kernel version (eselect kernel set n), where n is the number next to the kernel source you wish to use when you first use the eselect kernel list.

Once you have the symlink set, you need to accept the broadcom license agreement in /etc/make.conf thusly:

cach0rr0 · Posted: Sat Jan 09, 2010 6:19 am Post subject:

cach0rr0 · Posted: Sat Jan 09, 2010 6:29 am Post subject:

pappy_mcfae · Posted: Sat Jan 09, 2010 6:35 am Post subject:

No. The ebuild doesn't check for that, or should I say the last time I set up a new kernel and followed it up with braodcom-sta, it didn't. I run it as my preferred wireless driver. It beats the hell out of the b43 module, hands down.

BB!
P
_________________
This space left intentionally blank, except for these ASCII symbols.

DONAHUE · Posted: Sat Jan 09, 2010 6:46 am Post subject:

as presented in the original post:

cach0rr0 · Posted: Sat Jan 09, 2010 6:57 am Post subject:

nixnut · Posted: Sat Jan 09, 2010 11:11 am Post subject:

Moved from Installing Gentoo to Networking & Security.
networking stuff, so moved here
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand

d2_racing · Posted: Sun Jan 10, 2010 12:08 am Post subject:

Maybe there a bug inside the ebuild too.

pappy_mcfae · Posted: Sun Jan 10, 2010 12:14 am Post subject:

I am at a loss. I've been using that kernel setup for this machine since I moved to broadcom-sta, which was about as soon as it became available. I haven't emerged it in a while, but it also hasn't shown up as an update.

I'll emerge it right now and see what happens. Nope. No issues at all. Color me as confused as y'all.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

d2_racing · Posted: Sun Jan 10, 2010 1:49 am Post subject:

Maybe it's about the kernel...2.6.32-zen3, can you try with the Gentoo-source ?

pappy_mcfae · Posted: Sun Jan 10, 2010 6:37 am Post subject:

I've tried this with 2.6.32-zen2, and it works just fine. At this point, it's time to ask the original poster to post his .config, the results of lspci -n, and cat /proc/cpuinfo as well as his /etc/fstab file, and I'll see what I see.

BB!
P
_________________
This space left intentionally blank, except for these ASCII symbols.

cach0rr0 · Posted: Sun Jan 10, 2010 6:46 am Post subject:

pappy_mcfae · Posted: Sun Jan 10, 2010 7:42 pm Post subject:

I agree on that point. Having had my try at improving the ebuild, I can say that there were a few bugs in it earlier on. While things have gotten better, fighting kernel "improvements" seems to be the biggest problem that the broadcom-sta driver faces. That's why I try it with new kernel versions when they move from rc status to "stable".

I'm pretty sure the bug report on the broadcom-sta driver is still open. You could report this issue there, or start a new one. Considering what the SSB module can do to broadcom-sta, that should be checked for, and the ebuild should bomb upon finding it enabled.

BB!
P
_________________
This space left intentionally blank, except for these ASCII symbols.

cach0rr0 · Posted: Mon Jan 11, 2010 5:20 am Post subject:

right, so, I was blind, and missed the tilde before B43 and SSB

This is why it warns rather than bombing out

Still logging a bug, with a suggestion they change these to being full-on blockers.

Hopefully I don't ruffle any feathers, but near as I can tell since this is going to cause problems, and prevent the merged package from functioning correctly, it should be changed.

I will assume the maintainers had a reason for their decision on this, but I figure at worst they mark the bug as invalid, and provide an explanation for why it isn't blocked.

suggested change:

pappy_mcfae · Posted: Mon Jan 11, 2010 6:53 am Post subject:

Don't worry. I signed on to it as well. I'll keep them honest. hehehehe

BB!
P
_________________
This space left intentionally blank, except for these ASCII symbols.

d2_racing · Posted: Mon Jan 11, 2010 2:50 pm Post subject:

Yeah, that bug is something.

At least there a bugzilla, so we just have to wait and see