Return-path: Received: from mail-fx0-f225.google.com ([209.85.220.225]:55255 "EHLO mail-fx0-f225.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753214Ab0AEXtS convert rfc822-to-8bit (ORCPT ); Tue, 5 Jan 2010 18:49:18 -0500 Received: by fxm25 with SMTP id 25so10318594fxm.21 for ; Tue, 05 Jan 2010 15:49:17 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B43C496.4040609@gmail.com> References: <4B43C496.4040609@gmail.com> From: =?ISO-8859-1?Q?G=E1bor_Stefanik?= Date: Wed, 6 Jan 2010 00:48:57 +0100 Message-ID: <69e28c911001051548ke40422ao49cb3ad2a141a33a@mail.gmail.com> Subject: Re: b43: must set qos=0 on to connect To: John Daiker Cc: linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Jan 6, 2010 at 12:00 AM, John Daiker 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 -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)