My hardware: MSI x399 Meg Creation 2990WX 64GB ram @2933Mhz Radeon 7 Sata: Samsung 130GB SSD M.2: Samsung 970 Pro 1TB(latest firmware)
Using OpenCore 0.5.6 (NVMeFix NVMeDxe installed) I have successful installed OSX catalina onto my 130GB. It works flawlessly.
and then I figure I should do it on my M.2 drive. It installs flawlessly, at the last stage of installation, it naturally restart and thats it. I can not boot into this newly installed OS on the M.2 drive. it keeps throwing: "error loading kernel cache 0x1"
I have tried deleting the prelinkedkernel from recovery partition. Tried rebuilding cache(I have not installed any kext into L/E).
All this time, I can use the same boot USB to boot into catalina on my sata 130Gb SSD working just fine.
attached is my EFI folder. I have tried all the suggested SMBios iMacPro1,1 MacPro6,1 MacPro7,1
is this ruled out that samsung 970Pro doesnt work?
I have a strange issue with my MacBook air (guess it's software, and I used the premium version of Avast to check any viruses). Some of the keyboard lettering doesn't work. I mean not the keyboard keys but really the letters. For example : when i Push the A on an azerty keyboard it doesn't work. But if I switch to Qwerty it's still the A who doesn't work. The keys working perfectly fine.
If I plug an USB keyboard this one works absolutely fine.
Also, when I click only the alternative click is working. With the trackpad or a bluetooth mouse.
But here is the strangest thing of all :
If I go to accessibility -> keyboard -> and click on enable sticky keys everything works perfectly fine : the click and the keyboard but not for a long time (actually it changes, sometimes it works for hours and some other for minutes)
To be totally exhaustive : When I tried to access my session I needed to type the password. But I needed the "a" which wasn't working (with the USB keyboard and the other). I went to the recovery system. There, the USB keyboard was working fine so I changed the password to use usable characters. But...The password wasn't changed.
So I used a bootable version of Catalina on a USB drive. The problem with the trackpad and the keyboard remained, but the UBS keyboard was working fine. And, this time the password asked to access the contents of the other users...was the one I changed and not the original one.
I erased the integrated drive, and re-installed the OS. But the issue remains.
I guess I need to go deeper in the system but i don't know how.
The MacBook has an other issue for a long time. When I close it, it doesn't go on standby. And now, even after going in standby he wakes up 2 minutes after.
Me (and many other people) experience eye-ache from new Macbooks (and windows machines).
I have spent two years of trial-and-error and found that installing macOS Mavericks on my MacBook (pro 13 late 2013, Intel Iris 1536 MB) resolves the issue of eye ache completely. (it is believed that newer systems use harsher version of temporal dithering that causes of a certain group of indivisuals eye aches).
I cannot stay at Mavericks because of software support and security issues, so the only thing is an issue now:
How can I take drivers from Mavericks and install them on Catalina? (I tried replacing .kext in /System/Library/Extensions with old files but it didn't work).
Greetings to the Forum,
i recently followed a guide on hackintosh,and also i am complete noob in this field.
all is working great, as i am using macpeets codec with layout id=18 cause i like to manually switch to my headphones.
only one thing doesnt work and its my mic. I tried all the layout ids but no luck.
i am using ASROCK Fatal1ty b450 k4 with amd r5 2600.
wich has alc 892.
Can you please help me? Thank you very much
I am having issues with VoodooInput. It loads fine, no errors or KPs, but movement is erratic. It seems when I am moving the cursor with my index finger and then try to click with my thumb, the cursor will shoot to the bottom of the screen, causing erroneous clicks and a lot of headaches. Sometimes it shoots to the top instead. Sometimes it performs as expected. It's unpredictable.
I have used VoodooI2C + VoodooI2CHID instead, and they work perfectly fine, but unfortunately they cause KPs. Plus, I like that VoodooInput is a singular kext. This is why I am trying to see if there's any way to fix this issue.