The panel is the same, but you must make sure to use an eDP card with the correct EDID setup in its firmware for the display will be correctly recognized.
> My USB ports are properly mapped and I am using the same kext with both network cards but still I have the issue with one
You shouldn't need to have USBInjectAll.kext then.
> Also in Windows 10 I am experiencing the same behaviour
IF it does it with different Operating Systems, then you...
Your BT chipset is powering off when your computer goes to sleep. That's why your BT devices can't wake your computer up.
So need to create a custom USB kext that matches your ports.
The New Beginner's Guide to USB Port Configuration
You can try to compare the ioreg between Clover EFI that causes the corruption and the one that works to see if the same framebuffer and settings are being used.
Make sure
-> your iGPU is set as primary in your BIOS.
-> DVMT is enabled and set to 64
Install latest Lilu and WhateverGreen (that one is missing in your kexts/Other folder) and use that config.plist
Sorry for the late reply, I've been busy recently and completely forgot to check my notifications.
You can still try to use that drive and if it starts creating issues again, you'll know that it is physically damaged.
Check its health with a S.M.A.R.T compliant app.
There's a kext that prevents your touchscreen to work when booting in normal mode
Try using that calibration tool for your touchscreen (eGalaxHidDaemon_v1.5) from the manufacturer
Please post screenshots of Hackintool >> USB and PCIe.
Also post your new zipped EFI folder and a screenshot of...
Did you create a USBPorts.kext that matches your motherboard with Hackintool?
https://www.tonymacx86.com/threads/the-new-beginners-guide-to-usb-port-configuration.286553/
https://dortania.github.io/OpenCore-Desktop-Guide/troubleshooting/troubleshooting.html#bios-reset-or-sent-into-safemode-after-rebootshutdown
3. BIOS reset or sent into Safemode after reboot/shutdown
Issue with AppleRTC, quite a simple fix:
config.plist -> Kernel -> Quirks ->...
You're wasting your time. I already told them to not put this in the config.plist, but they ignored all my advices and kept showing the same verbose errors because they keep using their original misconfigured config.plist.
To fix that they must use the config.plist I gave them that actually...
You can zero it out with dd command in the terminal
sudo dd if=/dev/zero of=/dev/rdisk# bs=65536 count=1000
Replace # with the disk number you want to erase.
WARNING: you must triple check that number with Disk Utility app (View >> Show All devices >> select that disk (not its volumes below)...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.