[Openchrome-devel] [Bug 94210] Unknown Card-Ids (7122|1458|D000), Chipset: VX900

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=94210

--- Comment #17 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to Dariusz Gadomski from comment #15)

Hi Dariusz,


> Hey Kevin
> 
> Ok, so if the unknown Card-id is not the problem do you see anything
> suspicious there that could be the reason of a blank display currently?
> After switching the display driver to VESA X starts up the given app
> correctly, while using OpenChrome it stops at a blank display.
> 
> The only suspicious lines I could spot there are:
> (EE) CHROME(0): [drm] Failed to open DRM device for pci:0000:00:01.0: No
> such file or directory
> (...)
> (EE) AIGLX: reverting to software rendering
> 
> but I guess in that case it should just work without hardware rendering. Do
> you think anything else that could cause that behaviour?
> 
> 

I am a little getting lost.
Are you saying that the current master branch OpenChrome code produces a blank
screen after OS boots?
One known configuration that causes this is if you use DVI to VGA adapter.
Another configuration is if you use VX900 chipset (or possibly CX700, VX700,
VX800, or VX855 chipset) where VGA is not available, device is detected via
weird known device table, and LCD enable option is not listed in the weird
known device table.
If you can clarify your particular system configuration, that will be
appreciated.


> It's totally doable for 16.04.1 once the release is ready - I will provide
> any help necessary in that area.
> 

Okay, that is fair.
People who install Ubuntu 16.04 LTS will eventually update system via patches,
so they will eventually get the fix via Update Manager.


> Regarding 14.04: I will be more than happy to help you with backporting the
> fix and releasing it on top of 0.3.3 - as this is what the SRU allows.
> 
> Was this the fix you had in mind for this issue?
> https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/
> ?id=ecb1695ac2de1d840c036f64b5b71602e0f522a4
> 

You are probably right that the particular commit fixes the bug.
That being said, this happened way before I assumed the project maintainer
role, so there is no incentive for me to figure this out.


> Once we agree on which changes are needed to backport I can start with the
> paperwork.
> 
> However, I doubt that the Ubuntu Security Team would agree to introduce a
> whole new release of the driver to a stable release as a security update.
> There are some rigid requirements for this:
> https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures
> 
> Nonetheless I can provide any help necessary to fix the already-released
> 0.3.3.

I do understand that Canonical people do not want to tinker with the code, and
"think" that the current code is stable.
It is not.
Between Version 0.2.904 (used by Ubuntu 10.04 LTS and 12.04 LTS) and Version
0.3.3, the previous developer broke VGA detection code if DVI to VGA adapter is
used.
This is a fatal regression.
One of the reason why I am holding up Version 0.3.4 release is due to this.
The major difference between Version 0.2.x and Version 0.3.x is the OpenChrome
DDX support for KMS.
However, the DRM module that supports KMS has not been mainlined, and the
instructions on building was not sufficient for me to build it for now.

https://www.freedesktop.org/wiki/Openchrome/TtmGemKms/

Other than that, there is little difference in terms of feature support.
As far as I know, the compilation infrastructure used to compile OpenChrome has
not changed, so OpenChrome Version 0.3.4 should completely replace OpenChrome
Version 0.2.904 assuming that I can figure out the DVI to VGA adapter VGA
detection issue.
At the very least, Version 0.3.3 should be replaced with Version 0.3.4 as soon
as possible since Version 0.3.4 is merely a bug fix released compared to
Version 0.3.3.

-- 
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/20160304/9f33c2aa/attachment.html>