b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Faulty 14e4:4315 (BCM4312)?
Date: Thu, 9 Jun 2011 01:47:04 +0200	[thread overview]
Message-ID: <BANLkTikXnXR2f1TUrJ7bhC9KdBe0XevN7Q@mail.gmail.com> (raw)
In-Reply-To: <4DF0062F.6030602@lwfinger.net>

W dniu 9 czerwca 2011 01:30 u?ytkownik Larry Finger
<Larry.Finger@lwfinger.net> napisa?:
> On 06/08/2011 06:14 PM, Rafa? Mi?ecki wrote:
>>
>> W dniu 9 czerwca 2011 01:05 u?ytkownik Larry Finger
>> <Larry.Finger@lwfinger.net> ?napisa?:
>>>
>>> On 06/08/2011 05:55 PM, Rafa? Mi?ecki wrote:
>>>>
>>>> W dniu 8 czerwca 2011 23:19 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com>
>>>> ?napisa?:
>>>>>
>>>>> Forcing rate to 1M workarounded this issue.
>>>>
>>>> Working state seems to be random and not related to rate.
>>>>
>>>> Even if I manage to connect, I do not have a chance to achieve 1MB/s.
>>>>
>>>> At least ndiswrapper seems to work fine. I got easy&stable connection
>>>> and speed around 10MB/s. Nice to know my card is not faulty.
>>>
>>> What is the nature of that 4315 card? Mine is currently in use and has
>>> been
>>> working correctly. This is one of the original PCIe units with the SPROM
>>> at
>>> 0x1000.
>>>
>>> When I use the one in the netbook with the SPROM at 0x0800, the unit is a
>>> lot less stable.
>>
>> 14e4:4315
>> Mini PCIe
>> MMIO 16K
>> BCM94312HMG / DW1397
>> SSB 2.6
>> BCM4312
>> SPROM 8 (0x1000)
>> PMU 1
>> PHY LP / 1
>> RADIO 0x2062 / 2
>
> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
> ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
> ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
> ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
> ssb: chipcommon status is 0x10
> ssb: Found rev 1 PMU (capabilities 0x02A62F01)
> ssb: SPROM offset is 0x1000
> ssb: SPROM revision 8 detected.
> ssb: Sonics Silicon Backplane found on PCI device 0000:04:00.0
> b43-phy0: Broadcom 4312 WLAN found (core revision 15)
> b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2
> b43 ssb0:0: wlan0: Features changed: 0x00004800 -> 0x00004000
> b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
> b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 64-bit DMA initialized
> b43-phy0 debug: QoS enabled
>
> 04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g
> LP-PHY [14e4:4315] (rev 01)
> ? ? ? ?Subsystem: Hewlett-Packard Company BCM4312 802.11b/g Wireless LAN
> Controller [103c:137c]
> ? ? ? ?Flags: bus master, fast devsel, latency 0, IRQ 21
> ? ? ? ?Memory at fc000000 (64-bit, non-prefetchable) [size=16K]
>
> Other than mine is HP-branded, they appear to be the same. I am also 2 m
> from the AP and my rate is 36 Mbps.

Yeah, that's exactly the same card. The same cores, revisions, cc
status, PMU capabilities.

I just didn't try 508.1084 firmware. I've been playing with 410.2160,
478-104, 508.1103, 508.1107 however, so switching to your's version
probably won't help.

What is your network encryption and freq?

BSS 00:23:69:c2:65:06 (on wlan0)
        TSF: 665805184 usec (0d, 00:11:05)
        freq: 2427
        beacon interval: 100
        capability: ESS Privacy ShortSlotTime (0x0411)
        signal: -14.00 dBm
        last seen: 778 ms ago
        SSID: zajec_poznan_160
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 4
        ERP: <no flags>
        Extended supported rates: 24.0 36.0 48.0 54.0
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 16-PTKSA-RC (0x000c)
        WMM:    * Parameter version 1
                * BE: CW 15-1023, AIFSN 3
                * BK: CW 15-1023, AIFSN 7
                * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                * VO: acm CW 3-7, AIFSN 2, TXOP 1504 usec

network={
        ssid="zajec_poznan_160"
        key_mgmt=WPA-PSK
        proto=WPA RSN
        pairwise=CCMP TKIP
        group=CCMP TKIP
        psk="psssst"
}

-- 
Rafa?

  reply	other threads:[~2011-06-08 23:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 20:25 Faulty 14e4:4315 (BCM4312)? Rafał Miłecki
2011-06-08 20:37 ` Gábor Stefanik
2011-06-08 20:59   ` Rafał Miłecki
2011-06-08 20:59   ` Rafał Miłecki
2011-06-08 21:08     ` Gábor Stefanik
2011-06-08 21:19       ` Rafał Miłecki
2011-06-08 22:55         ` Rafał Miłecki
2011-06-08 23:05           ` Larry Finger
2011-06-08 23:14             ` Rafał Miłecki
2011-06-08 23:30               ` Larry Finger
2011-06-08 23:47                 ` Rafał Miłecki [this message]
2011-06-09  0:27                   ` Larry Finger
2011-06-11  7:53                   ` Rafał Miłecki
2011-06-11 16:20                     ` Rafał Miłecki
2011-06-11 17:36                       ` Rafał Miłecki
2011-06-12 20:46                         ` Rafał Miłecki

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=BANLkTikXnXR2f1TUrJ7bhC9KdBe0XevN7Q@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.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).