From: Hai Zaar <haizaar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: vesa fb is slow on 2.6.15.1
Date: Sat, 28 Jan 2006 02:31:41 +0200 [thread overview]
Message-ID: <cfb54190601271631v3af78d70v8993cae358fe9994@mail.gmail.com> (raw)
In-Reply-To: <43DA5681.2020305@gmail.com>
>
> Looks harmless to me.
>
> Can you check /proc/iomem just to verify if that particular address has
> been reserved by the OS.
Relevant iomem entries are:
f0000000-f7ffffff : PCI Bus #40
f0000000-f7ffffff : 0000:40:00.0
f0000000-f7ffffff : vesafb
f8000000-f9ffffff : PCI Bus #40
f8000000-f8ffffff : 0000:40:00.0
f9000000-f9ffffff : 0000:40:00.0
After I load nvidia.ko, it changes to:
f0000000-f7ffffff : PCI Bus #40
f0000000-f7ffffff : 0000:40:00.0
f0000000-f7ffffff : vesafb
f8000000-f9ffffff : PCI Bus #40
f8000000-f8ffffff : 0000:40:00.0
f8000000-f8ffffff : nvidia
f9000000-f9ffffff : 0000:40:00.0
>
> And, are you experiencing any problems with your nvidia card, ie, are
> you able to launch X?
X is working fine. KDE runs, glxgears reports 890fps on full screen (1280x1024)
I usually boot with 'quiet' option, so this error is very evident. I
personally can live with it, but I'll surely get a bunch of mail from
my users reporting the "problem". I hope it will be fixed new next
releases.
Anyway. Thanks a lot for your help guys!
next prev parent reply other threads:[~2006-01-28 0:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 14:20 vesa fb is slow on 2.6.15.1 Hai Zaar
2006-01-26 14:51 ` Antonino A. Daplas
2006-01-26 16:06 ` Hai Zaar
2006-01-26 16:40 ` Alistair John Strachan
2006-01-26 22:04 ` Antonino A. Daplas
2006-01-27 0:10 ` Hai Zaar
2006-01-27 0:19 ` Hai Zaar
2006-01-27 6:02 ` Antonino A. Daplas
2006-01-27 16:32 ` Hai Zaar
2006-01-27 17:21 ` Antonino A. Daplas
2006-01-28 0:31 ` Hai Zaar [this message]
[not found] ` <cfb54190601271628j774df3d0xce0ab24c8abca845@mail.gmail.com>
[not found] ` <43DABCF6.4000904@gmail.com>
2006-01-28 0:54 ` Hai Zaar
2006-01-28 1:02 ` Antonino A. Daplas
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=cfb54190601271631v3af78d70v8993cae358fe9994@mail.gmail.com \
--to=haizaar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).