public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clem Taylor <clemtaylor@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: radeonfb driver doesn't properly configure DVI monitor (2.6.8.1)
Date: Wed, 18 Aug 2004 00:41:21 -0400	[thread overview]
Message-ID: <4122DDF1.5070306@comcast.net> (raw)

I have an older Radeon 8500 LE on my dual Opteron box. The radeonfb 
driver doesn't properly configure the DVI monitor output on startup. The 
analog output looks okay, but the DVI output is covered with redish 
noise that gets progressively worse as the system runs. It looks like 
some PLL or DLL is not being configured correctly. The monitor reports 
the correct resolution and refresh rate, so at least hsync/vsync timing 
is correct. The right edge of the image contains a fixed pattern that 
moves with screen scroll. Also, the last 5-10 lines of the analog output 
contains a series of random colored characters. It looks like the text 
buffer isn't being fully cleared (the LCD panel I'm using is 1920x1200).

X (xorg) properly configures the DVI, but when I switch back to the 
console, the output looks less broken but still contains a fairly strong 
RGB noise pattern.

On boot the radeonfb driver reports:
radeonfb: Invalid ROM signature 0 should be 0xaa55
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=275.00 Mhz, 
System=275.00 MHz
radeonfb: Monitor 1 type DFP found
radeonfb: EDID probed
radeonfb: Monitor 2 type CRT found
radeonfb: EDID probed
radeonfb: ATI Radeon QL  DDR SGRAM 64 MB

Another curious point is that the DVI output doesn't work at all from 
the BIOS, which means I have to switch to the analog output to boot. I 
updated the firmware on the graphics card, but that made things worse, 
the noise problem showed up in the BIOS and starting X didn't fix the 
noise (so I reverted to the previous version). ATIs response to this was 
that it was a BIOS problem and then that the card was old.

Has anyone else seen similar problems? I haven't tried compiling with 
CONFIG_FB_RADEON_DEBUG, but I think that should be the next thing.

                  --Clem

                 reply	other threads:[~2004-08-18  4:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4122DDF1.5070306@comcast.net \
    --to=clemtaylor@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox