[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 #15 from Dariusz Gadomski <dariusz.gadomski at canonical.com> ---
Hey Kevin

(In reply to Kevin Brace from comment #6)
> Thank you very much for getting back with me.
> Please ignore the unknown device message you see in Xorg.0.log.
> This occurs due to the use of a weird known device table inside OpenChrome.

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?


> Looking at the link you provided, I feel like updating OpenChrome Version
> 0.3.3 is quite warranted based on the following clauses I saw in the link
> you provided.
> (...)
> Anyway, since the bug is a fatal one, and a severe regression from Version
> 0.2.904, is there a way the newer version can be treated as a security fix
> update so that Canonical can replace OpenChrome Version 0.3.3?
> Also, can OpenChrome Version 0.3.4 go into Ubuntu 16.04.1 LTS if not Ubuntu
> 16.04 LTS?

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

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

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.

-- 
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/20160302/2222a07b/attachment.html>