I confirm this bug. Sometimes, displayconfig want to use the VESA driver only and display only VESA available mode. Another possible cause is that sometimes displayconfig force refresh rates that are not compatible with the native screen resolution. You have to remove it manually from the xorg.conf file to get your native resolution.
To solve this bug, displayconfig should be more intelligent when dealing with drivers and : 1) only display the drivers supported by the current hardware 2) Do not impose refresh rates or anything. In fact, the refresh rate should not be displayed at all if the screen is not CRT. 3) When an user choose a given driver, actually use it for real ! (it works 1 time in 10 when it works) 4) Keep the xorg.conf file at the minimum. X.org is really intelligent those days. 5) Try to do whatever it can do to use the native resolution of the screen is the screen is LCD. Well, in fact, there tons of bug to report about displayconfig but the principle of displayconfig in itself is broken : if an user cares about the driver he want to use, there's already jockey. Displayconfig should only be used to set and second monitor or something fancy like that. No user should even know what a driver is and any LCD screen should automatically be set at its native resolution. -- Displayconfig does not detect the screen resolution https://bugs.launchpad.net/bugs/150467 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
