[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91966

--- Comment #155 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to Christopher from comment #154)

Hi Christopher,

> For the sake of completeness -- I've managed to figure out some of the
> potential issues and get rid of them.
> 
> One, bit-depth has been corrected to 16 rather than 24.
> 
> Two, I disabled GLX.
> 
> Results in all cases are the same: a screenful of gunk.

You should continue to use 24 bit or 32 bit color.
I do not use 16 bit color at all, although in theory, it should work.
Furthermore, I am concerned that the OS crashes after loading GLX.

______________________________________________________________________
. . .
[   169.253] (II) Module "extmod" already built-in
[   169.253] (II) LoadModule: "glx"
[   169.260] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
______________________________________________________________________

I feel like there is an issue other than loading GLX.
If possible, it will be preferable if you can use the OS environment virtually
identical to what you had in September 2015.
I am also wondering if you got the pre-patched version OpenChrome from the Git
repository, will the OS get to the previous point of where you were? (i.e.,
Screen was not recognized, but you were able to get access to Xorg.0.log.)
And, after you confirm that it got to that point, if you can install the
patched version OpenChrome then we are now performing "before and after"
analysis.
I appreciate getting the Xorg.0.log though since without it, there is not much
I can do to begin with.

Regards,

Kevin Brace

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openchrome-devel/attachments/20160125/46597e85/attachment.html>