| 1 |
Hi, |
| 2 |
|
| 3 |
i'm not an expert on this subject myself but i found it nonetheless |
| 4 |
interesting, here's what i found mostly by grepping and googling: |
| 5 |
|
| 6 |
Here's someone who is also getting these huge reported memory sizes: |
| 7 |
http://lkml.org/lkml/2005/9/12/35 |
| 8 |
Found it by googling for 983552MB, there's more there. |
| 9 |
|
| 10 |
There's is some info on mtrr's with vesafb here: |
| 11 |
/usr/src/linux-2.6.13-gentoo-r3/Documentation/fb/vesafb.txt, line 176 |
| 12 |
Seems to suggest trying video=vesafb:nomtrr if you're using vesafb. |
| 13 |
|
| 14 |
Also some other reports seem to hint at Xorg as the culprit: |
| 15 |
https://bugs.freedesktop.org/show_bug.cgi?id=4310 |
| 16 |
and others found by googling "mtrr: type mismatch for". |
| 17 |
|
| 18 |
You might want to also grep Xorg.log for the addresses provided by |
| 19 |
'cat /proc/mtrr' or just the prefix such as |
| 20 |
'grep -in 0xd /var/log/Xorg.0.log' in my case, that should some results |
| 21 |
(Xorg.log doesn't seem to mention mtrr literally, as far as i can see). |
| 22 |
|
| 23 |
I'm sorry that I don't have an answer to the actual problem, but I'm |
| 24 |
very thankful for the interesting explanations about mtrr from both of |
| 25 |
you (Duncan and Mark). |
| 26 |
|
| 27 |
Cheers, |
| 28 |
Marco |
| 29 |
-- |
| 30 |
gentoo-amd64@g.o mailing list |
Archives