Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  • Days Won


arsradu last won the day on February 8

arsradu had the most liked content!

About arsradu

  • Rank
    InsanelyMac Deity
  • Birthday 04/21/1985

Profile Information

  • Gender

Recent Profile Visitors

6,880 profile views
  1. Corrupted boot menu after monitor upgrade

    Well, my GTX 650 didn't have a UEFI GOP VBIOS initially (and officially). Requested one on MSi forum, flashed it, all fine ever since. So it's definitely not a lost cause. Also, in my experience, the CSMVideoDxe driver created more issues than it solved. Personally I would suggest pushing towards a UEFI VBIOS, if possible, and solving this issue once and for all. At least that's my opinion.
  2. Corrupted boot menu after monitor upgrade

    I see... Ok, so the glitch is probably caused either by booting with two cards...oooorrr, by the lack of UEFI VBIOS... Or, as you said, maybe the motherboard UEFI... I don't know. I guess we'll see. Anyway, don't worry. I think we'll get it done in the end. It has to work.
  3. Corrupted boot menu after monitor upgrade

    You're very welcome. There are actually ways you can flash your card from DOS. So no Windows 10 needed. How would you do it with that USB drive anyway? What's your plan? I'm not sure I understood that part.... Anyway, what you will need, is a USB drive. That you already have. And I'm not sure about safe mode.... But I guess you can switch again to the working card, get the USB drive done and ready, then add the second card (or maybe just REPLACE one card with the other...you will see why I'm saying that in a second) and give it a try. I found a really long (but very comprehensive) article on how to do DOS flashing here. It doesn't matter if it's for the 290X. The method is the same. I would say go check it out when you have some time. Also, the article advises against using multiple cards at the same time. So after getting the USB drive ready with the working card, maybe try to remove that card and replace it with the other one (the one you're about to fix). About Intel GPU...I know I read somewhere that this doesn't apply there for some reason. I just can't remember why. Also, just out of curiosity, is CSM still set to Always in this case? Are you able to boot in full resolution with the Intel GPU? I'm just curious. Anyway, when you have more info, if you wanna share it, I'm here to help.
  4. Corrupted boot menu after monitor upgrade

    I guess you made a backup of your current VBIOS before flashing, right? Did the flashing itself go well? Did you flash both cards at the same time? Did you try booting with a single card? Did you try loading optimised defaults in BIOS? Did you try clearing NVRAM? What do you mean you can't boot? What happens when you try to boot? I would suggest trying to request a newer version on the manufacturer's forum, if you can. I don't particularly trust techpowerup in terms of BIOS files. When I flashed my GTX650, the guys on the forum told me they need the card's serial number, to assure the BIOS they provide is perfectly compatible for my card. They also mentioned the model is not enough. Now, of course, yours is an AMD card, mine is Nvidia. Yours is from Sapphire, mine is from MSi. What I'm trying to say is that there are clear differences here. So..it might be different for you. Still, I tend to believe the card model is not enough. So the BIOS might or might not be compatible with your specific card. I actually tried to flash an R9 270X from Gigabyte if I'm not mistaken. And although the flashing went ok, and everything seemed to work perfectly fine, after a while, I had all kinds of troubles with the newer BIOS. So I reverted to the backup I had and everything went back to normal. Now, of course, in my case, I was able to boot with no issues. So your issue is definitely more difficult. But I still have hope for it. If you still the issue UEFI related (which I doubt, because you're not the only one with this issue), you can also try an update on that side (but careful :)). You don't want your motherboard to fail now. That would be really bad. Although there are solutions for that case, too. And Gigabyte boards usually feature dual-bios (which is awesome, in my opinion). It's still not something to be desired. But let's hope we won't have to go there.
  5. Heeey, someone actually listened to the feedback and decreased the size of the "bezels"! It's not a landing strip anymore. Good job. And thank you! Also, I LOVE the LinusTechTips dark theme. Actually, that's what I have activated on their forum, too. :))) So...if we could have that...to me it would be heaven! I love it! For as far as I know, that occurs on larger files, for some reasons... It could be a limit, or...something else.
  6. Corrupted boot menu after monitor upgrade

    Alright. Then what I would suggest is to try and find out if both of your cards actually do use a UEFI GOP VBIOS. Unfortunately, the only way I know to find that out, is through Windows, using GPU-Z... Yeah, I know. You would think there's a software for Mac, as well. And it probably is...I just don't know of any. Also, one thing that you might want to check is your VBIOS version. You can do that too with the same GPU-Z. I don't think that's what's causing the issue. In fact, now I'm pretty sure it's the CSM, but just to have some extra information, it would be a good thing to know. Right now, I think one (or both) of the cards is not using a UEFI GOP VBIOS (although it does support it, it's just not currently installed/in use), forcing the BIOS to revert CSM back to Always, so you can boot properly. So let's see if I'm correct. Let's check the UEFI status of your cards. And also, please, do make a note of your BIOS version, as well. You can take screenshots even. That might be easier. And you can capture more data in a shorter time. Here's what you should be seeing in GPU-Z if the card is currently using UEFI GOP VBIOS.
  7. Corrupted boot menu after monitor upgrade

    Hmm... I don't think it's the same thing. But I'm still investigating that part. But since now you posted your hardware info, I can get searching. In the meantime, I read somewhere that your Graphics Card has a button, as in physical button you can press to enable UEFI GOP booting? Can you make sure it's pressed on both cards? Update: Ok, it seems that, when you select Other OS, CSM is set to ALWYAS. Which is NOT what we want. It has to be set to Never (EVER!) :)). And for that, if I understood correctly, you need to manually specify Windows 8 and set CSM to NEVER. CSM is the Compatibility Support Module. And it's used only by legacy Windows versions. If you don't use Windows, or if you use Windows versions newer than XP and 7 (I think Windows 8 is the first one with UEFI support), you should be fine with that option turned OFF. Also, when it's OFF, it enables the system to run in full UEFI mode, including full native resolution. So yeah, that s**t needs to go.
  8. Corrupted boot menu after monitor upgrade

    Hmm...someone (SavageAUS) suggested disabling CSM in BIOS in a post above. Did you try that? Cause it is important. Also, I hope you're not using CSMVideoDxe driver. You shouldn't need that, and, in my experience, it can also create resolution issues. So no CSMVideoDxe (especially since the card should be UEFI supported by default) and CSM disabled in BIOS (should be somewhere under Windows settings...something like that). If you can't locate it, post the model of your motherboard and I'll try to guide you through it. Also, when you have a bit of time, it would be really useful if you could add your hardware information to your signature, for easy access. It helps a lot.
  9. Corrupted boot menu after monitor upgrade

    Hey! Glad you fixed it. Yeah, actually a few things about your config. Uhm...why is Clover GUI set to 1600x900 resolution in your config if your monitor's native resolution is 2560x1440? :)) Also, if you're not using the Intel graphics card, why Inject Intel in config? Also also, when you're uploading a config file, it helps a lot to actually have it attached to the post, instead of copy-pasted into it. Especially if it's the full config and not just a part of it. If you can't attach it as plist file, make a zip archive of it and attach it like that. It's a loooot to scroll when you're simply pasting it into the post. Also, obviously you can't use Clover Configurator to open it in a more user friendly way. Anyway, don't worry, I managed to paste it in one of my config.plist files so I can see it with CC. I've got a curiosity, does this occur if you only use one of the two cards? With stream 1.2 whatever.. I'm not sure it's relevant in this case, to be honest. But then again, I can't deny the fact that it strangely works when you lower it to 1.1... Could be an incompatibility somewhere, too.
  10. Corrupted boot menu after monitor upgrade

    Hmm...if it didn't work with a DVI to HDMI cable, I would have probably said it could be something related to the Clover. Since, from what I understand, it doesn't occur in BIOS (UEFI) and it doesn't occur when the video drivers are initialised (which is on the second stage boot). So...it only happens while in Clover GUI. Which usually points to a problem with the config. Did you try with a fresh config? A brand new config generated with Clover Configurator, for example? Is it the same? Also, I know you mentioned that this issue doesn't occur with the BGM theme...but does it occur with the default one? This might also be interesting to see. If it's not too much trouble, and ONLY after you clean all your serial numbers and stuff from it, could you, please, upload your current config.plist here to check it out? So far, I'd say it is a Clover issue. But...then again, it works with a different connectivity...so..I don't know what to make of this. The config might bring some light into this, if you can share it for analysis.
  11. Far from being done. But this is kinda what I have in mind for a dark theme. As I said, it's faaaar from being ready. There are plenty of things still needing tweaking. I'll let you guys know when I'm close to finish if you wanna take another look. Until then, here's a little preview.
  12. So I guess I'm not the only one. Just posted this just a few posts before. Good to know I'm not the only one.
  13. Corrupted boot menu after monitor upgrade

    I see... Does the port layout look like in the image below? So, I guess you're using one GPU connected DP to DP and the other one connected DP to MiniDP, right? If so, then...I don't know what else you could do. I mean, aside from what you've already done... Sometimes, something like switching cables could help... I'm not saying it will definitely work. I'm just saying it might be worth trying, as weird as it may sound. Also, a different cable could also help with this, if the ones you're currently using are maybe not the best quality or something and they somehow interfere with each other. As I said, I've never seen something like that before. So..I can only guess what's going on, and suggest possible solutions based on that.
  14. I think this tool injects it into your desired website (you will see that it actually asks for a URL to be provided) before it loads. So it takes your changes and applies them there, then lets the site load normally, along with them. If anything, I think Shaneee might be able to help you more with this. He's an awesome guy and he has a lot more experience using the tool than I do (i just started using it yesterday so...yeah). Question: Guys, is it intended to be logged out when you click News? It doesn't seem right to me. I'm logged in when I'm on the forum, but when I go to the main page (News section), I'm asked to log in again... Not sure why. Sorry if this has been reported before. I hope I didn't miss it.