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

Hi Christopher,

> I'm confused. There is no need for a network stack with the instructions I
> supplied, only a USB drive or two. The term you are looking for is
> "sneakernet" ;)
> 
> Puppy at the command line is very limited, as it's primarily a graphical
> operating system. Given that, and that the way Puppy works 'under the hood'
> is very different (or so I'm told) from most Linuxes -- yes, it can be
> confusing.
> 
> Very well. I will pay the $20 for another WYSE client, to verify whether or
> not the original complaint (which was on TahrPup 6.0.2 and X-Tahr 1b2... 1b3
> had not yet been released) has been filled.
> 
> While that forces me to put off for next month, another project I had wanted
> to accomplish, it's not a big deal.
> 
> I'll keep you posted.

Please understand that I do not like using Puppy Linux at all.
It is a huge pain to use it in the first place, and from now on, I will not
spend time trying to figure out how to operate it in the first place.
I will keep a copy of Puppy Linux 5.7.1 (precise puppy) for testing purposes
only, just to test VGA coming from DVI to VGA adapter and straight DVI sometime
in the future when I fix the code.
If the network stack of Puppy Linux 6.0.x worked, I probably should have tried
it a little more, but I am giving up on it.
    Very late last night, I managed to figure out how to build OpenChrome on
Xubuntu 14.04.4 LTS.
Due to a bug in their packager, building the dependency should have ripped the
OS apart if I done it normally, but this time, I managed to workaround the
problem.
I compiled OpenChrome Version 0.4.0 against it, and confirmed that the code
works with X Server 1.15.
The chipset I tested was CN896 chipset.
Hence, I now have confirmation that OpenChrome Version 0.4.0 works with Trusty
Tahr based OS (Ubuntu 14.04 LTS).
    Christopher, at this point, I will have to say that there is something
going wrong within your environment, and I am not really interested in trying
to figure out what that is since I have other bug fix projects I also need to
work on (There are other bugs other users want to see repaired.)
I have spent enormous amount of time trying to fix your bug since November
2015, I do not really want to be blamed for not coming up with a solution since
the bug you reported is related to the lack of probing I2C bus 2, and this bug
was already fixed last month.
Furthermore, in the future, please upload the Xorg.0.log every time you do a
new testing rather than just saying that stuff did not work.
Without Xorg.0.log, I have no visibility into what is going on.
You also need to really ensure that openchrome_drv.so located at
/usr/lib/xorg/modules/drivers is really the latest one (i.e., compare it
against timestamp).
I will not fix any issues anything older than Version 0.4.0 from now on.
For any testing, please use Version 0.4.0 from now on.
    If compiling OpenChrome is such a problem, please ask the Puppy Linux
developers to do it, and create a new image of with OpenChrome Version 0.4.0.
Eventually, this problem will solve itself (hopefully) since some Linux
distributions started to switch to OpenChrome Version 0.4.0.
Arch Linux has already put the code into their testing repository, and
hopefully other distributions will do so in the near future.
In the case of Canonical, Ubuntu 16.04.1 LTS will probably get OpenChrome
Version 0.4.0 (but not 16.04 LTS), so if a future version of Puppy Linux is
built from 16.04.1 LTS, you will see a fix (at least for VGA from a DVI to VGA
adapter).

-- 
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/20160405/6ad7b0f7/attachment.html>