100 wasn't available to me. 'Worked', it has always, because I always needed an 
xorg.conf (and an XF86config earlier). Only, what *did* work until and 
including nv_99, were the modes specifications. Meaning, gdm always came up 
with 1024x768, but then, after authentication, X would switch to 1600x1200 
immediately. Since nv_101 it doesn't; see that other thread on the problem with 
the GF6150/6200, where you yourself said you would be working on the 
'meta'-problem 
(http://www.opensolaris.org/jive/thread.jspa?threadID=81020&start=15&tstart=0). 
That latter only came up on nv_101, and I hadn't changed my xorg.conf for ages. 
Plus, it doesn't contain any meta modes:

[i]# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (@builder29)  Mon Apr 16 20:34:19 PDT 2007


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
    RgbPath         "/usr/X11/lib/X11/rgb"
    FontPath        "/usr/X11/lib/X11/fonts/misc/:unscaled"
    FontPath        "/usr/X11/lib/X11/fonts/100dpi/:unscaled"
    FontPath        "/usr/X11/lib/X11/fonts/75dpi/:unscaled"
    FontPath        "/usr/X11/lib/X11/fonts/misc/"
    FontPath        "/usr/X11/lib/X11/fonts/Type1/"
    FontPath        "/usr/X11/lib/X11/fonts/100dpi/"
    FontPath        "/usr/X11/lib/X11/fonts/75dpi/"
    FontPath        "/usr/X11/lib/X11/fonts/TrueType/"
    FontPath        "/usr/X11/lib/X11/fonts/Type1/sun/"
    FontPath        "/usr/X11/lib/X11/fonts/F3bitmaps/"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "IA"
    Load           "bitstream"
    Load           "xtsol"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/mouse"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "keyboard"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       30.0 - 110.0
    VertRefresh     50.0 - 150.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "RenderAccel" "True"
    Option         "AllowGLXWithComposite" "True"
    Option         "AddARGBGLXVisuals" "True"
    SubSection     "Display"
        Depth       24
        Modes      "nvidia-auto-select" "nvidia-auto-select" "1600x1200" 
"1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Section "Extensions"
    Option         "Composite" "Enable"
EndSection[/i]

Since nv_101 this dies horribly, with all side effects, and never sets the 
screen right. Meaning, there is a real problem on 'your' (=SUN) side. I 
couldn't even set it with NVIDIA X Server Settings, it would never accept 
1600x1200, always only 1280x1024 (or so), and then I'd have to enter the 
1600x1200 another time, and then only it would 'bootstrap' to 1600x1200; and 
usually take the panel applet down with it. You can find the whole lot in 
message ID 304416, in case you're interested. 

Next botched job on 'your' side: Now it does get the 
(II) NVIDIA(0): HorizSync : 30.000-121.000 kHz
(II) NVIDIA(0): VertRefresh : 50.000-160.000 Hz
, but it doesn't use this info, not at all. (Except that it *allows* me to set 
the monitor to 1600x1200 manually, using the NVIDIA-applet, long after log in.) 
The log file that I sent shows this. Despite all funtastic resolutions as 
calculated before, it ends at
CRT-0: "nvidia-auto-select"
(II) NVIDIA(0):         Size          : 1024 x 768

No point using the old driver. It 'worked', with a .conf, but the EDID never 
did. I guess due to the auto-detect in the normal case recently, some sloppy 
coding has set in, conveniently discarding both modes and horiz/vert 
frequencies at bringing up X.
Since we are at it, one of the problems since nv_101 was, that it starts gdm at 
1024x768, but with a virtual screen size of 1600x1200, with the gdm applet in 
the upper left quadrant. So in order to log, since nv_101 (and using 'modes') I 
needed the mouse to navigate the virtual screen to reach the gdm applet. And 
then the panel crashes rather regularly, then that meta-mode message comes up, 
then the 1600x1200 inevitably turn out to be 1280x1024, and then yet another 
effort only gets to 1600x1200. 
Let's face it, it is just rotten since nv_101.

Uwe
-- 
This message posted from opensolaris.org

Reply via email to