Is it possible your update killed fwcutter?  I would try this
1. download a known good fwcutter
2. download a known good firmware
3. modprobe -r bcm43xx
4. modprobe -r bcm43xx_mac80211
5. modproble bcm43xx
6. dmesg and make sure it loaded the firmware, saw the cores, activated, etc.
7. resume normal life.

If that doesn't work, I would also go back to the 2.6.22-rc4 tree and do make modules_install

Ehud

Chuckk Hubbard wrote:
Hi.
I have a 4311 on a Gateway MX6447. I am running 64studio, an offshoot of Debian. I downloaded kernel 2.6.21 and patched it to 2.6.22-rc4 (for my soundcard), copied the configuration, and made sure all the bcm43xx options were selected. I compiled the kernel, installed bcm43xx-fwcutter, and ran it on wl_apsta.o from http://boredklink.googlepages.com/wl_apsta.o

I entered my wep code and was online for a while. I had added Debian unstable to my repositories, and did an update/upgrade, and immediately after it finished the wireless went down. However, I doublechecked that bcm43xx and /lib/firmware weren't involved in any of the upgraded packages, and the kernel is still my custom kernel. The network dialog still shows eth1 active, still shows the list of APs, and still has the passcode; "iwlist eth1 scan" still shows a list of APs, including mine. The access point was showing as invalid, but after I turned the radio LED off and on, it showed as an address. I've rebooted the system a few times, rechecked everything. Still no errors, still shows as connected, but nothing received. I did try "modprobe bcm43xx" just in case, no difference.

I did try re-cutting the firmware, and now "bcm43xx-fwcutter /lib/firmware ./wl_apsta.o" says that wl_apsta.o has an invalid checksum; however, when I checked the sum under Windows, it told me a different number than what fwcutter said.

Can anyone help me?
-Chuckk

--
http://www.badmuthahubbard.com
------------------------------------------------------------------------

_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to