Contribute
Register

Surface pro 6 - Kernel panic After 6 seconds.

Status
Not open for further replies.
1) Clover 15h58 is a copy of Mojave on Acer Swift 3 Guide. I changed ig-platform-id in 0x12345678. I did F2 but F4 froze the laptop. In the zip, I only boot with F2.
Result: Black screen

Why do you expect a CLOVER setup for an Acer to work with your Microsoft Surface?
That config.plist doesn't even have -cdfon (for WhateverGreen.kext), which will likely be needed for any kind of HiDPI display...

2) Clover 16h17 is a standard version with your clover, lastest Kexts.
I just copy and paste the config.plist of Clover 15h58 with the modification.
Result: End randomseed

This config.plist is not from my guide... In fact, it has a bunch of hotpatch content which would require very specific SSDTs in ACPI/patched. Nothing in ACPI/patched. Not sure why you would expect this setup to work.
 

Attachments

  • CLOVER 1212 16h35.zip
    4 MB · Views: 92
I tried others clover with similar CPU and GPU to see if I can go further.

I reused Clover 16h17, a standard version with your clover, lastest Kexts.
I add the config_HD615_620_630_640_650.plist (from https://github.com/RehabMan/OS-X-Clover-Laptop-Config/archive/master.zip).
I changed ig-platform-id in 0x12345678.

Result: End Randomseed

Make sure you're using a USB2 flash drive.
As is written in the guide, USBInjectAll.kext may be useful, as may XHCI-unsupported.kext.
You also forgot SATA-unsupported.kext.
Also, as per guide, OsxAptioFixDrv-64.efi instead of AptioMemoryFix-64.efi is something you should try.
 
Yes, we tried on USB2 Flash drive.
 
As is written in the guide, USBInjectAll.kext may be useful, as may XHCI-unsupported.kext.
You also forgot SATA-unsupported.kext.
Also, as per guide, OsxAptioFixDrv-64.efi instead of AptioMemoryFix-64.efi is something you should try.

The laptop doesn't have SATA but NVMe SSD Hynix. So we did see the point to add SATA-unsupported.kext.
1) So, I tried 4 combinaison between : USBInjectAll.kext, XHCI-unsupported.kext, OsxAptioFixDrv-64.efi , AptioMemoryFix-64.efi
Result: End Randomseed.

2) I was thinking to install IONVMeFamily.kext as I have a NVMe SSD Hynix.
But, there's no need according your message in https://github.com/RehabMan/patch-nvme

10.13 High Sierra
With 10.13, Apple has fixed their IONVMeFamily.kext and now it supports 512 byte block sizes natively. This means for many NVMe SSDs, you do not need these patches. Still, the special patches for LiteOn/Plextor/Hynix SSDs may be necessary (see above).

3) As I have a NVMe SSD Hynix, I planned to install the Special patches for LiteOn/Plextor/Hynix NVMe
I read http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/page-42#entry2356251.
I was thinking to add in my config.plist this text: https://github.com/RehabMan/patch-nvme/blob/master/NVMe_patches_10_12_6_sec2018-005.plist.

I followed the instruction of How To Patch M2 NVME Mac OS Sierra with Easy.
Just 2 copy and paste in right place : <key>VanillaMD5</key> and <key>KextsToPatch</key>
Pike R. Alpha name appeared correctly in plistedit pro.
Boot it.
Result: End Randomseed.
 

Attachments

  • CLOVER NMVe patch + XHCI-unsupported + AptioMemoryFix-64.zip
    4 MB · Views: 60
  • CLOVER USBInjectAll + AptioMemoryFix-64.zip
    4 MB · Views: 85
  • CLOVER USBInjectAll + OsxAptioFix3Drv-64.zip
    4.1 MB · Views: 83
  • CLOVER XHCI-unsupported + AptioMemoryFix-64.zip
    4 MB · Views: 99
  • CLOVER XHCI-unsupported + OsxAptioFix3Drv-64.zip
    4 MB · Views: 105
Last edited by a moderator:
The laptop doesn't have SATA but NVMe SSD Hynix. So we did see the point to add SATA-unsupported.kext.
1) So, I tried 4 combinaison between : USBInjectAll.kext, XHCI-unsupported.kext, OsxAptioFixDrv-64.efi , AptioMemoryFix-64.efi
Result: End Randomseed.

2) I was thinking to install IONVMeFamily.kext as I have a NVMe SSD Hynix.
But, there's no need according your message in https://github.com/RehabMan/patch-nvme

10.13 High Sierra
With 10.13, Apple has fixed their IONVMeFamily.kext and now it supports 512 byte block sizes natively. This means for many NVMe SSDs, you do not need these patches. Still, the special patches for LiteOn/Plextor/Hynix SSDs may be necessary (see above).

3) As I have a NVMe SSD Hynix, I planned to install the Special patches for LiteOn/Plextor/Hynix NVMe
I read http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/page-42#entry2356251.
I was thinking to add in my config.plist this text: https://github.com/RehabMan/patch-nvme/blob/master/NVMe_patches_10_12_6_sec2018-005.plist.

I followed the instruction of How To Patch M2 NVME Mac OS Sierra with Easy.
Just 2 copy and paste in right place : <key>VanillaMD5</key> and <key>KextsToPatch</key>
Pike R. Alpha
name appeared correctly in plistedit pro.
Boot it.
Result: End Randomseed.

AptioMemoryFix*.efi and OsxAptioFix*.efi are mutually exclusive.
 
Yes, i didn't put them together.
You can see on clover names I attached on my peeprevi message.
 
Yes, i didn't put them together.
You can see on clover names I attached on my peeprevi message.

For you to check. I'm not going to look at all the ZIP files you uploaded.
Also, NvmeExpressDxe-64.efi is not recommended, not needed.

You should really do some google research for specific information on your laptop.
 
Status
Not open for further replies.
Back
Top