- Joined
- Dec 15, 2012
- Messages
- 82
- Motherboard
- Gigabyte GA-Z77X-UP5 TH
- CPU
- i7-3770K
- Graphics
- RX 580
- Mac
- Mobile Phone
Hi Milesree
That is strange. A couple of questions:
1. Are you booting with GraphisEnabler=Yes or =No? Whichever one you are using, try the other. You can just try it first by typing in the command at the Chimera boot loader screen instead of modifying your org.chameleon.boot.plist file. Although my build description says to use GraphicsEnabler=Yes (which worked fine for me), I've found that GraphicsEnabler=No now also works (i.e. nothing changes). However I only tried this after installing the nVidia drivers and the latest version of Chimera, so I'm not sure if that had something to do with it. I'm almost certain that before installing the nVidia drivers and/or the new Chimera that I could only boot with GraphicsEnabler=Yes. Note that I still need to have the device properties in the org.chameleon.boot.plist file in both cases.
2. When you changed back to "init display = Auto", did you still have a monitor plugged into the mobo DVI? If so, disconnect it and then boot and see if it fixes the problem. If not try "Init display = PEG" which will only initialise your discrete GPU.
With your setup I'd only be initializing your discrete GPU (Init display = PEG) and have both screens plugged into it. The only reason I have the HD4000 enabled is because the only configuration I can get my 2 x 24" cinema displays to work properly is to have one plugged into the single displayport on the GTX 670 (via a MDP --> DP adaptor) and the other plugged into the MDP/thunderbolt port on the HD4000. With the monitor plugged into the GTX 670 set as the primary display, graphics acceleration to both monitors is via the GTX 670.
I hope this helps.
That is strange. A couple of questions:
1. Are you booting with GraphisEnabler=Yes or =No? Whichever one you are using, try the other. You can just try it first by typing in the command at the Chimera boot loader screen instead of modifying your org.chameleon.boot.plist file. Although my build description says to use GraphicsEnabler=Yes (which worked fine for me), I've found that GraphicsEnabler=No now also works (i.e. nothing changes). However I only tried this after installing the nVidia drivers and the latest version of Chimera, so I'm not sure if that had something to do with it. I'm almost certain that before installing the nVidia drivers and/or the new Chimera that I could only boot with GraphicsEnabler=Yes. Note that I still need to have the device properties in the org.chameleon.boot.plist file in both cases.
2. When you changed back to "init display = Auto", did you still have a monitor plugged into the mobo DVI? If so, disconnect it and then boot and see if it fixes the problem. If not try "Init display = PEG" which will only initialise your discrete GPU.
With your setup I'd only be initializing your discrete GPU (Init display = PEG) and have both screens plugged into it. The only reason I have the HD4000 enabled is because the only configuration I can get my 2 x 24" cinema displays to work properly is to have one plugged into the single displayport on the GTX 670 (via a MDP --> DP adaptor) and the other plugged into the MDP/thunderbolt port on the HD4000. With the monitor plugged into the GTX 670 set as the primary display, graphics acceleration to both monitors is via the GTX 670.
I hope this helps.