[P4M900] incorrect screen detection [openchrome]

[Johan Walles]

Binary package hint: xserver-xorg-video-openchrome

I'm trying to run Hardy Alpha 3 on a Fujitsu/Siemens Amilo Li1705 laptop.

It has a (wide) screen of 1280x800 (according to Windows).

The live CD gives me a resolution of 1920x1200, which means that a lot of pixels are outside of the physical screen. I would like the Live CD to detect the screen size of 1280x800 by itself.

My Xorg.0.log (will attach) says:
"
...
(II) CHROME(0): Configured Monitor: Using default hsync range of 31.50-37.90 kHz
(II) CHROME(0): Configured Monitor: Using default vrefresh range of 50.00-70.00 Hz
(WW) CHROME(0): Unable to estimate virtual size
(II) CHROME(0): Attempting to use 60Hz refresh for mode "800x600" (115)
(II) CHROME(0): Attempting to use 60Hz refresh for mode "640x480" (112)
(--) CHROME(0): Virtual size is 1920x1200 (pitch 1920)
...
"

I'm guessing (haven't tried) that adding my screen resolution to xorg.conf would work around this, but it would still be better if this worked out of the box.
[lspci]
00:00.0 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
01:00.0 VGA compatible controller: VIA Technologies, Inc. Chrome9 HC IGP (rev 01)

[Johan Walles (walles)]

The GNOME screen resolution settings doesn't give me any (!) resolutions to choose from. Using xrandr from the command line doesn't work either (see attachment).

[mikko (mikko-)]

Same problem, I have Acer Aspire 1362 with Via K8M800, laptop's max resolution is 1024x768.
Now I have 1600x1200, it's max for the external monitor. But I don't have a such.
And I can't change resolution in Screen and Graphics Preferences, all menus are empty.

ubuntu@ubuntu:~$ xrandr
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected
   1600x1200 0.0
   1400x1050 0.0
   1280x1024 0.0
   1280x800 0.0
   1280x768 0.0
   1024x768 0.0
   800x600 61.0
   720x576 0.0
   720x480 0.0
   640x480 60.0

[mikko (mikko-)]

Screenshot shows the whole 1600x1200 but I can see only the upper left corner in my laptop's monitor.

[Timo Aaltonen (tjaalton)]

Filed upstream:

http://openchrome.org/trac/ticket/156

thanks for testing!

[Jarek (jarhuba)]

Same problem, my Fujitsu Siemens Amilo L7310W (with PN800) doesn't display correct resolution 1280 x 800 but 1920 x 1440 (max for external monitor).
When I tray to switch to external monitor nothing appear on CRT.
When I switch to vt and back to X then "unable to determine the refresh rate, using 60.00. Plesae check your configuration." appear in Xorg.0.log
My Xorg.0.log also say "Unable to estimate virtual size"

[mikko (mikko-)]

I had same problem in Gutsy already. But nobody didn't recognize it..
https://bugs.launchpad.net/xorg-server/+bug/134951

I had to configure X manually in Gutsy (sudo dpkg-reconfigure xserver-xorg) but it's not possible in Hardy, I tried today. It didn't ask anything about screen, only keyboard and mouse questions.

[jarondl (jarondl)]

Same here.. Reinstalled hardy, and the maximum resolution is set to 600x800..
like mikko sorri, I've tried dpkg-reconfigure, but it doesn't ask anything about screens any more... This is probably due to
https://blueprints.launchpad.net/ubuntu/+spec/hardy-hardware-detection
but that doesn't help, because no workaround is suggested there....

[mikko (mikko-)]

Is it possible to force xorg to use 1024x768?

[jarondl (jarondl)]

I've succeeded in reconfiguring xorg, and now I can change the resolution by System >> Preferences >> Screen resolution.
first, and MOST IMPORTENT, backup your /etc/X11/xorg.conf file.
the following command might wreck your graphical system..Do it only if you safe about going to other tty's and trying to recover X

sudo dpkg-reconfigure -phigh xserver-xorg

