Bug 24456

Summary: monitor on DVI output "out of range"
Product: xorg Reporter: Oliver Freyd <Oliver.Freyd>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium CC: christopher.m.penalver
Version: 7.3 (2007.09)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf
none
Xorg,0,log
none
The video bios (kt690/mITX board by kontron) none

Description Oliver Freyd 2009-10-11 01:47:49 UTC
Created attachment 30267 [details]
xorg.conf

A 1920x1080 LCD monitor on DVI output is driven
semingly at half dot clock, monitor displays "33 kHz x 30 Hz"
horizontal and vertical frequencies, for a 1920x1080x60Hz mode.

The image is somewhat unsteady, and grayscales look dithered, as if 
it uses less than 8 bits per pixel.

After about one minute, monitor switches off.

This only happens on the DVI output, the VGA is running fine.

Hardware is a Kontron kt690-mITX board, with embedded ATI RS690
graphics. 

I'm running ubuntu jaunty, with xorg-edgers ppa, which be quite update with respect to the radeon driver  	
xserver-xorg-video-ati 1:6.12.99+git20091009.f4407962-0ubuntu0tormod~jaunty. 

I've tried to switch modes with xrandr, works fine on VGA, but 
on DVI the same symptoms persist, even in different resolutions.
Always the monitor complains about frequencies out of range, and vertical
refresh is about 30 Hz.

I'll attach my xorg.conf and the Xorg.0.log.

BTW, the board also has a LVDS connector, which is empty, but Xorg 
wants to drive it at 1280x800, so try to disable that output with an extra
monitor section with the line
Option "Disable" "true"

not sure if that actually works, xrandr reports the LVDS anyway.
Turning it on with xrandr gives an CRTC error though.

If I set 
Option "Ignore" "true"
for the LVDS, xorg fails completely, saying it does not find any screen!

But that is maybe another bug...
Comment 1 Oliver Freyd 2009-10-11 01:49:19 UTC
Created attachment 30268 [details] [review]
Xorg,0,log
Comment 2 Alex Deucher 2009-10-12 08:55:06 UTC
Do any modes other than 1920x1080 work on the DVI port?  Also, do you have a card in the pcie x16 slot assuming the board has one?  If so, can you remove it?
Comment 3 Oliver Freyd 2009-10-12 11:48:51 UTC
It's an onboard graphics card, and the board has a PCIEx8 interface (in a x16 slot), which is empty. The onboard graphics has only DVI-single-link, not dual!

I'tried to add a 1920x1080 mode with reduced blanking, with the cvt program,
and I've also tried other modes, I think down to 1440x900, all with the
same result, running at the half frequency. 

I could try some other monitor the next days...

BTW, some weeks ago I was still running the xorg server and radeon driver from 
jaunty, and the DVI-port didn't work at all. It didn't recognise any monitor.
That seems to be fixed now.

Well, tell me if I should try some patches, or run some diagnostic tool,
I'll try that...
Comment 4 Alex Deucher 2009-10-15 15:20:16 UTC
Can you attach your video bios?

As root:
cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom 
Comment 5 Oliver Freyd 2009-10-16 12:57:04 UTC
Created attachment 30488 [details]
The video bios (kt690/mITX board by kontron)

This is the video bios, exctracted with your instructions.

I hope this is somehow useful...

BTW, do you think it is a bug in the BIOS? I know there are 2 newer
BIOS versions that I could upgrade to, but I am a bit reluctant as
it's a bit of a hassle, with only linux on this machine...
Comment 6 Alex Deucher 2009-10-21 13:23:50 UTC
can you try with ati from git master?  Specifically commit 66b194a78c470cb3978f310828dd96c3f3e96944.
Comment 7 Oliver Freyd 2009-10-22 15:48:52 UTC
I've tried now, compiled the xf86-video-ati from git 
(e57b54daf318ff59315a1c9ed21934f288c5c782) which is 2 commits
after the one you proposed to me.

I see no difference, VGA output works, DVI runs on 30 Hz vertical frequency,
monitor switches off after a minute.

BTW, I see no difference in the log file regarding PLL dividers etc.
Just the same as for VGA, only it does not work :-(
Comment 8 Alex Deucher 2010-10-19 18:34:35 UTC
Is this still an issue with kms or a newer driver?
Comment 9 Oliver Freyd 2010-10-20 01:27:41 UTC
Hello,

some months ago, I was running Ubuntu 10.04 with xorg-edgers
repository, so I had a quite bleeding edge xorg, 
I think in august it was still an issue.
but I'll try DVI again (simply I'm running the machine on VGA
and didn't quite care about the broken DVI anymore.

I'll also try a new driver again. BTW, it is running KMS,
so the mode switching stuff is in the kernel, 
so I just have to compile a bleeding-edge kernel.

Anyway, thanks for your message, I'll report back in a few days...

regards,

     Oliver

-------- Original-Nachricht --------
> Datum: Tue, 19 Oct 2010 18:34:35 -0700 (PDT)
> Von: bugzilla-daemon@freedesktop.org
> An: Oliver.Freyd@gmx.de
> Betreff: [Bug 24456] monitor on DVI output "out of range"

> https://bugs.freedesktop.org/show_bug.cgi?id=24456
> 
> --- Comment #8 from Alex Deucher <agd5f@yahoo.com> 2010-10-19 18:34:35 PDT
> ---
> Is this still an issue with kms or a newer driver?
> 
> -- 
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
Comment 10 Christopher M. Penalver 2016-02-25 01:50:05 UTC
Oliver Freyd, Ubuntu 10.04 reached EOL on May 9, 2013. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.