Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


arsradu last won the day on August 4

arsradu had the most liked content!

1 Follower

About arsradu

  • Rank
    InsanelyMac Deity

Profile Information

  • Gender

Recent Profile Visitors

7,721 profile views
  1. I had a GTX 650 (from MSi). Never had such issues with that one. :)) But I never tried Mountain Lion... And starting with Mevericks, I never had such issue. So....maybe this is something all the way from Mountain Lion...? Damn, that's a looong way back.
  2. Thanks! Did any of these work for you? Cause I've got the following results: all of them flash, some of them boot, most of them don't. The only ones that allowed me to boot were: Dayman Guariba Orinoco Yelcho All the other ones were losing signal on second stage boot (boot to black screen).
  3. You can use the MacPro/iMacPro SMBIOS, as I suggested above. Also, it would be nice to know what other hardware components do you have. So I would recommend adding that information to your signature.
  4. Not sure they're related. But if you feel like they are, just enable the iGPU in BIOS, use WhateverGreen and remove NoVpaJpeg kext. Or, use a MacPro/iMacPro SMBIOS to fix the Preview issue and you won't need NoVPGAJpeg in the first place. I cannot speak for the automatic reboots. If you don't have that already enabled, you should probably try enabling KernelPM in Kernel & Kext Patches of your Clover config.
  5. Even when the resolution doesn't change, that flash is still there...unfortunately. What bothers me the most is the fact that it's inconsistent. Sometimes it works with absolutely no flash whatsoever. Other times, it fills almost the entire screen. Whatever causes this, is random as hell. And I'm most interested in what happens when the issue does NOT occur. Again. It's not like it's only a small strip at the bottom of the display. There's no flash at all. Same computer, same everything. One time works perfectly fine, the other one it doesn't. If it was occurring 100% of the times, I would say: you know what, that's just the way it is. But it doesn't! It's not always like that. Which means that it has the potential to work perfectly. It just, 99.9% of the times it decides not to...for whatever reason. :)) I know, I know. It's a small issue. I've heard that way too many times. :)) But let me ask you something: if you knew your computer had the ability of running everything perfectly fine, every time, on every boot, not just once in a blue moon, wouldn't you at least try to achieve that? Cause I would. Yeah, you can call me crazy if you want. :)) I don't care. I just want to at least understand what's happening in this case (both when it works and when it doesn't), if I can't actually fix it. Everything starts with understanding the cause of the problem. After that, you can assess if it can be fixed or not, and how, based on that.
  6. I suspected so, too... But....I have no custom framebuffer selected. It seems to be using the default AMD,RadeonFramebuffer right now. And Orinoco, which is probably the most appropriate one for this card, has the same result. Which other FB would you suggest...? Or...how do we find out which one should be used for this case? As I said, for as far as I could see, Orinoco seems to be the only compatible one, due to the ports layout. But I'm open to suggestions.
  7. Hey! Thanks for sharing your experience. So...are you sure you don't have that screen flash upon startup? Cause...although I know there are SOME people who don't (including myself at times), I've never managed to find out what's different in their case. If you really don't have this issue, would you be willing to help us debug it a little further to see what's different and why does it work for you, but doesn't work for the rest of us? And, to answer your question,well, no.. I mean, sometimes. Usually, it doesn't cover the entire screen. Most of the times it's only on the lower part of the screen. But sometimes, it does cover the entire screen (or most of it anyway). And sometimes I myself don't have any flash at all. That's the annoying part. You know it CAN be without a flash. You just don't know what the hell makes it work perfectly fine when it does. I'm referring to this issue below . Could you record your screen as well? I find it really strange (though I'm happy for you) that you don't have this issue, even with the exact same graphics card... Something has to be different. IMG_0649.MOV
  8. Yeah, I was suggesting trying to set IGD Multi-monitor to Enabled. Glad to hear that. That is not related to this topic. Depending on what method are you using for sound (hopefully Lilu + AppleALC), you can try different Layout IDs. Some of them have EAPD enabled and you shouldn't lose sound after sleep. Alternatively, you can get CodecCommander.kext, put it in S/L/E (doesn't work from Clover/kexts/Other) and it should have the same effect. I personally had issues with it under Mojave, so I chose one of the other Layouts in order to fix this issue. Now, unfortunately, your motherboard uses a different codec than mine, so I can't suggest the same Layout ID that worked for me. But what I can suggest is taking a look at the list of supported codecs from here and trying a different one than the one you currently have. Your codec is ALC 887, so choose one of these Layout IDs: 1, 2, 3, 5, 7, 11, 13, 17, 18, 33, 50, 99 Also, select ResetHDA in your Clover config. Might help with that. For more information on AppleALC, here's the official thread: Also, in case you want to discuss the flashing during boot issue which you probably have with that RX 580 (if you don't, I would be VERY interested to know more details), feel free to share your experiences here: You're definitely not the only one with that issue. If I can help you with anything else related to this topic, please, let me know. Also, while we're at it, I would recommend using the Edit feature when you want to add something and nobody else replied to you. Otherwise you will create a lot of different posts, which may look a bit spammy. Just a suggestion. And welcome to the forum! Cheers!
  9. Well, you've got multiple options. And your setup is actually very similar to mine. So I guess I have some experience with that. Let's start with: which SMBIOS are you currently using? If you went for iMac14,2 for example or even iMac18,3 make sure the iGPU is enabled in BIOS (you can easily enable it by going under dual-monitor and enabling that option). Add 64MB for the iGPU and that's all. Make sure you use WhateverGreen.kext so your computer doesn't freeze on certain websites. Alternatively, you can simply use a MacPro5 or MacPro6,1 SMBIOS and you won't have to worry about the iGPU anymore, since those don't have iGPUs in the first place. So, if you're going the SMBIOS route, make sure you either enable the iGPU in BIOS and use WEG, or use an SMBIOS like the ones for Mac Pro or iMac Pro which don't require you to enable the iGPU. I actually tried the NoVPAJpeg kext myself and just like you, it didn't do anything for me. Maybe I missed something, maybe there are other reasons why it didn't work. I didn't have the time to investigate that. But personally, I already have at least 2 other methods to get this to work. And I already described them for you above.
  10. That might be quick and easy for you. But it's definitely not a solution for everyone. What's your SMBIOS? Some of them (such as MacPro5, MacPro6, iMacPro) do work without an iGPU. But whether or not it's enabled in BIOS, should not affect anything, since in many cases, the iGPU is not even recognised. :)) Still, I'm curious to know what's your current SMBIOS.
  11. arsradu

    Clover Theme Manager

    Hi blackosx, Sorry for the huuuuge delay in feedback. I said I'll come back with feedback on the https issue, and I totally forgot about it. I'm deeply sorry. The good news is that everything works perfectly fine in the same environment, with the newest version (0.76.8). Great job! And thank you very much!
  12. Personally, I don't think so. I don't think it will break anything. Worst case scenario, it might stop working at some point. But that will probably be fixed with an update. I guess we'll have to wait and see. And if that fails, you'll always have one of the other options to fix this issue. So, I wouldn't worry about it too much. Personally, I'm not using it. I tried it. For some reason it didn't work for me. Changing the SMBIOS or activating the iGPU in BIOS did the trick though. So, as I said, I wouldn't worry about it too much.
  13. Yeah, that works too. I've added it to the main post, as well. Thanks for the tip.
  14. Yeah, CSM (or Compatibility Support Module) needs to be Disabled in BIOS. Usually that setting is under "Windows 8/10 options" or something like that, since those should support UEFI booting by default. For Windows 7 and earlier, you need it Enabled, since those are using Legacy booting. Depends on the motherboard. But most UEFI motherboards should have it, under one name or another.