All of lore.kernel.org
 help / color / mirror / Atom feed
From: jim watson <jim@amarooas.com.au>
To: sparclinux@vger.kernel.org
Subject: Sunblade100 Red Dots persist
Date: Wed, 04 Jul 2007 00:11:28 +0000	[thread overview]
Message-ID: <468AE5B0.1090705@amarooas.com.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]

Emanuele Rocca wrote:
>  What about the "red dots" issue? Is that already known upstream?
>   
>
> I don't know about this one, my blade 2k is not affected.
>
> Jim, could you please try the last rc kernel (2.6.22-rc7) and send a
> report to sparclinux@vger.kernel.org if the bug is still present?
>
> Thanks.
> ciao,
>     ema
>
>   
I built 2.6.22-rc7 on my Sunblade100 debian/unstable and find the red 
dots issue is still there.

A few red dots will be seen on any window opened on the desktop. If the 
window is dragged around  a few times then more dots accumulate mostly 
along a few vertical lines near each side of the window. Some dots are 
seen on the window decorations and sometime a few are just outside the 
window borders but move with the window. This affects any window, but it 
is easier to see in a black terminal window.

The dots remain fixed relative to the moving window. There is also a 
flickering of vertical black broken lines near the physical centre of 
the LCD screen when a desktop window is moved.

The dots go away if the window is resized, and re-appear when it is moved.
 
A related problem is also seen in a plain console (Ctrl-Alt-F2) where a 
few white dots will be displaced horizontally from some characters and 
are displayed further to the right. 

Please see the attached screenshot.

This issue can be avoided by booting with video=atyfb:off

thanks

jim


[-- Attachment #2: Screenshot-1.png --]
[-- Type: image/png, Size: 214936 bytes --]

                 reply	other threads:[~2007-07-04  0:11 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=468AE5B0.1090705@amarooas.com.au \
    --to=jim@amarooas.com.au \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.