Re: vesa fb is slow on 2.6.15.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>
> 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!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux