John,

I never said it was the NVIDIA-driver. If it didn't change much (not at all), 
Gnome changed considerably from 99 to 101. It might as well be a botched Gnome 
integration.
And since OpenSolaris has recently endangered data and the sanity of those who 
entrust their desktops (== production) to it, I am reluctant to remove a 
principally working driver, at least as of now. I took the safe road and simply 
replaced the minimal xorg.conf with the one used since ages, the one that used 
to define the modes, and given as above. Now I am on 103, and the result is 
miserable:

1. The virtual screen is set to 1600x1200, so that the gdm applet is mostly 
hidden in the upper left rectangle. The log file proves this. 

2. Then I log on, and stay with 1024x768, the nicely arranged desktop icons 
illegibly overlap one another (and will stay like this even later when 
1600x1200 is achieved),

3. the panel crashes (it doesn't always, but one out of two starts of X deliver 
this; the crash report is attached as well. Then NVIDIA X settings: It stands 
on automatic, 1024x768. 

4. When I select the 1600x1200, it comes up with that meta mode message 
"MetaMode 2 of Screen 0 is the same as Meta Mode 1.All Meta Modes must be 
unique." That can't possibly come from the NVIDIA, because there is no meta 
mode. It could be a stale setting in Gnome?
Whatever. Auto-fix it this time didn't crash it, but 

5. brought the usual 1280x1024; not the prescribed 1600x1200. Calling it up 
another time, and another time setting it to 1600x1200 finally brings out the 
best in it.

Be aware, that all this crap does not happen with the reduced xorg.conf, that 
contains but the horizontal and vertical frequency ranges. Only, X doesn't 
start 'high', but needs to be to 1600x1200. Which it does without murmur. 
Actually, I created the reduced xorg.conf by removing everything except 
Monitor, Device and Screen, and there I also removed all options and the modes. 
That's my way to tell the NVIDIA X applet that, yes, it allows me to set to 
1600x1200 when I want to. Otherwise it wouldn't offer anything but the modes 
for the default frequencies. That is quite logical, because the EDID is 
unavailable.

With respect to loading the nv99-driver, I am somewhat reluctant. I might even 
bet a small amount that it won't do any changes. This machine has been updated 
from nv70 or nv81. I guess there is some cruft in the configuration. On the 
other hand, it is my main desktop machine, with all settings, mails, data. So I 
can't do a 'clean' install of 101/103 just to find out if it behaves properly 
in that case.
I can confirm that the update from 99 to 101 was anything but clean, since it 
broke the predefined modes (necessary due to the lack of EDID data).
It is a clear mistake, that a virtual desktop of 1600x1200 is started, when the 
screen is only 1024x768 for the gdm applet. The frequent panel crashes are not 
warranted neither, and - again - happen only in conjunction with predefined 
modes. It is a clear mistake, when 1600x1200 is offered by the NVIDIA X applet, 
but 1280x1024 is activated instead. 

I hope this helps to start debugging the problem. 

Uwe
-- 
This message posted from opensolaris.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: application/octet-stream
Size: 108774 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/xwin-discuss/attachments/20081216/724a125a/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Panel_crash
Type: application/octet-stream
Size: 2728 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/xwin-discuss/attachments/20081216/724a125a/attachment-0001.obj>

Reply via email to