According to the specs on the actual laptop, it's a "Draft N" router.
I had thought that the b/g part would be pretty much the same as other
adaptors (and work) with the "N" part being added functionality (that
I can't use regardless, since my router is only B/G). However I
haven't had much luck getting the sucker to work under linux just yet,
except for the works-but-disconnects-regularly driver supplied by
Broadcomm.
I was hoping to at least have some luck with ndiswrapper but even that
one hasn't been giving me much love with this card. Luckily I've got
an old USB-G adaptor kicking around that I can use in the meantime.
Let me know if there's any other information you need...
Here's the dump from "lspci -vv"
08:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n
Wireless LAN Controller (rev 01)
Subsystem: Hewlett-Packard Company Unknown device 137f
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 7
Region 0: Memory at d1100000 (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 PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [58] Vendor Specific Information
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [d0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <4us, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <4us, L1 <64us
Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 21-00-36-ff-ff-00-be-89
Capabilities: [16c] Power Budgeting
And from "lspci -nvv"
08:00.0 0280: 14e4:432b (rev 01)
Subsystem: 103c:137f
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 7
Region 0: Memory at d1100000 (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 PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [58] Vendor Specific Information
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [d0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <4us, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <4us, L1 <64us
Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 21-00-36-ff-ff-00-be-89
Capabilities: [16c] Power Budgeting
Let me know if there's any other info I can provide.
- TJA
On Wed, Sep 10, 2008 at 12:42 PM, Larry Finger
<[EMAIL PROTECTED]> wrote:
> Tyler Aviss wrote:
>>
>> Hey All,
>>
>>
>> First of all, a quick introduction of myself. In general, I'm more of
>> a sysadmin than a kernel developer, though in the odd case I've
>> tracked down a few driver or FOSS-project bugs here and there (webcams
>> and gatekeeper proejcts, small bugs usually caused by simple
>> mistakes). So while I've never really delved heavily into writing
>> drivers, I can at least do a step-by-step testing in many cases.
>>
>> I'm joining the list because:
>>
>> a) I have a bunch of laptops with Broadcomm cards, which - thanks to
>> you developers - now happily work without me needing to use
>> NDISwrapper
>> b) I have a newer laptop with a Broadcomm card which seems to be
>> something of an enigma at the moment.
>>
>> Now onward to (b), and what is currently one of the driving causes
>> behind my joining this list. I notice that on the "LinuxWireless"
>> page, the origins/status of the BCM4322 chipset seems to be somewhat
>> unknown. The current comment in the unsupported section is:
>>
>> * BCM 4322 - We are working on support for this device (FIXME: what
>> the hell is a BCM4322? –mb)
>>
>> I'd be happy to lend and support I can in supplying info/dumps/etc and
>> testing the driver on this chipset as needed. Broadcomm actually has
>> their own Linux/closed-source driver that somewhat works for this
>> chipset (wl), but at the moment it's buggy as heck and tends to
>> regularly disconnect and reconnect. I'd love to see the B43 driver get
>> this chipset working, both so that I can have a working card and so
>> that users can use a "true" FOSS driver rather than a buggy
>> closed-source one.
>
> When you issue an 'lspci -nnv' for one of these devices, what is the PCI ID
> for the BCM4322?
>
> I suspect that this is an 802.11n device. If so, the reverse engineering for
> this device is going slowly. We had one person working on decompiling a MIPS
> Broadcom driver, but he has been busy with other things lately. I have been
> busy with working on the LP PHY (an 802.11g variant) for a couple of reasons
> - it is a lot more like the other G PHYs, and I personally have one of the
> devices. Once the LP PHY is working, then I will start on the N PHY code.
>
> Larry
>
--
Tyler Aviss
Systems Support
LPIC/LPIC-2
(647) 302-0942
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
