Hi all - I have reasonable amount of success now, and have resolution on 118 as good as on 111b.
In summary: 1. On nv111b I specified radeon as the device driver, and got 1680x1050. If I didn't provide an xorg.conf, the monitor would display 'out of range' on an otherwise blank screen. 2. On nv117/118 I got the same result. My mistake was to give up on radeon device driver too soon and fall back to vesa, which does not provide either the desired 1920x1080 or the previously used 1680x1050, so I got the lower resolution I described in opening post of this thread. 3. I added a ModeLine for 1680x1050, and that worked. Note that I did NOT have a 1680x1050 ModeLine or Mode in the 111b version of xorg.conf. 4 .ModeLines for 1920x1080 were ineffective: Xorg.0.log has 1680x1050 listed among the "Supported Future Video Modes", but 1920x1080 is not: it shows up in reported device settings (eg: h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0), and as a generated Modeline: (II) RADEON(0): Printing DDC gathered Modelines: (II) RADEON(0): Modeline "1920x1080"x59.9 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz) But if you try to use that modeline, or if you use the Screen Resolution applet (right click on empty part of desktop, select Screen Resolution, select resolution 1920x1080) then you get back to the blank screen and "Out Of Range" displayed. Ideally, I'd have the full pixel range supported by the video card and monitor - Windows supports it, so I know it can display at this resolution, but the resulting resolution is more than adequate. I hope that the radeon driver is updated at some point to permit this. I also suggest that it is somewhat misleading to display modelines in Xorg.0.log for resolutions that the driver does not actually support. The advice I got here was invaluable in getting the display to be acceptable again. Thanks to all! regards, Jeff -- This message posted from opensolaris.org
