Search results

Y Yes, I’ve tried every single Aptio fix, and have tried enabling/disabling EmuVariableUefi. I’m not sure what else to try, since it’s clearly trying to boot, but not quite getting there.

No, it’s HFS+ I don’t think createinstallmedia will even work with an APFS formatted drive. I think that message is just the APFS driver checking for newly inserted storage, that’s the best I can come up with

So, interestingly enough, if I unplug the “booted” USB drive and plug it back in, upon insertion, it will bring up a message that is show in the image here

Secure Boot is disabled, and it does detect and attempt to boot into the USB stick, as I've made sure it knows where to find the .efi file in the BIOS. The problem is that it just freezes up whenever it tries to boot, and just shows an unresponsive black screen. I'll get a picture up in a moment

Okay, so I updated my profile, and I followed all of the instructions exactly when setting up Clover. I haven't been able to even get into Clover, so I can't get any "Problem Reporting Files." I have been hackintoshing for a while, so I can manage on my own once I get to the Clover screen, but...

I am attempting to create a hackintosh out of my Dell Inspiron 3558, but I'm having trouble. The system allows for adding UEFI entries into the BIOS, and I have made sure it can detect and attempt to boot to the USB drive, which is simply a createinstallmedia drive with Clover on top of it. I...

Tyler 1790 17.4 2.2 3110416 187992 ?? U 2:13PM 0:34.84 /Applications/GFXBench Metal.app/Contents/MacOS/gfxbench_metal Tyler 1814 0.0 0.3 2502804 21948 ?? Ss 2:14PM 0:00.26...

Bump? Anyone? I just need a way of detecting what API is being called if I use an app that supposedly uses Metal so I can test this. Any way I can do this that anyone knows of? Any free applications that use Metal as their API?

Here is an example of what I'm talking about. The SMBIOS reports my GPU as Iris 6100, but I have HD 5500, reported by System Information.

But the app detects that I have Iris 6100 Graphics... And I don't... So obviously it's not seeing my hardware, just whatever is reported to it, in my case, anyways.

No, that's not quite what I meant... Let me rephrase: My SMBIOS reports to the system that I am using Intel Iris 6100 Graphics I actually have Intel HD 5500 Graphics How do I know the app doesn't just look at the 6100 Graphics and think "Yep, that's compatible with Metal!" and report that back...

I have a fully working laptop hackintosh, with an intel Core i5-5200U CPU and HD 5500 Graphics. I have seen that supposedly Apple's "Metal" API will work with HD 4000 and newer, but since the HD 5500 is NOT supported by Apple by default, is there a way to check if programs can use Metal on my...

Fair point, no it's not

It seems to work well enough on my Mac Mini and my other laptops here, but I guess it just comes with having a hackintosh

I got my power management working thanks to this! My battery life thanks you very much I will try to get another monitor to test the HDMI out soon, but I just realized I am running from HDMI to DVI, which should work fine, being that they are both digital signals, but I don't know too much...

I tried detect displays, didn't work. I haven't tried another monitor but I will soon. This could be the case, so I will try that when I get the chance. I removed virtualbox drivers. I do not know how to enable CPU power management, but if you have a guide to link me to, that would be great.

Ok, so after a lot of trial and error, I got both patches to work by just using DropOem=YES and patching the DSDT.aml and the SSDT-9.aml with both patches, which seems pretty self explanatory now, but for some reason took me a lot longer than it needed to. In any case, my display is STILL not...

Here is my current clover folder. I have config2.plist as the config with the DropOem for the SSDT's enabled and in the ACPI/Patched folder I have DSDT2 and DSDT3 as DSDT2 with the IGPU patch and DSDT3 as the B0D3 patch. I use these renames to quickly change the names of the files clover will be...

Just tried using DROP OEM for both DSDT and SSDT and it wouldn't boot at all. Maybe one or the other would work? Also the original problem is apparently still not fixed, as it just happened again.

Well, I added the fix across all the SSDT's as well, and this time when I went to start up with testing both the IGPU and the B0D3, I ended up with the same kernel panic on the B0D3 and this (the picture) for the IGPU right before it restarted. Instead of a KP it just gets to this point and...