Search results

I have come to the conclusion that it's a frame buffer issue. I have booted with it now, shows up as AMD 8xxx in SysProf Booted with Radeon and seems fine now. Will need to figure out how to patch my FB if someone could help me with. Previously I used Baladi with patched FB somewhere on...

Yes I have updated clover and I can boot into OS X 10.12.4 perfectly fine with my iGPU. Whenever I switch to or boot with the 390 (with iGPU still as primary) it goes straight to blank screen (monitor doesn't have signal).

Hey guys, I know this has probably been asked a lot and might have been answered already, but I need some assistance with getting my R9 390 (non-x) working in 10.12.4. Was working perfectly fine in previous versions but the latest update broke it and now it only shows black screen. Same setup...

Is there another solution than using a previous Unibeast edition? I was wondering if it's the Clover version that it is using for Unibeast and if there is a version that works.

Not only could I not boot into my UEFI SSD and hence into Clover, Clover on the USB (as with the OP) does not detect my internal Clover system so I can add the boot option. Anyway I gave up and installed Clover Legacy through Multibeast and left it at that for now. AFAIK using the "Install for...

Yes I'm pretty sure this was the case for me too, previously working in El Capitan, I was able to add entries from within Clover too. Still no luck here.

Having this same issue right now -- been at it for 3 hours and still cannot find a solution that would work. I'm not sure if my motherboard fully supports UEFI (mobo is in profile), but pretty sure it does as I have the option to boot EFI or Legacy. Anyway point is I've successfully installed...

Seems as though coincidentally someone posted the exact same question in a thread below. Sorry if the duplicates annoy you.. As I mentioned above, for some reason my system won't boot into clover with iGPU as primary. All it comes up is with is a blank screen and a blinking cursor. Maybe it is...

Hi guys, long time lurker. Previously we have been able to run the R9 390 on El Capitan by spoofing the ID to the 290x/390x? in clover and injecting ATI and framebuffer. I've managed to direct update my system (albeit troublesome as I needed USBInjectAll.kext since half my ports broke), to...

Sounds complicated. Thanks for the info anyway.

I thought that was generally the case... That if OS X requires x amount of iGPU memory but the system isn't allowing it, problems occur like artifacting. If that is incorrect then so be it I'll just live with it.

Well anyway, still doesn't answer artifacts caused by a mismatch of allocated memory and the framebuffer. Still have no idea how to patch connector tables either lol

With a locked BIOS I don't think it's possible through those means, but trial and error seems like the only viable option. I know in Windows I get around 17xxmb of shared graphics memory whereas OS X reports only 1536. Maybe it's missing some?

Right well I've read through this whole thread hopefully it'll bring light to my situation. Currently running OS X 10.9.4, QE/CI works and FHD with a HD4400 (I know this thread is about 4600 but they're almost same I believe?) Only issue is (as being described here??) is that there is a...

I was going to PM you this- but only greeted by the "you must have 75 posts" screen.. Hey phaberest- Just a quick question with regards to your thread on the Sony VAIO Duo; as I own the VAIO Pro with similar configurations I'd like to ask if you've had any progress on your end? More...

Unfortunately, the link down below is mainly for ATI cards, there might be a similar method of patching your VBIOS but I wouldn't risk it. How to set your Hackintosh bootscreen to a widescreen resolution (VESA modes) This will fix things.. I haven't actually done it yet because 1, I use my...

Can be fixed by patching/flashing your VBIOS to force a certain VESA mode mode. There's a tutorial link somewhere floating I dunno, but it's because your graphics' VESA mode is fixed at 1 mode (e.g. 640*480*16), that's why it doesn't stretch out and go full resolution. Flashing may be risky...

Reinstall Mountain Lion. Most likely you broke your kexts. IF You don't want to do that, try copying the kexts from your installation media (i.e. USB or DVD or whatever) in /S/L/E of the installation. Remember to fix perms and use a compatible SMBios. I also suggest you using Chimera as I find...

Well, technically you should be choosing the SMBios that matches closely to your system. Not just choosing any one of them willy nilly. Hahaha

Hmm, patched bios and I still get 52 errors in DSDT, and I can't use DSDT Editor and Patcher to fix the errors. Errors such as Object does not exist (NGPH), or Object does not exist (NPME) No errors arise on my edited dsdt..