Jump to content
8 posts in this topic

Recommended Posts

Has anyone with a card that Mac OS X picks up as an airport extreme been able to run the enabler successfully?

 

My card (Netgear WN311B) has the Broadcom BCM4321 chipset and was picked up by OS X as an AirPort Extreme as soon as I popped it into the computer. For giggles I tried the enabler, only to find out that I needed the AirPort Extreme update first, so I grabbed that, and it changed the description of my card from supporting only 802.11g to 802.11 a/b/g.

 

I still get an issue trying to run the enabler, though.

 

 

This is the install.log I see after I try to open the package:

 

Feb 16 08:55:04 mck-mac : @(#)PROGRAM:Install PROJECT:Install-141 DEVELOPER:root BUILT:Jul 13 2006 20:14:15\n

Feb 16 08:55:04 mck-mac : @(#)PROGRAM:Installer PROJECT:Installer-94 DEVELOPER:root BUILT:Jul 2 2006 00:22:31\n

Feb 16 08:55:04 mck-mac : Hardware: ADP2,1 @ 2210 MHz (x2), 2048 MB

Feb 16 08:55:04 mck-mac : Running OS Build: 8L2127

Feb 16 08:55:04 mck-mac : AirPort Extreme 802.11n Enabler Installation Log

Feb 16 08:55:04 mck-mac : Opened from: /Volumes/AirMac Extreme 802.11n Enabler/AirMac Extreme 802.11n Enabler.pkg

Feb 16 08:55:04 mck-mac : Distribution: AirPort Extreme 802.11n Enabler

Feb 16 08:55:04 mck-mac : It took 0.239189 seconds to finish launching.

Feb 16 08:55:04 mck-mac : Installation checks failed.

Feb 16 08:55:04 mck-mac : Installation check failure. (null). Your computer does not meet the hardware requirements for this update..

 

 

Any idea if this might be caused by a cpu check hidden in the .dist file? I looked in the various Info.plist files and didn't see any requirements to edit out, unlike the Parallels 3150 install.

 

If anyone has some ideas or knows a potential way around it, it would be cool to see this working :thumbsup_anim:

For fun, really. It uses the same innards, I believe.

 

 

The Netgear router associated with this particular card is eerily similar to the Airport Extreme, also.

 

Figured it was worth a shot, and the airport update worked perfectly.

 

The other reason I tried is because it wasn't clear that it was an update to the firmware, I thought the feature could have been disabled in software in Apple's driver for the airport extreme cards.

 

If it really is a firmware update as you say it is, then of course it isn't going to work with the card. I had just thought since OS X thinks Apple makes my card, that it would be worth a try :thumbsup_anim:

Edited by Andrmgic

I tried extracting the driver from the archive.pax.gz inside, but it doesn't seem to work when I put it into extensions, there is a .dist file in there, but I'm not sure how or if it is even possible to open those up. I've pretty much given up hope of it working at this point

Greetings,

 

The Airport Enabler flashes the firmware on the actual network adapters shipped with the Core 2 systems (The adapter itself can handle 802.11n) and allows the system to see it as a draft n card. If your card has n capabilities it might be a while, you could modify the kext and try to match vendev ids but chances are nill, the kext will most likely being using EFI firmware on the network card just as their video cards. I personally think this is a useless venture, you would be better off finding the flags used to report your card as an n card and modify the wireless kext currently used to report this feature, just then might your "extreme" card work.

 

Regards,

 

{censored}-x

×
×
  • Create New...