and then restart X by log-out. (no, ctrl+alt+backspace doesn't seem to do enough)
Good luck

[Vital Urbonavi (vital.urbonavi)]

The same problem here. Can anybody suggest a work around? Thanks
sudo dpkg-reconfigure -phigh xserver-xorg
didn't work

[mikko (mikko-)]

Maybe this is not openchrome but hardware-detection bug? If I select safe driver from live-cd boot menu, resolution is 800x600, not 1024x768.
Who can fix the problem? Ubuntu Hardy will be useless in many VIA-laptops before that.

[Johan Walles (walles)]

Mikko, "safe mode" doesn't use the openchrome driver, I think it uses the VESA driver.

Any problems with safe mode are unrelated to this bug report.

Please file a separate report.

[mikko (mikko-)]

Yes, I know safe mode uses vesa driver. But maybe the cause is same and the problem is not only in the openchrome driver. Resolution with vesa-driver was also ok before hardy.

I don't know so much about drivers but which one makes the resolution decision, driver (openchrome or vesa) kernel, or something else? In Gutsy driver read resolution from xorg.xonf but now?

Resolution with openchrome driver was ok before Hardy too. That's why I think Jarondl is right. Problem is in new hardware detection system, maybe in xorg, not in openchrome driver.

[Jarek (jarhuba)]

I found workaround for this, just modify Screen section in xorg.conf
It should look similar to this:

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 DefaultDepth 24
 SubSection "Display"
     Depth 24
     Modes "1280x800"
 EndSubSection
EndSection

If acceleration for your card (like my PN800) is broken, put this line into Device section
 Option "NoAccel" "true"

Desktop is very slow, but not messy and works.

[mariano.iannuzzi (mariano-iannuzzi)]

The workaround worked for me.

Thanks dude.

I just wonder if this will not mess future updates up? I mean would new updates re-write xorg.conf?

[mariano.iannuzzi (mariano-iannuzzi)]

BTW, acceleration does not work for me either...

[Jarek (jarhuba)]

#If acceleration for your card (like my PN800) is broken, put this line into Device section
# Option "NoAccel" "true"

In this case (if you have artifacts) you can tray to use:
Option "EnableAGPDMA" "false"
in Device section xorg.conf

[mikko (mikko-)]

Modifying Screen section in xorg.conf worked. But only with livecd. I installed hardy to hard disk and 800x600 is the best resolution I get. I have done all tricks I know without success.
Also "openchrome" or "via" in xorg.conf didn't help.

[mariano.iannuzzi (mariano-iannuzzi)]

What concerns me a bit is that this bug has not been assigned yet...I could help but since I am not a programmer the only thing I can do is test solutions :( or post bugs...

[Tomasz Dominikowski (dominikowski)]

I just got this working with a CN700 (DRI works fine too). The driver or Xorg or whatever doesn't detect the hsync and vsync values properly. You have to add them to xorg.conf manually to work around this bug.

For example for my 1280x1024 LCD screen these are my Monitor and Screen sections of xorg.conf:

Section "Monitor"
 Identifier "Configured Monitor"
 Option "DPMS"
 HorizSync 30.0 - 80.0
 VertRefresh 56.0 - 75.0

EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
        Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Obviously for your 1280x800 laptop screen you'd need to edit the horizsync, the vertrefresh and display modes, but I'm sure once you input the right values everything is going to work.

Back to 2001 everyone.

[mariano.iannuzzi (mariano-iannuzzi)]

Anyone working on this bug????

[Jarek (jarhuba)]

You can try compile randr branch.
http://openchrome.org/trac/browser/branches/randr_branch?order=name
There is some new code which should resolve this bug.
We must wait for merging and new release openchrome drivers.

[Adam Niedling (krychek)]

I just made a discovery. When I boot from Hardy Alpha 5 live cd using normal mode I get that huge resolution. When i try to reboot it freezes at the end. When i boot using safe graphic mode I get a decent desktop and it won't freeze when I reboot. It just ejects the cd and turns off when I press enter. Anyone experiencing this thing?

[Adam Niedling (krychek)]

Bug still exist on Hardy Alpha 6 with my Amilo La 1703 laptop which is almost the same as the original poster's laptop. (Hardy is gonna be great otherwise ;) )

[blackest_knight (blackest-knight)]

Bug effects EEE-pc as well has nothing for a 800 by 480 screen
i lost the proper resolution by turning off desktop effects.

[erik veninga (ejopzee)]

Bug exist on Hardy Alpha 6 Fujitsu Amilo Pro 3515. Resolution is not detected.

Edit of /etc/X11/xorg.conf

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
        DefaultDepth 24
        SubSection "Display"
                Modes "1280x800"
        EndSubSection
EndSection

Is doing the trick. A bit much if you have no experience on the commandline or an editor in linux.

Adjusting screenresolution via the menu's is not working. Not the livecd and not installed.

[Adam Niedling (krychek)]

It just got worse with Hardy beta live cd. I'm attaching the Xorg.0.log file and a picture of my screen.

[Adam Niedling (krychek)]

There are dots on the screen.. it doesn't like nice and it's flickering too. The resolution is still way too high.

[mariano.iannuzzi (mariano-iannuzzi)]

I updated to Hardy Beta (Averatec 3280) and now the work-around does not work...

The live CD booted to the wrong resolution but I could change it on the System Preferences dialog. After the installation, the system boots fine but at the end the screen goes black and nothing happens. After about 5 minutes a windows pops up saying that Ubuntu was booting in low resolution. I said ok, proceed and the PC halted again without showing the GDM.

I then booted in text mode and installed OpenChrome from source. After that modified the xorg.cong file to set the resolution to 1024x768. Running "/etc/init.d/gdm restart" brings the Ubuntu Log-in screen. After logging in, the systems shows a light brown screen and halts there...

Any ideas?

Is there any file I could upload so someone could take a look?

Thanks!

Mariano

[sibidiba (sibidiba)]

I can confirm this bug, and Jarek's workaround (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/182778/comments/19).

Although the livecd worked (with a wrong resolution), after the first boot gdm/X does not started. In the log I found: (EE) No screens found .

I modified xorg.conf this way:

Section "Device"
        Identifier "Configured Video Device"
        Driver "openchrome"
EndSection

Now X worked, but with the resolution of 1600x1200. Other modes in xrandr had refresh rates of 0, trying them resulted in a totally broken display.

Applying the changes below resolved that:

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 SubSection "Display"
     Modes "1280x800"
 EndSubSection
EndSection

[George Kontis (giormatsis)]

sudo displayconfig-gtk does some job . does anybody know the screen model of Amilo L7310W ???

[hugo (hugo-zanker)]

I think I have this problem too. The best I could get it was to have the right resolution. The refresh rate and all other options remain unavailable. In fact the refresh rate is reported as being 0 hz (Impossible). The graphics work alright and look good except for huge glitches (See attachment) every few minutes.
My hardware is <S3 Unichrome Pro VGA Adapter (rev 01) running fully updated Hardy 64.

[Chris Chan (crazytales)]

I also have a '0hz' refresh rate on my averatec. my screen glitches up as
well sometimes, but I don't have the laptop now (I broke the power adapter
connection just before going on vacation)

On Wed, Jul 30, 2008 at 7:14 AM, hugo <email address hidden> wrote:

> I think I have this problem too. The best I could get it was to have the
> right resolution. The refresh rate and all other options remain unavailable.
> In fact the refresh rate is reported as being 0 hz (Impossible). The
> graphics work alright and look good except for huge glitches (See
> attachment) every few minutes.
> My hardware is <S3 Unichrome Pro VGA Adapter (rev 01) running fully updated
> Hardy 64.
>
>
> ** Attachment added: "Screenshot.png"
> http://launchpadlibrarian.net/16420033/Screenshot.png
>
> --
> Wrong resolution on Hardy
> https://bugs.launchpad.net/bugs/182778
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Chris Chan
AIM: crztales
YIM: crazytales562
MSN: <email address hidden>

[unggnu (unggnu)]

I can confirm this with the 0 hz refres rate and have created another bug report for the screen corruption under Bug 259389. I have also reported it upstream. A confirmation would be great with information about your exact graphic chipset.

[coubi64 (frederic-valentin)]

Same problem for me with Intrepid Ibex.

Here are the logs:

http://launchpadlibrarian.net/18049355/dmesg

http://launchpadlibrarian.net/18049330/Xorg.0.log

[Johan Walles (walles)]

According to the upstream trac this is supposedly fixed in revision 594:
http://www.openchrome.org/trac/ticket/156

1:0.2.903-0ubuntu3 which is shipped in Intrepid right now is based on revision 588, which does not contain the fix:
http://www.openchrome.org/trac/browser/tags

Please upgrade the Intrepid packages to (at least) revision 594.

[Raphael Geissert (atomo64)]

@Johan Walles: Xavier asked to *retry*, he didn't in any way imply that it was fixed (although it might be :).

Could you please try the package at [1]? it is the latest revision by upstream.

[1] https://launchpad.net/~atomo64/+archive

[Johan Walles (walles)]

It's not my laptop and I can't play around with it unfortunately, so somebody else will have to test your packages.

I actually did look at the code though, and there *is* convincingly-looking detection code in there. I'm hopeful :-).

[harrydb (harrydeboer)]

but unfortunately it does not work. I tried the package on a cx700 and it gives a maximum resolution of 1920x1200 while my monitor (LCD on the DVI port) can handle only 1280x1024.

Btw I am also using VBEModes True because my panel otherwise does not work, however it does give some scrambled/scrolling output now without VBEModes (did not try with the standard package). In the past there was no output at all.

There are some other bugs which I should open new bugs for: VTs are garbage (both packages) and Xorg restarts when locking the screen (not sure that one is openchrome).

Harry

[Paul Sinnett (paul-sinnett)]

I'm having similar problems with an Acer 1362LC. Hardy incorrectly guessed the screen size after install and I had to modify it manually. With Intrepid RC I get a lock up after install. The only way in for me now is to modify xorg.conf to use Driver "vesa".

@raphael, I tried your updated driver, still locks up for me. I managed to get an xorg log...

[Johan Walles (walles)]

harrdydb, can you provide a copy of /var/log/Xorg.0.log after X fails to configure properly? Without a log file it's impossible to say what's going on for you.

Paul, please file a new bug about your crash. AFAICT it doesn't seem related to screen size detection (which this bug is about).

Regarding resizing, quoting your Xorg.0.log:
(--) CHROME(0): Chipset: K8M800/K8N800
[...]
(WW) CHROME(0): Panel on K8M800, PM800 and VM800 is currently not supported.

So your card still seems to be unsupported by the size-detection updates.

For reference, the panel-unsupported line used to read:
(WW) CHROME(0): Panel on K8M800, PM800, VM800, P4M890, K8M890, CX700 or P4M900 is currently not supported.

In my case the laptop has a P4M900/VN896/CN896 chipset, so I might still be lucky :-).

