linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Luigi Gangitano <luigi@debian.org>
Cc: Alexander Kern <alex.kern@gmx.de>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [Fwd: AtyFB in 2.6.10, still not perfect]
Date: Wed, 16 Mar 2005 04:39:05 +0800	[thread overview]
Message-ID: <200503160439.05644.adaplas@hotpop.com> (raw)
In-Reply-To: <200503151826.46073.adaplas@hotpop.com>

On Tuesday 15 March 2005 18:26, Antonino A. Daplas wrote:
> --- Luigi Gangitano <luigi@debian.org> wrote:

> 4.  Can you post the dmesg, config and fbset -i of both the
> working and non-working kernel?
>

The dmesg log you sent me showed this:

working:
atyfb: 3D RAGE (XL) [0x4752 rev 0x27] 8M SDRAM, 29.498928 MHz XTAL, 230 
MHz PLL, 100 Mhz MCLK

not working:
atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MHz PLL, 83 Mhz MCLK, 63 
MHz XCLK

The MCLK value is different.  Can you try booting with

video=atyfb:mclk:100

You can also experiment with xclk:

video=atyfb:mclk:100,xclk:63

Tony




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-03-15 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 10:26 [Fwd: AtyFB in 2.6.10, still not perfect] Antonino A. Daplas
2005-03-15 19:40 ` Luigi Gangitano
2005-03-15 20:39 ` Antonino A. Daplas [this message]
2005-03-15 23:20   ` Luigi Gangitano
2005-03-15 23:49     ` Antonino A. Daplas
2005-03-19 15:15       ` Alexander Kern
2005-03-22 20:06         ` Luigi Gangitano
2005-03-23 21:35           ` Alexander Kern
2005-03-24 16:06             ` Luigi Gangitano

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=200503160439.05644.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=alex.kern@gmx.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=luigi@debian.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;
as well as URLs for NNTP newsgroup(s).