mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: X sloow under 2.6.9 and up - mtrr ?
Date: Tue, 16 Nov 2004 22:45:37 +0000	[thread overview]
Message-ID: <1100645137l.8864l.0l@werewolf.able.es> (raw)

Hi all...

I have built 2.6.10-rc2-mm1, and as nVidia drivers do not work with it,
i configured xorg-6.8.1 to use the standard 'nv' driver.
But now X redraws are dog slow, you can count pixels redrawing on the
screen if you move a window in filled mode.

Somebodyt has a clue about why can this be happening ?
>From deep in my memory I remember this was related to mtrr settings.
With the nVidia driver I have:

werewolf:~> cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size=1024MB: write-back, count=1
reg01: base=0x3ff00000 (1023MB), size=   1MB: uncachable, count=1
reg02: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=1
reg03: base=0xe8000000 (3712MB), size= 128MB: write-combining, count=1

and with the nv standard driver:

reg00: base=0x00000000 (   0MB), size=1024MB: write-back, count=1
reg01: base=0x3ff00000 (1023MB), size=   1MB: uncachable, count=1
reg02: base=0xe8000000 (3712MB), size= 128MB: write-combining, count=1

One is missing. It is an i875P chipset.

Any idea ?

Ah, this also happens on one other box, also with an nvidia card, but this
box never had the binary drivers installed, it is just a server.
This one is a Via Apollo Pro266, and its mtrr:
nada:~# cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size=1024MB: write-back, count=1
reg01: base=0xf0000000 (3840MB), size=  64MB: write-combining, count=1
reg02: base=0xe8000000 (3712MB), size=  64MB: write-combining, count=1

TIA

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.9-jam1 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #10



                 reply	other threads:[~2004-11-16 22:47 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=1100645137l.8864l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®