[Rafał Próchniak (burlap)]

I've tried the packages from https://launchpad.net/~atomo64/+archive, but X did not start until I put XaaNoImageWriteRect and "Display" subsection with some modes into xorg.conf. It's a VIA P4M900 (Chrome 9 HC).

I'm on a clean Ibex (installed from the RC alternate cd and updated as of October 25th).

[Paul Sinnett (paul-sinnett)]

Okay, found screen lock up bug #274340. XaaNoImageWriteRect in display section fixes that problem for my laptop.

I still get incorrect screen size detection as expected. And Raphael's patch doesn't correct the problem for me as mine is K8M800.

[Johan Walles (walles)]

Rafał, can you post your /var/log/Xorg.0.log from a startup where screen resolution detection fails?

[Rafał Próchniak (burlap)]

Running with XaaNoImageWriteRect and svn599 packages I get correct resolution only after system startup. If I log out, resolution is broken.

And this is what I found, when I restarted X (X started with wrong resolution):
Oct 27 08:25:40 2133 kernel: [ 340.356792] Xorg[5166]: segfault at 0 ip 00000000 sp bfbca17c error 4 in Xorg[8048000+18f000]

I put some more comments and Xorg logs in bug #273775.

[Paul Sinnett (paul-sinnett)]

I did some debugging on this yesterday. It appears that when the panel is not supported it uses the function VBEValidateModes to choose the resolution and virtual resolution. If you haven't any virtual sizes in your xorg.conf file then the modeNames variable points to an empty string. That causes the "Unable to estimate virtual size" message. That code is inside xserver-xorg itself rather than this driver. But I don't think it's a bug there (although I couldn't find any documentation of VBEValidateModes.)

