[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 #277 from Kevin Brace <kevinbrace at gmx.com> ---
Hi Christopher,

Okay, I figured out (at least for me) a satisfactory way to test OpenChrome on
Wyse C00X with Puppy Linux.
I am using Precise Puppy 5.7.1 for testing purposes, and I have been pretty
frustrated not being able to use Git on my Precise Puppy despite having already
installed it on that system (in a USB flash storage device).
This is how I did it.

1. Build OpenChrome on the regular development system with debug messages
activated (normal operating procedure)

2. Copy openchrome_drv.so located in /usr/lib/xorg/modules/drivers to a USB
flash storage device

3. Copy libchromeXvMC.so.1.0.0 and libchromeXvMCPro.so.1.0.0 located in
/usr/lib to a USB flash storage device

4. Boot Puppy Linux

5. Set Puppy Linux up to save the session when it shuts down (important)

6. Copy openchrome_drv.so in a USB flash storage device to an active Puppy
Linux session's /usr/lib/xorg/modules/drivers

7. Copy libchromeXvMC.so.1.0.0 and libchromeXvMCPro.so.libchromeXvMC.so.1.0.0
and libchromeXvMCPro.so.1.0.01.0.0 located in a USB flash storage device to an
active Puppy Linux session's /usr/lib

8. Shut down the Puppy Linux session (the RAM disk's content should
automatically be save to the attached USB flash storage device)

9. Boot Puppy Linux

Optionally, the Puppy Linux's original openchrome_drv.so,
libchromeXvMC.so.1.0.0, and libchromeXvMCPro.so.1.0.0 can be saved, but it is
not absolutely necessary.
One important thing to note is that the OS used to build OpenChrome should be
similar to the version of Puppy Linux used.
For Precise Puppy, I used Lubuntu 12.04 i386.
I have not tested Tahrpup due to the fact that I currently do not have an
active development environment comparable to Ubuntu 14.04.
    Based on my own testing this is what happened.
Regarding Wyse C00X, VGA is now working.
Obviously, I used a DVI to VGA adapter for this.
Indeed, the lack of the use of I2C bus 2 for VGA monitor detection was the
culprit of this bug you reported.
That being said, DVI is still not working.
I have been making substantial changes to OpenChrome code base (i.e., removal
of the large known device table and VESA BIOS Extension based display mode
setting support), and unfortunately, the code stability is very fluid at this
point.
Obviously, it is my policy not to do a commit that will break the code, and at
least with my own test environment, the code happened to be working.
However, several other people have reported regression of the code,  
I am in the process of fixing the code, although this is somewhat stalled at
this point since I am trying to integrate newer save / restore code hoping to
fix long standing standby mode resume bugs.
The code for this was written last year, and I was looking for a chance for
integration at some point.
Personally, I had to get rid of "rot" in the code (i.e., the large known device
table and VESA BIOS Extension based display mode setting support) since the
display resource detection code was doing lots of strange things.
I have some good ideas on how to improve the display detection moving forward.
    Christopher, regarding the instability you have reported, I strongly
suspect the SD card reader you are using is the culprit, not the current
OpenChrome code base.
As for myself, I used a large enough (i.e., 4 GB or larger) USB 2.0 flash
storage device instead of an SD card.
I often get them at an electronics related trade shows for free, so I decided
to use one since I already have more than enough such devices at my place.
Anyway, this is the best USB flash storage device Puppy Linux installation
instructions I have found on the Internet.

http://www.murga-linux.com/puppy/viewtopic.php?t=54566

    I do not plan to close this bug any time soon since DVI related bugs
remain, but at least for the moment, the current OpenChrome code's display
detection capability is comparable to OpenChrome Version 0.2.904 (i.e., in the
box device driver for Precise Puppy).
The DVI coming from an external transmitter chip (VT1632A) is still broken, and
I plan to fix this in the very near future.

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