I have successfully installed 10.8 ML on following configuration :
- Gigabyte H67A-UD3H-B3
- Intel Core i7-2600K with HD3000
I use a DSDT from tonymacx86 for my mainboard (bios version F8). I patched it to change the HD3000 model identifier from 0x0122 to 0x0126 so the HD3000 gets enabled with QE/CI.
Additional devices works correctly :
- ACL889 soundcard
- Realtek 8167
I want to use a DWA-547 (PCI Card) to connected to my home WLAN. As far as I read, this card is supposed to works ootb.
It didn't showed up in the PCI Card section of System Profiler. The card has pci168c,29 as PCI identifier (ioreg provides this information). I had to add the PCI card EFI String to org.chameleon.Boot.plist so it got detected.
After rebooting and doing the kext stuff, the card shows up in the system profiler (capture1.png).
To force the usage of the Atheros kext, I added to IO80211Family.kext/Contents/Plugins/AirPortAtheros40/Contents/Info.plist the following identifier.
Next reboot, tadaaa !... the Airport logo shows up in the taskbar and the AirDrop one in the Finder. I can detect my wlan network (capture2.png).
After trying to connect to my wlan a first time, I get a Kernel Panic...
I tried another wlan kext : IO80211Family.kext/Contents/Plugins/AirPortAtheros21.kext which have the pci168c,29 identifier in its Info.plist (nothing to change). The card is detected exactly the same way as with as with the AirPortAtheros40 kext. (capture2.png)
The initator of the kernel panic (with debug=0x01 boot flag) is :
panic(cpu 6 caller 0xffffff800029dadb): "TLB invalidation IPI timeout: ""CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x3, NMIPI acks: orig: 0x0, now: 0x2"@/Source/Cache/xnu/xnu-2050.9.2/osfmk/x86_64/pmap.c:2337 Debugger called: <panic> Backtrace (CPU 6), Frame : Return Adress
It exactly happens like this :
- Airport > Activate Wi-fi
- Select mywlanssid
- The adapter gets connected
- about 10 seconds after... KP
When I leave Aiport off or if I don't connect to the access point, there is no KP at all : the machine remains rock stable.
Does anybody have a clue what could cause this kernel panic ?
Thanks in advance.