On Thu, 16 Sep 2010 12:04:57 -0400 (EDT), Tong wrote:
> Stephen Powell wrote:
>> Specifying "Modes" in the Display subsection of the Screen section, or
>> specifying the virtual desktop size, has always been sufficient for me. 
> 
> No, that don't work for me.  Specifying a bigger mode than the display 
> driver can handle can only give me a "virtual" desktop size, i.e., I need 
> to *pan* to reach every corner, which I don't like. Moreover, the wrong 
> resolution is damaging my monitor -- 2 days later the pixels started to 
> be "blowing" rightward.

If you need an oddball screen resolution, that's one thing.  But if
I recall correctly, what you wanted was 1280x1024, right?  That's a
standard resolution.  Without specifying a custom modeline, there
are two sources of information that the X server uses: (1) modelines
obtained from the monitor itself, if the monitor supports DDC2/EDID.
Most monitors made after 1993 support DDC2/EDID.  (2) There is also
a built-in set of default modelines that the X server can call upon.
Something like this "should" work:

     Section "Files"
     #
     # Note: the following fonts will be automatically appended by the X Server,
     # if they exist, and therefore they should not be explicitly specified 
here.
     # If they are, they will be included in the font path twice.
     #
     #       FontPath        "/usr/share/fonts/X11/misc"
     #       FontPath        "/usr/share/fonts/X11/cyrillic"
     #       FontPath        "/usr/share/fonts/X11/100dpi/:unscaled"
     #       FontPath        "/usr/share/fonts/X11/75pdi/:unscaled"
     #       FontPath        "/usr/share/fonts/X11/Type1"
     #       FontPath        "/usr/share/fonts/X11/100pdi"
     #       FontPath        "/usr/share/fonts/X11/75dpi"
     #       FontPath        "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
     EndSection

     Section "InputDevice"
             Identifier      "Generic Keyboard"
             Driver          "kbd"
             Option          "CoreKeyboard"
             Option          "XkbRules"      "xorg"
             Option          "XkbModel"      "pc104"
             Option          "XkbLayout"     "us"
     EndSection

     Section "InputDevice"
             Identifier      "Configured Mouse"
             Driver          "mouse"
             Option          "CorePointer"
             Option          "Device"                 "/dev/input/mice"
             Option          "Protocol"               "ImPS/2"
             Option          "Emulate3Buttons"        "true"
     EndSection

     Section "Device"
             Identifier      "Configured Video Device"
             Driver          "nv"
     EndSection

     Section "Monitor"
             Identifier      "Configured Monitor"
     EndSection

     Section "Screen"
             Identifier      "Default Screen"
             Device          "Configured Video Device"
             Monitor         "Configured Monitor"
             DefaultDepth    24
             Subsection      "Display"
                     Depth           24
                     Modes           "1280x1024" "1024x768" "800x600" "640x480"
             EndSubSection
     EndSection

     Section "ServerLayout"
             Identifier      "Default Layout"
             Screen          "Default Screen"
             InputDevice     "Generic Keyboard"
             InputDevice     "Configured Mouse"
     EndSection

The "Modes" line says what resolutions you want available, beginning with
the desired mode, but does not give specific timings.  The virtual desktop
size normally defaults to the size of the largest mode.

>> But if you're happy with the results, that's the important thing.
> 
> Yes, I am. Note that what I added is the correct "Modeline", telling nv 
> driver how to handle such situation, which is used to be the common 
> practice when X can't do the automatic detection before (10 years ago?). 

I would be interested in seeing the full contents of your /var/log/Xorg.0.log
file when used with an /etc/X11/xorg.conf file similar to the above.
Some reasons why it might not work:

(1) It is unable to determine the amount of video RAM present.
The default video RAM assumed is not sufficient for the resolution and color
depth desired.

(2) It cannot detect the maximum pixel clock rate for your video card.
The default value assumed is not high enough to satisfy the requirements
of the video mode.

(3) It cannot (or does not) detect the monitor's parameters correctly,
such as horizontal and vertical sync frequency ranges or video bandwidth.

These are only some of the possibilities.

If you are satisfied to leave well enough alone, that's fine, but if you'd
like to avoid using a custom mode line, please post the entire
/var/log/Xorg.0.log file, along with its corresponding /etc/X11/xorg.conf
file, and I'll see if I can figure out what needs to be changed to get
it to work with a standard mode.  If you could post your Squeeze output
using the same hardware, that would also be good for comparison purposes.

By the way, what kind of monitor are you using?  Is it a CRT or a flat
screen panel?  Are you using analog output (VGA) or digital (DVI)?

-- 
  .''`.     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/515229257.31536.1284656138293.javamail.r...@md01.wow.synacor.com

Reply via email to