From: Mark Hounschell <markh@compro.net>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: dmarkh@cfl.rr.com, Andrew Morton <akpm@linux-foundation.org>,
Michael Tokarev <mjt@tls.msk.ru>,
Linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: VERY slow scrolling on radeon graphics card: debugging a timing issue?
Date: Thu, 23 Dec 2010 07:53:11 -0500 [thread overview]
Message-ID: <4D134637.9020709@compro.net> (raw)
In-Reply-To: <1293089117.19556.109.camel@thor.local>
On 12/23/2010 02:25 AM, Michel Dänzer wrote:
> On Mit, 2010-12-22 at 05:55 -0500, Mark Hounschell wrote:
>>
>> I also see this very problem on several machines I have with radeon video.
>> For me the worst part is using vi in a konsole. Moving the cursor around
>> is so slow that I just can't use these machines directly and have to ssh
>> into them from another machine just to work on them.
>
> That's not the same problem as the one described by Michael, which is
> about the console on virtual terminals different from X.
>
> For your problem, try choosing a different font (a fontconfig one
> instead of a legacy X one) in konsole.
>
>
Hum, but I do in fact see the same thing he sees on a VT. A dmesg
command from a VT takes around 20 seconds to display. The same in a
konsole takes a fraction of a second.
So your probably right that my vi problem in a konsole is a different
issue. I do see the same thing as the OP does though. I just figured
they were probably related.
Changing fonts doesn't change anything though. I normally use the "Misc
Console" font FWIW.
Regards
Mark
next prev parent reply other threads:[~2010-12-23 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 20:58 VERY slow scrolling on radeon graphics card: debugging a timing issue? Michael Tokarev
2010-12-22 10:00 ` Andrew Morton
2010-12-22 10:55 ` Mark Hounschell
2010-12-23 7:25 ` Michel Dänzer
2010-12-23 12:53 ` Mark Hounschell [this message]
2011-01-02 9:00 ` Pavel Machek
2011-01-04 22:50 ` Michael Tokarev
2011-01-04 23:11 ` Michael Tokarev
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=4D134637.9020709@compro.net \
--to=markh@compro.net \
--cc=akpm@linux-foundation.org \
--cc=dmarkh@cfl.rr.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=mjt@tls.msk.ru \
/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