Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About stevekicks

  • Rank
    InsanelyMac Protégé
  1. AppleHDA for El Capitan discussion

    Hi guys, Up until yesterday I was using VoodooHDA and putting up with the occasional kernel panic until I got my head around DSDT and the aim for a cleaner OSX build. I've got a Gigabyte z77x-ud3h mobo and only using pjalm's DSDT patches for my board (HDEF section attached). Also using Clover as the bootloader in UEFI only mode. It seems the VT2021 codec is a little harder to find info for compared to the realtek chipsets. After trying a handful of AppleHDA kexts from various sites I stumbled upon a working 10.10.4 AppleHDA that works with the VT2021 (attached). I ran the kext through a comparison app to find the differences between a stock 10.10.4 kext and this modified one in the hopes I could edit my own in the future. Discoveries... Contents/MacOS/AppleHDA: 84 19 D4 was replaced with 41 04 06 in two places. Contents/PlugIns/AppleHDAHardwareConfigDriver.kext/Contents/Info.plist: <dict> <key>CodecID</key> <integer>283904133</integer> <key>ConfigData</key> <data> AZcdMAH3HeE= </data> <key>FuncGroup</key> <integer>1</integer> <key>LayoutID</key> <integer>12</integer> </dict> was replaced by <key>CodecID</key> <integer>285606977</integer> <key>ConfigData</key> <data> IkccECJHHUAiRx4RIkcfASJXHPAiVx0AIlce ACJXH0AiZxzwImcdACJnHgAiZx9AIncc8CJ3 HQAidx4AIncfQCKHHPAihx0AIoceACKHH0Ai lxzwIpcdACKXHgAilx9AIqccUCKnHTAipx6B IqcfASK3HGAitx2QIrceoSK3H5AixxzwIscd ACLHHgAixx9AItccICLXHSEi1x5FItcfByLn HPAi5x0AIuceACLnH0Ai9xzwIvcdACL3HgAi 9x9A </data> <key>FuncGroup</key> <integer>1</integer> <key>LayoutID</key> <integer>12</integer> </dict> Contents/Resources: In the downloaded and working kext - it only has two files: layout12.xml.zlib (328 bytes) Platforms.xml.zlib (8341 bytes) vs the stock kext which has the above two files but different sizes: layout12.xml.zlib (1036 bytes) Platforms.xml.zlib (16351 bytes) plus another 90 layoutxxx.xml.zlib files. Applying the discoveries to mod stock El Capitan AppleHDA.kext... The stock 10.11 AppleHDA binary had the same two hex entries which I swapped out for what the working kext has. The stock 10.11 AppleHDAHardwareConfigDriver Info.plist had the same Codec ID entry which I replaced with what the working kext has. As for the layout and platform files - I think this is where might be getting stuck and hopefully one of you fine gentleman can lend a hand. I cleared out all the files from the stock AppleHDA Resources folder and dropped in the two from the working kext (layout12.xml.zlib and platforms.xml.zlib) but the modded kext doesn't give me any sound. Just wondering if someone would be able to point out where I'm going wrong? Or if it is even possible? Thanks in advance! AppleHDA-10.10.4-Working.zip HDEF.txt
  2. AppleHDA for El Capitan discussion

    Hi guys, im trying to get this same codec to work under el capitan but having no luck. lacedaemon's page says he hasn't been around since june - so wondering if there was any chance someone could give a quick rundown on what to edit? I've disabled the codec as per Austere.J's instructions via clover - just not sure what to do next. Thanks in advance!
  3. i have usb problems, fix with dsdt?

    hey guys, i've got 2 PCs at home, both running osx86. my primary machine is running flawlessly - p55a-ud3r, i5 760, gtx 560, 10.7.2 GM, couldn't be happier with it. my second machine is a bit of an after thought. its an old MSI-7255 motherboard (SiS chipset) with a core2duo, 9600GT. so far i've used an ubuntu disc to extract my dsdt and have snow leopard 10.6.8 running nicely. the only major problem i'm having is that my apple usb network adapter only works if i do the following: - open terminal and start 'ping' - plug in the usb adapter if i dont run the ping, it stops working after a minute or two - then needs to be unplugged and plugged back in. mouse and keyboard seem to work fine. not sure if this is something that can be fixed, but i've attached my dsdt in hope that someone can have a quick look for me. thanks in advance! dsdt.aml.zip
  4. OS X Lion 10.7.2 11C71--- 11C73 GM

    awesome thanks. i'll play around with it when i get home... i've attached my dsdt if theres anything that can be done with it... dsdt.zip
  5. OS X Lion 10.7.2 11C71--- 11C73 GM

    cool i'll give those a shot. will it even boot without the dsdt? from memory, i've attempted booting the machine without a dsdt in the past and it always panic'd but will give it a go. here is the -v output if it helps:
  6. OS X Lion 10.7.2 11C71--- 11C73 GM

    hey guy, im having an issue with all the 10.7.2 releases. I get the dreaded "waiting for root device" message... im running a gb-p55a-udr3 with tonymacs DSDT, SSD on the ICH AHCI controller, only using FakeSMC.kext and both Lion 10.7.1 and snow leopard work without any dramas... not sure what has changed in 10.7.2 that's stopping it from booting...
  7. Fermi Graphics Power Management

    awesome thanks man.. that's working now. one thing i've noticed is that when im watching flash videos online, they stop and start every now and then. having a look at the console shows me: that was about 30 seconds of low quality flash with nothing else running. another thing is that my video card fans spin up more with the power management on than when i've removed the kext all together. Maybe these cards aren't meant to be controlled?
  8. Fermi Graphics Power Management

    hey camoguy, thanks heaps for your hard work on this. it's much appreciated. i'm using that file you just posted but am having no luck in getting the card to change modes. when the AGPM.kext is removed from S/L/E, i get full performance. As soon as it's back in with the Info.plist you provided above, it only gets me 7fps in cinebench. The extension seems to be loaded (ie it's in system profiler), but can't see any logs in the console - even though logcontrol is set to 1. this is my ioreg -l | rep attached: "attached-gpu-control-path" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/pci-bridge@3/IOPCI2PCIBridge/display@0/NVDA,Display-A@0/NVDA/AGPM" i'm using a DSDT from tonymacs database. motherboard is a GB P55A-UD3R, card is a 560 Ti. I'm running my system as a MacPro4,1. Any advice or recommendations would be great.
  9. Fermi 5XX works with Lion DP4/GM!

    so i went out and bought a 560 ti, popped it in and didn't work. i read around a did the following: - ensured "GraphicsEnabler" was set to YES in my boot.plist file (using latest chimera) - edited info.plist to have 120010de - tried PCIRootUID=0 and 1 - tried removing GraphicsEnabler=Yes from boot.plist and tried ATY_Init.kext - removed entry under "GraphicsMode" in boot.plist all of them cause the same issue. it'll say "NVDAGF100Hal is loaded and registered", then panics and reboots. not sure what else to try...
  10. Anybody get SLEEP to work?

    i have the same board (well, the P55A version) and my sleep works flawlessly. you need a couple of things: 1. DSDT from tonymacs database that matches both your motherboard and bios version 2. in energy preferences, enable "automatically start after a power failure" 3. the below binary patch for applertc (paste into terminal): perl -pi -e 's|\x8b\x45\xc8\x39\x45\xcc\x74\x0b|\x8b\x45\xc8\x39\x45\xcc\xeb\x0b|; s|\x8b\x45\xb4\x39\x45\xb8\x74\x08|\x8b\x45\xb4\x39\x45\xb8\xeb\x08|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC With those 3 things - it works perfectly. mkext isn't used any more as samsonluk mentioned. Here's what to do: 1. put all your required kexts into /System/Library/Extensions 2. apply root:wheel ownership, and 644 permissions to those kexts 3. put the following into your com.apple.boot.plist file: <key>UseKernelCache</key> <string>Yes</string> 4. delete /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache and reboot your machine. It'll rebuild the kernelcache file and the bootloader will use it upon startup. whenever something changes in /S/L/E, that kernelcache file will rebuild itself.
  11. Got my sleep working perfectly on my ga-p55a-ud3r with dsdt from tonymacs database. Simply had to run the patch from this thread and enable "Startup automatically after a power failure" in energy settings. Beautiful!
  12. Kexts are being processed on every boot

    i had the exact same problem using the mkext file. switching to the UseKernelCache option fixed this for me.
  13. i tried that patch but it only prevents the cmos corruption. rather than sleep -> cmos corruption its sleep -> reboot
  14. Kexts are being processed on every boot

    Here's some info on using kernelcache... It works well, but the down side is that all the kexts you want to use have to be in /S/L/E. So for me, i've got: - AppleHDA.kext (from 10.6.2) - RealtekRTL81xx.kext - ALC8xxHDA.kext - FakeSMC.kext - JMicron36xSATA.kext These kexts need to have the root:wheel ownership, and 644 permissions. In your com.apple.boot.plist file, put in the following: <key>UseKernelCache</key> <string>Yes</string> Once that's done - simply delete /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache and reboot your machine. It'll rebuild the kernelcache file and the bootloader will use it upon startup. The upside to using this method is that the kernelcache file is rebuilt when new kexts are installed. When using an mkext file, you have to keep it up to date yourself. Of course - using this method will not touch your /E/E or /EFI/E/E kexts. If you want these to be processed as a once off - just boot with the -f option and it will ignore all caches. Just thought i'd share
  15. GM and EFI partition

    you guys have EFI partitions? have you been able to use Snow Leopard in 64 bit mode? if so - try using an internal SATA disk rather than USB.