[Openchrome-users] X fails with Openchrome: Unknown Card-Ids...

[Kevin Brace]

Hi Kaveh,

I am the developer who got rid of what I coined, "known device table."

https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=9822064f0cf2675fbaa1390b86a83e5bdd61fbf2

It was removed prior to Version 0.4.0 release (it should have been called Version 0.4) by me.
Everything has moved to automatic detection of display hardware, so there is no need for this impossible to manage table.
    Regarding DVI related issues, you will need to see if Igel's VX900 chipset thin client's DVI is getting at least one of the DVI from Silicon Image SiI 164 or VIA Technologies VT1632A external DVI transmitter.
You will have to open the box to check this.
The primary DVI is likely to be DVI-I.
Regarding the secondary DVI (likely DVI-D), it appears that this DVI's hardware registers are connected to VX900's undocumented HDMI transmitter, not CX700 / VX700 chipset's fairly straight forward integrated TMDS transmitter that shares the pins with their integrated LVDS transmitter.
To support VX900 chipset's DVI, I will likely have to backport drm-openchrome's (the next generation OpenChrome DRM with DRI2 / KMS support) HDMI code to OpenChrome DDX.
That will likely happen around OpenChrome DDX Version 0.7 or 0.8.
If you see SiI 164 or VT1632A inside the box, then DVI-I (a DVI connector you can hook up DVI to VGA converter to pass through analog signals) should work since several users have reported HP T5550 / T510's DVI-I to work. (either DVI or VGA, but not simultaneously)
While OpenChrome DDX Version 0.6 is still not out yet, you can use the latest development code currently at Version 0.5.175.
    Another thing is, if you are using Linux kernel 4.5 or later, you will need to blacklist vesafb or OpenChrome DDX will fail to initialize.

https://bugzilla.kernel.org/show_bug.cgi?id=120281


Regards,

Kevin Brace
The OpenChrome Project maintainer / developer


> Date: Thu, 10 Nov 2016 15:22:58 +0100
> From: Kaveh Hoodeh <khoodeh at gmail.com>
> To: Xavier Bachelot <xavier at bachelot.org>,
> 	openchrome-users at lists.freedesktop.org
> Subject: Re: [Openchrome-users] X fails with Openchrome: Unknown
> 	Card-Ids...
> 
> Hi,
> 
> I filed a bug report regarding a missing card ID for VX900 for over 2
> years ago.. downloaded the driver today (source from git) and the ID
> is still missing!?
> The manufacturer is Igel Technoligies, and the device is an Igel UD5
> Thin Client, any chance we can get this ID in the source for further
> releases?
> See old mail conversations below for more info.
> 
> Regrds, Kaveh
> 
> 
> 
> 2014-10-15 12:34 GMT+02:00 Kaveh Hoodeh <khoodeh at gmail.com>:
> > Hi again,
> >
> > This is where im standing now, I have recompiled the driver with the
> > following line added via_id.c:
> > {"Igel UD5 Series",                           VIA_VX900,   0x101B, 0x1305,
> > VIA_DEVICE_CRT},
> >
> > Im getting a bit further with the start of X.. actually it starts now
> > compared to before when it just died with errors, however, im still not
> > getting any video output!
> >
> > When X starts the screen goes black, and after a few second the monitor goes
> > into power saving mode. ..so far i haven't been able to wake it back up when
> > this happens! Even if i kill X with Ctrl+Alt+Backspace the screen wont turn
> > back on (I have been able to verify that im actually back in the console adn
> > that X is dead since i am able to type commands which will return beeps from
> > the PC-speaker)
> >
> > ..I have included a new Xorg.log from when i run X with the patched
> > openchrome and also my xorg.conf if it might help you to digg further into
> > this issue.
> >
> > Thanks for your input so far, regards
> >
> > /Kaveh
> >
> > 2014-10-14 9:54 GMT+02:00 Kaveh Hoodeh <khoodeh at gmail.com>:
> >>
> >> Hi Xavier,
> >>
> >> The board is from a thin client, an Igel UD5, orginaly designed for
> >> windows 7 embeded.
> >> Here is the datasheet:
> >> https://www.igel.com/fileadmin/user/upload/documents/PDF_files/Datasheets_EN/H710C_IGEL_manual_2011-09-28_01.pdf
> >>
> >> I have the screen connected on the DVI, and have also therefor the option
> >> "ActiveDevice" set to "DFP" in xorg.conf.
> >>
> >> I will try the included patch later and get back to you.
> >>
> >> Regards,
> >> Kaveh
> >>
> >>
> >> 2014-10-14 9:34 GMT+02:00 Xavier Bachelot <xavier at bachelot.org>:
> >>>
> >>> On 12/10/2014 14:38, Kaveh Hoodeh wrote:
> >>>>
> >>>> Hi Guys,
> >>>>
> >>>> I cant get my graphics to work with the openchrome driver even though im
> >>>> using a VX900.. see attached Xorg.log
> >>>>
> >>>> I will be very grateful for any suggestions that might solve this issue
> >>>> for me. =)
> >>>>
> >>>> Thanks & cheers,
> >>>>
> >>>> /Kaveh
> >>>>
> >>> Hi Kaveh,
> >>>
> >>> What is the board's manufacturer and model ?
> >>> What are the available outputs (VGA, DVI, etc...) ?
> >>>
> >>> Please try the attached patch, it may help with your issue, but I'll need
> >>> the answers to the questions above before pushing it.
> >>>
> >>> Regards,
> >>> Xavier
> >>>
> >>>
> >>
> >
> 
>