[ktuomain (kari-tuomainen)]

I tried the openchrome package at https://launchpad.net/~atomo64/+archive and it seems to fix the resolution problem with my HP 2133 when using the openchrome driver on Ubuntu 8.10. I also had to add the following lines to to the device section on /etc/X11/xorg.conf:

Option "XaaNoImageWriteRect"
Option "SWCursor" "true"

[Raphael Geissert (atomo64)]

Updated package which is said to fix the bug is to be uploaded soon

[NomAAd (nomaad)]

I would like to confirm, that with a fresh installation of Hardy (without update) the following workaround gave satisfactory results.

By modifying /etc/X11/xorg.conf with the following:

Section "Device"
        Identifier "Configured Video Device"
        Driver "openchrome"
 Option "XaaNoImageWriteRect"
 Option "SWCursor" "true"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
        DefaultDepth 24
        SubSection "Display"
                Modes "1280x800"
  Virtual 1280 800
        EndSubSection
EndSection

[pvincent (pvincent974)]

With a fresh install of intrepid (8.10), your workaround works like a charm.
thank you

[Yannis Tsop (ogiannhs)]

I have the same problem here. I tried to force 1440x900 but no luck :(. I have removed the original monitor (it was broken) and I have tried with 2 different monitors and I get a 1900x1200 (or so). I attach my xorg log

[NomAAd (nomaad)]

Please attach your xorg.conf too!

[Yannis Tsop (ogiannhs)]

The default is:

Section "Device"
        Identifier "Configured Video Device"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
EndSection

I have also tried this one:

Section "Device"
        Identifier "Configured Video Device"
EndSection

Section "Monitor"
        Identifier "My Monitor"
        Modeline "1440x900" 103.97 1440 1496 1624 1856 900 900 902 933
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "My Monitor"
        Device "Configured Video Device"
        DefaultDepth 24
        SubSection "Display"
                Viewport 0 0
                Depth 24
                Modes "1440x900"
        EndSubSection
EndSection

[NomAAd (nomaad)]

Please try it again by adding
Virtual 1440 900
to SubSection "Display"!

[Yannis Tsop (ogiannhs)]

I removed (i think it is not needed):
        Modeline "1440x900" 103.97 1440 1496 1624 1856 900 900 902 933

I added:
                Virtual 1440 900

but I cannot see what happens (I am using ssh), I'll see at Monday.

I would like to ask is there a way to see the resolution of the xserver (from the command line)?
I see in the log file (both with the new and the old configuration) that although the mode 1440x900 is found to be supported by the monitor but the driver reports:
(II) CHROME(0): Not using mode "1440x900" (no mode of this name) [line 1727]

issuing:
grep "Mode:" Xorg.0.log
you can see it is not listed!

[Sebastian Urban (surban)]

I can confirm that this bug is NOT fixed in the latest Jaunty version.

[Yannis Tsop (ogiannhs)]

Still not working. Is there anything we can do??

[Yannis Tsop (ogiannhs)]

There are no 16:9 or 16:10 resolutions reported by the driver, so there is no matching with the monitor.

[Bryce Harrington (bryce)]

> Still not working. Is there anything we can do??

Flagging a patch would help. Given that there's 1 days until FinalFreeze, there isn't much time for this being fixed for Jaunty unless a patch already exists.

[Yannis Tsop (ogiannhs)]

http://www.openchrome.org/trac/ticket/156

It is supposed to be in trunk.

[Yannis Tsop (ogiannhs)]

Unfortunately even the last trunk revision (747) does not fix this.

[Bartosz Kosiorek (gang65)]

@ Yannis T.
Please build latest Openchrome according to
https://help.ubuntu.com/community/OpenChrome

and apply patch which I attached
panel_pm800.patch

It is helps you?

[Yannis Tsop (ogiannhs)]

After applying the patch the X did not start (blank screen). I have already attached my xorg log file.

http://www.openchrome.org/trac/attachment/ticket/291/xorg.log-patch

[Bartosz Kosiorek (gang65)]

Hi.
Please apply this patch to the latest openchrome driver.

Is it works for you?
Please attach Xorg.0.log file.

[Yannis Tsop (ogiannhs)]

No luck with this one too :(

Here is my Xorg.log

[Yannis Tsop (ogiannhs)]

I also tried with revision 742 and activated debug messages log: rev742-dbg-patch2-Xorg.log

[Yannis Tsop (ogiannhs)]

I tried with revision 750 and activated debug messages log: rev750-dbg-patch2-Xorg.log

[Lesseps (fernando-famo)]

Same problem in Xubuntu Jaunty (9.04) installed in VMWare Player 2.5.2 build-156735. First, the problem is described, second, the solution based on this page.

1. PROBLEM

It seems that screen resolution and other "hardware" configurations, such as Caps Lock "On" are not saved when closing session. I installed several times, even tried first installing Ubuntu and adding Xubuntu through synaptics. Also, after installed in Xubuntu, Gnome session configurations are saved, but choosing back Xfce the problem is still there.

Runs correctly if installed in Sun VirtualBox 2.2.4 r47978.

Ubuntu, OpenSuse, Windows XP, Mint, all run properly, in VMW Player.

Back to Xubuntu in VMWP, a line of Xorg.0.log was "Unable to estimate virtual size" as appears also in Bug #194783 (comment there by David Mills on 2008-02-23).

2. SOLUTION

Screen problem solved using comment by Tomasz Dominikowski on 2008-02-17. the only change was higher mode to 1152x864, instead of 1280x1024:

Section "Monitor"
 Identifier "Configured Monitor"
 Option "DPMS"
 HorizSync 30.0 - 80.0
 VertRefresh 56.0 - 75.0

EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
        Modes "1152x864" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

[Lesseps (fernando-famo)]

Forgot to say: without the Section "Monitor", did not work, I tried before, the other day.

[Sebastian Urban (surban)]

For your information:

This bug is NOT present in OpenSolaris 2009.06. Xorg.log is attached.

Maybe this helps. Can you provide us with a live CD for testing? I do not wish to break my X configuration.

[Johan Walles (walles)]

Works for me in Karmic alpha 2.

[harrydb (harrydeboer)]

For me too (cx700), although the VT's don't work now, I'l open another bug for that later (if there isn't already one)

[Bartosz Kosiorek (gang65)]

This bug was fixed in Karmic alpha 2.

[Tim Webster (tdwebste)]

Not fixed with Posh Book P10

The openchrome driver loads without problem, but will not
use 1024x600 which is the ownly display mode know to supported
by the posh book P10.

  (II) CHROME(0): Not using mode "1024x600" (no mode of this name)

The selected mode is not supported by the posh book P10 lcd monitor.
 (II) CHROME(0): Name: 800x600
  (II) CHROME(0): Clock: 40000

Also, but not critical
  (EE) CHROME(0): [dri] VIADRIScreenInit failed -- version mismatch.
  [dri] libdri is 5.0.0, but 5.4.x is needed.
  [dri] Disabling DRI.

--------------------------------------
VESA supports mode 1024x600

(--) VESA(0): Virtual size is 1024x600 (pitch 1024)
(**) VESA(0): *Built-in mode "1024x600"

 (II) VESA(0): Setting up VESA Mode 0x203 (1024x600)

#####xorg.conf
Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "Device"
 Identifier "Configured Video Device"
# Driver "vesa"
# Driver "openchrome"
    Option "PanelSize" "1024x600"
 Option "sw_cursor"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
 # Option "PreferredMode" "1024x600"
 # Option "DPMS"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
    Subsection "Display"
        Depth 24 # Depth 16 broke
        Modes "1024x600"
    EndSubsection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Synaptics Touchpad"

[Bartosz Kosiorek (gang65)]

Hi Tim.
Please raport a new bug.

Attach your /var/log/Xorg.0.log file.

Try build/install the latest openchrome driver and enable debug mode.
The detail build instruction for Ubuntu/Debian is available at:
https://help.ubuntu.com/community/OpenChrome