All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Daiker <daikerjohn@gmail.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: b43: must set qos=0 on to connect
Date: Tue, 05 Jan 2010 16:10:59 -0800	[thread overview]
Message-ID: <4B43D513.3030300@gmail.com> (raw)
In-Reply-To: <69e28c911001051548ke40422ao49cb3ad2a141a33a@mail.gmail.com>

On 01/05/2010 03:48 PM, Gábor Stefanik wrote:
> On Wed, Jan 6, 2010 at 12:00 AM, John Daiker<daikerjohn@gmail.com>  wrote:
>> I have a BCM4312 rev 01 (14e4:4315) card in my HP Mini netbook.  I am having
>> troubles connecting to any WEP secured AP.
>>
>> I know the trick about having to load with pio=1 for the device to stay
>> happy (and forget about using DMA), so no issues there, I hope.
>>
>> With qos=1 (by default, IIRC), I am unable to establish a connection with
>> said WEP connection, and notice many 'PHY transmission error' messages in my
>> dmesg output.
>>
>> With qos=1, I can successfully connect to my WEP connection without issue,
>> and without any error messages or warnings.
>>
>> I have a BCM4318 rev 02 (14e4:4318) in a desktop that works with
>> enabled/disabled qos not matter what.  Also, a RT2500-based card works fine
>> on the connection as well.
>>
>> Both card are using the 478.104 firmware.
>>
>> Please advise what steps I should take to further debug this issue.
>>
>> Thanks,
>> John Daiker
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
> Hi!
>
> Is this the new 4312 (BCM94312HMGB AKA 575920-001), with integrated
> Bluetooth? I haven't seen this issue on my machines with a regular
> 4312, so it is probably related to the DMA error, or maybe it is
> specific to the new 4312. If you can, please check whether the actual
> model number printed on the card is the new one.
>
> Thanks,
> Gábor
>

Gábor,

I just pulled the card, and it's not the chip you mention.  It's a 
"BCM94312HMG"  (Notice that it doesn't have the "B" at the end.  I would 
assume that indicates the Bluetooth integration.)

I've taken few photos of the front and back of the card.  Let me know if 
you want to see them... I can post 'em on my website or flickr for your 
viewing pleasure.

Thanks,
John Daiker

  reply	other threads:[~2010-01-06  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 23:00 b43: must set qos=0 on to connect John Daiker
2010-01-05 23:48 ` Gábor Stefanik
2010-01-06  0:10   ` John Daiker [this message]
2010-01-06  0:34     ` Gábor Stefanik

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=4B43D513.3030300@gmail.com \
    --to=daikerjohn@gmail.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.