Bug 26797

Created attachment 33637 [details]
boot.msg

I've sent the requested mmio-trace.

Created attachment 33758 [details] [review]
dcb_type_4_hack.patch

Bad news... The TMDS tables in your BIOS are stale and do *not* describe how to set up this external TMDS encoder (instead they describe an integrated encoder that doesn't really exist in your card). 

It could still be that the modesetting process is encoded somewhere else using a different bytecode format but I seriously doubt it, the output from this command might give us a clearer answer:
# ./vbtracetool -l -d -s 317 2>trace.log

You can get vbtracetool here [1]. If you're very lucky the patch I'm attaching will improve things, but probably not: most likely your encoder chip will need its own stand-alone driver.

[1] http://cgit.freedesktop.org/~stuart/vbtracetool/

The patch didn't work. :(

Are you sure the suggested vbtracetool command is right ?
Screen turns black immediately and I get a log of ~2GB !!??

(In reply to comment #4)
> The patch didn't work. :(
> 
> Are you sure the suggested vbtracetool command is right ?
> Screen turns black immediately and I get a log of ~2GB !!??
> 

That's a bit unexpected but possible, any chance I could have a look at e.g. the first 100MB? You could use "dd" to cut it, like:
$ dd if=trace.log of=trace1.log bs=1M count=100

Compression should also make it a good deal smaller.

Created attachment 33788 [details]
First 100MB of the vb-trace

LZMA compresses the whole 2 GB to 14.1 MB (!).
So I could send it, too.

(In reply to comment #7)
> LZMA compresses the whole 2 GB to 14.1 MB (!).
> So I could send it, too.
> 

It would be interesting as well. Thanks.

As attachment or per mail (like the mmiotrace) ?

(In reply to comment #9)
> As attachment or per mail (like the mmiotrace) ?
> 

Per mail, preferably to the mmio.dumps account.

(In reply to comment #7)
> LZMA compresses the whole 2 GB to 14.1 MB (!).
> So I could send it, too.
> 

Thanks, that's been useful, but sadly your BIOS does it with a bunch of ad-hoc x86 code, as in the old days.

The blob used to let out the names of any external encoders when you gave it a high enough verbosity level. They often have register-level specs available so implementing a driver for it would possibly involve little RE-ing, but still a good deal of work.

(In reply to comment #11)
> The blob used to let out the names of any external encoders when you gave it a
> high enough verbosity level. 

Is there a way to increase the verbosity level ?
Anything else I can do ?

(In reply to comment #12)
> (In reply to comment #11)
> > The blob used to let out the names of any external encoders when you gave it a
> > high enough verbosity level. 
> 
> Is there a way to increase the verbosity level ?

I'd try "Xorg -logverbose 8".

> Anything else I can do ?
> 

I'm not sure, making this work will probably involve too much new code to be carried out remotely and not go mad at the same time. :)

(In reply to comment #13)
> > Anything else I can do ?
> 
> I'm not sure, making this work will probably involve too much new code to be
> carried out remotely and not go mad at the same time. :)

Well, I can checkout remote repositories/branches for testing ;)

The sh.. is, that this GPU is blacklisted by the nv-driver (screen corruption), so people are stuck with VESA when the blob is declared as "legacy" one day (soon ?)...

Created attachment 33861 [details]
Xorg.0.log with "-logverbose 8" (Nvida driver 195.36.08)

The TDMS is a

Silicon Image
TMDS PanelLink
Sil1364ACTU
Q6?844.1-1 (? is D/O/0)
0611
AD??KD2 (? is D/O/0)


Can't find a datasheet, maybe you have more luck / better connections ;)

For reference: the MB is a ASUS M2N-VM DH

(In reply to comment #16)
> The TDMS is a
> 
> Silicon Image
> TMDS PanelLink
> Sil1364ACTU
> Q6?844.1-1 (? is D/O/0)
> 0611
> AD??KD2 (? is D/O/0)
> 
> 
> Can't find a datasheet, maybe you have more luck / better connections ;)
> 
> For reference: the MB is a ASUS M2N-VM DH
> 

That's interesting, it's an sDVO TMDS transmitter, the intel driver has code [1] for a similar piece of hardware.

[1] http://cgit.freedesktop.org/nouveau/linux-2.6/tree/drivers/gpu/drm/i915/dvo_sil164.c

According to [1]+[2], sDVO is used by

nForce430 + Geforce 6150SE
nForce430 + Geforce 6100

[1] http://www.nvidia.de/page/legacy_gpu_mobo_tech_specs.html
[2] http://www.nvidia.de/page/gpu_mobo_tech_specs.html

It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team

This bug report still applies to the latest kernel.
A driver for the Sil1364 is missing.

Which kernel is the latest kernel? Could you put up a dmesg from it? Also, could you supply your VBIOS? (/sys/kernel/debug/dri/0/vbios.rom)

(In reply to comment #21)
> Which kernel is the latest kernel?
3.10
I'm on Radeon hardware since then and I can't switch back easily.

> Could you put up a dmesg from it? 
Nothing has changed, DCB type 4 is still unknown.

> Also, could you supply your VBIOS? (/sys/kernel/debug/dri/0/vbios.rom)
Already sent 3 1/2 years ago. See comments #6-11


Please read the the whole bug report.
The reason why the connector doesn't work, is that the DVI connector is realized with a Sil1364 sDVO and there is no driver for it yet.
I don't have access to datasheets of the Sil1364.
If we have a driver for this device one day, I'll be glad to test it.

I did read the whole bug report. What you attached was not the vbios. The vbios should be ~50-60K. There was support added semi-recently for external encoders (in 3.9), but I just checked and it was only on nv50+.

*** Bug 40138 has been marked as a duplicate of this bug. ***

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/6.