attempting v4 firmware loading won't hang the system, i believe. In my case, a hang only came when actually trying to connect to something. I believe the multiple error messages in dmesg occur before the hang, during boot, so it should be possible to detect these problems during card activation At least, that's how I imagine it. The question is, what then? Maybe something like this could be attempted during package configuration? Attempt to activate the card with v4 firmware and try falling back to v3 firmware if there is an error?
-- Broadcom bcm43xx broken with 2.6.20.8 kernel https://launchpad.net/bugs/85099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
