Re: 1080i EDID modes broken in 100.14.19
I notice if I run "X -verbose 6 > /tmp/X.log 2>&1" as root then the log will indicate a specific reason why a mode would not validate, such as the refresh rate being out of range. As "user" I would get a verbose log but minus the invalidation reasons. Of course you could also use startx -- -verbose 6 (i think there is also a -log-verbose 6 setting) but I dont really use that method while troubleshooting.
I'm not sure what would cause that, but it does add in difficulty towards troubleshooting the problem.
EDIT: after discovering my parameter typo, X -logverbose 6 or startx -- -logverbose 6 produces the same results and is easier