linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Radeon in LK 2.4.21pre7
@ 2003-07-20  5:43 Kristofer T. Karas
  2003-07-22 12:55 ` Benjamin Herrenschmidt
  2003-08-01 10:43 ` Benjamin Herrenschmidt
  0 siblings, 2 replies; 5+ messages in thread
From: Kristofer T. Karas @ 2003-07-20  5:43 UTC (permalink / raw)
  To: ajoshi, benh; +Cc: Marcelo Tosatti, Linux Kernel Mailing List

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.
See http://enterprise.bidmc.harvard.edu/~ktk/temp/radeonfb/screen-1.jpg
(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.
See: http://enterprise.bidmc.harvard.edu/~ktk/temp/radeonfb/screen-2.jpg

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
time.

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.

HTH,
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



^ permalink raw reply	[flat|nested] 5+ messages in thread
* Re: Radeon in LK 2.4.21pre7
@ 2003-07-20 20:28 Lars Ehrhardt
  0 siblings, 0 replies; 5+ messages in thread
From: Lars Ehrhardt @ 2003-07-20 20:28 UTC (permalink / raw)
  To: linux-kernel

Hi,

Kristofer T. Karas wrote:

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

Yes, I can confirm that this problem is still present in 2.4.21-bk14.
See http://www.cs.helsinki.fi/linux/linux-kernel/2003-28/0165.html
for the details of my hardware.

Will this be fixed before 2.4.22 comes out?

bye lars


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2003-08-01 10:47 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-20  5:43 Radeon in LK 2.4.21pre7 Kristofer T. Karas
2003-07-22 12:55 ` Benjamin Herrenschmidt
2003-07-25  2:03   ` Kristofer T. Karas
2003-08-01 10:43 ` Benjamin Herrenschmidt
2003-07-20 20:28 Lars Ehrhardt

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