[Bugme-new] [Bug 20822] New: Poor wireless scan results with WUSB54GS (BCM4320a)
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Wed Oct 20 15:43:19 PDT 2010
https://bugzilla.kernel.org/show_bug.cgi?id=20822
Summary: Poor wireless scan results with WUSB54GS (BCM4320a)
Product: Drivers
Version: 2.5
Kernel Version: 2.6.36-rc7
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: network-wireless
AssignedTo: drivers_network-wireless at kernel-bugs.osdl.org
ReportedBy: Pitxyoki at gmail.com
CC: jussi.kivilinna at mbnet.fi
Regression: No
When using iwlist scan, this device shows very few results comparatively to
what would be expected.
If I do a scan right after booting (to ensure there are no caching or other
optimizations taking place), I see only two or three SSIDs. If I keep retrying,
it can take a long time until my network's beacon is detected. NetworkManager,
for example, usually takes 20 to 30 minutes until it finally detects the
correct SSID and is then able to establish the connection.
Even without previously detecting the beacon, I can use iwconfig to set up the
device and connect to my network (see bug#20152 ). Once it is established,
there are no problems with the connection: it's fast and stable, so I can't say
that the long time to detect the beacon is related to a long distance or weak
signal. When the connection is established, subsequent scans always show my
network's SSID (out of a total of three or four SSIDs).
Also, my laptop is usually placed at about one meter from this device (it has
an Intel Wifi Link 5100 device -- iwlagn driver). After a cold boot it shows
15~20 networks right on the first scan, including my own network. This makes me
think that the BCM4320a driver is really not detecting well all these beacons
and that it's not just a problem with my setup.
Best regards,
Luís Picciochi
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Bugme-new
mailing list