While in console only mode via runlevel 3, I saw an xorg.conf in this directory:
It is now not in there. In that xorg.conf was a line I had previously used to fix and error that was being thrown by one of my displays.
Option “ModeValidation” “DFP-5: NoMaxPClkCheck, NoVertRefreshCheck, NoHorizSyncCheck”
I added that yesterday, not today. That line WAS NOT in the nvidia.conf or that 90-mhwd.conf. I made sure it was removed. It was still in this xorg.conf though located in /etc/X11.
I thought that was weird that it was there, and that there was an xorg.conf file located in that directory at all. I removed the line there and the display loaded up.
So, mhwd-gpu --setxorg is still pointing at /etc/X11/mhwd.d/nvidia.conf
Why did there being an xorg.conf file in /etc/X11/ cause the problem if its not meant to be looking there? Is the system looking to that xorg.conf file at boot still then Im somehow editting the existing display in nvidia.conf, but its only doing that in the live display?
My nvidia settings wants to default to this save location:
Mod edit: uploaded image(s) removed
After I ran mhwd-gpu --setxorg /etc/X11/mhwd.d/nvidia.conf trying to fix my issue though, I made sure to start saving the configuration to /etc/X11/mhwd.d/nvidia.conf because I believed thats where the system would be looking now.
Has the system NOT be looking at /etc/X11/mhwd.d/nvidia.conf all this time and instead looking at /etc/X11/xorg.conf ? If so, why do I not see an xorg.conf in that directory now?
Im assuming its something to do with the sym-linking, and what file is or is not trying to by the system.
