archive mirror
 help / color / mirror / Atom feed
From: "Kristofer T. Karas" <>
Cc: Marcelo Tosatti <>,
	Linux Kernel Mailing List <>
Subject: Radeon in LK 2.4.21pre7
Date: 20 Jul 2003 01:43:11 -0400	[thread overview]
Message-ID: <1058679793.10948.47.camel@ktkhome> (raw)

Ben, Ani, et al,

Just tried Linux kernels 2.4.21pre6 and pre7 with my Radeon 8500LEE and
have had some dreadful corruption problems related to pixel clearing
during scroll and ypan.  This is probably old news to you; so <aol>me
too</aol>.  I first noticed this in the -ac kernels, but a variant is
now in mainline -pre.

Problem #1:  When scrolling, radeonfb fails to erase the portion of the
screen at the bottom, leaving all sorts of random pixels in the bottom
line.  Further scrolling propagates these pixels upwards.
(Sorry for camera-shake; hand-held in dim room...)

Problem #2:  When one VC has scrolled up some number of lines, causing
it to display somewhere in the middle of its virtual Y buffer, and you
switch consoles to one that is still displaying from some other Y-start
value, the screen tends to redraw itself in an odd location (not at the
bottom) thus leaving large portions as they were from the previous VC.

Problem #3:  Possibly a side-effect of problem #2, when switching VCs
via Alt-<F1...Fn> the new VC often fails to appear.  The cursor
disappears, but the screen remains as it was.  Hitting <Enter> to scroll
the screen has no effect.  Interestingly, pressing <Alt>-<SysRQ>-? to
get a magic-sysrq help line restores the screen to operation, and it
displays all further output normally.  This occurs perhaps 50% of the

Workaround #1:  Setting vyres == yres causes the aforementioned issues
to go away.  However, it also takes accelerated scrolling with it.
# fbset -vyres 10240
# time locate xine
[lots of screen output]

real	0m0.935s
# fbset -vyres 1024
# time locate xine
[lots of screen output]

real	0m2.548s

Problem #4:  I think this was already reported.  But when running X,
switching to a text console (with <Ctrl>-<Alt>-<F1...Fn>) results in
complete corruption of the output.

Kris Karas

P.S.  Hardware is an ATI brand Radeon 8500 LEE:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon QL (prog-if 00 [VGA])
	Subsystem: ATI Technologies Inc Radeon 8500
	Flags: bus master, stepping, 66Mhz, medium devsel, latency 255, IRQ 11
	Memory at e0000000 (32-bit, prefetchable) [size=128M]
	I/O ports at c000 [size=256]
	Memory at ed000000 (32-bit, non-prefetchable) [size=64K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [58] AGP version 2.0
	Capabilities: [50] Power Management version 2

             reply	other threads:[~2003-07-20  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20  5:43 Kristofer T. Karas [this message]
2003-07-22 12:55 ` Radeon in LK 2.4.21pre7 Benjamin Herrenschmidt
2003-07-25  2:03   ` Kristofer T. Karas
2003-08-01 10:43 ` Benjamin Herrenschmidt
2003-07-20 20:28 Lars Ehrhardt

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:

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

  git send-email \
    --in-reply-to=1058679793.10948.47.camel@ktkhome \ \ \ \ \ \

* 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).