not working on Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

I should also mention that I have blacklisted bcm43xx in /etc/modprobe.d/blacklist while trying to get ndiswrapper working.

My laptop is an HP Pavilion zv5405us. More detailed specs here: http://words.haddons.net/archives/000039.html and http://h10025.www1.hp.com/ewfrf/wc/genericDocument?cc=us&docname=c00286662&lc=en&jumpid=reg_R1002_USEN

Thanks, Tom

broadcom wlan on my acer aspire5024wlmi don't run

Tom,\

I also have a hpzv5000 and in breezy I wasn't able to get wpa working, did you ever try wpa?

BTW: I've reported a problem booting and also my mouse isn't being recognized sometimes. The mouse works fine on another laptop also running 6.06 beta but that one is i386 not x86_64. Any problems like that?

Regards,

Wink Saville

I never tried WPA, but WEP always worked fine. I don't have any other
hardware problems, but am running i386, not AMD64. I tried AMD64 in
Hoary but reverted to i386 as I didn't want to muck around with chroots
so much...

Thanks, Tom

On Sat, 2006-04-29 at 16:11 +0000, wink saville wrote:
> Tom,\
>
> I also have a hpzv5000 and in breezy I wasn't able to get wpa working, did you ever try wpa?
>
> BTW: I've reported a problem booting and also my mouse isn't being recognized sometimes. The mouse works fine on another laptop also running 6.06 beta but that one is i386 not x86_64. Any problems like that?
>
> Regards,
>
> Wink Saville
>

Tom Haddon
mailto:<email address hidden>

You will hear good news from one you thought unfriendly to you.

-----------------
Random quotes courtesy of fortune.

Eh, why is the version of ndiswrapper-utils at 1.8 while the version of the ndiswrapper kernel driver at 1.15 or 1.16? It's pretty important that these be similar. Try upgrading your -utils to 1.15 or 1.16, and see if it still happens.

http://http.us.debian.org/debian/pool/main/n/ndiswrapper/

The version numbers of the utils and the module are no longer in sync. As far as I know 1.8 is the latest version of the utils.
Download the source and check yourself.

Could you explain how to do that, or point me in the direction of a
how-to?

On Tue, 2006-05-16 at 18:35 +0000, Andreas Gnau wrote:
> The version numbers of the utils and the module are no longer in sync. As far as I know 1.8 is the latest version of the utils.
> Download the source and check yourself.
>

Tom Haddon
mailto:<email address hidden>

It may or may not be worthwhile, but it still has to be done.

-----------------
Random quotes courtesy of fortune.

Hey everyone,
  After much tears and many blurry eyed hours staring at forum posts, I got the native bcm43xx driver to work. Essentially, ndiswrapper and bcm43xx conflict, so if you upgraded from Breezy (like I did), then Dapper now tries to load bcm43xx, which is why ndiswrapper does not work. You have two options, outlined here:

https://wiki.ubuntu.com/WifiDocs/Driver/bcm43xx

Just look at the section for Dapper. I got my BCM4306 (dell branded) card to work by removing all traces of ndiswrapper and then using the firmware package provided in the link. That was the real crux-I was trying to use the same version as the one on my windows partition, but it kept failing. Installing the deb, and then manually copying the firmware files from /usr/lib/firmware/bcm43xx to /lib/firmware and following the rest of the guide did the trick for me. (For some reason, the dpkg-reconfigure for that package wasn't working for me, so I manually copied it over).

Btw, eth1 is now the wireless device (when using bcm43xx at least).

Hi Jason,

First of all, congrats on getting it working finally!!

My question is, which deb package are you using? I tried wget
http://ubuntu.cafuego.net/pool/bcm43xx/bcm43xx-firmware_1.1-0ubuntu1_all.deb

and when I installed, there was no /usr/lib/firmware/bcm43xx, and none
of the files in /lib/firmware had today's timestamp on them as if they'd
been created through the install of the package.

Am I missing something? Seems like I'm so close here, and would love to
finally get this working...

Thanks, Tom

Hey Tom,
  I just realized I'm using an older version of the firmware, but at this point, whatever works, right? I used this one:

http://ubuntu.cafuego.net/pool/bcm43xx/bcm43xx-firmware_1.0-0ubuntu1_i386.deb

which should place the firmware files under /usr/lib/firmware/bcm43xx

I then removed all bcm* files from the /lib/firmware/ directory and then copied all the files from /usr/lib/firmware/bcm43xx to /lib/firmware. I then rebooted and it worked like the guide.

Good luck,
-jason

Thanks, I'll give that a try.

Tom

Still didn't work for me.

sudo iwlist eth1 scan returns no results. I've tried the firmware that's listsed in the wiki (which I think is newer than the one you mentioned) and also the one you mentioned and neither brought me any better results.

This is getting desperate. I don't know how long it is before I try another distro...

You are using a bcm4306? Usually when I sudo iwlist eth1 scan and get no results, then that means my wireless was disabled when I loaded the bcm43xx module... are you sure its enabled?

That being said, I have to agree Ubuntu's wireless for the bcm43xx series is abit flaky ... my connection is somewhat unstable - sometimes it works great, other times it seems to stall. I think this can be traced to the softmac authentication... But sorry, I don't have any simple answer for you. When you replaced the firmware, did you reload the module (ie rmmod bcm43xx and then modprobe bcm43xx)? I find that I usually have to do a `sudo ifdown eth1 down` and then a `sudo ifdown eth1 up` after the module loads for it to correctly load my settings...

Sorry, hope this helped somewhat, but I'm still kind of confused as well...

If I do rmmod bcm43xx and them modprobe bcm43xx it doesn't seem to do much for me, and I get this in dmesg:

[4297699.848000] bcm43xx driver
[4297699.852000] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNK3] -> GSI 17 (level, low) -> IRQ 225
[4297700.259000] ADDRCONF(NETDEV_UP): eth1: link is not ready

The dreaded "eth1: link is not ready"

Fraid it doesn't seem to be working for me still (I even tried the ifdown eth1 down/up sequence)...

Actually, I do get the same message. I think I've isolated it down to the SoftMAC (firmware/program?) Evidently, eth1 is not ready because softmac has not yet authenticated with whatever ap you're using. What happens for me is that I cannot get a dhcp address until the softmac authentication message appears in the dmesg output. When it does, then I can connect. Try doing something like setting up all your settings, having associated with your AP by using either the iwconfig or ifconfig eth1 up commands, but then wait. If the message that "SoftMAC: Open Authentication completed with XX:XX:XX:XX:XX:XX" appears in the dmesg output, then then do a sudo ifdown eth1 and then a sudo ifup eth1. The basic thing is to be patient - the SoftMAC message needs to appear (at least it does on my machine). Also, are you using the bcm43xx script someone posted on the ubuntu webpage in conjunction with ifup? It calls for a sleep command between iwconfig statements, which i think is useful for the firmware to catchup to the computer...

Well, it turns out we can file this one under user error. Apparently all it needed was to press the Wireless "button" (which I didn't even know was a button, and have never used it before), and now it's working fine.

Sorry :(

User error - needed to press the wireless button itself to activate it. Didn't know it even was a button, so there's something new...