[VM800] Xorg freeze, grey screen, no pointer during X start

[Jovaro]

Binary package hint: xserver-xorg-video-openchrome

When trying to start X using the startx command, a grey screen appears without a pointer or anything. Changing the driver to "vesa" in xorg.conf gives a working X.

The issue started when I updated from 9.10 to 10.04 and only happens on the TV-out. Unfortately I use the pc only for my CRT TV so I really need the TV-out.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
Architecture: i386
Date: Sat Nov 6 20:37:40 2010
DkmsStatus: nvidia-current, 195.36.24, 2.6.32-25-generic, i686: installed
ProcCmdLine: root=UUID=ae2fde25-0b8f-4d28-9b07-574c40fb19a7 ro nosplash video=uvesafb:mode_option=1024x768-24,mtrr=3,scroll=ywrap
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 04/03/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: CN700-8237
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/03/2009:svn:pn:pvr:rvn:rnCN700-8237:rvr:cvn:ct3:cvr:
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-25-generic

[Jovaro (bug-jovaro)]

Both Xorg logs that were automatically attached used the vesa driver. Here is a log when the openchrome driver is used.

[Jovaro (bug-jovaro)]

I just attached a working xorg.conf that I got with some help from penguin42 in #ubuntu-bugs.

So the problem really is that X -configure doesn't give a working xorg.conf

I'll open a new bug for the crash that happens when not using an xorg.conf tomorrow

[Bartosz Kosiorek (gang65)]

I think this bug was resolved in the latest openchrome revision:
http://openchrome.org/trac/changeset/862

Please 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

Is this problem appears also on that openchrome revision?

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.