Contribute
Register

[Guide] HP Elite X2 1012 G1 / G2, Clover UEFI, VirtualSMC, Hot Patch

Joined
Aug 19, 2011
Messages
23
Motherboard
HP X2 1012 G2
CPU
i5-7200U
Graphics
Intel HD 620
does any have issue with installing Mojave or Catalina and laptop reboot at 2 minutes remaining? the clover setup work fine if fully installed.
 
Joined
Nov 28, 2015
Messages
125
Motherboard
HP Elite X2 1012 G2-Clover
CPU
i7-7600U
Graphics
HD620, 2736x1824
No, there shouldn't be any patches necessary other than for OSYS (which you have). Post your troubleshooting files, hard to know where you're going wrong just from your Clover folder.
Thanks for looking into it! I have been trying to get the touchscreen working for awhile now.
 

Attachments

Joined
Aug 19, 2011
Messages
23
Motherboard
HP X2 1012 G2
CPU
i5-7200U
Graphics
Intel HD 620
can someone upload G2 bios ver 1.25 rev a? thank you.
 
Joined
Dec 3, 2011
Messages
408
Motherboard
HP Elite X2
CPU
i5-7600U
Graphics
HD 620 2736 x 1834
Mac
MacBook Pro, Mac Pro
Classic Mac
128K, 512K
Mobile Phone
iOS
Thanks for looking into it! I have been trying to get the touchscreen working for awhile now.
It's a simple mistake, the Apple I2C kexts are loading. You should add this to the Kext to Patch section of your config.plist to prevent them from doing so -

Code:
            <dict>
                <key>Comment</key>
                <string>Prevent Apple I2C kexts from attaching to I2C controllers, credit CoolStar</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                SU9LaXQ=
                </data>
                <key>InfoPlistPatch</key>
                <true/>
                <key>Name</key>
                <string>com.apple.driver.AppleIntelLpssI2C</string>
                <key>Replace</key>
                <data>
                SU9LaXM=
                </data>
            </dict>
 
Joined
Nov 28, 2015
Messages
125
Motherboard
HP Elite X2 1012 G2-Clover
CPU
i7-7600U
Graphics
HD620, 2736x1824
It's a simple mistake, the Apple I2C kexts are loading. You should add this to the Kext to Patch section of your config.plist to prevent them from doing so -

Code:
            <dict>
                <key>Comment</key>
                <string>Prevent Apple I2C kexts from attaching to I2C controllers, credit CoolStar</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                SU9LaXQ=
                </data>
                <key>InfoPlistPatch</key>
                <true/>
                <key>Name</key>
                <string>com.apple.driver.AppleIntelLpssI2C</string>
                <key>Replace</key>
                <data>
                SU9LaXM=
                </data>
            </dict>
Thanks. I made the addition, but now I'm seeing this in syslog..

Code:
2019-10-27 22:31:00.767731-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Starting I2C controller
2019-10-27 22:31:00.767758-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Set PCI power state D0
2019-10-27 22:31:00.767781-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Publishing nub
2019-10-27 22:31:00.771478-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Probing controller
2019-10-27 22:31:00.771484-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Found valid Synopsys component, continuing with initialisation
2019-10-27 22:31:00.771596-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerNub::pci8086,9d60 SSCN not implemented in ACPI tables
2019-10-27 22:31:00.771602-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerNub::pci8086,9d60 FMCN not implemented in ACPI tables
2019-10-27 22:31:00.771605-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Warning: Error getting bus config, using defaults where necessary
2019-10-27 22:31:00.771626-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Publishing device nubs
2019-10-27 22:31:00.771635-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Found I2C device: WCOM483E
2019-10-27 22:31:00.771720-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::VoodooI2CDeviceNub Could not find an I2C Serial Bus declaration
2019-10-27 22:31:00.771724-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::TPL0 Could not get device resources
2019-10-27 22:31:00.771727-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Could not initialise nub for WCOM483E
Are there any DSDT patches or `.aml` files I should also be including for initializing I2C devices with this tablet?
 

Attachments

Joined
Dec 3, 2011
Messages
408
Motherboard
HP Elite X2
CPU
i5-7600U
Graphics
HD 620 2736 x 1834
Mac
MacBook Pro, Mac Pro
Classic Mac
128K, 512K
Mobile Phone
iOS
Thanks. I made the addition, but now I'm seeing this in syslog..

Code:
2019-10-27 22:31:00.767731-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Starting I2C controller
2019-10-27 22:31:00.767758-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Set PCI power state D0
2019-10-27 22:31:00.767781-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Publishing nub
2019-10-27 22:31:00.771478-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Probing controller
2019-10-27 22:31:00.771484-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Found valid Synopsys component, continuing with initialisation
2019-10-27 22:31:00.771596-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerNub::pci8086,9d60 SSCN not implemented in ACPI tables
2019-10-27 22:31:00.771602-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerNub::pci8086,9d60 FMCN not implemented in ACPI tables
2019-10-27 22:31:00.771605-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Warning: Error getting bus config, using defaults where necessary
2019-10-27 22:31:00.771626-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Publishing device nubs
2019-10-27 22:31:00.771635-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Found I2C device: WCOM483E
2019-10-27 22:31:00.771720-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::VoodooI2CDeviceNub Could not find an I2C Serial Bus declaration
2019-10-27 22:31:00.771724-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::TPL0 Could not get device resources
2019-10-27 22:31:00.771727-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Could not initialise nub for WCOM483E
Are there any DSDT patches or `.aml` files I should also be including for initializing I2C devices with this tablet?
Two things, in your config.plist, you have have the _OSI to XOSI rename, but you are already manually patching your DSDT for Windows 2015. You have to choose one method or the other -- ie either use the rename + the XOSI SSDT, or manually patch your DSDT and do not use the rename. So just disable the XOSI rename in your config. Second, you also have the _DSM to XDSM rename enabled in your config.plist which probably isn't necessary. Also, don't forget to add the AlpsT4USB kext to get multitouch on the touchpad as well. :)
 
