search for: 896x672

...x800 59.99 59.97 59.81 59.91 1152x864 75.00 75.00 70.00 60.00 1280x720 60.00 59.99 59.86 60.00 50.00 59.94 59.74 1024x768 75.05 60.04 75.03 70.07 60.00 960x720 75.00 60.00 928x696 75.00 60.05 896x672 75.05 60.01 1024x576 59.95 59.96 59.90 59.82 960x600 59.93 60.00 832x624 74.55 960x540 59.96 59.99 59.63 59.82 800x600 75.00 70.00 65.00 60.00 72.19 75.00 60.32 56.25 840x525 74.96 69.88...

I think I may have updated the tv firmware between when it worked and when it didn't. I wonder it it has to do with bit depth. I use lubuntu and it doesn't let me pick the bit depth so I don't know what it using.

> > OK, so I think that these are not the HDMI/DP outputs connected to > your secondary device. They are the ones connected to your primary > device (might not be pinned out, or might only be available via an > optional dock). Normally there'd be an extra -1- in the name of such > outputs. But who knows with modesetting - perhaps it doesn't stick > that in and sticks

...d primary 1920x1080+0+0 (normal left inverted right x axis y > axis) 344mm x 194mm > 1920x1080 60.02*+ 47.99 > 1400x1050 59.98 > 1280x1024 60.02 > 1280x960 60.00 > 1024x768 60.04 60.00 > 960x720 60.00 > 928x696 60.05 > 896x672 60.01 > 800x600 60.00 60.32 56.25 > 700x525 59.98 > 640x512 60.02 > 640x480 60.00 59.94 > 512x384 60.00 > 400x300 60.32 56.34 > 320x240 60.05 > HDMI-1 disconnected (normal left inverted right x axis y...

I seem to be able to run a video game in 1024x867 (what ever it is) as a window, by selecting the window mode button in the game. However, i can not run the game in window mode with a resolution set about 1024x867. What is going on? I am assuming i am missing something in wine or the game that does not allow the video game to be run in any resolution greater than 1024x867 in window mode.

...280x960 62.0 63.0 1152x864 64.0 65.0 66.0 67.0 68.0 69.0 70.0 1024x768 71.0 72.0 73.0 74.0 75.0 76.0 960x720 77.0 78.0 960x600 79.0 960x540 80.0 928x696 81.0 82.0 896x672 83.0 84.0 840x525 85.0 86.0 87.0 88.0 89.0 832x624 90.0 800x512 101.0 720x450 102.0 720x400 103.0 700x525 104.0 105.0 106.0 107.0 680x384 108.0 109.0 640x512 110.0 111...

...+0 0mm x 0mm 1920x1080 50.0* 1400x1050 51.0 52.0 1280x1024 53.0 54.0 55.0 1280x960 56.0 57.0 1152x864 58.0 1024x768 59.0 60.0 61.0 62.0 63.0 64.0 960x720 65.0 66.0 928x696 67.0 68.0 896x672 69.0 70.0 832x624 71.0 800x600 72.0 73.0 74.0 75.0 76.0 77.0 78.0 79.0 80.0 81.0 720x400 82.0 700x525 83.0 84.0 640x512 85.0 86.0 87.0 640x480 88.0 89.0 90.0 91.0 9...

...kHz) (II) NOUVEAU(0): Modeline "960x720"x60.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz) (II) NOUVEAU(0): Modeline "928x696"x60.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz) (II) NOUVEAU(0): Modeline "896x672"x75.0 130.50 896 944 1052 1228 672 672 674 708 doublescan -hsync +vsync (106.3 kHz) (II) NOUVEAU(0): Modeline "896x672"x60.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz) (II) NOUVEAU(0): Modeline "832x624 at 75"x74.6 57.30 832 864 92...

Be forewarned, I am new to Linux. I am using Ubuntu 9.10 (Karmic Koala). I have installed wine (1.1.38) and I am able to run RollerCoaster Tycoon 3 both with and without a virtual desktop. It runs with no problems except for the fact that it does not receive keyboard commands! I have looked all over the Internet and still have yet to find a solution. Someone help, please! I haven't

> > No, that line is actually expected (just means accel won't work, since > NVIDIA hw now requires signed firmware, but they won't release the > ctxsw fw). Are you absolutely sure that you're seeing the outputs in > xrandr? Could you provide the output of xrandr as well as an Xorg log? > > Thanks, > > -ilia Many thanks for you help. All data below :

...quot;1600x1200" (vrefresh out of range) [ 4325.340] (II) NOUVEAU(0): Not using default mode "800x600" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1792x1344" (hsync out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "896x672" (hsync out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1792x1344" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "896x672" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1856x1392&quot...

...0): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "896x672" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "896x672" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1856x1392" (insufficient memory for mode) (II)...

...quot;928x696"x75.0 144.00 928 992 1104 1280 696 696 698 750 doublescan -hsync +vsync (112.5 kHz d) [ 7.165] (II) modeset(0): Modeline "928x696"x60.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d) [ 7.165] (II) modeset(0): Modeline "896x672"x75.0 130.50 896 944 1052 1228 672 672 674 708 doublescan -hsync +vsync (106.3 kHz d) [ 7.165] (II) modeset(0): Modeline "896x672"x60.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d) [ 7.165] (II) modeset(0): Modeline "960x600&quot...

https://bugs.freedesktop.org/show_bug.cgi?id=92991 Bug ID: 92991 Summary: Nouveau module loading regression in 4.4-rc1 on optimus system Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...ximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.02*+ 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.04 60.00 960x720 60.00 928x696 60.05 896x672 60.01 800x600 60.00 60.32 56.25 700x525 59.98 640x512 60.02 640x480 60.00 59.94 512x384 60.00 400x300 60.32 56.34 320x240 60.05 -- You are receiving this mail because: You are the assignee for the bug....

...sing default mode "1600x1200" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1792x1344" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1792x1344" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1856x1392" (excee...

...sing default mode "1600x1200" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1792x1344" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1792x1344" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1856x1392" (excee...

...20"x120.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "928x696"x120.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "896x672"x120.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "960x600"x120.0 77.00 960 984 1000 1040 600 601 604 617 doublescan +hsync -vsync (74.0 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "960...

...g default mode "1600x1200" (hsync out of range) (II) NOUVEAU(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1792x1344" (height too large for virtual size) (II) NOUVEAU(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1792x1344" (height too large for virtual size) (II) NOUVEAU(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1856x1392&quo...

...cStart : 1344, 1345 (II) NVIDIA(0): VSyncEnd, VTotal : 1348, 1394 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (204.8 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "896x672": (II) NVIDIA(0): 896 x 672 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 102.400 MHz (II) NVIDIA(0): HRes, HSyncStart : 896, 960 (II) NVIDIA(0): HSyncEnd, HTotal : 1060, 1224 (II) NVIDIA(0): VRes, VSyncStart : 672, 672 (II...