LockDown Posted March 7, 2019 Share Posted March 7, 2019 (edited) Solved! Add this in config.plist: <key>Graphics</key> <dict> <key>BootDisplay</key> <integer>1</integer> </dict> __________________________________________________________ Hi! Monitor (single monitor) - DVI & HDMI port GPU - GTX 1050 (dvi, hdmi & displayport) OS - macOS 10.13.6 If i use DVI, it works! Problem; If i use HDMI, it it shows GUI, apple logo then it goes to blacksceen just before it reaches the login screen. Any input regarding this? Thanks. Edited March 8, 2019 by ellaosx Link to comment Share on other sites More sharing options...
Allan Posted March 7, 2019 Share Posted March 7, 2019 The WebDrivers are updated? Are you using any patch for HDMI at config.plist? Link to comment Share on other sites More sharing options...
LockDown Posted March 7, 2019 Author Share Posted March 7, 2019 Hi @Allan Using latest web driver (.122). As i mentioned, i have no issue at all if using DVI port. My config.plist dont have any patches regarding HDMI. Link to comment Share on other sites More sharing options...
Allan Posted March 7, 2019 Share Posted March 7, 2019 Run this app, and upload the file result here, I'll (or other member) take a look. RunMe Link to comment Share on other sites More sharing options...
LockDown Posted March 7, 2019 Author Share Posted March 7, 2019 @Allan I will once i get home. Thank you Allan for taking your time to check my issue. Appreciated! 1 Link to comment Share on other sites More sharing options...
LockDown Posted March 7, 2019 Author Share Posted March 7, 2019 BTW @Allan is it ok to run RunMe connected to DVI (which i dont have an issue)? coz i can't do it if connected to HDMI. Link to comment Share on other sites More sharing options...
LockDown Posted March 7, 2019 Author Share Posted March 7, 2019 (edited) Hi @Hervé I am also thinking of clover's bootdisplay feature. I will try your suggestion too. Im using nv_disable=1 to be able to boot HDMI on my USB or macOS partition. Will it affect NVCAP's output? I can do all of these later at home Edited March 7, 2019 by ellaosx Link to comment Share on other sites More sharing options...
LockDown Posted March 7, 2019 Author Share Posted March 7, 2019 i have fixed it. Setting bootdisplay to 1 in config did it. Thank you @Allan & @Hervé for your time looking at my issue. 1 Link to comment Share on other sites More sharing options...
Allan Posted March 7, 2019 Share Posted March 7, 2019 Good to know that you got this problem fixed. 3 hours ago, ellaosx said: Setting bootdisplay to 1 in config did it. Would be good if you show us how you did it, using images, this can help the new members. 1 Link to comment Share on other sites More sharing options...
Recommended Posts