Jump to content
5 posts in this topic

Recommended Posts

Well, I recently got delivery of my squeaky-clean retail copy of Snow Leopard, and managed to install it on my machine (which I'd bought, already Hackintosh'd with Leopard, from some dude on Kijiji, and subsequently upgraded parts of) using Empire EFI 1.08. Some things about this upgrade have been easier than they ever were with my Leopard install — for instance, enabling support for my video card (specs below) was a matter of checking one of the .kexts in the myHack installer, whereas before I'd had to go through the whole rigamarole with Windows, ROM images, EFI strings, etc. Anyway.

 

All is not well in Snow Leopard Land, however. Surprisingly, my wireless network card, which has never quite fully worked under Leopard (i.e. it'll only join a network via Network Diagnostics) worked as well as if it were a bona fide AirPort card under 10.6.0. Score! Well, not quite.

 

To avoid running into various scary bugs, I quickly upgraded to 10.6.2. After replacing the SleepEnabler.kext to get around the kernel panic, I logged in to discover that the wonderful support for my wi-fi card had vanished, leaving a hollow, lonely wedge sitting in my menu bar. Clearly, my chipset had dropped out of Apple's favour at some point between 10.6.0 and 10.6.2. I tried rummaging through the installer DVD using Pacifist and replacing IO80211Family.kext with the older version (I couldn't find any other wireless-related kexts in the Snow Leopard partition or the DVD), and while that thankfully doesn't seem to've broken anything further, neither has it fixed anything. Dang, I was sure that woulda worked.

 

There are also some less pressing issues present: the motherboard's onboard audio isn't recognized (it is in my Leopard install, but I don't want to just copy that kext over to SL without checking first); and, while sleep does sorta work (which is a huge improvement over the state of things in Leopard), the power light stays green instead of turning orange like it should, and the power supply's fan can still be heard running.

 

I greatly appreciate any insight you fine folks can provide. I've already done three fresh installs of SL so far (after various missteps), so I'd like to see if I can make this work after all. On to the juicy stuff!

 

Specs

 

Motherboard: ASUS IPILP-LC

Processor: 1.6 GHz Intel Core 2 Duo

RAM: 2.5 GB 667 MHz DDR2 SDRAM (1x2048MB + 1x512MB)

Graphics: nVidia GeForce 9500 GT 512MB

Audio: Onboard Realtek ALC888

Wireless: D-Link DWL-G510 (Atheros AR5212 chipset)

 

Software

 

Mac OS X 10.6.2 Snow Leopard — retail install of 10.6.0 using Empire EFI 1.08, upgraded using downloaded Combo Update installer package

Chameleon 2 RC3 bootloader (installed using myHack package)

Kexts in /Extra/Extensions:

- fakesmc.kext

- FramebufferDisabler.kext

- LegacyAppleRTC_32bit_Only.kext

- NullCPUPowerManagement.kext

- OpenHaltRestart.kext

- PlatformUUID.kext

- SleepEnabler.kext

 

(Edit: I guess my main question is, are there any other files from the 10.6.0 DVD that I should be looking at in order to bring back the support for my card? Or any other relatively clean methods to get SL on speaking terms with it again?)

 

(Edit 2: Edit Harder: Issue has been solved. Thanks anyway, folks.)

  • 4 weeks later...

hello, i have the same deam problem with my wireless card. i dont know what to do, well may be buying a new one, i have a jensen air link 7354 (im from norway and i got this card from mymother) ive been looking and i think that the card uses atheros chipset. i dont know what to do, i replaced the iofamily kexts but nothing happened.

som help please ?

thanks

I was able to resolve this problem a while ago and just forgot to post about it here, sorry. :(

 

After perusing some more forum threads here, I downloaded Netkas' AtherosFix.kext (it can be found pretty easily by searching its name; one such occurrence is here). I was fortunate in that I have an existing Leopard installation where the card already worked, so I was able to go into System Profiler and look up the Vendor and Device ID for my card, and then add it to the Info.plist of the aforementioned AtherosFix.kext, which I'd placed in /Extra/Extensions. (In my particular case, it was pci168c,3a13) If you don't have that, you may be able to use Windows (or, I'm sure, even Linux) to look up that information, as the system reads it from the card itself.

 

Looking in my SL drive to double-check, it is indeed only the AtherosFix.kext that's had its Into.plist changed, not the Apple kexts in /System/Library/Extensions.

 

Happy to report that the D-Link card now works flawlessly, as if it's a native AirPort card. The audio, sadly, is another matter. :P

I was able to resolve this problem a while ago and just forgot to post about it here, sorry. :D

 

After perusing some more forum threads here, I downloaded Netkas' AtherosFix.kext (it can be found pretty easily by searching its name; one such occurrence is here). I was fortunate in that I have an existing Leopard installation where the card already worked, so I was able to go into System Profiler and look up the Vendor and Device ID for my card, and then add it to the Info.plist of the aforementioned AtherosFix.kext, which I'd placed in /Extra/Extensions. (In my particular case, it was pci168c,3a13) If you don't have that, you may be able to use Windows (or, I'm sure, even Linux) to look up that information, as the system reads it from the card itself.

 

Looking in my SL drive to double-check, it is indeed only the AtherosFix.kext that's had its Into.plist changed, not the Apple kexts in /System/Library/Extensions.

 

Happy to report that the D-Link card now works flawlessly, as if it's a native AirPort card. The audio, sadly, is another matter. :(

 

jesus ! i just runed both of them and magic! airport extreme is on :P

thanks a lot !!

jesus ! i just runed both of them and magic! airport extreme is on :P

thanks a lot !!

Awesome, man! Glad it worked for you too. :P

 

If only the audio were going to be as easy...even System Profiler here on Leopard is saying there's no built-in audio, even though the motherboard audio is working fine, so I can't just pick up the details and type them in. Anyway, that's a matter for another thread, another time. :)

×
×
  • Create New...