[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 #36 from Christopher <laserhawk64 at gmail.com> ---
The logs from the Git master are already attached to this thread. They are
clearly labeled... re-compiling from Git and replacing those logs will provide
no changes, so I will refer you to those that are already attached.

When it fails, it fails exactly the same way every time -- it can't detect or
communicate with the monitor and proceeds to march itself off a cliff instead.

I will get the xorg.conf shortly. I can also provide the script that generates
it -- there are three xorgwizard scripts within Puppy. The one at initial
first-boot is 'xorgwizard-automatic'; there's also 'xorgwizard-cli' (which is
used when manually invoked as 'xorgwizard' from bash) and 'xorgwizard', which
determines whether the automatic or the CLI version is what runs. I will copy
those over in case you want them, so that I won't have to boot the machine more
times than necessary. (There is no CLI networking within Puppy, and so I have
to sneaker-net everything with a USB flash drive.)

I will also download v.0.3.2x of openchrome, as well as re-downloading the
0.2.90x versions that I had previously tried, so that I can try to compile them
again.

I'll do what I can tonight and tomorrow -- but tomorrow evening I have to have
a minor medical procedure (nothing serious, I promise) and I'll be gone after
about 5pm till sometime late Tuesday afternoon, US Eastern time... won't be
able to do anything till I get back, obviously.

-- 
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/20151018/9a8e4986/attachment.html>