dpkg-reconfigure xserver-xorg and screen resolution

In Debian etch, when you install the xserver for the first time, you are asked about the correct screen resolution. I have now got a different monitor and want to change this setting but dpkg-reconfigure xserver-xorg doesn't give me the possibility to change the resolution. Even when I set the debconf priority to 'low' I can't change the screen resolution. What can I do?

5
Average: 5 (2 votes)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: dpkg-reconfigure xserver-xorg and screen resolution

Have you edited /etc/X11/xorg.conf? dpkg-reconfigure gives up in that case. Does dpkg-reconfigure ask you any questions at all? If it does, do you get a question offering "Advanced" as a method of monitor configuration? "Advanced" should give you options for choosing resolutions.

dpkg-reconfigure xserver-xorg and screen resolution

I haven't edited xorg.conf, it asks questions about graphics card, mouse and keyboard, etc. It doesn't give me an advanced option and this behaviour is true for a number of computers that I have tested.

Re: dpkg-reconfigure xserver-xorg and screen resolution

Sorry about that-- I don't get a question about advanced settings anymore (maybe that was a few months ago). I'm rerunning dpkg-reconfigure xserver-xorg now, and I get these questions after the questions about the keyboard and mouse:

Attempt monitor autodetection? (maybe try "no" here)
Identifier for the monitor: (Generic Monitor in my case)
Video modes to be used by the X server: (resolutions listed here)

Are you getting any of these monitor questions?

dpkg-reconfigure xserver-xorg and screen resolution

Yes, the latest update of xserver-xorg brought back this configuration option. So, problem solved.

dpkg-reconfigure xserver-xorg and screen resolution

Great! This is the type of thing that I'll try to remember next time I'm happily running stable etch and say to myself, "Gee, I really wish I could try package foo. Maybe I should upgrade to unstable." :-)

Syndicate content