followed instructions here:http://hp2133.umsw.de/
the problem was b43-fwcutter step did not recognize the firmware.$b43-fwcutter -w /lib/firmware/ broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
This file has an unknown MD5sum

The 4312 seems to be a LP PHY, so a little different than what the kernel knows about already. There’s already enough code in the wireless-testing kernel tree thanks to Michael Buesch (but EXPERIMENTAL and BROKEN) to get the chip operational, and recognised by NetworkManager, by alas, 95% of the setup code is needs to be written.

I'm happy for you that something worked at last. But it's probably important for you and future readers of this thread to remember that Fedora has sort of a strict FOSS policy. I don't believe that Ubuntu encumbers itself that way. In fact, Ubuntu's published philosophy and license policy admit that some binary drivers are included with Ubuntu. That may very well account for stories like yours here about things "just working" with Ubuntu. Next, Fedora just isn't for everybody to begin with. It's kind of a testbed for Red Hat to "incubate innovative new technologies". So it's not uncommon for a new release to have busted stuff all over the place. To me, it's almost comical to sit back and listen to the eruption of calamitous cacophony perfectly timed with the release of a new Fedora version every spring and fall. Whereas Ubuntu's published philosophy appears to include spreading itself "to all parts of the world". So I don't really believe it's completely fair to describe Ubuntu as a "fix" for something broken in Fedora. But I think I do understand how you feel and what you meant. Anyway, I "grew up" with Red Hat and Fedora. I dearly love it. And I think that's required in order to use it.

Great points stoat.
Fedora and Ubuntu have some slight and important trade-offs for purpose of serving their guiding philosophy. This problem that is the topic of this thread is emblematic of that trade-off.

I too grew up on Red Hat linux (and now Fedora). I still run it on my home server. And I still love it.
Based on the quote in my second post above, it appears there is currently no way for F11 to work with the BCM4312 hardware. Therefore, the only reasonable "fix" (even after spending at least a total of 14 hours on this, including install time) was to install Ubuntu.

I know you're probably "fed up" with all of this for now. But if you ever want to try again someday, one thing missing from all that stuff that you tried in the first post is the binary version of broadcom-wl found in the RPM Fusion Non-free repositories. Your post clearly shows that you tried compiling it yourself, but it appears to have failed, I guess. All of the other attempts (including the Dangermouse thing) are b43 methods but with various Broadcom driver files for the firmware. Since you probably aren't abandoning Fedora, you might want to try this idea someday. Chris Nolan (aka BlueC around here) did a lot to teach us how to use it and tweak it in the early days of it, and now maintains those binary packages at RPM Fusion. See his web site here...

What is not always clearly understood is that there are three versions of the broadcom 4312 hardware. When lspci reports 4312 it conceals those differences. Unfortunately, even lspci -vnn doesn't reveal one of the differences.