Jump to content

Odiolitos

Members
  • Content Count

    5
  • Joined

  • Last visited

About Odiolitos

  • Rank
    InsanelyMac Protégé
  1. Odiolitos

    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!
  2. Odiolitos

    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.
  3. Odiolitos

    CINTIQ COMPANION 2!

    Hi guys, I'm having a bit of (another) problem: after cloning the usb drive to the internal disk, am I supposed to install clover in that partition from the installation usb? Where should I put the config.plist? I can't see an EFI partition for it, and can't boot the computer from it when I select the partition to boot. Could this be a bad clone? I've tried several times to clone it, and always get the same result, so obviously I'm doing something wrong. Thanks!
  4. Odiolitos

    CINTIQ COMPANION 2!

    Also, I'm considering swapping the internal SSD, but I'm in doubt as to which I should get. I've seen some m.2 SSDs have two "blocks" of pins, while others have three. Can anyone who has opened the device tell me what the drive looks like? I've read some SSDs have NVME support, others don't. Is this something take into account, too? Thanks a ton! EDIT: I missed the fact that an appropriate SSD form factor was suggested by Chuppiejones already. It's a 2280 m.2 SSD.
  5. Odiolitos

    CINTIQ COMPANION 2!

    Hi guys, Absolute noob here, but wanted to give this a try. I followed Bertolin's guide to dual boot the CC2, but ran into some problems/doubts along the way: - "About my Mac" tells me my graphics card is 5100, but I know it's a 6100 model (Windoze told me!). Running from the USB key, graphics are a tiiny bit laggy, but my guess is it's the reading from a USB that's causing it. Should I do anything to tell the CC2 it's actually rocking a different card? I tried to change ig-platform-id through clover configurator to 0x1620002 as schwarzgrau suggested, but I still get a 5100 reading, and a message on boot stating that [iGPU] Graphics drivers failed to load: could not register with Framebuffer driver. - None of the cameras in the device are recognised. I suppose this could have something to do with the USB ID? Anyway, not a vital part to me, but it would be nice to have it working. - Surprisingly, I have read access to the SD card (it's formatted in exFat), and it recognizes its whole 128 gb, so relatively few problems there. I know it shouldn't be working from the guide, but you never can tell. Funnily enough, when I boot into Windows 10 again, it changed its mounting letter (which I had fixed in Disk management). If there's an explanation for that, I'm all ears!! Apart from the sound issues and my doubts regarding the graphics card, I'm almost ready to bite the bullet and clone it to my internal SSD. I'll keep this post as a log of sorts for the whole process, so newcomers like me have some extra reference. [EDIT: I ACTUALLY SOLVED THE ISSUES LISTED BELOW, AND I'LL TRY TO EXPLAIN HOW BENEATH MY OWN QUESTIONS] - ACPIBatteryManager.kext doesn't seem to be working: when I try to patch my DSDT through Battery CC2 Patch.txt, MaciASL tells me there's 21 errors and it won't save the .aml file. Also, even if this came out fine, I wouldn't know where to put it. My guess is EFI/CLOVER/PATCHED/ACPI, but I just couldn't tell... I was considering re-extracting the original DSDT and SSDT and re-patching them, but before that I applied the DellXP18 battery patch. On the next reboot, I got 100% battery sign, so I'm guessing battery management is solved, in spite of the problems it had before. I honestly can't tell which solved the issue, though... - After installing to SierraHD (the second USB), Sierra runs fine, but can only boot if install_osx (the first USB key) is there. I've read somewhere that could be a matter of the USB key being slow, and I can live with that, since the intention is to put OS in my internal drive, but I'm not sure if that could signal a problem. There seemed to be some trouble with kexts, and rebuilding cache seemed to do the trick. Also, I hadn't gone through the whole process of actually removing every other BIOS entry BUT UEFI:USB KEY. I'm not sure which of the two did the trick, but I can now boot from SierraHD. In that regard, I'm one happy camper! - I checked IO in my CPU, but there was no mention of X86PlatformPligin there. Because I can't get the CC2 to connect to the internet yet (tried one of those USB to ethernet dongles to no avail, as well as a regular WIFI USB dongle: no dice!), and because I happen to have the same model as Bertolin, I copied his SSDT.aml to EFI/CLOVER/ACPI/patched, but still got this result. Am I supposed to be doing anything except copy the patched files in place in the EFI partition? Again, this may have been solved by rebuilding cache via terminal: I previously repaired them through kextwizard. - VoodoHDA PrefPane only shows HDMI as a possible output, so I have no sound (couldn't check this with any HDMI monitor with speakers!). Is there anything I'm missing? It actually got to work out of the blue once, and on reboot had lost "speakers" as an option. It seems like the internal speakers option is lost if you enter the "audio" preference pane instead of the VoodooHDA one. Every time I've booted the system since, it found the speakers. Haven't tried the microphone yet, so I'm not calling this a victory just yet... ____________________________________________________________________________________________ Sorry for all the noob questions, and for asking in what may be the wrong place, but I'm a bit lost! Oh, and thanks to all of you for the work you put into this! Cheers! Carlos.
×