Recently Browsing 0 members
No registered users viewing this page.
Hi, I made sure I got the right kexts and bios settings for my system, and followed every step I could take on Dortania's opencore github guide but I was met with kernel panic. I sanity checked my config.plist and made sure I had the exact settings for my Whiskey Lake laptop. I've dumped my DDST and generated SSDTs using the SSDTTime method, except XOSI (I tried manually recompiling the GPIO SSDT but I also got the same kernel error). I made sure I deleted unnecessary kexts and ACPIs. I'm thinking that my Zenbook laptop has a specific way of handling Hackintosh. If anyone could take a look into my EFI folder and find what's causing them It would be greatly appreciated.
EFI and kernel panic picture is attached below
ASUS Zenbook UX331FN
Intel UHD Graphics 620
8GB of SDDR4
Im working myself trough this guide: https://github.com/daliansky/XiaoMi-Pro-Hackintosh
Worked quite good so far. Mac OS is running.
Internal Wifi is working and i patched the bios for better graphics and undervolting later.
However i cant seem to get NVMEFix.kext running with OpenCore 0.6.3
I put the kext into the kext Folder and when i add it to my config.plist the Laptop kenel panics on the apple logo.
So do i something wrong in the config or is it just broken ?
Could someone who has that running post his plist ?
I have a Samasung 970 Evo in the Laptop and i heard from multiple sources that card would need the fix for better performance.
My plist: https://pastebin.com/7jg624tu
What i add the get NVEM running (after all the other kext in der Kernel section): <dict> <key>Arch</key> <string>x86\_64</string> <key>BundlePath</key> <string>NVMeFix.kext</string> <key>Comment</key> <string>NVME\_Fix</string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>16.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict>
Thanks for the help!
PS: I wanted to post this in the NVMEFix Section but the forum won't let me so hoping the devs there will see this :-)
Thanks for your great help!
Hi. I need help if possible.
I tried installing Big Sur on my Hackintosh with OC and Catalina working. Every time I try to boot it I receive a kernel panic relative to ACPI. The strange thing is that this kernel panic occurs only with Big Sur and High Sierra. Every other macOS version boots (I tried from 10.9 to 11).
My build is:
Motherboard: Gigabyte X79-UD3 CPU: Intel Core I7 4820K GPU: XFX Radeon RX570 I'm attaching the kernel panic and my EFI configuration (I still need to map the USBs 'cause I switched to OpenCore yesterday).
PS. In the OC folder there's not a resources folder because I deleted it to upload it
Kernel panic Big Sur.rtf
This post is targeted at users who have an Ice Lake-based laptop.
- Major Updates on Sep 5:
Both fixes have been integrated into WhateverGreen and will be available as of v1.4.2, so public tests are now over and thanks for your participation.
I have renamed this post, so feel free to use it as a general discussion thread.
Mobile Ice Lake processors can be classified by their integrated graphics card into three categories, G1, G4, and G7.
You could find information about your processor in the following table.
Note that Apple uses NG* processors on genuine Macs.
Even though device IDs of UHD Graphics on G1 series processors are not listed in Info.plist, the driver itself does support the hardware.
As a result, you need to spoof the device ID (e.g. 0x8A5A) to make UHD Graphics work with full acceleration.
As far as I know, there are two major issues one might encounter while trying to make the integrated graphics card work on macOS Catalina.
1) The kernel panic due to an unsupported CD clock decimal frequency can be resolved by adding the boot argument `-igfxcdc`.
panic: "[IGFB][PANIC][DISPLAY ] " "Unsupported CD clock decimal frequency 0x158\n" @/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-14.7.8/IONDRV/ICLLP/AppleIntelFramebuffer/AppleIntelClocks.cpp:348
2) The kernel panic due to an unsupported ICL SKU is related to DVMT pre-allocated memory.
You might find something similar to the following lines right above the kernel panic message.
[IGPU] HWCAPS - GPU Sku: 0 [IGPU] HWCAPS - VEDBOXEnableFuses:0xf00ff VEBox units enabled: 4 VDBox units enabled:8 [IGPU] HWCAPS - NumSlices: 0 SlicesCountFuse:0x0 [IGPU] HWCAPS - NumSubSlices:32 SubSliceCountFuse:0x0 [IGPU] HWCAPS - MaxEUPerSubSlice:8 EUDisableFuses:0x0 ExecutionUnitCount:256 [IGPU] ERROR: Unsupported ICL Sku! You could resolve this issue by changing the DVMT pre-allocated memory to 64MB or above in your BIOS.
If your BIOS does not provide such options, you could try EFI Shell (setup_var) or RU.EFI to modify BIOS settings.
If your laptop uses a custom UEFI firmware or has a strict BIOS protection, you should add the boot argument `-igfxdvmt` to solve the problem.
Once you have applied above fixes, you should be able to boot into desktop with full graphics acceleration.
If you get stuck in `gIOConsoleUser`, you should try different `ig-platform-id`s and make sure that you have enabled other necessary fixes, for example the Core Display patch (`-cdfon`) for built-in 4K display.
You need to compile the latest WhateverGreen from the upstream repo (https://github.com/acidanthera/WhateverGreen) until Acidanthera officially releases v1.4.2.
3) Apple has removed the assertion of DVMT stolen memory from the framebuffer driver on ICL platforms, but you are strongly encouraged to patch the framebuffer properly to get rid of the insufficient stolen memory error.
You could find the following line in your kernel log.
kernel: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][DISPLAY ] Insufficient stolen memory You should adjust the size of framebuffer and cursor memory, so that the total amount of required stolen memory is less than the one pre-allocated by BIOS. This might also fix the distorted image around the mouse cursor.
I managed to install Mojave on my MSI GP62-6QE laptop with somewhat success. The only annoying thing left is that everytime I shut it down it seemingly kernel panics and I get the "Your computer has restarted because of a problem" at startup.
I tried many different things such as removing emuvariablesuefi64, checking FixShutdown in CloverConfig but it seems the NVRAM is causing this issue.
I have deleted the nvram file from the EFI partition but it seems stuck somewhere else, I can't clear out the nvram from the terminal or in single user mode as it returns a "Not permitted" error.
Clearing out the nvram by pressing F11 at the boot menu screen works however.