Arch Linux

Any error you can receive? Maybe log into the system via ssh. I've read something about enabling kms with this release.

I restored xf86-video-openchrome-0.3.0-1-i686 and appended nomodeset to my syslinux boot and still had a blank screen. No error messages on the screen. I cannot open another terminal with <ctl><alt><F3>. Other info, I use xdm and feh in openbox and if you think it is worth trying can disable both of these. Nothing in the xdm.log either.

You'd better get in contact with upstream to sort this out.

From [URL]http://cgit.freedesktop.org/openchrome/xf86-video-openchrome/tree/NEWS[/URL]
[Quote]openchrome 0.3.0 (20/07/2012)
-----------------------------

The 0.3.0 release is a major step forward for the openchrome X.org
driver. It brings most of the features that are needed with todays X
server. The code has seen a major overhaul, with a lot of new features
and a lot of cleanup. It has been tested on most of the available VIA
IGPs and we believe there are no regression at this point. However, the
testing was done on a limited range of hardware, so your mileage may
vary. Please let us know if you have any trouble using it.

* New Features :
- TTM/GEM support.
- KMS support.
- Better RandR support.
- XAA removal.
- DGA removal.
- Support for X server 1.13 API.
- Code cleanup and bug fixes.

* Known bugs and limitations :
- Dual screen is not fully working.
- EXA compositing is disabled.
- KMS-enabled DRM module is not in upstream kernel yet.

Starting with the 0.3.0 release, please submit bugs and patches to
freedesktop.org bug tracker.
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/openchrome

The old ticket tracker is kept as a reference only. It is still
available at : http://www.openchrome.org/trac/report/1?asc=1&sort=ticket[/Quote]


Does it matter that the DRM module is not in the upstream kernel yet?

Please do a plain boot with appending "3" if you use initscripts or boot systemd into nongraphical state.

Now check dmesg/everything.log/journal. Then try to get some useful output wiuth starting "startx" and watching Xorg.0.log and ~/.xsession-errors.

Anything else is a wild guess.

The only thing that seems to come up is this glib-critical error in .xsession-errors. The error message does not occur with the older xf86-video-openchrome driver
" (process:770): GLib-CRITICAL **: g_hash_table_foreach: assertion `version == hash_table->version' failed
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 2783 requests (2780 known processed) with 0 events remaining.
XIO: fatal IO error 4 (Interrupted system call) on X server ":0"
after 1566 requests (1566 known processed) with 0 events remaining.
real transparency off.... depth: 24"

You'd better get in touch with upstream. No idea if there's something broken in the code
or if we broke the build by missing some new required (make)dependencies.

The upstream bug site requires an email address. I only have one (I'm a luddite who likes to keep it simple) and they advise using a webmail address like yahoo. I just deleted 3 spams associated with Linkedin so I am loath to register my email address insecurely.

Doesn't this class of error have to do with the gcc version? Is it possible that the Arch version is >> than that the developers use? I assume your build system is current. I will download the source and look to see if there are any configure flags and report back

I also just experienced this bug with an Everex VA250W. Same symptoms. I've yet to really investigate, but I'll try to look into it if get more time.

Use something like mailinator if an email address is required by the bug tracker. If you create the ticket and post the link here I'll try to supply what information I can.

I also had to downgrade because of the above problem.

lspci says this about my card:
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)

LouL (DrZaius) and Steffen Weber (boenki);

It looks like we all have newer Chrome 9 HC cards. I checked and the via drm module is enabled in the Arch Kernel and I tried the new driver with the via.modeset=1 option passed to the kernel at boot with no success.

If either of you have a non-critical email address feel free to submit an upstream bug report.
Perhaps you could link the Arch bug reports. The new openchrome bug report link is here:

https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/openchrome

Same issue here. Downgrade did the trick. On a VIA Technologies, Inc. EPIA-CN

Reported upstream:

Bug 53307 - xf86-video-openchrome 0.3.0 locks system
https://bugs.freedesktop.org/show_bug.cgi?id=53307

CC'ed

Please check 0.3.1 in extra.

With 0.3.1 same error as before: Black screen. I cannot even change to a VT anymore :(

Upstream wants Xorg.0.log (and dmesg) from 0.3.*. Unfortunately this file is not created for me due to the severity of the crash. If anyone else can post the correct log that would be helpful.

@DrZaius

I no longer have Arch on my laptop. Usually the Xorg.0.log maintains the last 2 Xorg.0.logs. So if after the crash, if you reboot in run level 3 (no xorg) you should have the Xorg.0.log waiting for you. You can also generate a dmesg in run level 3. The openchrome group also released a drm-openchrome package about 6 days ago. I think the drm-openchrome is a kernel package so the latest is probably not in the arch kernel you are using. Something else to try would be passing the "via.modeset=1/via.modeset=0" options to the kernel at boot.

0.3.1 appears to provide the same behavior as 0.3.0 for me.

Upstream has closed the bug. Can you please check what commit(s) are needed to apply?

I can confirm this bug is fixed in mainline git.
I am finally running the latest xserver and xf86-video-openchrome(-git) again!
But I don't know what commit is needed to apply. Sorry.

It was 76515c8:
http://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=76515c8a369346d76864e55610a6a747d9b152d8

@LouL (DrZaius) : You're right.
That's the patch that makes it work for me, too.
I made an updated PKGBUILD and will try to attach it