From: Robert Martin <robertm83@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..
Date: Mon, 04 Dec 2006 13:17:15 -0500 [thread overview]
Message-ID: <4574662B.8000903@gmail.com> (raw)
In-Reply-To: <1165221950.5553.49.camel@johannes.berg>
I've only had the laptop (Compaq V6000Z series) for about a week, so I'd
be unable to tell you if the driver had worked before, but I seem to
have had the same problem that Paul Collins did pertaining to frequency
mismatch. Setting it manually to the value "iwlist" gave me for the AP
makes it work, albeit at very slow speeds (driver issue?). I might have
been mistaken about the PCI-E, the lspci -n gives me...
03:00.0 0280: 14e4:4311 (rev 01)
...and lspci -vvv gives me...
03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card (rev 01)
Subsystem: Hewlett-Packard Company Unknown device 1363
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, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at b3200000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/0
Enable-
Address: 00000000 Data: 0000
Capabilities: [d0] Express Legacy 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, Port 0
Link: Latency L0s <4us, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
...although I could have sworn I read somewhere that this series uses
the PCI-E mini bus. Thank you for your time.
Johannes Berg wrote:
> On Sun, 2006-12-03 at 16:21 -0500, Robert Martin wrote:
>
>
>> I would be happy to give more
>> information if requested, or try different kernel/firmware options.
>>
>
> Has it ever worked? I'm curious because the PCI-E chips are 4318s which
> are known to not work properly due to missing/wrong TX power
> calibration.
>
> johannes
>
next prev parent reply other threads:[~2006-12-05 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 21:21 NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull Robert Martin
2006-12-04 8:30 ` Paul Collins
2006-12-04 13:00 ` Dan Williams
[not found] ` <1165237252.2738.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-12-04 18:28 ` Paul Collins
[not found] ` <45745D2B.1090700@gmail.com>
2006-12-04 23:50 ` Paul Collins
[not found] ` <45746370.4070205@gmail.com>
[not found] ` <45746370.4070205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2006-12-05 0:28 ` Paul Collins
2006-12-04 23:46 ` Robert Martin
2006-12-04 8:45 ` Johannes Berg
2006-12-04 18:17 ` Robert Martin [this message]
2006-12-05 9:25 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4574662B.8000903@gmail.com \
--to=robertm83@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).