AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Hackintool shows nvidia audio2/20/2023 ![]() EFI 2 is the EFI folder I have now with the issue still unresolved, even though I've made a bunch of other fixes in the meantime such as audio & WiFi. Here is a google drive folder with the resources I've gathered surrounding this issue: EFI 1 is the EFI folder I had when I started tackling this issue. ![]() I've tried: Every framebuffer 3-4 times Creating and using a device-id field BusID patching on each combination of 6 busIDs and 3 indexes with connector type 0x00000002 (meant for internal displays like mine, AFAIK) -igfxblr igfxonln=1 igfxfw=2 -igfxvesa agdpmod=pikera -igfxmlr boot arguments Macmini8,1 MacBookPro16,1 iMac20,1 SMBIOSes CPUID spoofing (I was told that the CPU extended model 0xA5 was not compatible with the Big Sur kernel, so I spoofed it to 0x8E with Cpuid1Data E2060800 00000000 00000000 00000000 and Cpuid1Mask F0000F00 00000000 00000000 00000000) (That said, I didn't try every permutation of these variables so if two or more of these fixes were necessary at once it's likely I missed it) Smears the screen and/or reboots itself if I use a headless framebuffer (zero connectors) Sits with a black screen if I use framebuffer 0x3E9B0007. However, if I do not use this boot argument then my computer: Reboots itself after verbose if I use any framebuffer with nonzero connectors other than 0x3E9B0007. Whenever I use the -igfxvesa boot argument the computer boots up fine but there's no graphics acceleration and the VRAM on the "About My Mac" pane reads 7 MB. Hello, I seem to be having an issue with GPU acceleration.
0 Comments
Read More
Leave a Reply. |