Bug 18466

Created attachment 20189 [details]
Xorg-modedebug=on.0.log

Xorg.0.log from Ubuntu system with driver 2.3.1 and modedebug=on

Created attachment 20190 [details]
Xorg.conf

Created attachment 20191 [details]
Xorg.conf

So what's the sympton? And you forgot to attach xrandr output.

The git driver version should be 2.5.x.

Regarding the git source, my tree is old and I cannot get anything 2.4.0 or newer to compile on my system without upgrading DRM also.

I will attach the missing xrandr -q output.

The symptom is that no picture is ever displayed on the second monitor.  The output of VGA is present, the output of VGA-1 not so.

Created attachment 20243 [details]
latest xorg.conf

Created attachment 20244 [details]
output of xrandr -q --verbose

Created attachment 20246 [details]
Xorg.0.log with modedebug=on

Some additional notes:

BIOS (Award) is configured for CRT+CRT video at boot and 2nd screen shows picture at boot and when at Linux console (and always under Windows with Intel driver).

I don't know if there's some confusion with the SDVO-DVI chip (Silicon Image Sil1362CLU) on the same SDVO channel as the SDVO-VGA chip (Chrontel CH7021A-TEF).

If the DVI output (TMDS-1) is enabled then the monitor gets synch but still not picture is displayed.  I will check a full SDVO-DVI configuration just to double check that works but SDVO-VGA is what I need to get working for my paying customer.

I have observed that if I start the computer up with a monitor connected only to the SDVO-VGA connector then the picture appears correctly on that output appears correctly.  It seems that on-board VGA alone or SDVO-VGA alone do work but both together does not work.

Have you tried more recent drivers? How about removing "TMDS-1" ignore option first?

(In reply to comment #5)
> Regarding the git source, my tree is old and I cannot get anything 2.4.0 or
> newer to compile on my system without upgrading DRM also.
> 
> I will attach the missing xrandr -q output.
> 
> The symptom is that no picture is ever displayed on the second monitor.  The
> output of VGA is present, the output of VGA-1 not so.
> 

Aidan, 2.3.1 is too old for us to fix this bug. we do need your help to provide us latest status when using latest release or git repository. One hint is to use the latest LiveCD from various distributions. If you have a chance to try, please upload your xorg.log with modedebug turns on.. thanks.

Aidan, could you give some info on your hardware? Looks there're two SDVO encoders on your board?

In reply to comment #13:

| Aidan, could you give some info on your hardware? Looks there're two SDVO
| encoders on your board?

Correct.  The board is our custom DPX-117 which we sell to the casino gaming industry.  We use a mobile 945-based chipset.  We offer a range of video options.  Normally just on-board VGA as standard but there's a MXM/PEG slot that can take either ATI/Nvidia's MXM-format GPUs or an Intel SDVO-based solution.  The SDVO solution is what's the problem here: the card is both a SDVO-DVI chip (Silicon Image Sil1362CLU) on the same SDVO channel as the SDVO-VGA chip (Chrontel CH7021A-TEF).  This allows us to offer VGA+VGA or VGA+DVI.

(In reply to comment #14)
> In reply to comment #13:
> | Aidan, could you give some info on your hardware? Looks there're two SDVO
> | encoders on your board?
> Correct.  The board is our custom DPX-117 which we sell to the casino gaming
> industry.  We use a mobile 945-based chipset.  We offer a range of video
> options.  Normally just on-board VGA as standard but there's a MXM/PEG slot
> that can take either ATI/Nvidia's MXM-format GPUs or an Intel SDVO-based
> solution.  The SDVO solution is what's the problem here: the card is both a
> SDVO-DVI chip (Silicon Image Sil1362CLU) on the same SDVO channel as the
> SDVO-VGA chip (Chrontel CH7021A-TEF).  This allows us to offer VGA+VGA or
> VGA+DVI.

Thanks for your info, but I strongly suggest you use the latest version because we have appended new features and logs, which can accelerate our modification.

Thanks
Ma Ling

hi Aidan,

I find the sdvo-vga is not attached succesfully. by using latest version, could you paste log when it works fine --Comment #10.

Thanks
Ma Ling

ping Aidan ~

My apologies for delays replying.   I have been on vacation for a while and the equipment required to test the latest drivers will have to be reclaimed.  I have not stopped working on this however.

(In reply to comment #18)
> My apologies for delays replying.   I have been on vacation for a while and the
> equipment required to test the latest drivers will have to be reclaimed.  I
> have not stopped working on this however.

hi Aidan

If everying is ready, Please let me know .

Thanks
Ma Ling

ping Aidan Dixon ....

I have the equipment in place now.  I have driver 2.5 ready too.  Just need to update kernel DRM2 driver.

hi Aidan Dixon

from dump register in xorg log:
 
(II) intel(0):                SDVOB: 0x80480084 (enabled, pipe A, stall disabled, detected)
(II) intel(0):                SDVOC: 0xc0480080 (enabled, pipe B, stall disabled, not detected)
(II) intel(0):              SDVOUDI: 0x00000000
(II) intel(0):               DSPARB: 0x00001d9c
(II) intel(0):               DSPFW1: 0x00000000
(II) intel(0):               DSPFW2: 0x00000000
(II) intel(0):               DSPFW3: 0x00000000
(II) intel(0):                 ADPA: 0x80000010 (enabled, pipe A, -hsync, +vsync)

There should be a conflict between VGA and SDVO-VGA.

So after you update driver, start Xorg, then paste Xorg log file again.


Thanks 
Ma Ling

ping Aidan Dixon ....

Thanks
Ma Ling

ping... please attach a log of 2.5 or 2.6 driver, with modedebug=on.

(In reply to comment #10)
> I have observed that if I start the computer up with a monitor connected only
> to the SDVO-VGA connector then the picture appears correctly on that output
> appears correctly.  It seems that on-board VGA alone or SDVO-VGA alone do work
> but both together does not work.
> 

please also either attach a reg_dump or xorg log with modedebug turns on of this senario... thanks.

Hi Michael (and Team)

I have been unable to work on this bug due to illness.  I do not know when I will be able to continue working.  You may close the bug if you feel that necessary.  

Kind Regards,
Aidan

hi  Aidan 
we are sorry to hear that, hope you get better soon!
I close the issue now. If it still occurs after using our latest version, please reopen it.

Best Regards!
Ma Ling