linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net, Robert.Siemer@backsla.sh
Subject: Re: radeonfb: DDC read wrong?
Date: Sat, 24 Jun 2006 20:11:46 +0800	[thread overview]
Message-ID: <449D2C02.8010101@gmail.com> (raw)
In-Reply-To: <20060620140152.GB5414@polar.elf12.net>

Robert Siemer wrote:
> Hello everybody!
> 
> problem: booting kernel overdrives monitor with 200Hz refresh
> 
> kernel: 2.6.16
> kernel which worked fine: 2.6.14
> 
> Monitor: EIZO FlexScan F563-T
> Graphic adapter: ATI Technologies Inc Radeon RV250 If [Radeon 9000]
>  (from Xorg.log)
> 
> I switched to 2.6.16 and booting the kernel overdrove my monitor with
> 200Hz refresh rate.
> 
> As I notice now I have a limit configured in X (I will try it without
> limitation to see what X is doing...).
> 
> The only interesting line so far from X-log:
> (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=20000 max=40000;
> xclk=20000
> 
> 
> Any comments?

Can you change #undef DEBUG to #define DEBUG in drivers/video/fbmon.c
then post your dmesg?

If your monitor's EDID block is faulty, we can add it to our
monitor database for fixups.

Tony

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-06-24 12:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 14:01 radeonfb: DDC read wrong? Robert Siemer
2006-06-24 12:11 ` Antonino A. Daplas [this message]
2006-06-24 17:47   ` Robert Siemer
2006-06-24 21:33     ` Antonino A. Daplas
2006-06-24 21:56       ` Robert Siemer
2006-06-24 23:27     ` Antonino A. Daplas
2006-06-25  0:00     ` Antonino A. Daplas
2006-06-26 17:01       ` Robert Siemer
2006-06-26 20:55         ` Antonino A. Daplas
2006-06-27 19:11           ` Luca

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=449D2C02.8010101@gmail.com \
    --to=adaplas@gmail.com \
    --cc=Robert.Siemer@backsla.sh \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).