[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 #45 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to Christopher from comment #31)

Hi Christopher,

> Compilation failed with both intermediate versions. 'make' couldn't find
> xf86.h and threw itself off a bridge in both cases.
> 
> Commands were --
> 
> # ./configure --prefix=/usr
> # make
> 
> -- and would have included --
> 
> # make install
> 
> -- if I'd gotten that far.


At this point, I am not an official maintainer or developer of OpenChrome, but
between June to early September 2015, I have worked on trying to fix a bug that
causes LCD screen to get lost when the computer resumes from ACPI S3 State
(Suspend to RAM or STR).
So far, I was not successful in fixing this bug, but in the process, I did
learn something about OpenChrome device driver.
In my opinion, many portions of the UMS (User Mode Set) display management code
paths are broken.
This is ultimately the root cause of why things are not working out on your
end.
    I do own one laptop with VN896 chipset (MSI VR321 laptop I am now typing
this posting from.) and the OpenChrome I obtained from freedesktop.org
anonymous Git repository works fine except ACPI S3 State resume.
I also own VX800 chipset-based mainboard from VIA Embedded, but it is in
storage right now (I can get it ready if I have to.).
I do not currently own VX855 or VX875 chipset-based mainboard, so I am not able
to do the precise testing on that mainboard, but I can definitely report that
OpenChrome 0.3.3 works fine with VX800 integrated graphics except ACPI S3 State
resume.
Anyway, here is the very detailed instructions on how to compile and install
OpenChrome compiled from the source code.

http://www.freedesktop.org/wiki/Openchrome/Installation/

The only thing to watch out is to actually make a backup of the original
OpenChrome compiled device driver files just in case you need to restore it.
Other than that, if you follow the instructions, the compiled device driver
code should get installed without too many issues.
If you want me to, I can start looking into the VX855 / VX875 UMS display
management code path to see what the device driver is doing.
Let me know what you will like me to work on (Other than a vague demand like
"fix my problem right now!").

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/20151101/ff56605e/attachment.html>