Hi Rob - Happy ThanksGiving:
First - there are specific and well known bugs in Ubuntu with that Intel Integrated GMA:
Reference:
http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100
Suggestions:
A) Try the 915resolution tool:
1. To install the package run the command sudo apt-get install 915resolution
2. Now run sudo 915resolution -l
3. You should see a list of different modes of resolution, like this,
Intel 915GM VBIOS Hack : version 0.1
Chipset: 915GM
Mode 30 : 640ื480, 8 bits/pixel
Mode 32 : 800ื600, 8 bits/pixel
Mode 34 : 1024ื768, 8 bits/pixel
Mode 38 : 1280ื1000, 8 bits/pixel
Mode 3a : 1600ื1200, 8 bits/pixel
Mode 3c : 1920ื1440, 8 bits/pixel
Mode 41 : 640ื480, 16 bits/pixel
Mode 43 : 800ื600, 16 bits/pixel
Mode 45 : 1024ื768, 16 bits/pixel
Mode 49 : 1280ื800, 16 bits/pixel
Mode 4b : 1600ื1200, 16 bits/pixel
Mode 4d : 1920ื1440, 16 bits/pixel
Mode 50 : 640ื480, 32 bits/pixel
Mode 52 : 800ื600, 32 bits/pixel
Mode 54 : 1024ื768, 32 bits/pixel
Mode 58 : 1280ื800, 32 bits/pixel
Mode 5a : 1600ื1200, 32 bits/pixel
Mode 5c : 1920ื1440, 32 bits/pixel
Mode 60 : 1280ื770, 8 bits/pixel
Mode 61 : 1280ื770, 16 bits/pixel
Mode 62 : 1280ื770, 32 bits/pixel
Mode 63 : 512ื771, 8 bits/pixel
Mode 64 : 512ื771, 16 bits/pixel
Mode 65 : 512ื771, 32 bits/pixel
3. To change to the desired mode, say for example, mode 5a, which is 1600ื1200 with 32 bpp, you would run
915resolution 5a 1600 1200 32
Now to fully set the mode, type sudo gedit /etc/default/915resolution,
a relatively short text file will pop up, edit this file by changing
MODE to the MODE that you selected. Eg, the mode line should now be ;
MODE=5a
Change the XRESO and YRESO values to correspond with your selection, for our example, they should look like this;
XRESO=1600
YRESO=1280
Finally, set the BIT value to the bpp you selected, in our case,32;
BIT=32
Now save the file and exit it.
4. Now restart x by pressing
<CTRL>-<ALT>-<BACKSPACE>. The 1st time you log in, X might
crash and restart itself at the new
resolution, so dont worry if it does that.
Reference: http://mcsp.wartburg.edu/figura/D620.html
A) It appears as if your modeline is not correct - Go here and get the correct modeline:
http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
C) Here's an example configuration from someone who had finally successfully done both with an Intel x3310 and external monitor:
http://www.linux-on-laptops.com/forum/archive/index.php/t-2702.html
www.Obnosis.com | http://en.wiktionary.org/wiki/Citations:obnosis |
http://www.urbandictionary.com/define.php?term=obnosis (503)754-4452
Catch the January PLUG HackFest! Kristy Westphal, CSO for the Arizona Department of Economic
Security will provide a one hour
presentation on forensics.
> Date: Wed, 26 Nov 2008 10:39:18 -0700
> From: wultsch@gmail.com
> To: PLUG-discuss@lists.plug.phoenix.az.us
> Subject: X11 issue
>
> I just did a fresh install of Ubuntu 8.10 on to a box with an intel
> x3100 integrated graphics card connected to a 22 inch lcd (toshiba
> 22LV505) display that should be capable of 1680x1050. I do not care
> about video acceleration, the box has a quad core that should be able
> to deal well enough without, though it would be nice.
>
> Using 'vesa' X11 works, but only for less than optimal values of works
> (800x600). Using 'intel' I see a momentary bit of display screen, and
> then black.
>
> Does anyone have any suggestions (or for that matter example xorg.conf
> 's ?) I have included the relevant log and (rather pathetic) conf
> files.
>
> I see a couple of things that look interesting in the X11 logs:
> (WW) VESA(0): Bad V_BIOS checksum
> WTF?
>
> (II) Module "ddc" already built-in
> (II) VESA(0): VESA VBE DDC supported
> (II) VESA(0): VESA VBE DDC Level none
> (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
> (II) VESA(0): VESA VBE DDC read failed
>
> Can I take this to mean that X11 could not pull compatible modes from
> the monitor?
>
> (II) VESA(0): Total Memory: 127 64KB banks (8128kB)
> (II) VESA(0): Configured Monitor: Using default hsync range of 31.50-37.90 kHz
> (II) VESA(0): Configured Monitor: Using default vrefresh range of 50.00-70.00 Hz
> (WW) VESA(0): Unable to estimate virtual size
> (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
> (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
> (WW) VESA(0): No valid modes left. Trying less strict filter...
> (II) VESA(0): Configured Monitor: Using hsync range of 31.50-37.90 kHz
> (II) VESA(0): Configured Monitor: Using vrefresh range of 50.00-70.00 Hz
> (WW) VESA(0): Unable to estimate virtual size
> (II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
> (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
> (II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)
> (--) VESA(0): Virtual size is 800x600 (pitch 800)
> (**) VESA(0): *Built-in mode "800x600"
> (**) VESA(0): *Built-in mode "640x480"
> (==) VESA(0): DPI set to (96, 96)
> (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
> (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
>
> Refresh rate issues, I would think...
>
> --
> Rob Wultsch
Color coding for safety: Windows Live Hotmail alerts you to suspicious email. Sign up today.