New monitor, how to change screen resolution?
Hello, I just changed monitors and the new one has a different resolution. How do I configure my system to account for the change?
Re: New monitor, how to change screen resolution?
On Thu, 29 Apr 2010 07:42:58 -0400 (EDT), James Stuckey wrote: I just changed monitors and the new one has a different resolution. How do I configure my system to account for the change? You didn't provide much information, James. I'm afraid that there's no one size fits all answer to that question. It depends on a lot of things. Please provide the following information: (1) The make and model of your computer (2) The make and model of your video card (3) The make and model of your monitor (4) The type of monitor (CRT, LCD, etc.) (5) The type of video connection used (digital, analog, etc.) (6) The contents of /etc/X11/xorg.conf, if it exists (7) The contents of /var/log/Xorg.0.log (8) Which release of Debian you are running (Lenny, Squeeze, Sid, etc) -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/674417720.81786.1272545865761.javamail.r...@md01.wow.synacor.com
Re: New monitor, how to change screen resolution?
You didn't provide much information, James. I'm afraid that there's no one size fits all answer to that question. It depends on a lot of things. Please provide the following information: (1) The make and model of your computer (2) The make and model of your video card (3) The make and model of your monitor (4) The type of monitor (CRT, LCD, etc.) (5) The type of video connection used (digital, analog, etc.) (6) The contents of /etc/X11/xorg.conf, if it exists (7) The contents of /var/log/Xorg.0.log (8) Which release of Debian you are running (Lenny, Squeeze, Sid, etc) Hi Stephen, (1) I'm on AMD64/Asus motherboard P5Q (2) NVIDIA 9800GT (3) ASUS VH242H (4) LCD (5) Digital connection, not DVI (6) Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath built-ins EndSection Section Module Load record Load extmod Load glx Load dri Load dbe Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse OptionProtocol auto OptionDevice /dev/input/mice OptionZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor # [bool] #Option HWcursor # [bool] #Option NoAccel# [bool] #Option ShadowFB # [bool] #Option UseFBDev # [bool] #Option Rotate # [str] #Option VideoKey # i #Option FlatPanel # [bool] #Option FPDither # [bool] #Option CrtcNumber # i #Option FPScale# [bool] #Option FPTweak# i #Option DualHead # [bool] Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName G92 [GeForce 9800 GT] BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection (7) X.Org X Server 1.7.6 Release Date: 2010-03-17 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-4-amd64 x86_64 Debian Current Operating System: Linux debian 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-amd64 root=UUID=cca7add1-981f-469f-9285-ae17722e24bd ro quiet Build Date: 05 April 2010 02:21:15PM xorg-server 2:1.7.6-2 (Timo Aaltonen tjaal...@ubuntu.com) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Apr 29 19:58:58 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled,
Re: New monitor, how to change screen resolution?
On Thu, 29 Apr 2010 14:30:40 -0400 (EDT), James Stuckey wrote: Stephen Powell wrote: You didn't provide much information, James. I'm afraid that there's no one size fits all answer to that question. It depends on a lot of things. Please provide the following information: (1) The make and model of your computer (2) The make and model of your video card (3) The make and model of your monitor (4) The type of monitor (CRT, LCD, etc.) (5) The type of video connection used (digital, analog, etc.) (6) The contents of /etc/X11/xorg.conf, if it exists (7) The contents of /var/log/Xorg.0.log (8) Which release of Debian you are running (Lenny, Squeeze, Sid, etc) (1) I'm on AMD64/Asus motherboard P5Q (2) NVIDIA 9800GT (3) ASUS VH242H (4) LCD (5) Digital connection, not DVI Digital connection, but not DVI? Hmm. This may be out of my league. I don't have any experience with that. (6) Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath built-ins EndSection Section Module Load record Load extmod Load glx Load dri Load dbe Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse OptionProtocol auto OptionDevice /dev/input/mice OptionZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor # [bool] #Option HWcursor # [bool] #Option NoAccel# [bool] #Option ShadowFB # [bool] #Option UseFBDev # [bool] #Option Rotate # [str] #Option VideoKey # i #Option FlatPanel # [bool] #Option FPDither # [bool] #Option CrtcNumber # i #Option FPScale# [bool] #Option FPTweak# i #Option DualHead # [bool] Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName G92 [GeForce 9800 GT] BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection It's the proprietary nvidia driver! Oh no! ;-) My first question is, how did you come up with this config file? Did you create it yourself by hand? Did you run a script to create it? Did the proprietary nvidia driver installation program create it for you? It seems way over-specified to me. (7) ... (++) using VT number 8 This is off topic, but did you notice that the X server initialized itself on VT number 8 instead of VT number 7? That means, for example, that if you are on virtual console number 1 (text mode) and wish to switch to the X server, you will need to use Ctrl+Alt+F8 instead of the usual Ctrl+Alt+F7. I've noticed this bug too lately. In fact, it's possible that you have have two copies of the X server running. One on VT 7 and one on VT 8. Wouldn't that be a hoot? ... (II) Apr 29 19:58:59 NVIDIA(0): Virtual screen size determined to be 1920 x 1080 Is that the resolution you are trying to obtain: 1920x1080? It's not a standard 4:3 aspect ratio, so it's most likely probed from the monitor. ... (8) Squeeze with Sid nvidia drivers -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to
Re: New monitor, how to change screen resolution?
On Thu, 2010-04-29 at 15:20 -0400, Stephen Powell wrote: On Thu, 29 Apr 2010 14:30:40 -0400 (EDT), James Stuckey wrote: [snip] (1) I'm on AMD64/Asus motherboard P5Q (2) NVIDIA 9800GT (3) ASUS VH242H (4) LCD (5) Digital connection, not DVI Digital connection, but not DVI? Hmm. This may be out of my league. I don't have any experience with that. HDMI perhaps? [snip] (7) ... (++) using VT number 8 This is off topic, but did you notice that the X server initialized itself on VT number 8 instead of VT number 7? That means, for example, that if you are on virtual console number 1 (text mode) and wish to switch to the X server, you will need to use Ctrl+Alt+F8 instead of the usual Ctrl+Alt+F7. I've noticed this bug too lately. In fact, it's possible that you have have two copies of the X server running. One on VT 7 and one on VT 8. Wouldn't that be a hoot? I noticed that on my system as well, and you might be correct, although VT7 only gives you a black screen with blinking cursor. You might be right about the 2 x servers: ste...@pc-steven:~$ ps aux | grep gdm root 2215 0.0 0.0 15372 1716 ?Ss 21:15 0:00 /usr/sbin/gdm root 2220 0.0 0.1 15712 3248 ?S21:15 0:00 /usr/sbin/gdm root 2229 2.3 2.1 77360 66380 tty7 Ss+ 21:15 1:22 /usr/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 steven3880 0.0 0.0 3116 768 pts/0S+ 22:14 0:00 grep gdm Might be a bug in the NVidia kernel module? Or is this something we can fix in the X configuration? (it would be nice to have in on VT7 again as default) ... (II) Apr 29 19:58:59 NVIDIA(0): Virtual screen size determined to be 1920 x 1080 Is that the resolution you are trying to obtain: 1920x1080? It's not a standard 4:3 aspect ratio, so it's most likely probed from the monitor. It's probably a TV, I have one of these myself, quite nice for watching films. ... (8) Squeeze with Sid nvidia drivers -- .''`. Stephen Powell : :' : `. `'` `- James, about your resolution, have you tried nvidia-settings (needs to be invoked as root in an x session, start a terminal session from the menu, it's also listed in the System menu, but doesn't get invoked as root). If you don't have that tool, you can get it from the repositories. Regards, Steven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1272572858.2785.14.ca...@pc-steven.lan
X server starts on the wrong console (was: New monitor, how to change screen resolution?)
On Thu, 29 Apr 2010 16:27:38 -0400 (EDT), Redalert Commander wrote: Stephen Powell wrote: James Stuckey wrote: (7) ... (++) using VT number 8 This is off topic, but did you notice that the X server initialized itself on VT number 8 instead of VT number 7? That means, for example, that if you are on virtual console number 1 (text mode) and wish to switch to the X server, you will need to use Ctrl+Alt+F8 instead of the usual Ctrl+Alt+F7. I've noticed this bug too lately. In fact, it's possible that you have have two copies of the X server running. One on VT 7 and one on VT 8. Wouldn't that be a hoot? I noticed that on my system as well, and you might be correct, although VT7 only gives you a black screen with blinking cursor. You might be right about the 2 x servers: ste...@pc-steven:~$ ps aux | grep gdm root 2215 0.0 0.0 15372 1716 ?Ss 21:15 0:00 /usr/sbin/gdm root 2220 0.0 0.1 15712 3248 ?S21:15 0:00 /usr/sbin/gdm root 2229 2.3 2.1 77360 66380 tty7 Ss+ 21:15 1:22 /usr/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 steven3880 0.0 0.0 3116 768 pts/0S+ 22:14 0:00 grep gdm Might be a bug in the NVidia kernel module? Or is this something we can fix in the X configuration? (it would be nice to have in on VT7 again as default) First of all, I need to correct myself. When switching from a text console to the X console, you don't need Ctrl. For example, Alt+F7 (or Alt+F8 in this case) will work fine. Ctrl is only needed when switching from the X console to a text console. For example, Ctrl+Alt+F1. I know you know that, but for the sake of correcting my earlier mistake I mention it. Second, the problem with the X server starting on the wrong console seems to be related to a failure to deallocate virtual terminal 7 when the old X server stops. I'm using the nv driver, which is also from nvidia, though it is open source. I'm wondering if anybody has seen this on a non-nvidia driver. If I switch to a text console, login as root, and issue deallocvt 7 I get an error something like this: Device or resource busy Someone gave me the tip some time ago that if I kill the process console_kit or something like that (I don't remember the exact name) then I can do a deallocvt 7 and it will work. Then, in theory, restarting the X server again (such as with /etc/init.d/gdm restart) should cause the X server to restart on vt 7. This used to work, but the last time I tried it I ended up with two X servers, one on VT 7 and one on VT 8! I had to reboot to clean things up. This situation is a mess and seems to be getting worse. As long as you login to GNOME only once per boot and shutdown the system from GNOME you won't have this problem. The initial allocation of VT 7 after a reboot works fine. But if you logout of GNOME after logging in, you're likely to have this problem. It doesn't seem to fail all the time, though. Perhaps it is a timing-related problem. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1837243773.98097.1272576916545.javamail.r...@md01.wow.synacor.com
Re: X server starts on the wrong console (was: New monitor, how to change screen resolution?)
On Thu, 2010-04-29 at 17:35 -0400, Stephen Powell wrote: and it will work. Then, in theory, restarting the X server again (such as with /etc/init.d/gdm restart) should cause the X server to restart on vt 7. This used to work, but the last time I tried it I ended up with two X servers, one on VT 7 and one on VT 8! I had to reboot to clean things up. This situation is a mess and seems to be getting worse. As long as you login to GNOME only once per boot and shutdown the system from GNOME you won't have this problem. The initial allocation of VT 7 after a reboot works fine. But if you logout of GNOME after logging in, you're likely to have this problem. It doesn't seem to fail all the time, though. Perhaps it is a timing-related problem. I've noticed this too lately, although i use the nvidia driver created by module assistant. I wonder if anyone not using the nv or nvidia driver also see this? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1272577438.12886.2.ca...@debian.ok.shawcable.net
Re: X server starts on the wrong console (was: New monitor, how to change screen resolution?)
On Thu, 2010-04-29 at 14:43 -0700, Alan Ianson wrote: On Thu, 2010-04-29 at 17:35 -0400, Stephen Powell wrote: and it will work. Then, in theory, restarting the X server again (such as with /etc/init.d/gdm restart) should cause the X server to restart on vt 7. This used to work, but the last time I tried it I ended up with two X servers, one on VT 7 and one on VT 8! I had to reboot to clean things up. This situation is a mess and seems to be getting worse. As long as you login to GNOME only once per boot and shutdown the system from GNOME you won't have this problem. The initial allocation of VT 7 after a reboot works fine. But if you logout of GNOME after logging in, you're likely to have this problem. It doesn't seem to fail all the time, though. Perhaps it is a timing-related problem. I've noticed this too lately, although i use the nvidia driver created by module assistant. I wonder if anyone not using the nv or nvidia driver also see this? I seem to have this all the time, even right after booting, although... I have 3 displays, and 2 ports on my GPU, so I often switch them, after doing so, I copy the relevant xorg.conf to it's proper location, and restart gdm. In doing so, I only log in into the first console, using ctrl+alt+F1, do the copy and /etc/init.d/gdm restart, at this point x is running in VT8, not 7. Up till this point, I haven't logged in to gnome. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1272579986.22626.8.ca...@pc-steven.lan
Re: X server starts on the wrong console (was: New monitor, how to change screen resolution?)
On Thu, 29 Apr 2010 18:26:26 -0400 (EDT), Redalert Commander wrote: On Thu, 2010-04-29 at 14:43 -0700, Alan Ianson wrote: On Thu, 2010-04-29 at 17:35 -0400, Stephen Powell wrote: Then, in theory, restarting the X server again (such as with /etc/init.d/gdm restart) should cause the X server to restart on vt 7. This used to work, but the last time I tried it I ended up with two X servers, one on VT 7 and one on VT 8! I had to reboot to clean things up. This situation is a mess and seems to be getting worse. As long as you login to GNOME only once per boot and shutdown the system from GNOME you won't have this problem. The initial allocation of VT 7 after a reboot works fine. But if you logout of GNOME after logging in, you're likely to have this problem. It doesn't seem to fail all the time, though. Perhaps it is a timing-related problem. I've noticed this too lately, although i use the nvidia driver created by module assistant. I wonder if anyone not using the nv or nvidia driver also see this? I seem to have this all the time, even right after booting, although... I have 3 displays, and 2 ports on my GPU, so I often switch them, after doing so, I copy the relevant xorg.conf to it's proper location, and restart gdm. In doing so, I only log in into the first console, using ctrl+alt+F1, do the copy and /etc/init.d/gdm restart, at this point x is running in VT8, not 7. Up till this point, I haven't logged in to gnome. But the key is restarting the X server, not necessarily a logout and login to the GNOME desktop. A login/logout sequence is simply the most common way to restart the X server. The X server can only start once safely. After that, who knows what VT it will end up on, and what parts of the old instance of the server will get terminated. Has anyone seen something like this on a non-Nvidia driver (not nv and not nvidia)? -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/489890958.104820.1272593228318.javamail.r...@md01.wow.synacor.com
