Bcm Wireless Drivers For Mac
Update: 2009-04-29 4:39PM Since it seems to be sort of difficult for new users to edit kext-files, I've written a small script which automatically adds the PCI IDs of all Broadcom wireless cards, which are AirPort compatible. And this is where I need your feedback: Please post your Broadcom device IDs in this topic, if you have simply added them to the AppleAirPortBrcm4311.kext. Then I can add them to my script so new users can simply download the script and get their Broadcom wireless card to work. So please post the PCI ID and maybe a little description (at least if the card is 802.11a, b or g).
Note: Only post the PCI ID if you simply have to add the ID to AppleAirPortBrcm4311.kext in order to get it working! Which version of Mac OS X are you using? Did you try it with the JaS install DVD? What does dmesg say? Can you give a dump of your syslog?
I don't really think that the AirPort-driver is the cause for the crash. I'll answer this as I am in a similair situation. The results are the same no matter which distribution I use. If I have my BCM4311 mini PCI express card installed OS X crashes at boot. Am currently on my desktop so don't have the exact error message in front of me, but basically it gives a kernel panic when it tries to load the IO80211 kext. I have tried installing the kext from different versions including 10.4.6,.7,.8, and of course.9. It is just very odd as this is the closest one can get on a Hackintosh to having a true airport card.
It even has the exact same 14e4,4311 device/vendor ID. I'll answer this as I am in a similair situation. The results are the same no matter which distribution I use. If I have my BCM4311 mini PCI express card installed OS X crashes at boot.
Am currently on my desktop so don't have the exact error message in front of me, but basically it gives a kernel panic when it tries to load the IO80211 kext. I have tried installing the kext from different versions including 10.4.6,.7,.8, and of course.9.
It is just very odd as this is the closest one can get on a Hackintosh to having a true airport card. It even has the exact same 14e4,4311 device/vendor ID. This is extremely odd. I have never experienced this behavior. Did you try to delete the AppleAirPort2.kext??? Are you using a laptop (internal Broadcom card) or are you trying to install this card in a standard mini PCI-Express slot of your desktop PC's mainboard? Anyway, actually it should not matter at all, I could imagine that this is a PCIe related issue.
OK, I tried deleting the AirPort2.kext and still the same results, kernel crash. I have been able to leave my 4311 card in now without causing a kernel crash. I am still unable to get the card to power on though. Here is how I got around the kernel panic: 1. Just got a new HD so performed a fresh install with Uphuck 1.3 10.4.9 release. (Leave the card out of the laptop for now) 2. DO NOT Install the 10.4.5 80211 kext at installation.
Completed install as normal. Applied all updates (i.e.
Bcm Wireless Drivers For Mac
Security Update 2007-005, Airport update, etc.) 5. Using the Uphuck 1.3 DVD install the 10.4.5 80211 kext 6. Install wifi (Ubuntu recognizes the card as a 'Dell Wireless 1390', Hardware ID 0x14e4,4311 You will now be able to boot with the card installed and NOT get a kernel panic. Unfortunately this still does not do any good as it seems like the only way to bring the radio online is through Windows.
Ub down for mac. Even Ubuntu sees the card, but can make zero use of it. Even Ubuntu sees the card, but can make zero use of it.
BTW: Of course you could use this card with Linux. But the bcm43xx kernel module requires you to install the required firmware manually (using bcm43xx-fwcutter). Since the firmware is not open source it can not be included in a standard Linux distribution. Check the bcm43xx-fwcutter manpage.
Sierra Wireless Drivers For Mac
Darwin probably crashes because it expects the card to be turned on. There has to be a pretty crappy software power switch in the card you are using.
This is the only thing I could think of right now. I am beginning to think this is NOT a problem with the card itself. I am thinking more along the lines of the mini PCI express bus is not being properly recognized. Unfortunately that is beyond my skill level to address. It would be great if one of the guru's looked into this problem. It may be something as simply adding the proper device and vendor ID to the appropriate kext file.
That is totally just a guess at this point though. I suppose the clencher would be finding another mini PCI-E wifi card and testing it.