Jump to content

schwarzgrau

Members
  • Content Count

    28
  • Joined

  • Last visited


Reputation Activity

  1. Like
    schwarzgrau reacted to Odiolitos in CINTIQ COMPANION 2!   
    Hi! 
     
    I changed mine last summer, and it worked perfect. Had to ditch the hackintosh project, as it wouldn't recognise the cloned partition, but the card did work from the USB, so you should have no problems. 
  2. Like
    schwarzgrau reacted to Odiolitos in CINTIQ COMPANION 2!   
    Yup, it worked without having to install anything new (as far as I remember, I gave up hackintoshing this baby six months ago...) from the USB. It did use that chipset, and regarding form factor... I'd say it's the very same I got. It was a breeze after having installed the hard drive and RAM, so I'd say go for it!
  3. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    Sorry for my late reply, I was pretty busy with some jobs.
    Yea, basically I stuck to your tutorial, except of the changes you mentioned and another config.plist (which I should clean up).
    I attached the files from my EFI/Clover directory. Maybe they could be helpful for someone with the same Companion.
     
    I've also installed this kexts
    ACPIBatteryManager.kext
    FakePCIID_XHCIMux.kext FakeSMC.kext IntelBacklight.kext VoodooHDA.kext XHCInjectorCC2.kext   Some things still doesn't work: internal WIFI (as expected) SD card reader (as expected) volume buttons (as expected) only one USB port is a true USB 3 port the audio drivers doesn't load most of the time.  CLOVER.zip
  4. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    Sorry for my late reply, I was pretty busy with some jobs.
    Yea, basically I stuck to your tutorial, except of the changes you mentioned and another config.plist (which I should clean up).
    I attached the files from my EFI/Clover directory. Maybe they could be helpful for someone with the same Companion.
     
    I've also installed this kexts
    ACPIBatteryManager.kext
    FakePCIID_XHCIMux.kext FakeSMC.kext IntelBacklight.kext VoodooHDA.kext XHCInjectorCC2.kext   Some things still doesn't work: internal WIFI (as expected) SD card reader (as expected) volume buttons (as expected) only one USB port is a true USB 3 port the audio drivers doesn't load most of the time.  CLOVER.zip
  5. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    Sorry for my late reply, I was pretty busy with some jobs.
    Yea, basically I stuck to your tutorial, except of the changes you mentioned and another config.plist (which I should clean up).
    I attached the files from my EFI/Clover directory. Maybe they could be helpful for someone with the same Companion.
     
    I've also installed this kexts
    ACPIBatteryManager.kext
    FakePCIID_XHCIMux.kext FakeSMC.kext IntelBacklight.kext VoodooHDA.kext XHCInjectorCC2.kext   Some things still doesn't work: internal WIFI (as expected) SD card reader (as expected) volume buttons (as expected) only one USB port is a true USB 3 port the audio drivers doesn't load most of the time.  CLOVER.zip
  6. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    Yeah, but it's better for now that we are using static patching that you use [sys] Fix Shutdown patch in your DSDT. I think I forgot to mention this patch in my previous list.
     
    Glad to hear you finally found a platform that works for you! Congrats! It seems you have almost everything working right now. 
     
    As final tests, I recommend to check your states using AppleIntelInfo. This is for checking CPU/IGPU power management, you will see states for CPU and IGPU (the more the better). I guess if you want to ensure it is working, you should compare yours results to those you could find in a similar CPU guide.
    Run some GPU benchmark like LuxMark and post results, my Haswell Iris gives me a little more than 1600.
     
    Glad it works for your device, mate! I've ckecked an IOReg I saved when I used Yosemite. Yosemite detected all ports and made them work ok, so I check and compare how it assigned my ports to what I did in my custom injector. It seems I need to change a couple of things, HS08 is in a wrong location and I want to ensure all connector types are ok. 
    I have a similar issue than yours, my USB3.0 devices work ok in all ports except for an HDD in a USB3.0 case that only is connected trough 3.0 speed if it's plugged in bottom port. But curious thing is that my WD 2,5" 1TB USB3.0 works as 3.0 in any port. So, definitely my injector needs some work to be perfect.
     
    So for what I saw and guess, changes in my guide for your i7-5557U/Iris 6100 would be:
    - ig-platform-id > Broadwell Iris 6100 > 0x162b0000 (others will need tests and proper DVMT-prealloc/framebuffer patches)
    - SSDT.aml from Pike's script for CPU PM.
    - XHC pci device change > Haswell i5-4258U comes with 9c31, Broadwell i7-5557U with 9cb1 > Injector needs customization 
     
    Am I missing something, guys?
  7. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    I must read again everything about USB too, long time past from my tests. But for what I remember, and checking your SSDT-UIAC, these are my thoughts.
     
    HS01, HS02 and HS03 are the usb2.0 pins for SSP1, SSP2 and SSP3, if I'm explaining myself right.
    What I'm trying to say is each usb3.0 ports counts as two, one for connecting usb3.0 devices and another for usb2.0 devices. If you experiment plugging/unplugging devices into your ports while looking at IOReg, you'll see 2.0 are connected to HS01-03 and 3.0 to SSP1-3. This is important in order to be under the 15 ports limit.
    Well, so those are external ports. This is translated into SSDT-UIAC putting "UsbConnector", 3. "3" means external usb3.0 port.
    Ports HS05, HS06, HS07, HS08 must be set as internal I think, so it will be "USBconnector", 255. "255" means internal port.
     
    There's one important thing, in my device HS08 contains an HUB where USB2.0-CRW (microSD reader), Cintiq Companion 13HD Touch and Cintiq Companion 2 are attached. So you probably will need to override hub info. I did that in my custom injector but since this is not working for you, I think it's time to read and test, mate. I don't know how this is done in SSDT-UIAC.
     
    NOTE: your XHC pci device is different than mine, that's why my injector isn't working for you. I would try to edit my injector doing the following:
     
    - Go into my injector (right click, show content package).
    - Open Info.plist with PlistEdit Pro.
    - Look for my pci device value and replace with yours (mine is 9c31, yours 9cb1)
    - Save and install the kext.
    - Post results
  8. Like
    schwarzgrau got a reaction from midi-sama in CINTIQ COMPANION 2!   
    I started by checking which ports are in use and which not.
     
    HS01 : USB3 (bottom) HS02 : NOT USED  HS03 : USB3 (center) HS04 : USB3 (top)! HS05 : cam 1 HS06 : cam 2 HS07 : bluetooth HS08 : Cintiq HS09 : NOT USED HS10 : NOT USED HS11 : NOT USED SSP1 : USB3 (bottom) SSP2 : USB3 (top) SSP3 : USB3 (center) Then I installed Rehabmans USBInjectAll.kext and added this to the boot arguments in my config.plist
    uia_exclude=HS02;HS04;HS09;HS10;HS11 But since you mentioned I should create a SSDT-UIAC and cause it seemed like the more future proof and "clean" approach I tried to create one, removed the boot argument and added my SSDT-UIAC.aml to the SortedOrder.
    Unfortunately some of the ports behave kinda weird: the USB3-port I've using for my boot-stick doesn't detect the stick anymore if booted in El Capitan. If I unplug and replug the stick it get's detected. And after pluging in the wifi-dongle I get a message, that the device needs more power. After restarting the same port seems be ok for the dongle.
    I've attached my SSDT-UIAC, it would be great if you could take a look at it.
    SSDT-UIAC.zip
  9. Like
    schwarzgrau got a reaction from midi-sama in CINTIQ COMPANION 2!   
    I started by checking which ports are in use and which not.
     
    HS01 : USB3 (bottom) HS02 : NOT USED  HS03 : USB3 (center) HS04 : USB3 (top)! HS05 : cam 1 HS06 : cam 2 HS07 : bluetooth HS08 : Cintiq HS09 : NOT USED HS10 : NOT USED HS11 : NOT USED SSP1 : USB3 (bottom) SSP2 : USB3 (top) SSP3 : USB3 (center) Then I installed Rehabmans USBInjectAll.kext and added this to the boot arguments in my config.plist
    uia_exclude=HS02;HS04;HS09;HS10;HS11 But since you mentioned I should create a SSDT-UIAC and cause it seemed like the more future proof and "clean" approach I tried to create one, removed the boot argument and added my SSDT-UIAC.aml to the SortedOrder.
    Unfortunately some of the ports behave kinda weird: the USB3-port I've using for my boot-stick doesn't detect the stick anymore if booted in El Capitan. If I unplug and replug the stick it get's detected. And after pluging in the wifi-dongle I get a message, that the device needs more power. After restarting the same port seems be ok for the dongle.
    I've attached my SSDT-UIAC, it would be great if you could take a look at it.
    SSDT-UIAC.zip
  10. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    Yes, you must create a custom SSDT-UIAC (look at RehabMan repo for examples) to enable/disable or change port connections you need. Remember to add this SSDT to SorterOrder in config.plist. It requires some read and test but I think you will be able to do it, mate
  11. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    I did the changes you mentioned in my config.plist. Thank you.
     
    Unfortunately XHCInjectorCC2.kext doesn't seem to fix the problem. I guess I have to read RehabMans readme to his USBInjectAll a few times more. Till it starts to make any sense to me.
    If I understood it right it activates all ports, but isn't meant to be used constantly. So I should use it to see which ports needs to be activated/fixed. Is this right?
  12. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    Graphic's name may be just cosmetic, it never showed Unknown to me. If everything is working, it doesn't matter. Run some graphic benchmark like LuxMark to check it.
     
    - Remove patches from ACPI/DSDT/Patches, we're renaming EHC1/EHC2 in DSDT manually and emulating Windows with DSDT patch.
    - Remove boot flags from Boot/Arguments, they aren't needed. Use -v (verbose boot flag) until everything is right, it will help you to detect issues (my recommendation).
    - Remove DisableDrivers section, you already deleted VBoxHfs.efi and put HFSplus.efi instead.
    - Remove any entry starting with #. This symbol make entry disabled so since everything is booting good, they're not needed.
    - Remove ForceKextsToLoad from KernelAndKextPatches, not needed.
    - In KernelAndKextPatches/KextsToPatch there are a lot of disabled patches. Leave there only what you need after testing in order to leave a more cleaner config.plist.
     
    Well, about USB. If you take a look into your IOReg, you will see EH01 having two ports (PR01 and PR12). PR01 show a hub with many ports and PR12 is empty/unused.
    XHC is managing all your connected devices for what I see, but HS08 is lost, don't know why. If I remember well, there is where the Wacom hub must be present, that's why your driver can't find a tablet.
     
    Recommendation: Install the custom injector from my guide and report back.
  13. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    I sticked pretty much to your guide and installed El Capitan. The graphics seem to instantly detected in some way, cause it was a lot faster than Yosemite only the image was kind of darken. After generating a new SSDT.aml and patching new DSDT and SSDT files this issue was gone. Now my graphic card is kind of detected, not by name, but OS X seems to understand it uses 1536MB. I hope this missing name is only cosmetics, like you mentioned in your guide.
     

     
     
    Battery, bluetooth, wifi (dongle) and app store works, audio doesn't work. But my biggest problem at the moment is that OS X doesn't seem to detect the Cintiq itself.
     

     
    Something which seems weird, since the Cintiq-part was always something which does work from the beginning. Could it have something to do with the different USB support? I don't have any problems with my USB ports on the outside, but I remember I read something about the Companion using some USB-ports internally?
     
    I attached my config.plist (a simple one from Rehabman, with some tiny changes) and my IOReg. It would be great if you could look at it, if you find the time.
    config_ioreg.zip
  14. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    In El Capitan some other things have changed, for example how system manage USB ports. Now, in Yosemite all ports are working OOB but in EL Capitan you will see some of them are lost. You need to read how they are managed now and possible solutions, but these are what worked for me:
    - Install USBInjectAll from RehabMan repository, this kext will enable all ports. This step is needed to see which are needed or not in order to disable them and/or correct port type (internal, external, usb2.0, usb3.0) with a custom SSDT-UIAC (more info from RehabMan in his repo).
    - You can also install Fake_PCIID_XHCIMux, this kext will route any usb2.0 device connected to usb2.0 pins in XHC to be used by EHC1 instead. Then you can create a custom injector kext to disable unused ports and/or correct them (very similar to SSDT-UIAC).
    - What I'm using now (I've probed the other two methods and it worked for me as well) is a custom injector kext for XHC. This makes EH01 to have zero ports and everythings is managed by XHC. In order to fully disable EH01 I'm including in EFI/CLOVER/ACPI/patched a SSDT-Disable_EHC from RehabMan repo.
     
    USB is tricky in el Capitan (or Sierra), you must take a look in how Yosemite manage them and which ports are assigned to each device, do the same in El Capitan using USBInjectAll and use any method to enable/disable what you need and change port connector type. Here, IORegistry Explorer is needed, so start having a look at it and you will learn things at first just guessing. Look for guides about USB in El Capitan for examples of everything I'm talking about. You can also install the custom injector from my guide, I think it will work for you.
     
    Other things have changed too:
    - Clover patch for Boot Glitches
    - Clover patches for enable BCM94352Z
    - Kext for enable bluetooth is different, you must install BrcmPatchRAM2 instead of BrcmPatchRAM.
  15. Like
    schwarzgrau reacted to bertolin in [Guide] macOS Sierra 10.12.1 + Windows 10 - Dual boot - Cintiq Companion 2   
    NOTE: This guide mixes static patch with hotpatch. It will be edited to make it works only with static patch soon. There's zero issues with this guide but it seems better not to mix patching methods (thanks, RehabMan)
     
    Hello, everybody! 
     
    After two years of using my Cintiq Companion 2 with Yosemite thanks to mactabletman’s guide and reading, testing a lot and trying to understand what I was doing, I’m in a good path to share my experiences and help you to install macOS Sierra in your Companion 2 keeping your Windows installation.
    There are a few things that need to be solved, like sleep/wake (Cintiq goes to sleep, led blinks but display doesn’t wake up, maybe framebuffer, IOKit or PWR related) or audio using AppleHDA for codec ALC286 instead of VoodooHDA (I will add notes in each section about all this).
     
    WE HAVE GOOD NEWS, CINTIQ MODE WORKS!!
    (see notes at the bottom)
     
    No need to say that I’m taking zero responsibilities of what happened if you follow this guide. We are all grown people and before taking any step you better read all the info you can find about what you are trying to accomplish. 
     
    This guide is done for the Cintiq Companion 2 i5-4258U 128GB model (DTHW1310L) with the last BIOS version (MB01) but can be useful as a start for other CPU/graphic models. I’m assuming you updated or reinstalled and have Windows 10 running but same procedure is required for Windows 8/8.1.
     
    WORKING: All except wake from sleep using Power Button (wake well if previously connected in Cintiq mode), PCI Realtek SD Card Reader, volume buttons and HDMI audio.
     
    So first, things you are going to need:
     
    - 2 usb drives (16GB and 32GB minimum), one for create an installer and another to install Sierra into.
    - 1 usb keyboard and 1 usb mouse since Clover has no support for touch devices and touch doesn't work natively in Sierra as it does in Yosemite.
    - 1 usb drive for Clonezilla (*optional but recommended)
    - 1 external hard drive to backup your whole internal SSD using Clonezilla (*optional but recommended)
    - An original Apple computer to create installer.
    - A BCM94352Z WiFi and Bluetooth 4.0 card to replace default Intel wireless card. You can check how to open your device here.
     
    * In order to create a Clonezilla Live USB, I recommend to use Yumi. You can create a multiboot installer for your Windows version, Ubuntu, Wifislax… very useful stuff. 
     
     
    CREATING THE INSTALLER…
     
    Ok, you did a backup of your data, so let’s create a usb installer for macOS Sierra:
     
    - Download macOS Sierra from App Store, this will download the last update 10.12.1 
    - Open Disk Utility and format your 16GB usb to HFS+J, GUID partition and rename it to install_osx.
    - Copy and paste these commands in Terminal, one by one:
    sudo "/Applications/Install macOS Sierra.app/Contents/Resources/createinstallmedia" --volume  /Volumes/install_osx --applicationpath "/Applications/Install macOS Sierra.app" --nointeraction sudo diskutil rename "Install macOS Sierra" install_osx INSTALLING CLOVER IN USB INSTALLER…
     
    Now open the Clover installer and select your Install macOS Sierra USB, click on “Customize” and use this configuration:
     
    - Check Install for UEFI booting only, Install Clover in the ESP is also automatically selected
    - Check embebbed theme.
    - Check OsxAptioFixDrv-64 from Drivers64UEFI
    - Check PartitionDxe-64 from Drivers64UEFI
    - Check EmuVariableUefi-64 from Drivers64UEFI*
    - Check Install RC scripts on target volume from Drivers64UEFI*
    - Click Install.
     

     
    After install Clover, a EFI partiton is mounted. Go to EFI/CLOVER, delete that config.plist and put my config_install.plist there. Rename it to config.plist. 
     
    - Go to EFI/CLOVER/Drivers64UEFI and delete VboxHfs-64.efi. Put there HFSPlus.efi.
    - Go to EFI/CLOVER/kexts/ and leave only "10.12" and “Other” folders. Put FakeSMC.kext inside both of them.

    Now your installer USB is ready.
     
    *NOTES ABOUT NVRAM
     
    EmuVariableUefi-64 and Install RC scripts on target volume might be needed to make NVRAM works in a dual boot configuration since both systems read and write there (I guess). Or maybe our device has not NVRAM hardware, I don’t know. Anyway, I’ve tested it. To test NVRAM, type this in Terminal:
    sudo nvram MyVar=TestValue Check/show NVRAM:
    nvram -p You should see the following entry among others: 
    MyVar=TestValue Reboot, check NVRAM again and if above entry persists, your NVRAM is working. Mine didn’t installing only OsxAptioFixDrv-64, so I reinstalled Clover with EmuVariableUefi-64 and Install RC scripts on target volume.
     
     
    BIOS CONFIGURATION…
     
    Check your BIOS. Press power button while holding volume up button to enter BIOS.
    - CPU Configuration: Boot performance mode: Turbo performance; EIST: enabled; Turbo Mode: enabled; Performance/Watt: Performance; Configurable TDP: TDP Nominal.
    - Intel Smart Connect Technology: disabled.
    - CSM configuration: CSM Support: enabled; Network: Do not launch; Video: Legacy.
    - Chipset/System Agent (SA) Configuration/Graphics Configuration: Aperture Size: 256MB; DVMT Pre-Allocated: 128MB; DVMT Total Gfx Mem: MAX.
    - BOOT: Fast Boot: disabled; Boot mode select: dual; all fixed boot order priorities disabled except for UEFI USB KEY.
    - Save & Exit.
     
     
    BOOTING INSTALLER…
     
    Now, to boot into Clover you just need to reboot with your installer usb plugged, so your motherboard recognize the UEFI entry in that drive. Click on power icon in Windows, and while pressing SHIFT, click on reset to go to Windows Boot Manager. Click on "Use a device" and next on "UEFI: SanDisk, Partiton 1" (if you are using SanDisk drive, if not it will be diferent but easily to discover).
     
    Click enter in your keyboard to boot "Install macOS Sierra". You will se the verbose log in order to fix any boot issue (you shouldn't need to if you follow this guide). 
     
    Open Disk Utility and format your 32GB drive to HFS+J, GUID partition and give it a name, for example, SierraHD. Close Disk Utility and Select Install macOS Sierra and install it to your SierraHD drive. Wait until it reboots after creating the Recovery partition. You will need to boot again into Clover and boot this time from your new boot entry in your SierraHD drive to finish installation.
     
     
    INSTALLING CLOVER TO SIERRAHD USB…
     
    After install macOS Sierra you might want to install Clover to your SierraHD drive so you don’t need both usb drives to be plugged in order to boot. Follow same steps than before in INSTALLING CLOVER IN USB INSTALLER…
     
    Ok, now you’re able to boot into your macOS Sierra but you don’t have CPU PM, IGPU PM, backlight control, battery level… Some of them will be fixed installing kexts, other with DSDT patches or renames, some with Clover… 
     
     
    ACPI FILES - DSDT & SSDT
     
    ACPI Tables Extraction using Clover
     
    Press F4 in Clover boot menu and OEM ACPI tables will be placed in EFI/CLOVER/ACPI/origin. Copy only those files named DSDT.aml and SSDT-X.aml (where X is any number) to your desktop in a new folder called ACPI that we will use to disassemble with iASL.
     
    Disassembling ACPI files
     
    Download iASL to your Downloads directory, type this in Terminal:
    cd ~/Downloads git clone https://github.com/RehabMan/Intel-iasl.git iasl.git cd iasl.git make sudo make install Install MaciASL.app to your Applications directory and run this command in Terminal to update iASL:
    sudo cp /usr/bin/iasl /Applications/MaciASL.app/Contents/MacOS/iasl61 Now we are going to disassemble the files. Type in Terminal:
    cd Desktop cd ACPI iasl -da -dl *.aml You can also try to disassemble them using External declarations in a text file called refs.txt. This may help to fix some unresolved externals (symbols not defined in any file). Copy the following text and create a refs.txt into ACPI folder in your Desktop:
    External(MDBG, MethodObj, 1) External(_GPE.MMTB, MethodObj, 0) External(_SB_.PCI0.LPCB.H_EC.ECWT, MethodObj, 2) External(_SB_.PCI0.LPCB.H_EC.ECRD, MethodObj, 1) External(_SB_.PCI0.PEG0.PEGP.SGPO, MethodObj, 2) External(_SB.PCI0.GFX0.DD02._BCM, MethodObj, 1) External(_SB.PCI0.SAT0.SDSM, MethodObj, 4) External(_SB.PCI0.SAT1.SDSM, MethodObj, 4) External(_GPE.VHOV, MethodObj, 3) Type in Terminal:
    iasl -da -dl -fe refs.txt *.aml Using refs.txt or not, this will create .dsl files that we will use to patch. Open them using MaciASL and click “Compile” to check for errors. Main mission here is to have them compile without errors (warnings and optimizations are ok).
     
    We only need DSDT and all non dynamic SSDT files. Clover shows dynamic SSDT files adding "x" (SSDT-4x.aml for example). Use dynamic files only to disassemble.
     
    NOTE: never open .aml files with MaciASL and compile, if you ever get lost among DSDT and SSDT files, extract and disassemble them again.
     
     
    POST-INSTALLATION…
     
    Ok, we can boot our Sierra installation, we have our ACPI files disassembled and with no errors, not patched yet, so it’s time to start fixing things.
     
    First thing to fix must be CPU Power Management. For that we use ssdtPRGen.sh. In my CC2_PACK.zip there is a SSDT for my CPU (i5-4258U).
     
    If you have other CPU, you need to generate a proper one (you will need internet access so install now FakePCIID and FakePCIID_Broadcom_WiFi and copy all WiFi related Clover patches from config_OK.plist to your config.plist). Open Terminal and type this command to download ssdtPRGen:
    curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh Now change the file mode (+x) with:
    chmod +x ~/ssdtPRGen.sh Default SSDT generation:
    sudo ~/ssdtPRGen.sh Type n and n one more time. Open Finder and go to /Library/ssdtPRGen/. You will see a SSDT.aml, this is our CPU Power Management SSDT. Copy it to your EFI/CLOVER/ACPI/patched. You will see if PM is well implemented if X86PlatformPligin is loaded under CPU0@0 in IOReg (use IORegistryExplorer to check it. You can also use AppleIntelInfo.kext)
     
    Open SSDT-HACK.dsl with MaciASL, save it as SSDT_HACK.aml and put it into EFI/CLOVER/ACPI/patched. You can check SSDT-HACK.dsl to see what I did there (Basically, emulate Windows (_OSI to XOSI), injecting IGPU properties and ig-platform, disabling EHCI, injecting XHC properties, fixing GPRW to avoid instant wake and making EXEL and ESEL do nothing).
     
    Second thing should be IGPU Power Management. For that GFX0 needs to be renamed to IGPU in our DSDT and all SSDT files that contain any GFX0 reference. We will rename it in DSDT using Clover patch and manually find/replace in SSDT files (in our case, SSDT-7 has some GFX0 code).
     
    Third, we are going to install some kexts to enable Bluetooth, WiFi (if you replaced default wireless card with BCM94352Z), all USB ports and backlight control. Just open Kext Wizard (we will always use it to install kext files), click “Install” and look for:
     
    - FakeSMC.kext
    - FakePCIID.kext
    - FakePCIID_Broadcom_WiFi.kext
    - IntelBacklight.kext
    - XHCInjectorCC2.kext
    - BrcmPatchRAM2.kext
    - BrcFirmwareRepo.kext
     
    Any time you install any kext file, you must rebuild your cache and fix permissions. You can do it with KextWizard but it is recommended to use Terminal (see TIPS AND EXTRAS)
     
    Now that you have WiFi enabled, OS X probably put it at en1 while Bluetooth PAN is at en0. To reorder them just do the following:
     
    - Go to System Preferences > Network and delete all interfaces (WiFi and Bluetooth PAN). If you are asked about bluetooth reappearing again, click no.
    - In Finder go to ~/Library/Preferences/SystemConfiguration and delete NetworkInterfaces.plist.
    - Reboot, go to System Preferences > Network and add your WiFi interface again.
     
    This will reorder your interfaces, leaving WiFi as en0 and letting you to access Apple services as Mac App Store. You still needing to create a good SMBIOS profile, with a serial, etc. in order to activate everything: FaceTime, iMessage, Mac App Store… You can follow these guides:
     
    How to enable iMessage
    Clover: iMessage/Facetime Fix for Yosemite
     
    With all this you will have everything working except for battery status and audio/sound. Now it's a good time to install Wacom drivers.
     
    Battery status needs ACPIBatteryManager.kext to be installed and a patched DSDT. I’ve created a patch that you can use with MaciASL and your DSDT (you extracted and disassembled before, remember?), just click “Patch” and look for Battery CC2 Patch.txt, apply and save.
    NOTE: Recent tests with RehabMan probes my patch matches Dell XPS 18, so that will work too. Use any of them.
     
    IMPORTANT: Until now we were booting with ACPI/SSDT/DropOEM=false because we weren't using patched OEM files. Now we are going to use a DSDT file, so we must also provide all patched SSDT files, set DropOEM=true and set SorterOrder (same order than OEM files, making SSDT.aml the first and SSDT-HACK.aml the last, so it will be: SSDT.aml, SSDT-0.aml, SSDT-1.aml, SSDT-2.aml, SSDT-3.aml, SSDT-7.aml, SSDT-HACK.aml). You can do this with PlistEdit Pro or Xcode by yourself (check Clover Wiki for how-to). Anyway, I've prepared config_OK.plist with all these changes and more patches. Paste it in EFI/CLOVER/ and rename it to config.plist to continue with post-installation.
     
    I would like to avoid adding patched ACPI files transforming my DSDT patch to the new hotpach method (thanks Rehabman!), adding code to SSDT-HACK and adding DSDT/patches to Clover if necessary but is waaaay out of my league. Any help achieving this will be appreciated.
     
    NOTE: DSDT only needs Battery CC2 Patch for now. SSDT files only need names to be balanced, so any rename we are doing with Clover in ACPI/DSDT/Patches need to be do it as well in all SSDT (GFX0 to IGPU; B0D3 to HDAU…)
     
    If you did it all well, you should have battery status working.
     
    Audio/Sound can be achieved installing VoodooHDA. You will be able to use the internal microphone and speakers, so Siri will work. Airplay audio works too. HDMI needs work.
     
    A better choice would be to patch our codec and use AppleHDA, HDMI audio seem to work better this way and might help to fix sleep/wake. I’ve attached a dump from my Realtek ALC286 and my Intel Haswell HDMI if somebody want to help with this matter.
     
     
    CLONING TO INTERNAL DRIVE
     
    Now that you have an almost fully working hackintosh, you probably want to clone it to your internal SSD. For that, just follow these steps:
     
    - Boot into Windows, and shrink your C: partition using Disk Management.
    - Format new volume to FAT32 and give it a name (you can use MacDrive to format to HFS+J)
    - Boot using your USB installer, open Disk Utility and format your new internal partition to HFS+J (if you didn’t do it before using MacDrive). If you are prompted with an error, try it again. If error persists, try next step.
    - Clone your current installation selecting as source your SierraHD drive and destination your new internal partition.
     
    After clone, you still needing to install Clover in your internal EFI partition, so boot again your Sierra installation using your USB and repeat steps in INSTALLING CLOVER IN USB INSTALLER…  You also need to place proper config.plist and your ACPI patched files, SSDT.aml and SSDT-HACK.aml in EFI/CLOVER/ACPI/patched. Note that your internal EFI partition could have no name, mine in fact shows as NO NAME in Finder
     
    In order to boot your internal Clover installation, you might like to create an entry in your Windows Boot Manager. I use EasyUEFI for that. Just click on the Create a new entry icon, select Linux or other OS, and select the path to EFI/CLOVER/CLOVERX64.EFI. Give entry a name, for example macOS Sierra
     
     
    NOTES:
     
    I still having some doubts about this guide. For example:
     
    - Our graphics device 8086,0A2E is natively recognized but doesn’t show a name in DPCIManager, I don’t know if can be an issue.
    - PCI Realtek Card Reader 10EC,5229 has no support.
    - USB may need work to make wake from Power Button work properly. I’ve created an injector and disable EHC with SSDT-HACK.aml and it’s under 15 port limit. I did the same with a EHC injector and FakePCIID_XHCIMux.kext or USBInjectAll.kext and a SSDT-UIAC.aml. Same result, ports work, wake with Power Button doesn’t, some of them are lost when reboot after try to wake up from sleep (using Power Button)
    - There are some errors with methods in EC0 that probably need work (GBTT, SMB0._STA)
    - Good news!! Cintiq Mode works Just plug your cable to your PC or Mac, put your Companion to sleep and it should wake as a plain Cintiq and recognized by your PC or Mac. When you unplug your video cable, you Companion come back with everything working. Enjoy
     
    - I did another test and wake quite good but with black screen: go to sleep (no cable video plugged), plug video cable, this will make screen wake but remain black, unplug video cable, use screen sharing to access and change resolution or detect displays in SysPref to push the signal to your internal display.
     
     
    TIPS AND EXTRAS
     
    - If you want to install any software, you must enable the lost option inside Security and Privacy. Type this in Terminal:
    sudo spctl —master-disable - If you want to enable HiDPi resolutions, just copy DisplayVendorID-5c23 folder into ~/System/Library/Displays/Contents/Resources/Overrides and install RDM.
     
    - If you need to rebuild caches, run this in Terminal:
    sudo rm -r /System/Library/Caches/com.apple.kext.caches sudo touch /System/Library/Extensions && sudo kextcache -u / - Sometimes boot into safe mode is needed. Just add -x  to boot flags in Clover or push spacebar in Clover boot menu (this second option is not working for me right now, I don’t know why).
     
    - To enable playing a power chime sound effect when battery charged is plugged, type this in Terminal:
    defaults write com.apple.PowerChime ChimeOnAllHardware -bool true; open /System/Library/CoreServices/PowerChime.app & - If you want to try the new TouchBar present in new MacBook Pro, you can give it a try! Go here and follow instructions
     
     
    CONCLUSIONS AND THOUGHTS
     
    The Cintiq Companion maybe is not a famous tablet because its mainly client target are professional artists than doesn’t have too much time to play with this hackintosh stuff, but it works very well in my opinion, better than Surface devices. Geekbench results is same than MacBook Pro with same CPU and LuxMark gives a result of more than 1600 for what I checked.
     
    The only thing that it would need to be perfect, in my opinion, is to sleep and wake properly. We can do that just plugin the video cable and entering Cintiq Mode, unplug and wake but it would be nice to wake it with the Power Button. For those who could help, here you have some clues you may find helpful to solve it.
     
    Sleep works, display goes off, fans go off and led starts blinking. But when wake (only with power button) display goes back but remains black for seconds and suddenly go off, fans keep running, led keep on without blinking, but can’t access using VNC or screen sharing. If you enable the power chime sound effect, you will hear it if you unplug and plug your battery charger.
    The only way to come back is to force a restart by holding power button and next time you boot some devices are missing (WiFi and some USB). Restarting one more time makes all devices work again.
     
    Since I have no idea of binary patching, programming or ACPI concepts, it was very hard for me to get all this together. I’m probably doing something wrong or there’s a better way to make things work, so if you have any idea or suggestion, don’t hesitate to comment or ask. I'm doing this for two reasons, to share what I learned and to keep all the information together in one post.
     
    And this is everything, folks! I hope this help you to install macOS Sierra in your Companion 2. Now that new model is out (but far away from my budget) you can find some affordable second hand units.
     
    DOWNLOAD MY CC2_PACK
    It contains:
    ACPI folder, before and after patches (for those who want to check). Battery CC2 Patch. Kexts folder. Official BIOS folder, in case you didn’t update your Companion 2 or disabled CSM support and can’t see BIOS menu. SSDT Files folder, containing SSDT-HACK.dsl and SSDT.aml for i5-4258U PM. APPS folder: Clover Configurator 2, DPCIManager, PlistEdit Pro, Kext Wizard, MaciASL, IORegistryExplorer. EXTRAS folder: Brightness app (slider control in menu bar), Intel Power Gadget, iStat Pro widget, AppleIntelInfo.kext (for checking CPU PM). HiDPi: DisplayVendorID-5c23 folder and RDM-2.2.pkg codec_dump_ALC286.txt and codec_dump_HDMI.text for someone to may help patching AppleHDA.  
    I want to give a HUGE thanks to all the people that are involved in making this possible, from developers to testers (Piker, Rehabman, the-darkvoid, Slice, Allan... I don't know, I'm still learning who you are, people, you are a lot so don't be offended if I didn't mention you, please ). And sorry if there's some grammar mistakes or something, it's my first guide in english.
  16. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    From what I've read in different threads it could be a better choice to install El Capitan, instead of Yosemite, if you're using Broadwell graphics. At the moment I can't use Sierra, since a lot of the software I'm using has still problems with it, but maybe it would be a future proof choice to use El Capitan?
    Would there be something I need to take care of accept of removing kext-dev-mode=1 and adding the RtVariables?
  17. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    Thank you for the platform-ids, I'll check them tomorrow. I already checked these ids today (some are in your list too):
     
    A = it boots into Yosemite, but I get an error message while booting and the card isn't recognized. Probably just an invalid ID.
    B = no error while booting, but I only get the black screen with a mouse-cursor, instead of Yosemite
     
    0x162b0000 B 
    0x162b0002 B
    0x162b0004 B
    0x162b0006 A
    0x162b0008 A
    0x16260006 B
    0x162B8086 A
    0x0a160000 A
    0x0a16000c A
    0x04160000 A
    0x0c160000 A
    0x04002B16 A
     
    Since the B ones are in your list too, I get the impression they could be useable, but I have to fix something else first. I just don't know what it could be, since I finally included all SSDT and DSDT files.
    Oh and I attached an IOREG. It's the first time I tried to export this, so I hope I did the right thing.
    Klumpen.ioreg.zip
  18. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    Well, it seems you implemented well CPU power management if those warnings disappeared, mate. This is the very first and most important step, congrats. Now, graphic card.
     
    I've found some ig-platform-id in AppleIntelFramebufferAzul.kext to try with my hack. If you're curious, you can use Hex Fiend to open it and have a look at the code. You can search for a known line of code as a platform-id and start looking and guessing (take a look into Pike's R Alpha blog for some info).
     
    Maybe these are wrong but it won't hurt to try these ig-platform-id and report back. Also post an IOReg to have a look if you have the time. My Iris 5100 is ULT Mobile GT3, you can check yours in Windows with apps like CPU-Z or AIDA64. I guess it will ULT Mobile GT3 too. You can try some from here:
     

  19. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    Yesterday I finally received my Tontec wifi dongle. Surprisingly it uses the Realtek RTL8188CUS, the same as the Edimax EW-7811un, my previous dongle. Kind of luck, cause the Tontec drivers are out of date, but I could use the drivers from Edimax.
    Now I was able to run Piker's script to generate the SSDT.aml. The only thing I noticed, was the disappearing of the "unknown CPU" message. while booting.
     
    The biggest problem are the graphics. I tried a bunch of ig-platform-ids and can divide them into two groups:
    While booting I get [iGPU] Graphics driver failed to load: could not register with Framebuffer driver! two times in a row. Then it boots into Yosemite. The graphics are extremely slow and aren't recognized in "About this Mac" (Graphics Intel Unknown 14 MB) It boots a lot faster and I get no error-messages about my GPU, while booting. It seems to boot into Yosemite and the mouse-cursor is a lot more responsive, but all I see is a black screen and the mouse-cursor. Even if I can't use the companion with ig-platform-ids from group 2, it seems to be the better choice in some way, since I don't get error messages while booting and the more responsive cursor.
  20. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    While using PlistEdit Pro I noticed why it's the better choice. It's a lot easier to use.
     
     
     
    The config_NO_ACPI.plist produces an extremely glitchy image in Yosemite. But if I change the ig-platform-id from 0x16260006 to 0x162B8086 it works like before: I can boot and everything looks normal, but is extremely slow, cause the graphic card isn't recognized.
     
    If I use the config_ACPI.plist in combination with my ACPI files the booting freezes pretty fast, showing this message:
    System uptime in nanoseconds: 1221543219
    Which is really weird, since SetOrder uses exactly the files I included in the patched folder.
    I guess something is still wrong with my files, cause I'm still doing something wrong, but I have no idea what it is.
    But thank you for the files, good to have some decent config.plist to try something with.
     
     
     

    That's really good to know. If I remember correctly my ACPI files were generated using 256MB and now I'm using 128MB. But I'm not exactly sure if I tried something completely weird, like 96mb, to see if this makes any difference. I guess I should generate my ACPI-files again, to be completely safe.
     
     
     

    Since the LED of my wifi-dongle isn't glowing on my Macbook either I came to conclusion that this thing could be broken and ordered another one, which will arrive tomorrow. Hopefully I can use Pikers script with it. After four days without any progress I would be really happy to have the SSDT.aml.
    Oh by transalating the italian threads I found a SSDT.aml, made by Toleda for the Intel Iris 6100 and another SSDT.aml made for the Intel i7-5557U. Could they be of any use?
     
    EDIT: I set my DVMT-Pre-Allocated to 128MB, used Clover F4 and patched these ACPI files again. Now my Companion finally boots with ACPI files and your config_ACPI.plist.
  21. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    Never used Sublime-Text, I recommend to use Xcode or PlistEdit Pro. There's a few "don't use a text editor to edit your config.plist" around the web.
     
    Sorry, my mistake, config.plist I sent was for you, not for GrubLord 
     
    You must be careful and check when you're using ACPI files to set DropOEM=YES, Generate=NO and proper SetOrder. I've created two config.plist for you, one to boot without ACPI files and other to boot with them. Try them. Without ACPI should work with the installer you created and installation you made. Config set for ACPI will work if you correctly patch your DSDT/SSDT (what seems now to be ok, you didn't say nothing about errors).
     
     
    Neither I, man LOL But I'm starting to know why things are needed for this and I think it's time for me to give a hand.
     
    Cool, very similar to mine. You guys must know a thing about this:
    If you change any settings in BIOS, you're changing ACPI files inside the machine and you must extract them again and patch them. This means that if you have changed to 128MB as I said before but you're using ACPI files from a 256MB DVMT Pre-Allocated BIOS, it will give you a kernel panic and won't boot.
    So if you've already extracted your ACPI from 256MB, you can try setting in BIOS DVMT Pre-allocated 256MB again. If you want to try with 128MB, you must extract and patch again (sorry for my previous advice, I didn't give you all info and I noticed that if any of you changed that but are using different DVMT Pre-Allocated BIOS/ACPI, it won't work).
     
    Man, what I told you about linking to, you know, it's against insanelymac rules. 
     
    Oh, italian threads... I'm spanish and don't speak italian, so good luck with Google Translator. But for what I know:
    - CPU just need a proper generated SSDT.aml from Pike's script (but you can try at first with Generate=YES, check my config_NO_ACPI)
    - Graphics just need a proper ig-platform-id, Inject/Intel=YES, InjectEDID=YES
     
    HERE the files.
  22. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    GrubLord & schwarzgrau: Don't use Clover Configurator to edit your config.plist, use always PlistEdit Pro or Xcode. Clover Configurator seems to add unneeded data and corrupts your files. I just use it to mount EFI and generate SMBIOS.
     
    schwarzgrau: I think GrubLors is giving you some clues. For example, his Graphics section in config.plist seems to work, so you might try to copy his values. File is in this thread a few pages back, search for it and download it.
     
    You denitively don't need: LoadVBios, NvidiaSingle and PatchVBios. Remove these entries.
     
    For what I can get from my head right now, just leave there ig-platform-id I put in GrubLord config.plist, Inject/Intel=YES and InjectEDID=YES.
     
    IMPORTANT: It is a bad, bad idea to use ACPI files from another computer. Even having same hardware, lightly differences can output very different ACPI files. That's why it's always recommended to extract yours and use them. I know a lot of people don't take this seriously and use ACPI from other people, and sometimes works, but that's not the way, believe me. 
     
    I know this guide do that, provide patched ACPI files from mactabletman Companion 2. And I was using those during more than one year, but when I decided to learn how to do it myself (because not everything was working) I understood that wasn't the proper way. 
     
    I can't be more thankful to mactabletman (you rock, man) for made this possible, in fact I bought my Companion 2 because I wanted to work in OSX since I've been doing it since 11 years. But I think it's time to an update and with patches list I provided here everybody could extract their own and do it properly. If not, at least, info is here for those who want to learn or find some clues to their problems.
     
    I think, guys, that you will be able to install and have your Companion 2 properly working, almost everything, but you need to know what you're doing and why. I know this is hard (hey, I have no coder or programming background and here I am, you just need some time, get info while testing things, read a lot of threads here and there...).
     
    So good luck! I'll be here trying to help
     
    NOTE: I'm trying to fix my "wake from sleep using power button" issue and I recommend to do a first step before extract ACPI and starting to patch. If you enter BIOS and go to Chipset/System Agent (SA) Configuration/Graphics Configurtion/ you will se three entries and values. Mine by default are set to 256MB everywhere. Check yours and post your results.
     
    - I recommend to start setting DVMT Pre-Allocated to 128MB, leave the others in 256MB.
    - Extract ACPI files again, check my initial solutions (fix ADBG Error for DSDT and delete Packages in SSDT-2) to make them compile without errors and after that start applying patches.
    - Use Graphic section from GrubLord's config.plist.
    - If this doesn't work, maybe a custom patch for Clover to set DVMT-prealloc to 128MB for your ig-platform-id is needed. 
     
    Have any of you found a laptop guide with same CPU and graphics? I think if there's one it would bring mayor clues here.
  23. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    Thank you bertolin. You're right I used a MaciASL version from 2014. I got no compiling errors with the current version, but still can't boot with the SSDTs in place.
     
    Hi GrubLord,
     
    Ya, I came to the same conclusion about the DSDT files. The weird thing is not matter which DSDT.aml and SSDT-x.aml I put into CLOVER > ACPI > patched it won't boot with them. If I remove them I'm always fine. 
    I tried three different version, but had no luck with one of them. I guess I'm doing something wrong in the compiling part. Can you boot into OS X? If so could you send me your aml-files?
     
    And ya, I guess I still inject intel graphics. This is how the Graphics section of my config.plist looks like.
    <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <true/> <key>NVidia</key> <false/> </dict> <key>InjectEDID</key> <true/> <key>LoadVBios</key> <true/> <key>NvidiaSingle</key> <false/> <key>PatchVBios</key> <true/> <key>ig-platform-id</key> <string>0x162B8086</string> </dict> Do I need to set Intel to false? And could you maybe send me your config.plist? I know it's meant to be for Sierra, but currently I'm pretty much desperate, since I'm constantly trying things for the last few days without any progress. The wifi-dongle isn't working, therefore I can't use Pikers script to generate a SSDT, the graphics won't get recognized and I don't understand why it won't accept any of the DSDT.aml I'm trying.
  24. Like
    schwarzgrau reacted to bertolin in CINTIQ COMPANION 2!   
    ig-platform-id I put in your config.plist I think I saw it in a Broadwell graphics (same as you), but as I said before, it might need others things done before being full recognized. DVMT-prealloc is important, you might need to boot with a proper DVMT Pre-Allocated in BIOS and a custom Clover patch to set your graphics with same DVMT-prealloc.
    I might be wrong, different ig-platform-id can be used for the same graphic card. Right now, I'm struggling with that trying to get wake from sleep fully working and the issue is related to all this graphic stuff.
     
    About DSDT/SSDT, you're doing it well, mate. DSDT only needs Fix ADBG Error first, so it compile with no erros.
    SSDT-2 (a CPU SSDT related) needs this to be deleted:
    Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Package (0x06) { 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } I don't know why but this is printed out of _PSS method (I told about this before in this thread I think). Only removing this SSDT-7 compile with no erros.
     
    Here you have your ACPI files. You need to start patching again but these comes with no errors, so if you find some you know you're doing something wrong.
  25. Like
    schwarzgrau got a reaction from bertolin in CINTIQ COMPANION 2!   
    At the moment I can boot into Yosemite, but nothing really seems to work. I expected some change after installing the DSDT.aml and the SSDT-files, but if I understood everything I should try to generate the SSDT.aml first, am I right?
    My next idea would be trying to install all necessary kexts hoping to make the WIFI work. Can I use "some kind of beast who cannot be named" for this?  
     
    To be honest I still don't understand what is really important to make my graphics work for example. Do I need to try some other ig-platform-ids or something else in the config.plist? Has it something to do with the missing SSDT and DSDT files, I try to avoid at the moment or maybe something with some kexts? I tried to google it, but most of the time it's pretty hard to find some basic informations.
×