Joined
Dec 3, 2011
Messages
408
Motherboard
HP Elite X2
CPU
i5-7600U
Graphics
HD 620 2736 x 1834
Mac
MacBook Pro, Mac Pro
Classic Mac
128K, 512K
Mobile Phone
iOS
Thanks. I made the addition, but now I'm seeing this in syslog..

Code:
2019-10-27 22:31:00.767731-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Starting I2C controller
2019-10-27 22:31:00.767758-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Set PCI power state D0
2019-10-27 22:31:00.767781-0700 0x40e      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CPCIController::pci8086,9d60 Publishing nub
2019-10-27 22:31:00.771478-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Probing controller
2019-10-27 22:31:00.771484-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Found valid Synopsys component, continuing with initialisation
2019-10-27 22:31:00.771596-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerNub::pci8086,9d60 SSCN not implemented in ACPI tables
2019-10-27 22:31:00.771602-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerNub::pci8086,9d60 FMCN not implemented in ACPI tables
2019-10-27 22:31:00.771605-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Warning: Error getting bus config, using defaults where necessary
2019-10-27 22:31:00.771626-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Publishing device nubs
2019-10-27 22:31:00.771635-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Found I2C device: WCOM483E
2019-10-27 22:31:00.771720-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::VoodooI2CDeviceNub Could not find an I2C Serial Bus declaration
2019-10-27 22:31:00.771724-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::TPL0 Could not get device resources
2019-10-27 22:31:00.771727-0700 0x430      Default     0x0                  0      0    kernel: (VoodooI2C) VoodooI2CControllerDriver::pci8086,9d60 Could not initialise nub for WCOM483E
Are there any DSDT patches or `.aml` files I should also be including for initializing I2C devices with this tablet?
Wait, why aren't you just using the hotpatch files from post one again?
 
Joined
Nov 28, 2015
Messages
125
Motherboard
HP Elite X2 1012 G2-Clover
CPU
i7-7600U
Graphics
HD620, 2736x1824
Two things, in your config.plist, you have have the _OSI to XOSI rename, but you are already manually patching your DSDT for Windows 2015. You have to choose one method or the other -- ie either use the rename + the XOSI SSDT, or manually patch your DSDT and do not use the rename. So just disable the XOSI rename in your config. Second, you also have the _DSM to XDSM rename enabled in your config.plist which probably isn't necessary. Also, don't forget to add the AlpsT4USB kext to get multitouch on the touchpad as well. :)
Thank you!! I was able to get the touchscreen working by disabling _OSI to XOSI rename. Please note, I do need _DSM to XDSM as this is required for brightness controls.

Wait, why aren't you just using the hotpatch files from post one again?
First off, I want to say your contribution to macOS on this tablet has been incredible, and I mean you no disrespect. I am using Rehabman's HP ProBook scripts since they throttle the CPU down to 600MHz. Maybe it's due to me having the i7 variant or my use, but this makes a HUGE difference with heat dissipation my HP Elite X2. Also, I noticed sleep works better with his scripts as well. Therefore with his scripts and your contributions to the touchscreen (which wasn't working with his scripts) I have the ultimate HP Elite X2 for my needs.

If anyone wants my working config I have attached it to this post (with debugging logs showing the boot logs).

This has by far been the best Hackintosh tablet I have ever owned. Thanks everybody for making this possible!
 

Attachments

Joined
Dec 3, 2011
Messages
408
Motherboard
HP Elite X2
CPU
i5-7600U
Graphics
HD 620 2736 x 1834
Mac
MacBook Pro, Mac Pro
Classic Mac
128K, 512K
Mobile Phone
iOS
Thank you!! I was able to get the touchscreen working by disabling _OSI to XOSI rename. Please note, I do need _DSM to XDSM as this is required for brightness controls.



First off, I want to say your contribution to macOS on this tablet has been incredible, and I mean you no disrespect. I am using Rehabman's HP ProBook scripts since they throttle the CPU down to 600MHz. Maybe it's due to me having the i7 variant or my use, but this makes a HUGE difference with heat dissipation my HP Elite X2. Also, I noticed sleep works better with his scripts as well. Therefore with his scripts and your contributions to the touchscreen (which wasn't working with his scripts) I have the ultimate HP Elite X2 for my needs.

If anyone wants my working config I have attached it to this post (with debugging logs showing the boot logs).

This has by far been the best Hackintosh tablet I have ever owned. Thanks everybody for making this possible!
Oh no offense taken. :-D Glad you were able to get things working. Your heat issues are mostly caused by the NVMe drive. There's no power management currently for NVMe drives so they hurt you on two fronts -- power consumption and heat, which in turn causes the fan to run / more power consumption. Just switching it alone reduces idle usage by 1.5 watts, then you also idle at a lower temp and the fan shuts off. I have i7 as well and idle power consumption is just over .7W with the keyboard attached, .6 without it.
 
Top