I'll chime with another me too. BCM4306 rev.03 doesn't work. Doesn't
show networks in KNetworkManager, doesn't connect to manually configured
AP. It's screwed up. Is anybody actively working on this bug? It makes
Kubuntu-on-the-laptop much less usable... :-(
--
bcm4306, bcm4309, bcm4311, bcm4312
After my last report, I removed all packages associated with
broadcom4306 and then re-installed from source following the
instructions at http://www.linuxwireless.org/en/users/Drivers/b43
Since then my wireless has been working better than any time since I
installed hardy (beta4), not dropping
** Also affects: linux (Baltix)
Importance: Undecided
Status: New
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
You received this bug notification because you are a member of Ubuntu
Bugs, which is
same thing happens to me and it doesn't seem related to ASUS. I've an HP
zd8000 and `lspci -vvv` lists the wireless card as:
--cut
0b:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
Subsystem: Hewlett-Packard Company Presario R3000
If this problem is due to the ASUS hack mentioned earlier, a fix for
that has been submitted to the Ubuntu Kernel Team. I will be watching
this bug for progress.
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
You
Interestingly, my wireless fails completely now. I think this might be
since the last kernel upgraded (to 2.6.24-17). Knetwork manager
recognises that the device exists, however it won't find any networks,
regardless of what I do. As soon ad I modprobe either b43 OR bcm43xx,
knetworkmanager
Hi.
I'd like to confirm the issue with the Asus-based bcm4318 card as
already described in full length above. Some details follow, but nothing
new which has not already been told.
Using a fresh installation of Kubuntu Hardy 8.04 on a Dell Inspiron 531.
~$ uname -a
Linux gromp 2.6.24-16-generic
@krop
I had the same problem as Jimmey described. My broadcom 4306 v03 was working
under Gutsy (probably with bcm43xx), and then I did as suggested
- Blacklisted b43 and ssb in /etc/modprobe.d/blacklist
- authorized bcm43xx
- reinstalled the bcm43xx-firmware
reboot; wireless did not work
then
[quote]
sudo modprobe -r b43
sudo modprobe bcm43xx
[/quote]
That just means you're using the same workaround : unloading the b43
module and loading bcm43xx instead.
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
Actually not. b43 being blacklisted it isn't loaded at startup (I verified
it)
On the contrary I unload bcm43xx
load b43
unload b43
and then load again bcm43xx
It seems to me that b43 does some kind of initialisation which allows iwlist
scanning to work but not to associate with an AP. Then by
That is what is bug report is talking about.
We *know* bcm43xx is working... bcm43xx is now deprecated and will be removed
in future kernels.
The way you load or unload b43 or bcm43xx is irrelevant. The problem remains
the same : some wireless cards are unable to associate with their AP in
[quote]That is what is bug...
That is what this* bug... (sorry)
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi guys,
i have same problems with the b43 driver. I have a „Asus WL-138G v2“
wlan pci card. I can scan network but i can't connect. In the kernel log
I see timeouts . On ubuntuusers more than me have the same problems
(http://forum.ubuntuusers.de/topic/168892).
I have test it on an upgraded
Originally, I had the same problem - Dmesg reported that with b43 and
the correct firmware installed, using network-manager to try to connect
to my WPA protected network, the attempts to associate with the access
point would repeatedly time out.
Using Hardy Heron with 2.6.24-16-generic kernel.
Sorry for the double post, didn't figure out how to (if it's possible)
edit a comment.
Something pretty strange just happened to me.
I got the connection working fine - as posted above - so I restarted the
computer.
It came back up and the wlan0 was missing.
I tried all kinds of combinations
Sorry, it seems that removing then reloading the bcm43xx isn't enough -
I had to
sudo modprobe -r bcm43xx
sudo modprobe b43
sudo modprobe -r b43
sudo modprobe bcm43xx
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
@Jimmey : Actually, that's a workaround, not a solution. It seems this
bug won't be resolved in kernel 2.6.24.
If you don't need b43 nor ssb, blacklist them both. Only bcm43xx will be loaded.
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
Hello Guys:
I did some sniffing around the B43 mailing list and found a lengthy
thread about the ASUS WL-138G v2, which uses Broadcom Corporation
BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev2).
It seems that Asus mucked with the registers (sorry if I am using the
wrong
Hi guys,
I think I have the same bug here.
My details:
* 8.04 Hardy Beta (installed 2 weeks ago or so) with updates to now (April 12
11pm GMT +1)
* Kernel: Linux xxx 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008
x86_64 GNU/Linux (2.6.24-12 and 2.6.24-15 weren't working either)
*
** Summary changed:
- bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
+ bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP
doesn't work.
** Description changed:
+ Note to Triage Team : This bug is NOT about Ndiswrapper, NOT about
+ bcm43xx and NOT about
Hello:
I have an ASUS WL-138G V2 PCI wireless card with the following lspci
stamp:
02:07.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
54g] 802.11g Wireless LAN Controller (rev 02)
When I load B43 (have the b43-fwcutter) firmware all installed, I keep
getting the dreaded:
21 matches
Mail list logo
