search for: 1152x768

...port 0 0 Depth 16 Modes "1600x1200" "1600x1024" "1440x900" "1400x1050" "1280x1024" "1280x1024" "1280x960" "1280x960" "1280x800" "1280x800" "1152x864" "1152x864" "1152x768" "1152x768" "1024x768" "1024x768" "800x600" "800x600" "640x480" "640x480" EndSubSection EndSection

My OQO has a VIA chipset. From the hwconf: class: VIDEO bus: PCI detached: 0 desc: "VIA Technologies, Inc. CX700M2 UniChrome PRO II Graphics" vendorId: 1106 deviceId: 3157 subVendorId: 1106 subDeviceId: 3157 pciType: 1 pcidom: 0 pcibus: 1 pcidev: 0 pcifn: 0 When I install Centos, I default to the vesa driver, and it operates at the monitor's native 800x480. Of course I

...SubSection "Display" Viewport 0 0 Depth 24 Modes "1600x1200" "1600x1024" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection

I originally set up this monitor with an analogue lead. Everything seemed fine, so I didn't check xorg.conf at all. Then I bought a digital lead, and since then the monitor blinks. Running system-config-display identifies it as a 1280 x 1084 CRT monitor. It is an LCD monitor. That model is not on the drop-down list, so assuming that a specific driver wasn't available for it, I

I just put a 1680x1050 LCD monitor on my home system, and I went into system-config-display to configure it as such, and it just won't take. I had to tweak some of the settings by hand, but when I log out, I get the wide screen for both the Nvidia driver splash screen and the login screen. But, when I log in, It jumps back to 1280x1024 and refuses to run in wide screen mode. Here's the

...rent 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 60.0* 1024x768 60.0 800x600 60.0 56.0 640x480 60.0 1280x1024 60.0 1440x900 60.0 1280x960 60.0 1280x800 60.0 1280x768 60.0 1152x768 55.0 Now, here is the real issue: My laptop has a VGA port and an svideo port. To start working on smooth multi-head support for gnome, I obviously need use of at least the VGA port. As it stands, nouveau does not detect any of these outputs. As I understand it, xrandr should be reporting so...

...sync (59.6 kHz) (II) NOUVEAU(0): Modeline "1152x864 at 75"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (II) NOUVEAU(0): Modeline "1152x768 at 54"x54.8 65.00 1152 1178 1314 1472 768 771 777 806 +hsync +vsync (44.2 kHz) (II) NOUVEAU(0): Modeline "1024x768"x60.0 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz) (II) NOUVEAU(0): Modeline "1024x768 at 85"x85.0 94.50 1024 1072...

...4, 576 (II) NVIDIA(0): VRes, VSyncStart : 312, 312 (II) NVIDIA(0): VSyncEnd, VTotal : 314, 333 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1152x768": (II) NVIDIA(0): 1152 x 768 @ 55 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 64.995 MHz (II) NVIDIA(0): HRes, HSyncStart : 1152, 1178 (II) NVIDIA(0): HSyncEnd, HTotal : 1314, 1472 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II...

...state.video_ram: 0 id.xsetup.xserver.hwstate.videocard: Already dumped id.xsetup.xserver.hwstate.videocard_driver: vesa id.xsetup.xserver.hwstate.videocard_options: [] id.xsetup.xserver.hwstate.all_resolutions: [640x480, 800x480, 800x512, 800x600, 1024x600, 1024x768, 1152x768, 1152x864, 1280x800, 1280x960, 1280x1024, 1400x1050, 1440x900, 1600x1024, 1600x1200, 1680x1050, 1900x1200, 1920x1200, 1920x1440, 2048x1536] id.xsetup.xserver.hwstate.hsync: 31.5-37.9 id.xsetup.xserver.hwstate.vsync: 50-70 id.xsetup.xserver.hwstate.probed_video_ram: 0...

...II) S3VIRGE(0): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1152x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient mem...

...0 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz) (**) NOUVEAU(0): Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (**) NOUVEAU(0): Default mode "1152x768": 65.0 MHz, 44.2 kHz, 54.8 Hz (II) NOUVEAU(0): Modeline "1152x768"x54.8 65.00 1152 1178 1314 1472 768 771 777 806 +hsync +vsync (44.2 kHz) (**) NOUVEAU(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "1024x768"x85.0 94.50...

...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 panel dimensions) (II) NOUVEAU(0): Not using default mode "576x432" (bad mode clock/interla...