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

If you wanted to do a hard reset on the code you previously cloned from the Git
repository, type,

git reset --hard ("Commit ID")

If you wanted to see the the previous commit ID, type,

git log

For example, if you wanted to reset the code to the current head, type,

git reset --hard 47060a3d770b90ed96924b4260dce38bdafedfde

This is the current head (as of January 23rd, 2016).

http://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=47060a3d770b90ed96924b4260dce38bdafedfde

Now, make sure that no other patch files other than the ones I uploaded in the
past few days specifically for you are in the /xf86-video-openchrome directory.
Download those 8 patches (I updated two of them, and added one of them just
now.) to /xf86-video-openchrome.
>From inside /xf86-video-openchrome directory, apply the patches.

patch -p1 < 0001*.patch

If you can, cut and paste the text when you apply the commands (You don't have
to, but the use of cut and paste can reduce errors.) within the terminal.
Now repeat the above command 7 more times with "0001" incremented by 1 at a
time (i.e., 0002, 0003, etc.).
Alternatively, you can hard code the entire *.patch file name like this.

patch -p1 < 0001-Substitution-of-VIA_VM800-label-with-VIA_P4M800PRO-l.patch

If you do this, you need to type in the entire file name 7 more times.
This is why I used a wildcard to make your life easier (I guess it did not work
out too well.).
After you try it, please upload the Xorg.0.log file so that I can take a look
at what happened.
I am cautiously optimistic that the fix will work.
You should use the DVI to VGA dongle rather than direct DVI connection since
the fix I made only deals with VGA.
If straight DVI does not work, we will need to fix that in the near future.
I am hoping this fix will be included in the upcoming OpenChrome Version 0.3.4
release so that you do not have to ever suffer from the same issue in the
future.

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/20160124/bc327fab/attachment.html>