search for: 416x312

...73.0 720x450 74.0 700x525 75.0 76.0 77.0 680x384 78.0 79.0 640x512 80.0 81.0 640x480 82.0 83.0 84.0 85.0 576x432 86.0 87.0 88.0 89.0 512x384 90.0 91.0 92.0 416x312 93.0 400x300 94.0 95.0 96.0 97.0 320x240 98.0 99.0 100.0 any ideas? this is a fresh ubuntu. fresh wine install. Im not dual booting, so i installed BF2 in linux through wine.

...720x400 70.08 684x384 59.88 59.85 680x384 59.80 59.96 640x400 59.88 59.98 576x432 75.00 75.00 70.00 60.06 640x360 59.86 59.83 59.84 59.32 512x384 75.03 70.07 60.00 512x288 60.00 59.92 416x312 74.66 480x270 59.63 59.82 400x300 72.19 75.12 60.32 56.34 432x243 59.92 59.57 320x240 72.81 75.00 60.05 360x202 59.51 59.13 320x180 59.84 59.32 HDMI-1 connected 3840x2160+1920+0 (normal left inverted right...

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.

I am installing the original Stronghold Crusader when I install it using wine all seems to go well until I actually start the game then when the aspect ratio changes for the game there is no video but from what I can hear when I move my mouse everything else seems to be responding normally. I thought it might be related to the nVidia drivers that were installed by the "hardware drivers

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.

Nate Homier wrote: > I think I get it. So I added the modeline: > Modeline "1024x768 at 50" 51.85 1024 1056 1248 1280 768 784 791 807 > > But it still don't work. Running winedebug gives: > trace:x11settings:X11DRV_ChangeDisplaySettingsEx width=1024 height=768 > bpp=32 freq=50 (XRandR) > err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found

...149.5 120.0 640x512 150.0 120.0 640x480 120.0 85.0 75.0 72.8 75.0 66.7 59.9 720x400 85.0 70.1 640x400 85.1 576x432 150.0 640x350 85.1 512x384 170.0 150.1 140.1 120.0 416x312 149.3 400x300 170.5 144.4 150.2 120.6 112.7 320x240 170.4 145.6 150.0 120.1 360x200 170.1 320x200 170.5 320x175 170.5 This is a flat panel, and I'm quite sure it cannot accept modes above 85Hz, maybe even lower...

I trying play GTA San Andreas and it is returning " Cannot find 800x600x32 video mode". I worried so my wine Games pointed for a Working Directory that register a dosdevice instead of drive_c. Thereby I'm getting" /home/normal/.wine/dosdevices/c:/Program Files/Rockstar Games/GTA San Andreas" path and "win:EnumDisplayDevicesW ((null),0,0x177f6dc,0x00000000), stub!"

...111.0 112.0 640x480 113.0 114.0 115.0 116.0 117.0 118.0 119.0 120.0 640x400 121.0 640x350 122.0 576x432 123.0 124.0 125.0 126.0 127.0 128.0 129.0 512x384 130.0 131.0 132.0 133.0 134.0 416x312 135.0 400x300 136.0 137.0 138.0 139.0 140.0 360x200 141.0 320x240 142.0 143.0 144.0 145.0 320x200 146.0 320x175 147.0 800x600_85.00 83.8 Yes that's my new mode at the bottom!! My xorg.conf: Code: #...

...20x400 82.0 700x525 83.0 84.0 640x512 85.0 86.0 87.0 640x480 88.0 89.0 90.0 91.0 92.0 93.0 94.0 640x400 95.0 640x350 96.0 576x432 97.0 512x384 98.0 99.0 100.0 101.0 102.0 416x312 103.0 400x300 104.0 105.0 106.0 107.0 108.0 360x200 109.0 320x240 110.0 111.0 112.0 113.0 320x200 114.0 320x175 115.0 xrandr doesn't work with xinerama enabled. I'm using the propriatery nvidia driver (280.13) with...

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

> > 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

...2 524 592 672 384 385 388 403 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "512x384": 22.4 MHz, 35.5 kHz, 86.6 Hz (D) (II) S3VIRGE(0): Modeline "512x384" 22.45 512 516 604 632 384 384 388 409 interlace doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D) (II) S3VIRGE(0): Modeline "416x312" 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D) (II) S3VIRGE(0): Modeline "400x300" 28.15 400 416...

...60.0 kHz) (II) NOUVEAU(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz) (II) NOUVEAU(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz) (II) NOUVEAU(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz) (II) NOUVEAU(0): Modeline "400x300"x85.3 28.15 400 416 448 524 300 300 302 315 doublescan +hsync +vsync (53.7 kHz) (II) NOUVEAU(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300...

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

I have successfully installed Battlefield 2 using Wine 0.9.57 on Ubuntu 8.04, however when I launch the game I get the following error (It loads the splash, and loads a 800x600 window, and then the error dialog pops-up). I've followed most relevant instructions on the AppDB page for Battlefield 2, but nothing seems to make a difference. Error Message: [Image:

...uot;1920x1440" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "960x720" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "832x624" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "416x312" (vrefresh out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1400x1050" (hsync out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "700x525" (hsync out of range) [ 4325.341] (II) NOUVEAU(0): Not using default mode "1400x1050"...

...2, 864 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1152 (II) NVIDIA(0): VRes, VSyncStart : 624, 625 (II) NVIDIA(0): VSyncEnd, VTotal : 628, 667 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "416x312": (II) NVIDIA(0): 416 x 312 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 28.642 MHz (II) NVIDIA(0): HRes, HSyncStart : 416, 432 (II) NVIDIA(0): HSyncEnd, HTotal : 464, 576 (II) NVIDIA(0): VRes, VSyncStart : 312, 312 (II)...

...ine "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz d) [ 7.165] (II) modeset(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d) [ 7.165] (II) modeset(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz d) [ 7.165] (II) modeset(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz d) [ 7.165] (II) modeset(0): Modeline "400x300"x75....

...Not using default mode "1920x1440" (exceeds panel dimensions) (II) NOUVEAU(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "832x624" (vrefresh out of range) (II) NOUVEAU(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1152x768" (vrefresh out of range) (II) NOUVEAU(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "1152x864" (exceeds pa...