Jump to content
  • Announcements

    • Hervé

      April 2018: New Forum !   04/06/18

      We've migrated to an upgraded board and now have a new forum. We hope you'll like it. Whilst we took every step to ensure no loss of data and/or feature, we may have missed a few things and glitches may occur. Should you encounter a problem, please create a new thread in Feedback section of the forum, where we will endeavour to report on the follow-up until the issue is fixed. Thanks. OSXL Crew

Zackptg5

Members
  • Content count

    75
  • Joined

  • Last visited

  • Days Won

    1

Zackptg5 last won the day on January 4 2015

Zackptg5 had the most liked content!

Community Reputation

5 Neutral

About Zackptg5

  • Rank
    Sergeant
  1. Asus G75VW help topic

    If you follow the guide, multi touch does work. Asus g75vw has Intel graphics disabled by the manufacturer so that's moot point. I've never tested spdif out but in theory they should
  2. Gigabyte P35g v2: Yosemite/El Capitan

    Finally got around to installing El Capitan on it. Got everything up and running like before. Just took some updated kexts, clover patches, and the usb fix (the FakePCIID_XHCIMux and USB rename dsdt patch). Updated the guide with the new stuff. On another note, I attempted the upgrade process with clover and it surprisingly worked...somewhat. There was some glitchiness with stuff like sound and graphics stuttering so I just washed my hands of it and did the old fashioned clean install which worked like a charm.
  3. Asus G75VW help topic

    That's the same problem I ran into with clover which is why I ended up using chameleon. Then my laptop died before I got the chance to figure it out. But there is a device properties box in clover I think under boot or GUI or something like that along with a checkbox under it.
  4. Asus G75VW help topic

    Woops, good catch.
  5. Asus G75VW help topic

    In chameleons boot.plist file in E/E, create a new string called device-properties. Then open the hex file with textedit, then copy the contents of it to the device-properties in the boot.plist
  6. Clover or Chameleon

    It depends. From what you're describing, your windows 8 install is not UEFI but legacy. Chameleon is the same. Clover on the other hand can boot UEFI or legacy depending on how you install it. So to answer your question, both. Chameleon is the tried and true boot loader and what I would recommend using if you're new to the whole osx86 scene. If you're more of an experienced osx86 user and/or consider yourself to be tech savvy, than I would recommend clover. Clover has far more options and is far more complex than chameleon as a result, but if you learn it, you can get a more vanilla build than with chameleon. My laptop (Gigabyte P35G v2) is completely upgrade proof with clover. I can run OS X updates from the app store (such as 10.10.3 to 10.10.4) just like on a real mac without having to reinstall and kexts or patches because any such mods are run through clover at boot. Getting it to that point took a lot of work, but if paid off. Clover has a lot of documentation to read up on (and some of it is out of date which makes it a little more complicated) but is what I use for all of my builds now. I used chameleon back in my earlier days
  7. Gigabyte P35g v2: Yosemite/El Capitan

    No problem Updated guide for 10.10.4 (easiest update ever by the way, I literally just ran the update from the app store and did nothing else: most vanilla hackintosh update I've ever taken) Edit: Updated to 10.10.5, same process as 10.10.4
  8. GIGABYTE Aorus X7 V2

    You can extract them from Windows but the Linux method gets fewer errors in the long run. Learned that lesson the hard way. So yes, linux only
  9. GIGABYTE Aorus X7 V2

    Check out my guide here for an AppleHDA audio solution, backlight control, and TRIM support: http://forum.osxlatitude.com/index.php?/topic/8102-gigabyte-p35w-v2/ My battery patch may work for your laptop too. You just want to use Rehabman's ACPIBattery, rolling back AppleACPIPlatform and such is not good or power management and such. Also, for your dsdt and ssdts, you need to extract them from linux like I did in my guide or you'll get all sorts of weird errors.
  10. Special Thanks: Rehabman for helping me troubleshoot the various issues I had and helping me work them out EmlyDinesh for adding a custom fix to his ApplePS2SmartTouchpad kext for the brightness keys to work properly All developers who engineered the various tools/kexts/patches/etc to get this working Specifications: Processor : Intel Core i7-4710HQ Processor (6M Cache, up to 3.50 GHz) Graphics Processor (GPU) : Intel HD Graphics 4600 and Nvidia 860m 4gb Chipset : Intel HM87 Express Chipset Hard disk : Crucial MX200 256gb mSata SSD RAM : 16GB DDR3L 1600 MHz SDRAM Wifi : Intel Dual Band Wireless-AC 7260 (Swapped out for: Azurewave AW-CE123H (BCM4352)) Bluetooth : Intel Dual Band Wireless-AC 7260 Bluetooth 4.0 (Swapped out for: Azurewave AW-CE123H (BCM20702)) LAN : Realtek RTL8166G/8111G PCI Express Gigabit Ethernet Audio : Realtek ALC282 High Definition Audio USB 3.0 : Intel 8 Series Chipset Family xHCI Host Controller Touchpad : Elan v4 Touchpad Webcam : USB2.0 UVC HD WebCam Card reader : Realtek RTS5227 PCIE Card Reader Monitor : 15.6 LCD 1920x1080 Optical Drive : DVD Gigabyte P35w v2 Battery Patch.txt Disable from _REG (DSDT) Mod.txt Screen Brightness Keys Patch.txt config.plist.zip aDummyHDA.kext.zip
  11. Works with the Gigabyte P35w v2 with keyboard on PS2X with _Q28 as brightness down and _Q30 as brightness up
  12. ELAN and FocalTech (Smart Touchpad) driver Issues

    If you have synaptics trackpad, usr voodoops2 instead: https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads
  13. ELAN and FocalTech (Smart Touchpad) driver Issues

    Hi Emly, I have the Gigabyte p35w v2 laptop with elan touched. Touchpad works great and keyboard too except one issue: both the down and up screen brightness key acts the same by lowering the screen brightness. In other words, the up key does the down action too. After much troubleshooting here: http://goo.gl/MfR2U1 Rehabman deciphered that the issue was that both ps2 F14 and Acpi signals were being sent by the keyboard and in order to get it to work properly, we had to make a dsdt patch for the two keys: into method label _Q28 replace_content begin // Brightness Down\n Notify(\_SB.PCI0.LPCB.PS2K, 0x0205)\n Notify(\_SB.PCI0.LPCB.PS2K, 0x0285)\n end; into method label _Q30 replace_content begin // Brightness Up\n Notify(\_SB.PCI0.LPCB.PS2K, 0x0206)\n Notify(\_SB.PCI0.LPCB.PS2K, 0x0286)\n end; and disable the ps2 action as it was interfering with the Acpi action. The ps2 action that needed to be ignored was 65 and this was able to be done by adding it into the custom keymap of voodoops2keyboard 65=80 (80 is nothing) but I couldn't find that functionality here and this is the only kext that gives me working trackpad. This was all done on OS X 10.10.3 but I don't think the OS X version really matters with this case. If you could implement this into the keyboard driver or implement a way that I could use voodoo keyboard with your touchpad driver that would be great. Thanks!
  14. Yup. Any change to the internals of the kext requires it to be reinstalled/kext cache repaired
  15. Did you read the documentation here: http://forum.osxlatitude.com/index.php?/topic/5969-details-about-the-enhanced-keyboard-for-smart-touchpad-driver/ Try changing the fn mode to 3 and using ASUS vendor. Due to the complex nature of this kext and vast number of systems it supports, odds are it won't work without some adjustments for your system
×