[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#622842: firmware-brcm80211: not getting an associated point

Here it is:

result from lspci -vv:
03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
	Subsystem: Broadcom Corporation Device 051a
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: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at d0300000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [d0] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us
			ClockPM+ Surprise- LLActRep+ BwNot-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [13c v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 00-00-2c-ff-ff-4e-88-25
	Capabilities: [16c v1] Power Budgeting <?>

and result from dmesg:
[ 330.205983] brcm80211: module is from the staging directory, the quality is unknown, you have been warned. [ 330.212186] brcm80211 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[  330.212195] brcm80211 0000:03:00.0: setting latency timer to 64
[  330.268237] Found chip type AI (0x13814313)
[  330.271328] Changing max_res_mask to 0xffff
[  330.271330] Changing min_res_mask to 0x200d
[  330.277446] Applying 4313 WARs
[ 330.278330] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x51a macaddr: 88:25:2c:4e:9e:34
[  330.283578] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[  330.285363] wl_set_hint: Sending country code US to MAC80211
[ 330.285371] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver ( (Compiled at 04:19:31 on Apr 7 2011)
[  330.365121] ADDRCONF(NETDEV_UP): wlan0: link is not ready

By the way, before I used 'modprobe cfg80211 ieee80211_regdom=EU' . Perhaps the problem comes from that and line (dmesg) 330.285363 ? I need channel 13 ...

Best regards and thanks,


maximilian attems <max@stro.at> ha escrito:

reassign 622842 linux-2.6

On Fri, Apr 15, 2011 at 09:07:30AM +0200, Wenceslao wrote:
Package: firmware-brcm80211
Version: 0.29
Severity: important

module brcm80211 is not getting the associated point of a wifi, although it is
properly detected. With a usb wifi stick (a ralink one) is detecting and
attaching properly.

so you properly know the module and report against firmware, *woow*.

attach relevant dmesg or lspci output unless proven as currently this can
be close right away.

kind regards


Este mensaje ha sido enviado desde https://webmail.unav.es

Reply to: