1 |
On Mon, Aug 16, 2010 at 05:55:04PM -0500, Paul Hartman wrote |
2 |
> |
3 |
> I had a similar message, it was there because of the fact that i |
4 |
> specified the wrong (or failed to specify?) mtrr method in my kernel |
5 |
> boot parameters for the framebuffer. I'm using uvesafb and in kernel |
6 |
> documentation (/usr/src/linux/Documentation/fb/uvesafb.txt) it |
7 |
> explains the values and even gives an example of this error and what |
8 |
> to do about it: |
9 |
|
10 |
I'm using the Intel driver, which doesn't have those settings. And |
11 |
no, I do not want to drop down to a generic VESA driver with no hardware |
12 |
acceleration. Some more Google searching has turned up a lead. |
13 |
Apparently, it's possible to manually set the mtrr's, using cat and echo |
14 |
with /proc/mtrr |
15 |
|
16 |
According to "lspci -v", my integrated graphics chip has |
17 |
|
18 |
Memory at fb800000 (64-bit, non-prefetchable) [size=4M] |
19 |
Memory at d0000000 (64-bit, prefetchable) [size=256M] |
20 |
|
21 |
My mtrr setup, however, shows up like so... |
22 |
|
23 |
waltdnes@i3 ~ $ cat /proc/mtrr |
24 |
reg00: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back |
25 |
reg01: base=0x200000000 ( 8192MB), size= 1024MB, count=1: write-back |
26 |
reg02: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable |
27 |
reg03: base=0x0b4000000 ( 2880MB), size= 64MB, count=1: uncachable |
28 |
reg04: base=0x0b8000000 ( 2944MB), size= 128MB, count=1: uncachable |
29 |
reg05: base=0x1fc000000 ( 8128MB), size= 64MB, count=1: uncachable |
30 |
|
31 |
I'll read up more on how to set it up manually. One thing that has my |
32 |
curiousity right now... how come there's a gig of ram in write-back mode |
33 |
*STARTING* at 8 gigs, and ending at 9 gigs minus 1 byte, when I only |
34 |
have 8 gigs of ram in total? |
35 |
|
36 |
-- |
37 |
Walter Dnes <waltdnes@××××××××.org> |