Bug 54051

Can you please provide the xorg log with the crash ?
Anyway, I suspect this is already fixed by this commit : http://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=131175a7163a9189d70ed3118b45eaceb27898c0

openchrome 0.3.1 has been released. I believe it should fix this issue. Can you please confirm ?

Hi Xavier,

It looks like ubuntu 12.10 doesn't have the updated version yet.
Should I build the new version from source code or I can wait for ubuntu maintainers to build it? 

Thanks for support,
Sergey

It depends on how fast you want to confirm this is actually fixed or not. I'm not surprised Ubuntu doesn't have an updated package yet, I've uploaded the new release less than 24 hours ago ;-)

If you want to build from source, you might want to look at this : http://www.openchrome.org/trac/wiki/Installation#Installfromareleasetarball

Created attachment 66704 [details]
Xorg log

Hi Xavier,

I've managed to build openchrome 0.3.1 driver and now after X is started the screen gets black and I can't even get console (Ctrl+Alt+F1). I've checked Xorg.0.log(attached) but couldn't find any error message. Could it be something special with my system using VBE mode ?

Thanks,
Sergey

Created attachment 66710 [details]
Xorg crashed log with openchrome v0.3.0

Created attachment 66711 [details]
xorg.conf

Try to disable VBE mode, and attach Xorg.0.log from openchrome 0.3.1

Ok, so the 0.3.0 crash is gone and it was the breakage I suspected.
 
Now, let's address the other issue. What is your screen and how is it connected to the board ? Why do you use VBE ? What happens if you remove the X conf, which basically will just not force VBE mode ?

@Bartosz : you were quicker than me ;-) The X log from 0.3.1 with VBE is in comment 5.

Xavier,

I don't actually know how the display is connected. The PC is a monoblock.
Initially it never worked without VBE mode.

Thanks,
Sergey

What is the exact brand and model of the hardware ? Also, if you have a link to the manufacturer website, it could help.

Rather than using VBE, try to force LVDS panel detection with Option "ForcePanel"

Xavier,

PC specs are here http://www.wincomm.com.tw/product/pdf/WLP-6821-15.pdf

Besides VBE in xorg.conf I have modified grub configuration:
GRUB_GFXMODE=1024x768
GRUB_GFXPAYLOAD_LINUX=keep

This was supposed to make smooth handover from plymouth to xorg.

UPD: X now start using "ForcePanel", but Unity is so slow.

Thanks,
Sergey

Great to hear it works. The LVDS detection code is currently not as good as it could be. Please provide the xorg log, I'd like to take a look.

About 3D being slow, that is expected. The unichrome 3D driver has been dropped from Mesa because it is not yet ported to DRI2, so you are running on software rendering over LLVM pipe. Currently, the only way to improve the desktop experience would be to use another desktop manager which is not making such heavy use of 3D.

Created attachment 66763 [details]
Xorg log with ForcePanel=yes

Morning Xavier,

Please find attached Xorg.0.log of a working openbox session with ForcePanel=yes.
OpenBox has no perfomance issues.

I've just updated the pc with apt-get and noticed that xserver-xorg-video-openchrome 0.3.1 was installed. That is pretty fast I guess :).


Thanks,
Sergey

Closing the bug now you're all set.

Thanks,
Xavier