[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2010-08-28 Thread Przemysław Kulczycki
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more

Re: [Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2010-04-08 Thread Tom Dunham
10:05:27 AM Subject: [Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2010-04-08 Thread Przemysław Kulczycki
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2009-10-08 Thread Sameer
I have a broadcom 4306 rev 02. Works fine with WPA2 in Windows 7. In Ubuntu 9.10, using the b43legacy firmware, I am able to connect to my WPA2 network but the connection is intermittent at best. The speed changes constantly and usually after about 5 minutes it times out in which case I have to

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2009-01-02 Thread Cliff
FYI, I have just tested WPA2 on Windows XP on this laptop and it connects fine, so the hardware is capable of connecting to WPA2. I have a multi-boot setup and XP connects fine every time, but Ubuntu 8.10 etc. never connects. This particular test was of the Ubuntu 8.10 that I have permanently

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-12-09 Thread Cliff
@Chris Jackson I have just retested WPA2 (not WPA+WPA2) on 8.10. I cannot connect with WPA2. I can connect just fine with WPA. I even tried forcing AES or TKIP with WPA2. No dice. I have an RT2860 PCCARD that I test with in this same laptop and it connects fine to either WPA or WPA2

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-11-29 Thread Tom Dunham
I am able to run Intrepid with kernel 2.6.27-9-generic and ndiswrapper 1.53 with a BCM 4306 (rev 02) in an old compaq presario. I can connect well with excellent data rates but only with WEP security. Can't connect with WPA or WPA2. I can enable WPA or WPA2 separately on the access point, but

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-11-15 Thread Chris Jackson
I have had similar problems connecting with an HP 2517cl with the BCM4322 - I am running Intrepid with kernel 2.6.27-8.17 and ndiswrapper 1.52-1ubuntu1. After reading the workaround above to disable WPA/WPA2 on the accesspoint and use only WPA, I when to my AP ( a Belkin G ) and and found only an

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-11-13 Thread Nayr
Thanks Cliff worked perfectly. Ryan -- ndiswrapper bcm4306 rev 2 won't connect regression https://bugs.launchpad.net/bugs/276980 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-11-02 Thread Cliff
All facets of problem recreated with 8.10 Intrepid release: - Native driver for bcm4306 rev 2 wifi (ssb/b43legacy) is _severely_ crippled. It averages 75k bytes per second with many stalls as tested with scp. - Ndiswrapper/bcmwl5 (built in Broadcom 4306 rev 2 hardware) will not connect to a

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-11-02 Thread Cliff
Here is the syslog for the previous post ** Attachment added: syslog.log http://launchpadlibrarian.net/19237596/syslog.log -- ndiswrapper bcm4306 rev 2 won't connect regression https://bugs.launchpad.net/bugs/276980 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-11-02 Thread Cliff
VERY IMPORTANT INFORMATION JUST DETERMINED... (sorry for the caps but it is that important) Disable WPA2 in your wifi access point and enable just WPA and then your ndiswrapper/bcm4306rev2 problems will go away. (I had my wifi access point set up to allow both WPA and WPA2.) Ndiswrapper with

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-10-30 Thread Arthur
great information Cliff. i too have the BCM4306 rev 2 and cannot get it to work in intrepid using the b43legacy in the restricted drivers manager. very sad, this laptop has never been able to function with its internal wifi and ubuntu. i will hope that this will someday be fixed, but i'm

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-10-11 Thread Cliff
Tested Intrepid Beta (live version). - I purchased a different PCCARD Wifi card (RT2680 based) and it works well with ndiswrapper, proving that this regression is one that is limited to the BCM4306 rev 2 (and possibly related) hardware. I recall in much older versions of Ubuntu that the

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-10-02 Thread Cliff
The only work-around I have found is to disable WPA. I went to a completely open system with no auth and no encryption and it worked. iwconfig wlan0 essid x mode managed does not help. Here is my lshw -C network (while connected to an open WiFi AP): *-network:0 description: Wireless

[Bug 276980] Re: ndiswrapper bcm4306 rev 2 won't connect regression

2008-10-01 Thread Cliff
** Attachment added: dmesg from Intrepid Alpha 6 http://launchpadlibrarian.net/18129028/intrepida6.dmesg -- ndiswrapper bcm4306 rev 2 won't connect regression https://bugs.launchpad.net/bugs/276980 You received this bug notification because you are a member of Ubuntu Bugs, which is