linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Kern <alex.kern@gmx.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Jurij Smakov <jurij@wooyd.org>, debian-sparc@lists.debian.org
Subject: Re: Image defects with 2.6.14/atyfb/Sunblade 100
Date: Sun, 13 Nov 2005 21:08:19 +0100	[thread overview]
Message-ID: <200511132108.19391.alex.kern@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0511112134500.3900@bobcat>

Am Samstag 12 November 2005 06:51 schrieb Jurij Smakov:
> [Forwarding information to linux-fbdev-devel]
>
> Hello,
>
> Recently Luigi Gangitano has pointed out a linux-fbdev-devel thread [0]
> in which progress was achieved in fixing the atyfb bug resulting in
> console and X display corruption on SunBlade 100, filed as #321200 in the
> Debian bug tracking system [1]. The patch mentioned in the thread (which
> we plan to include in the next Debian kernel package release) is attached.
> While the situation with this patch is greatly improved, users testing the
> new 2.6.14 kernel packages have reported [2,3] that there is still some
> minor screen corruption in a form of red dots or lines. A screenshot
> (provided by Andrey Chernomyrdin) can be viewed at [4]. We'd appreciate
> any ideas which could lead to the resolution of this problem.
>
> Please CC the responses to me (and, optionally to the
> debian-sparc@lists.debian.org), as I'm not subscribed to this list.
>
> [0] http://marc.theaimsgroup.com/?t=111088248100003&r=1&w=2
> [1] http://bugs.debian.org/321200
> [2] http://lists.debian.org/debian-sparc/2005/11/msg00076.html
> [3] http://lists.debian.org/debian-sparc/2005/11/msg00087.html
> [4] http://www.wooyd.org/debian/tmp/sunblade.png
>
> Thanks and best regards,
>
> Jurij Smakov                                        jurij@wooyd.org
> Debian kernel team
> Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

Hello,

are you sure, you have these artefactes under X11 with "ati" driver too?
If yes,  it has nothing todo with "fbdev". "ati" chahges all chip settings on 
it own. Anyway "ati" was for me any time "refrence number one", and if they 
do not have solution, I don't have it for sure ;-(

What about ask maintainer of "ati"?

P.S.
I think these red dots caused by overclocking something(dotclock, memory, 
GPU).

-- 

Best Wishes
Mit freundlichen Grüßen

Alex Kern


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php

      reply	other threads:[~2005-11-13 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12  5:51 Image defects with 2.6.14/atyfb/Sunblade 100 Jurij Smakov
2005-11-13 20:08 ` Alexander Kern [this message]

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=200511132108.19391.alex.kern@gmx.de \
    --to=alex.kern@gmx.de \
    --cc=debian-sparc@lists.debian.org \
    --cc=jurij@wooyd.org \
    --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).