Contribute
Register

[solved] Surface Pro 4 Hackintosh - can't get HD520 working

Status
Not open for further replies.
Joined
Jul 6, 2018
Messages
15
Motherboard
Surface Pro 4
CPU
i5-6300U
Graphics
HD 520
I am currently trying to install Mojave beta on a Surface Pro 4.
Everything seems to go very well so far but I can't get my HD520 working.

I tried this method because it worked with Sierra on my SP4:

1. Booted successfully with platform-id 0x12345678
2. Added newest IntelGraphicsFixup.kext and newest Lilu.kext to Clover (/kexts/others)
3. Added RehabMan's Config.plist for HD520 as default config (config_HD515_520_530_540.plist)
4. Added -lilubetaall and -igfxbeta bootflags
5. Rebuilded cache (sudo kextcache -i / )
6. Rebooted with platform-id 0x19160000 (also tried 0x191B0000)

It results in a kernel panic (see attachment, sorry for the quality, this is the best I could do..)
I can't figure out whats the problem here. Thanks for any help :)
 

Attachments

  • 1.jpg
    1.jpg
    162.1 KB · Views: 602
  • 2.jpg
    2.jpg
    103.3 KB · Views: 467
  • 3.jpg
    3.jpg
    73.5 KB · Views: 424
  • 4.jpg
    4.jpg
    65.5 KB · Views: 426
Last edited:
I am currently trying to install Mojave beta on a Surface Pro 4.
Everything seems to go very well so far but I can't get my HD520 working.

I tried this method because it worked with Sierra on my SP4:

1. Booted successfully with platform-id 0x12345678
2. Added newest IntelGraphicsFixup.kext and newest Lilu.kext to Clover (/kexts/others)
3. Added RehabMan's Config.plist for HD520 as default config (config_HD515_520_530_540.plist)
4. Added -lilubetaall and -igfxbeta bootflags
5. Rebuilded cache (sudo kextcache -i / )
6. Rebooted with platform-id 0x19160000 (also tried 0x191B0000)

It results in a kernel panic (see attachment, sorry for the quality, this is the best I could do..)
I can't figure out whats the problem here. Thanks for any help :)

Must use correct minStolenSize patch. Refer to config_deprecated.plist from my laptop plist repo.
The github project is linked from the guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
Just to make sure I did it right, I added following entry to the config.plist:

<dict>
<key>Comment</key>
<string>Disable minStolenSize less or equal fStolenMemorySize assertion, 10.14 (credit Austere.J)</string>
<key>MatchOS</key>
<string>10.14.x</string>
<key>Name</key>
<string>com.apple.driver.AppleIntelSKLGraphicsFramebuffer</string>
<key>Find</key>
<data>dkBI/wVh6Qc=</data>
<key>Replace</key>
<data>60BI/wVh6Qc=</data>
</dict>

I still get the same kernel panic.
 
Just to make sure I did it right, I added following entry to the config.plist:

<dict>
<key>Comment</key>
<string>Disable minStolenSize less or equal fStolenMemorySize assertion, 10.14 (credit Austere.J)</string>
<key>MatchOS</key>
<string>10.14.x</string>
<key>Name</key>
<string>com.apple.driver.AppleIntelSKLGraphicsFramebuffer</string>
<key>Find</key>
<data>dkBI/wVh6Qc=</data>
<key>Replace</key>
<data>60BI/wVh6Qc=</data>
</dict>

I still get the same kernel panic.

Keep in mind you must wait until post install to apply any such patches (as you must rebuild kernel cache).

And it is not possible to tell what you're actually doing without PR files.

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
I already rebuild the kernel cache without any kext patches applied.
Sorry for missing PR files. (see attachment)
 

Attachments

  • 5.jpg
    5.jpg
    171.9 KB · Views: 311
  • 6.jpg
    6.jpg
    116.4 KB · Views: 298
  • CLOVER.zip
    2.8 MB · Views: 259
I already rebuild the kernel cache without any kext patches applied.
Sorry for missing PR files. (see attachment)

Attach full PR files (ioreg/kextcache/etc) with the setup you're using to rebuild cache.
 
Sorry, I got u wrong there, here are the files:
 

Attachments

  • debug_7104.zip
    2.6 MB · Views: 168
The Link will be helpful in the future, thanks for that.

Unfortunately, I'm sure the patch was suitable for the installed Mojave Beta 2. Nevertheless I changed it to the shortened version, I still get the same kernel panic.
 

Attachments

  • IMAGE 2018-07-10 22:38:54.jpg
    IMAGE 2018-07-10 22:38:54.jpg
    226.3 KB · Views: 226
Last edited:
Status
Not open for further replies.
Back
Top