I have a bcm4318 (rev 2) card.
I cannot get it to work.
The script to install manually also didn't help here.
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/182716
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Running fwcutter manually and a reboot helped me. Thanks!
# sudo /usr/share/b43-fwcutter/install_bcm43xx_firmware.sh
My Info:
# lspci | grep Broadcom\ Corporation
03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev
01)
--
bcm4306, bcm4309, bcm4311, bcm4312 don't wo
So I confirm it is unrelated to what I reported.
The triage team considers that every problem related to SSB are duplicates of
this one for unknown reasons.
I'm very happy we have learnt how to get rid of the wlan0_rename
interface (or at least get a proper name). I'm pleased to see that
ohci_hc
The issue is that ssb and ndiswrapper conflict. b44 relies on ssb, and is
loaded before ndiswrapper. Further, blacklisting will not prevent the b44,
b43, or ssb modules from being loaded.
On Mon, Mar 31, 2008 at 10:49 AM, krop <[EMAIL PROTECTED]> wrote:
> Since b44 is an ethernet module, I don't
Since b44 is an ethernet module, I don't understand how it can be the "same
problem", sorry.
If you don't use your ethernet card, just blacklist b44 or disable it your
computer bios (if possible).
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/1
Same problem here. I have an eth0 (broadcom 4401-b0) which uses module
b44 (and it pulls in ssb) and trying to use ndiswrapper for my wlan0
(broadcom 4328). wlan0 does not work when I load ndiswrapper, and no
error messages. However, if I rmmod b44 and ssb, then modprobe
ndiswrapper, wlan0 gets
First I'm unlinking this kernel bug since they never mention what kind of card
it is, and that fix does not work here.
http://bugzilla.kernel.org/show_bug.cgi?id=9402
I'm unlinking the Mandriva bug too, because that's about ssb loading when it
should not be, and that does not appear to be the is
Right. as of an upgrade yesterday, my card is no-longer being picked up
at all by knetworkmanager. I can't see any wireless networks.
attached is all the packages that I upgraded (or installed) yesterday,
from dpkg.log
** Attachment added: "dpkg.log.08.03.26"
http://launchpadlibrarian.net/1290
Yeah, ndiswrapper and bcm43xx seem to still work (mostly), so that's good.
@ krop, thanks for doing that. It's not specific to WPA, though... I get the
same with WEP. Probably unencrypted, too.
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/1827
This affects BCM4328 as well.
My solution is as follows:
rmmod b43
rmmod b44
rmmod ssb
rmmod ndiswrapper
modprobe ndiswrapper
modprobe b44
___
This fixes all troubles. SSB will load no matter what (even when
blacklisted) so the only solution I
I sent a message to bcm43xx-dev mailing list with a link to this bug
report. The answers should be readable here :
https://lists.berlios.de/pipermail/bcm43xx-dev/2008-March/007090.html
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/182716
You recei
Yeah, naught101 has a different card. krop and I have the same one. I guess
that's the difference?
So is it just this one card specifically or do other cards have the same
symptoms?
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/182716
You rece
@nattgew : I am using WPA and have the issue.
@naught101 : Thank you for your report. We have the same chipset (on different
pci cards). What I thought is now confirmed : this chipset *uses* b43 and not
b43legacy despite the rev. being < 4.
02:09.0 Network controller [0280]: Broadcom Corporatio
ignore that last sentence .
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/182716
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
I can successfully connect to my home network with wlassistant, but the
automatic dchp connection doesn't work, and I have to run "sudo
dhclient" after connecting. But it still seems to be dropping out
regularly (ever few minutes), and generally having trouble connecting to
websites, even though I'
Ok, thanks for the info.
I'll attempt a configuration with WPA sometime tonight or tomorrow (or the next
day?) to see if it works with that and not WEP.
Have you tried removing or killing network-manager (killall nm-applet), and
configuring it with the Gnome tool or command line?
--
bcm4306, bc
dmesg attached.
Today I cannot connect to my home wireless at all. It uses WEP. Since
installing hardy I've always been able to connect to my girlfriend's
home network, which uses WPA.
I'm getting lines like this in my system log:
24/03/08 13:08:27 naught101-laptopavahi-autoipd(wmas
Ok, can you do a dmesg for us? Maybe right after you boot and it works?
Also, have you updated from Alpha 6?
Yes, b43legacy should be it, but for me it does nothing. I find that b43 works
but gives the "link not ready" message.
I ran my Beta... did all kinds of module loading... got nothing. I
all I did was install from alpha6, then run the FWcutter script at
/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh
and it worked.
as far as I can tell, I SHOULD be using b43legacy, right? should all the
cards in this bug run under b43legacy?
ned
Nattgew wrote:
> That's odd that yours works
That's odd that yours works and ours don't... did you do anything special?
I did a base install of the Beta, put in the firmware for bcm43xx, rmmodded b43
and ssb, loaded bcm43xx, and updated and stuff over the wireless. I then
rmmodded bcm43xx and loaded b43... no go. This is what I had:
**
My bcm4306 rev 03 works reasonably well (drops out a lot on my home
network), with b43/ssb (NOT b43-legacy). Seems wierd, but it's true :)
(although I started this morning, and knetworkmanager isn't showing
up..)
happy to do testing if requested (be specific)
[EMAIL PROTECTED]:~$ lsmod|grep b43
b
@monoi: I am using the BCM4311 card with b43-fwcutter on Hardy beta.
With the same symptoms as many others in this thread are getting. My
post is FYI only to help solve this problem, wherever its root cause is.
Thanks, i'll investigate furher.
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with
Here's the working solution data.
** Attachment added: "WLAN Working network-manager 0.6.6-0ubuntu1"
http://launchpadlibrarian.net/12826076/WLAN%20Working%20network-manager%200.6.6-0ubuntu1
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/182716
I think that someone with the NM bug should report that. I had this bug
regardless of NM.
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work with b43 / ssb
https://bugs.launchpad.net/bugs/182716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
@ Juksu: I think your issue (which is identical to the one I saw) might
be the same as the one logged in https://bugs.launchpad.net/bugs/205259.
This thread is for a separate issue with the b43/b43legacy driver itself
and BCM4306 rev 03 cards.
--
bcm4306, bcm4309, bcm4311, bcm4312 don't work wit
Maybe we should split the networkManager bug and the "timeout when
authentificating" one since they don't seem to be linked ?
Look at the dates, I've been experiencing this issue for more than two
monthes now. The bug NM users have appeared a few days ago.
--
bcm4306, bcm4309, bcm4311, bcm4312 d
26 matches
Mail list logo
