Jump to content
6 posts in this topic

Recommended Posts

I've installed a 1000h following this guide (iDeneb 1.4):

http://www.enik.ch/2009/03/osx-leopard-105...-the-eee-1000h/

 

However, the broadcom card (BCM94321MC) doesn't seem to be recognized by OS X, even though it's used in Macbooks and should (?). Do you guys have any ideas of why?

It seems as it is detected until I apply the DSDT that comes along the package inside the guide. However, I'm not sure how to fix it.

 

EDIT: If I run OSx86 Tools Utility and View PCI Device/Vendor ID, I see the Broadcom card, but I'm not able to use it within my iDeneb install. I've also tried to repair permissions without success.

 

lspci reports as follows:

01:00:00 Network controller [0280]: Broadcom Corporation BCM4328 802.11a/b/g/n [14e4:4328] (rev 03)

I found the solution to get the card to show up as an Airport device. I needed to disable Boot Booster in bios.

 

However, there's new problems :( Whenever I try to join a network that's encrypted I get 'Connection timeout', I'm unable to connect to it. If I try to connect to my router by disabling the encryption, I get an self assigned IP.

 

If I look at the log messages in Console, this is the following output when trying to connect to a network:

AirPort: Link Up on en0

AirPort: Link Down on en0

Error: Apple80211Associate() failed -6

Error: process_command_dict() failed

Error: airportd MIG failed = -6 ((null)) (port = 59907)

Error joining HomeNet: Connection timeout(-6 timeout connecting)

 

If I look in the system profiler, this is the output of AirPort Card:

Wireless Card Type: AirPort Extreme (0x14E4, 0x88)

Wireless Card Locale: Worldwide

Wireless Card Firmware Version: Broadcom BCM43xx 1.0 (5.10.38.35)

Current Wireless Network: wireless network not available

 

I'm not sure what to do anymore, other people that has the same card has it working. But I can't simply get it.

I had this exact problem with my BCM94306MP; visible as a hardware device, but refused to load / work. I ended up swapping it out for a different revision card, and everything was fixed. The original was a 2001-2002 A00 card, while the working one was marked 2003 and Rev B. Same chipset and card looked exactly the same, but only one worked. This could be what you're running into.

  • 4 weeks later...
×
×
  • Create New...