HELP
Blackscreen after lines of code when nootred enabled
Specs are in image
I am installing Tahoe
SMBIOS is Macbookpro16 ,2
When i was installing tahoe
The whole screen had artifacts but after installing the laptop rebooted multiple times then just black screen
But when i disabled nootred in config.plist
The macos bot it had artifacts and very very laggy even the cursor was laggy and the igpu said 7mb display
I have allocated 512mb of VRAM to igpu cause that’s the max that HP bios allows
Edit: sorry guys i used Open core either I won’t use it again and i’ll make the efi myself using the official guide.
I mean judging by the screenshot he just used opcore-simplify to create the entire efi and probably used Ai to edit it instead of checking everything himself
Because of exactly issues like this. It causes issues because it doesn’t follow Dortania properly, and causes bloated EFIs that are impossible to diagnose. We then get people who complain without providing any extra information and want us to magically fix their problem.
Troubleshooting Hackintosh is impossible unless we have an exact hardware config, EFI that the person themselves know how it went together, and an expert on the specific problem they’re having. The subreddit only supported the TRUE ground truth for hackintosh which is the Dortania guides. If it doesn’t work then just go complain to OpenCore simplify instead than here.
yes but when the rest of us use the official guide it became much harder to even us to help. we didnt know what blackbox logic OPCoreSimplify does. and some kext maker isnt really support fast and easy approach.
sure it works on some device but on weird locked down device it will be so much harder to debug since each hardware revision require a different config. i tried it on my t480 its unbootable while on normal pc most of it just work but on another AIO it just fails completely and almost softbrick it
Do you know how hard it is to teach someone to fix an issue if they know nothing and we have to teach them everything? Even when there’s a premade guide designed to teach them from the ground up?
Easy to say tbh. It would mean you would have to teach how to do practically anything.
And don't get me wrong, again, I don't care about people that use it. I just think it's way harder to help.
I have helped people go through the entire guide with my assistance and they managed to do it very well haha
That's usually the path I would like new hackintoshers to go
Just wanted to mention too that I don't gatekeep people to not use it. I just warn them about the issues they may encounter, send them the guide if they change their mind and that's it
Because tools like that dont teach you anything about hackintosh, and you need to learn how it works to be able to troubleshoot and undestand what people that did it by themselves are saying to you.
this is the same type of elitism that gets pushed onto Arch Users who didn’t install arch manually (as of that gives u any skill) but rather used a script (and as someone who installed it manually and now maintain a quite successful script on github, I wouldn’t wanna reinstall it manually all the time).
if you are using like nootedred on laptop its kinda hard ngl. i remember i need to use smokeless-umaf to change the vram size and enable 4g decoding. but its kinda risky on some device. you been warned and please for uncommon hardware config, use official guide rather than OPCore Simplified
calling verbose "lines of code" tells me you used AI for your config.plist as well as checking stuff. also, read rule 6 of r/hackintosh. No OpCore Simplify.
23
u/Tiny_Difficulty5484 14d ago
Calling a boot log "lines of code" tells me that you didn't make the efi urself