Marco Matthies posted <[EMAIL PROTECTED]>, excerpted below, on Mon, 17 Oct 2005 02:18:06 +0200:
> Here's someone who is also getting these huge reported memory sizes: > http://lkml.org/lkml/2005/9/12/35 > Found it by googling for 983552MB, there's more there. > > There's is some info on mtrr's with vesafb here: > /usr/src/linux-2.6.13-gentoo-r3/Documentation/fb/vesafb.txt, line 176 > Seems to suggest trying video=vesafb:nomtrr if you're using vesafb. > > Also some other reports seem to hint at Xorg as the culprit: > https://bugs.freedesktop.org/show_bug.cgi?id=4310 > and others found by googling "mtrr: type mismatch for". > > You might want to also grep Xorg.log for the addresses provided by > 'cat /proc/mtrr' or just the prefix such as > 'grep -in 0xd /var/log/Xorg.0.log' in my case, that should some results > (Xorg.log doesn't seem to mention mtrr literally, as far as i can see). Same here. The address range corresponds, but mtrr isn't mentioned by name in xorg.conf. You can check video memory (and a couple other items) by running lspci -v. Look for the line that has a size in megs, under the correct video device, of course... <g> This is all great fun and I sure learned a lot yesterday researching, then putting it into words therefore anchoring it in my memory as well as forcing myself to contemplate angles for the purpose of writing that I wouldn't necessarily see, otherwise. However, Saturday nite is my Monday, and I spent all of my Monday nite researching and writing this and a couple other technical replies... and got only an hour or so of sleep! <g> So... tonite I'm going to try to avoid getting too deeply involved in this and ignore the additional research I now want to do given the above links! <g> Maybe that way I can get some sleep today (day=nite for me, nite=day)! ... One of the things that is making this interesting for me, is that I've been trying to run dual Radeons for some time, one AGP one PCI, each with two outputs so I can run FOUR 21" monitors instead of only TWO, like I used to run an NVidia (Twinview) with the closed drivers and an old cheap S3 Virge (giving me three monitors, then a 19" and two 17"), a couple years ago. However, I keep getting conflicting resources when I try. I've always wanted to take the time to see if I could grok things well enough to try and reconfigure around the issue, and this is giving me the motivation (and additional brain power) to grasp at least one angle of it. I'm not sure that's actually what's conflicting, as I haven't tried running it that way for awhile, but I'm at least developing enough understanding now to make a bit of sense of things and figure out from the errors where the problem actually is, now, when I get a chance to get back to it. That's /miles/ farther than I was, previously! In addition, few enough folks actually grok this stuff that if I can get it, I'm sure the knowledge will be of help to quite a few others, as well. Oh... Previously I was trying to run a separate "screen" config for each monitor, thus, two per card since each card has two outputs. I'm now running xorg's merged framebuffer for Radeons, so it's actually possible the problem will have disappeared when I actually try it again... So anyway, that's why I'm spending so much time on this myself... The knowledge gained at this point can be of help to at least two, and later others, so it's not just me gaining immediate benefit, nor is it just you. However, the research will work better when I'm rested, so tomorrow or later this week... -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
