Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About mac-fish

  • Rank
    InsanelyMac Protégé
  1. Hey everyone, I just got my XPS13 9360 (latest model with Kaby Lake Refresh i7 and UHD 620 IGPU, though the screen is FHD) almost set up in an acceptable state. I am currently running 10.13 and I've used this guide http://www.insanelymac.com/forum/topic/320471-guide-dell-xps-13-9360-on-macos-sierra-1012x-lts-long-term-support-guide/ as a base for installing. I also enabled HWP using the SSDT patch. However i am having some issues with USB-C to HDMI output (presumably due to the LTS guide still using a patched Skylake FB instead of native Kaby Lake FB). When a display is connected to my USB-C to HDMI adapter under OS X, i get a lot of screen flickering; the screen randomly flickers with a random (garbled image) every second to every few seconds (seems somewhat periodic) and sometimes the screen even turns off completely for a second, as if it was losing signal or having transmission errors. It works fine on windows however. Also, when i use Retina Display scaling and put the device to sleep and wake it back up, only a portion of the screen is being used to render the display output on the LVDS. Might be unrelated though. Has anyone managed to get Kaby Lake (or Kaby Lake R, specifically with this UHD 620 chip (platform-id seems to be 0x59178086 by the way...)) working with its native framebuffer? Or have you encountered similar problems? EDIT: I tried using Kaby Lake FB using RehabMans sample plist (using it as a whole and adjusting it) https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/config_HD615_620_630_640_650.plist as well as the updated FakePCI ID release with new device ids It works, however i haven't managed to get HDMI working, even with the proposed property addition in the plist. EDIT 2: I managed to get Kaby Lake FB working 100% using this repo as a base for my patches https://github.com/the-darkvoid/XPS9360-macOS Also managed to get HWP working properly and get the fan to spin up less (turbo toggle, gpu pm adjustments for lower base clock, frequency vector adjustments, some X86PlatformPlugin plist adjustments) and sleep is also working ( had to disable deepidle for that unfortunately ) The garbled image problem actually turned out to be some sort of ground-loop issue with another device connected to the power strip.
  2. Are you also using USBInjectAll.kext? I guess it's quite possible that it is the reason for this, since it's not meant for productive use after all. Also i've been able to fire up Intel Power Gadget since and the speedstepping (including turbo steps) is working fine after wakeup, although the graph updates really strangely (not periodic, random intervals it seems)
  3. Hey everyone, I recently kind of finished building my new Hackintosh Desktop. It has the following specs: OS X 10.13.1 Core i5 6600K 16GB DDR4 RAM @ 2144MHz GTX1070 8GB ASRock Z170 Extreme4 The install went pretty smoothly, and I am booting off Clover with the following kexts being injected: FakeSMC_ACPISensors.kext FakeSMC_LPCSensors.kext FakeSMC.kext IntelMausiEthernet.kext USBInjectAll.kext Lilu.kext NvidiaGraphicsFixup.kext as well as kernel patches for: xcpm bootstrap (probably not necessary anymore) xcpm reboot fix and kext patches: the 15 to 30 port fix for USB pikes APIC fix for skylake as well as SSDT for the CPU and pike's skylake USB fix (which i am not sure does anything for my system as of right now). My only problem is, when i suspend the system and wake it back up, it behaves quite oddly: Key presses sometimes register multiple times, and the system in general responds very slowly, as if the cpu clock wasn't set properly (which i can't verify because intel power gadget does not work after wake up somehow). I haven't found many clues about other people having this particular issue, so that's why i am asking here right now... has anyone of you had a similar issue? i've tried disabling xcpm, tried different SSDTs for the CPU, applying other ways to fix the USB (somehow i can't get around USBInjectAll.kext yet...) EFI.zip IOREG.zip
  4. Ivy Bridge: HD4000 on Sierra

    Hey Hervé, thanks for the hint, however in the meantime I figured it out myself The problem wasn't clover (It booted just fine as I mentioned, it worked without InjectIntel also). Also the backlight was on when the framebuffer loaded. The problem was I forgot to patch AppleIntelFramebufferCapri.kext, which is necessary for laptop LVDS to work. I applied the same method as described in a post from 4 years ago and it works fine with the Sierra driver as well. (here's the guide, there are many others as well though http://forum.osxlatitude.com/index.php?/topic/2945-guide-for-enabling-vga-and-hdmi-in-intel-hd4000-gpu/ ) Thanks anyway and I hope this will help someone out.
  5. Hey guys, I'm back to trying to set up my hack after getting tired of yosemite and being too lazy to upgrade for a year now. So I've updated clover to the latest version and got the kexts required for sierra and installed it onto a new partition. It boots and works quite well already, however I can't seem to get the IntelHD driver for Capri to work. On yosemite this worked fine with the igp platform id 016...03 in the clover plist. However this does not seem to work on Sierra anymore. I have verified that I am using the same boot flags. The issue is that the driver seems to load, however i just get a blackscreen on the LVDS as soon as LoginWindow would start. (can't test other outputs right now) So how could this happen? Did the definitions of the connectors according to the platform id change? Do i have to try different platform IDs all over again? The relevant info about the hardware: Generic Ivy Bridge laptop with i7 3720QM GTX675M and Intel HD4000 (Optimus, The GTX675M is disabled by DSDT patch, however in sierra there are some ACPI errors on boot, might be that the ACPI table format is incompatible? it works fine in yosemite...) I've also tried RehabMan's latest FakePCIID and its Intel HD module, but no luck. Any ideas?
  6. Disabling NVIDIA Optimus card on all laptops

    Here's a patched DSDT for Clevo P150EM based laptops with a GTX675M in my case (might work with other nvidia cards i don't know) I tried to also include the method LexHimself describes, not sure if i did it right, don't have a kill-a-watt or something similar to it. For anyone who might need it P.S.: you need to set ig-platform-id to 0x01660004 for Clover's intel injection to work on this model. DSDT.zip
  7. Disabling NVIDIA Optimus card on all laptops

    Oh wow, I guess i was just too stupid to find the latest version of iasl and use it Thanks a lot. Also i realised i have to replace the iasl binary in MacIASL when using that to compile.
  8. Disabling NVIDIA Optimus card on all laptops

    Hey, it's been a while since I've worked on anything hackintosh related, so I'm not really sure about any of this, I dumped the ACPI tables in linux and got the ones from clover and used the latest iasl version i could find. (20141107) but i keep getting errors about redefined namespaces etc. Does UEFI / BIOS mode make a difference for the ACPI table structure? I got these in UEFI mode. My laptop is a Clevo P150EM, gfx card a GTX670M. Would really appreciated it if someone would take a quick look and tell me if it's doable or help me out a bit tables.zip

    why are people bumping this thread. It will never work. GMA500 is using PowerVR, which is way too proprietary to ever work on os x since there isn't any source code on the driver. There are only pre-compiled drivers for win/linux which don't work properly either.... and you all know that.
  10. alright so after some time of not caring about the brightness issue, i got back to it with some spare time, and saw that the panic caused by brightness change was on CPU 0x2. so i booted with cpus=1 arch=i386, and there we go: brightness changing worked fine. no delayed panics or anything. any ideas how to fix this issue? is it caused by wrong busratio or something similar?
  11. i dont think its os x's issue now that this project is like 4 years old already and there have not been largely reported issues, i suppose your battery is just getting old or something of that kind or just bad drivers.
  12. try, as in this thread it was mentioned, injecting your EDID: http://www.insanelymac.com/forum/index.php?showtopic=208410 you can get it from windows linux / etc installs easily.
  13. I think it should be SL ACPIPlatform running because i installed a package that makes voodoobattery work again, which only works with 10.6.8 acpiplatform. but can you upload SL kext for me? or tell me the version? Also i just realized it randomly still panics to brightness change. sleep still not working.
  14. i've been only editing the 64bit offset, also it might be detected as CRT since i could'nt edit the ControlFlag. As soon as i edited it, the display stopped working completely. EDIT: i updated the 32bit offset, now brightness works, but sleep causes a panic. IOReg still shows the LVDS as display type 10 (CRT?) though
  15. 2nd try ;p i'll try that command. yes it should be recognized as LVDS, as it is in about mac (i edited personality so it is recognized properly, just edit the 3rd segment to 09010000 should work fine EDIT: pmset does not fix sleep, the device turns off for a second then starts back up and i get a blackscreen (no way to VNC into it too, probably crashed) but i still have sleepenabler in there, will try some other possibilities ioreg.txt