Jump to content
InsanelyMac Forum

AndersenTech

Members
  • Content count

    37
  • Joined

  • Last visited

About AndersenTech

  • Rank
    InsanelyMac Protégé
  • Birthday August 15

Contact Methods

  • Website URL
    http://www.andersentechwiki.net

Profile Information

  • Gender
    Male
  • Location
    Wilmington, Delaware
  1. Yes. Here's the IOKitPersonality key: <key>IOKitPersonalities</key> <dict> <key>Platform SMBIOS Match</key> <dict> <key>CFBundleIdentifier</key> <string>org.syscl.FakeSMBIOS</string> <key>FakeProperties</key> <dict> <key>compatible</key> <string>MacBookPro13,3</string> <key>model</key> <string>MacBookPro13,3</string> <key>product-name</key> <string>MacBookPro13,3</string> </dict> <key>IOClass</key> <string>FakeSMBIOS</string> <key>IOMatchCategory</key> <string>FakeSMBIOS</string> <key>IOProviderClass</key> <string>IOPlatformExpertDevice</string> <key>IOResourceMatch</key> <string>SMBIOS</string> </dict> </dict> On a different note -- has anyone else had some strange behavior with the SSDT/CodecCommander pair? I've had many boots where the audio device isn't recognized at all, others where everything works, and others still where the internal speakers work fine, but the headphone output is distorted. While I have had these hit-or-miss boots since the beginning, this new issue with the headphone jack has me stumped.
  2. I generated a dummy config.plist out of Clover Configurator and stripped the SMBIOS section from it, but here's the rundown: <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>11/30/16</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MBP133.88Z.0226.B08.1611301700</string> <key>Board-ID</key> <string>Mac-A5C67F76ED83108C</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardSerialNumber</key> <string></string> <key>BoardType</key> <integer>10</integer> <key>ChassisAssetTag</key> <string>MacBook-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>08</string> <key>Family</key> <string>MacBook Pro</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <true/> <key>ProductName</key> <string>MacBookPro13,3</string> <key>SerialNumber</key> <string></string> <key>SmUUID</key> <string></string> <key>Trust</key> <false/> <key>Version</key> <string>1.0</string> </dict> </key> Did you make sure to update FakeSMBIOS's Info.plist to reflect MBP13,3?
  3. Interesting note: when changing SMBIOS (both in Clover and kext) to MBP13,3, onboard HDMI and HDMI via the USB-C adapter stop working entirely. I can leave the kext alone (still MBP13,3) but change the Clover config back to MB9,1 and both ports start working again.
  4. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    Version 1.5b (beta) released on the Google Code page Notes: Contains an updated VoodooHDA kext tested with ML (10.8). Removes auto-startup function: Users must manually add the app to their login rules through the Settings App (system) or through login hooks (for use with /usr/bin/vd_startup). Keep in mind that this is a beta and likely should not be used on a daily basis. I do not have a Hackintosh here to personally test the updated loader and therefore, comments would be greatly appreciated!
  5. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    Hi all, Recently I've been super busy with school stuff and travel. I hope to resume work on this project as soon as I can get my rig fixed. It might be a while, but I'll try building on my other comp and updating more often. Hope I can fix some problems, AndersenTech
  6. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    Out of curiosity to you have a nVidia GeForce 240GT (or similar card)?
  7. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    So, today I was experimenting with some code and made the Terminal windows disappear when the script executes. You can use this if you want (and all the people who can't wait)! This is not a very well executed fix, but it works for now. You will still need to patch VoodooLoader with your custom next (if you use one) as it overwrites the old installation. The download is at the Google Code page http://code.google.com/p/voodoo-launcher/
  8. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    I'll take a look into this, this seems very interesting. This might take a while considering I haven't "merged" kexts before I should have an update for this soon that will log the problems I'm still looking into this. To be honest I haven't really had any time to really sit down and look at this project. Hopefully this weekend I'll have some time to look at all of the problems and fix it.
  9. AndersenTech

    VoodooPatcher

    Unfortunately, this is a problem with Tiger. I never intended for it to be used with Tiger so the modules are probably incompatible. Sorry
  10. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    What kernel and version (OS X) are you using? i386 or x86_64?
  11. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    So are your issues resolved? This is not related to Voodoo in any way, but I'm running a survey about hosting a Siri server for devices other than the 4S. Input would be greatly appreciated. Check it out here, thanks in advance
  12. AndersenTech

    Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    I've realized that my instructions weren't exactly very explicit and therefore have updated them. They should answer all of your questions about the installation procedure. As to VoodooPatcher issues when you open the application it will ask you to drag your modified VoodooHDA.kext to the window, from there it will change the permissions and move it to the VoodooLoader's directory, making it load on startup instead of the provided VoodooHDA.kext. You shouldn't see any output from the window until the installation is completed and says "All done" Hope this answers your question
  13. AndersenTech

    VoodooPatcher

    The fix is finally here! VoodooPatcher v1.1 should fix everyone's permission error. The updated version is avaliable on the Google site Hope this helps!
  14. AndersenTech

    VoodooPatcher

    Sorry for the delay, the last few weeks have been hectic, but I finally have some time off to take a look into this problem. Should be fixed by Monday
  15. AndersenTech

    VoodooPatcher

    The patcher already sets the permissions for the kext, however just for future reference, you must be logged in as the root user sudo -s chown -R root:wheel (KEXT) OR sudo chown -R root:wheel (KEXT) I hope this answers your question. Also, if you don't mind taking a screenshot and posting that would help if it's a problem with the launcher
×