Bug 70708

Summary:	Total freeze before loading X
Product:	xorg	Reporter:	Lucas Ribeiro <lucasout>
Component:	Driver/openchrome	Assignee:	Openchrome development list <openchrome-devel>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	medium	CC:	kevinbrace, lucasout, xavier
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Lucas Ribeiro 2013-10-21 01:04:58 UTC

Motherboard: A8V-MX
NorthBridge: K8M800

Tested on Fedora 19 x86_64. As soon as the system starts gdm, it hangs. What is troublesome is that no Xorg log is generated, so I assume the freeze happens when the module is loaded. Tried to do a 'modprobe openchrome', but the module was not found?

I tried with the openchrome version shipped with fedora 19, the 0.3.3 tag and the git head. They all freeze.

It works fine with VESA mode and on WinXP, though. Tried to mess with some BIOS options, but no results. Also, tried some options on xorg.conf but they all produced no results:

Option "XaaNoImageWriteRect"
Option     "EnableAGPDMA"               "false"

Again, I think the problem is before Xorg even starts.

Comment 1 Xavier Bachelot 2013-10-21 07:47:23 UTC

There is no kernel module named "openchrome", the DRM driver for VIA hardware is named "via".

Can you try to disable hardware acceleration ?
Option "NoAccel"

Comment 2 Lucas Ribeiro 2013-10-21 10:24:52 UTC

Will do, in 2 weeks when I have access to the system again. Thanks for the quick reply.

Comment 3 Lucas Ribeiro 2013-11-02 20:17:44 UTC

I tried disabling HW acceleration with the option "NoAccel", but had the same result: freeze before X loads.

I've also tried the following options:

Option "ActiveDevice" "CRT"
Option "DisableIRQ" "true"
Option "EnableAGPDMA" "false"
Option "NoAGPFor2D" "true"
Option "PanelSize" "1280x1024"
Option "SWCursor" "true"
Option "VBEModes" "true"


I'm willing to debug if you instruct me.

Comment 4 Lucas Ribeiro 2013-11-03 00:12:46 UTC

Just did a test with fedora 19 i686: no dice. Still freezes before X, had to install on vesa mode. The option "NoAccel" did not solve the problem.

Comment 5 Kevin Brace 2017-01-22 19:07:27 UTC

If you still have the hardware and sees the same issue persist with the latest code, let me know.
We no longer support Version 0.3.x code, and if you need support, please try Version 0.5 or later.
You can always test to older code to see if a regression has occurred, but other than that, we only support the latest code.
I will be closing the bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.