http://bugzilla.novell.com/show_bug.cgi?id=586053 http://bugzilla.novell.com/show_bug.cgi?id=586053#c10 --- Comment #10 from Felix Miata <mrmazda@earthlink.net> 2010-03-08 07:25:56 UTC --- (In reply to comment #9)
The fact, that there are still monitors around without (working) DDC/EDID doesn't justify any amount of work trying to support also these corner cases.
Of itself, you're probably right. But as I already wrote, just because working DDC/EDID exists does not mean what results from it is right for the user. There needs to be understandable and readily discoverable instructions for what mere mortal users with bad DDC/EDID need to do to get the results they want.
How to add a new mode by using xrandr. Basically this is
xrandr --newmode <newmode> xrandr --addmode <output> <newmode> xrandr --output <outpu> --mode <newmode>
See "xrandr --help".
I saw all of that. It's too terse. What's the difference between add and new? Why would anyone need to specify an output whenever there is only one output? In the past people have been able to configure X without ever having to start any display manager. I don't see any way to do this now. Installation, where I normally first did it at fresh install, now skips the whole process, apparently assuming xorg.conf-free automatic configuration cannot fail.
Documentation about the usage of xlog2xconf can be found in the first lines of the script.
I had no idea it was a script.
It's main purpose is to create a xorg.conf, which reflects the automatic configuration and then can be adjusted to your needs. Hope that helps.
In my first tries, example of which ends comment 7, it essentially requires knowledge to build all video-related file components from scratch. Maybe it does what it needs to do with mga, nv or radeon, which I've not yet had time to try in M2 or M3, but it sure doesn't seem at all helpful with intel. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.