From: "Lenar Lõhmus" <lenar@city.ee>
To: linux-kernel@vger.kernel.org
Subject: Re: Overlapping MTRRs in 2.6.1
Date: Mon, 19 Jan 2004 01:25:39 +0200 [thread overview]
Message-ID: <20040118232539.AB9B71A0C@xs.dev> (raw)
In-Reply-To: 1fsuY-4YG-9@gated-at.bofh.it
Ryan Reich wrote:
> I checked the archives and no one has posted a message on MTRR overlaps
> since
> 2002. At that time, Andrew Rodland wrote something about what appears to
> be this exact problem; a link to it is
Haven't bothered. But I'm getting those errors and the inability to set up
MTRR's by X too.
I've got a hunch that in my case it depends on how big MTRR vesafb driver
sets up for itself during boot ... if it's the same size X later asks then
everything is ok.
Usually it's 16MB for vesafb in my machine and 32MB for X. So i've always
just disabled the MTRR set up by vesafb (echo "disable=n" > /proc/mtrr) and
restart X before playing games. This way no problem.
lenar
next parent reply other threads:[~2004-01-18 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1fsuY-4YG-9@gated-at.bofh.it>
2004-01-18 23:25 ` Lenar Lõhmus [this message]
2004-01-18 21:11 Overlapping MTRRs in 2.6.1 Ryan Reich
2004-01-18 21:57 ` Mike Fedyk
2004-01-19 1:21 ` Ryan Reich
2004-01-19 9:50 ` Dave Jones
2004-01-19 14:19 ` Ryan Reich
2004-01-19 14:59 ` Dave Jones
2004-01-19 15:16 ` Ryan Reich
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=20040118232539.AB9B71A0C@xs.dev \
--to=lenar@city.ee \
--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