ilna: I notice that error now on my Fedora 11. I'm too lazy to check,
but it looks as if the kernel header changed and hijacked a symbol that
I had been using.
quick fix: issue this shell command in the mtrr directory
sed -i -e 's/\mtrr_type\/_dhr/g' mtrr-uncover.c
Then make again.
I am a
For D. Hugh Redelmeier: thanks for fix! In fact I have resolved the
issue with 'enable_mtrr_cleanup' boot option:
sudo cat /proc/mtrr
reg00: base=0x0 (0MB), size= 2048MB, count=1: write-back
reg01: base=0x1 ( 4096MB), size= 2048MB, count=1: write-back
reg02: base=0x17c00 (
ilna:
Glad to hear that the kernel's clean up code worked. Could you post the
/proc/mtrr contents when cleanup is not enabled? I'd like to see what
it is fixing.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping
This version of mtrr-uncover should compile cleanly with the new asm/mtrr.h
header file.
ftp://ftp.cs.utoronto.ca/pub/hugh/mtrr-uncover-2009august14.tgz
Thanks, ilna, for pointing out the problem.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB
For D. Hugh Redelmeier: It's here:
http://ubuntuforums.org/showpost.php?p=7774450postcount=1048
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received this bug
For D. Hugh Redelmeier:
I have tried to build mtrr-uncover-2009may13.tgz and got:
$ make
cc -Wall -gmtrr-uncover.c -o mtrr-uncover
mtrr-uncover.c:123: error: ‘mtrr_type’ redeclared as different kind of symbol
/usr/include/asm/mtrr.h:70: note: previous declaration of ‘mtrr_type’ was here
With regard to my earlier comment (
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/224404/comments/42
):
I have updated the mtrr-uncover a few times. Look for the newest appropriately
named tarball in the ftp directory: ftp://ftp.cs.utoronto.ca/pub/hugh/
--
Same here, using 8.10 rc with intel p35 chipset, 4gb ram and fglrx driver,
everything works!
[EMAIL PROTECTED]:~$ cat /proc/mtrr
reg00: base=0x ( 0MB), size=4096MB: write-back, count=1
reg01: base=0x1 (4096MB), size= 512MB: write-back, count=1
reg02: base=0x12000 (4608MB),
Ubuntu 8.10-rc fglrx works with 4GB and memory remapping enabled.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status: New = Fix Released
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
Hello,
Does this only apply to the 64-bits version, or is this also possible to get
full advantage of 4GB under the 32-bits version?
Thanks
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
I believe to get access to all 4GB of memory in 32 bit version requires
the use of PAE or a BIGMEM kernel. To get access to all the memory in 32
bit version you would have to enable memory-remapping. I know that this
bug will not affect someone using the stock kernel (but unsure of the
bigmem or
I just upgraded to Ubuntu 8.10 and I no longer need my manual MTRR fix
in /etc/rc.local ... everything is fine using the default config.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
I've also checked with Ubuntu 8.10 - release candidate. It now handles memory
remapping. In case people are wondering, my new mtrr tables:
[EMAIL PROTECTED]:~$ cat /proc/mtrr
reg01: base=0xe000 (3584MB), size= 512MB: uncachable, count=1
reg02: base=0x ( 0MB), size=4096MB:
still doesn't work
I have this messages:
[ 14.792019] uvesafb: NVIDIA Corporation, G86 Board - e416h01 , Chip Rev ,
OEM: NVIDIA, VBE v3.0
[ 15.034609] uvesafb: VBIOS/hardware doesn't support DDC transfers
[ 15.034722] uvesafb: no monitor limits have been set, default refresh rate
will
and also I have in /proc/mtrr:
reg00: base=0xc000 (3072MB), size=1024MB: uncachable, count=1
reg01: base=0x ( 0MB), size=4096MB: write-back, count=1
reg02: base=0x1 (4096MB), size=1024MB: write-back, count=1
--
MTRR is not properly setup on Intel Northbridge Chipset (P35,
I've written the program. It works on my one system. Who knows if it
works anywhere else.
Fetch it from ftp://ftp.cs.utoronto.ca/pub/hugh/mtrr-uncover-
2008sept18.tgz
Untar it. cd into the new directory. Type make. Read the manpage man
./ mtrr-uncover.8
Run the command (just a test!)
I'm trying to write a program to rejig MTRR settings to avoid this
problem. More details to follow if it works.
It would help me if people would post the contents of /proc/mtrr for
their systems. If you have a BIOS setting that avoids the problem,
please post /proc/mtrr for both. It would also
Just thought I would add my $0.02 because I have a Foxconn X38A board
with a C2Q 6600 and 4GB of RAM. I also have a Sapphire ATI 3870 card.
When I did a fresh install of Ubuntu 8.04, everything came up fine (and
very fast), then I enabled the fglrx driver and when the system came
back up, it went
I also had the same problem with a Dell Optiplex 755 with a Radeon HD
2400 Pro when using 4gb of memory on an amd64 (x86_64) install of
RHEL5.2. Disabling mtrr in the xorg.conf and disabling redhat's
graphical boot seemed to do the trick. I'd like the pretty graphics on
boot so users aren't
Output of cat /proc/mtrr
X48 4GB 32bit ubuntu 8.04.1 3870
reg00: base=0x ( 0MB), size=4096MB: write-back, count=1
reg01: base=0xe000 (3584MB), size= 512MB: uncachable, count=1
reg02: base=0xd000 (3328MB), size= 256MB: uncachable, count=1
reg03: base=0x1 (4096MB),
I have the same problem here,
MSI P35 Mainboard, dualcore, radeon hd3650, 4gb ram.
I found fix in the forums:
http://ubuntuforums.org/showthread.php?t=764214goto=nextoldest
btw. this a not so new problem and shouldnt bugs causing hard locks be
fixed faster?
--
MTRR is not properly setup on
The only issue is that the hard lock actually has something to do with a
closed source package (i.e. fglrx has an issue with the mtrr table, but
the mtrr table is actually handled by the BIOS and kernel - then this
problem lies with our ability to get information out of the fglrx binary
driver).
Similar situation:
When I use fglrx with default configuration it blanks the screen and hard locks
the system (VTs and network die). I have to disable AIGLX, Composite,
Accleration and DRI for it to work at all. If I change VTs it crashes.
I don't have a BIOS option for Memory Re-Mapping so I
Update: Removing the second stick of memory fixes the problem, but at
the cost of 2GB of RAM.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received this bug
I wonder if the xorg fix/workaround described here would work:
https://bugs.freedesktop.org/show_bug.cgi?id=2750
Description: When WC MTRR is set up, any previous MTRR region with
offending size will block correct MTRR setup.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38,
That could be a fix. However it appears to be in regards to x86 (IA32)
- although, this fix might work for 64 bit architectures.
Further, its a little troubling that the last comments on this bug are
from 2005-05 (I would expect that this code would have been rolled into
the xserver code base).
Rich Hewitt, can you post your mtrr tables fix?
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received this bug notification because you are a member of Ubuntu
Bugs,
My /etc/rc.local is below ... for what it's worth ... it's unlikely to
be of any use to anyone unless they have exactly the same machine,
memory size gfx card. A better general discussion on how to 'fix' the
mtrr is available at:
http://www.rage3d.com/board/showthread.php?t=33821469
-
echo
Thank you, sir. Yes I should've mentioned that I have the same exact
configuration as you down to the same video card. I've been trying out various
mtrr modifications for a couple of days now to no avail. Thought instead that
I'd just see if anyone had the same exact config/setup as me
I finally have aiglx+compiz running on my Optiplex 755 with 4GB. I have
to rewrite the MTRR in /etc/rc.local. I'm not convinced that the mtrr is
in any sense optimal, but so far so good.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with
I think the issue that we are seeing, is related to the kernel thinking
that the graphics card memory is uncachable. If the mtrr tables are
changed such that the memory at d000 is set to write-back rather
than uncachable
So:
reg00: base=0xd000 (3328MB), size= 256MB: uncachable, count=1
is
I also don't know whether it should be write-back or write-combining.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received this bug notification because you are a
Is this the same bug?
https://bugs.launchpad.net/linux/+bug/210780
the suggestion is its a bios problem.
I have:
reg00: base=0x ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xcff0 (3327MB), size= 1MB: uncachable, count=1
reg02: base=0xd000 (3328MB), size= 256MB:
I think this is the same bug ... but with a different graphics card.
I've added a quick post to the bug report and hopefully they'll notice
that this also affects the people using fglrx drivers.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM
That's a very good question Greg :P
On the other hand, reconfiguring mttr tables won't damage your hardware,
but can slow down the computer like a 8086, or cause a total crash
(without BSOD xD), requiring you to reset manually.
I needed two crashes before finding a compatible mtrr table.
It's
Does anyone know why the mtrr tables aren't setup correctly? Further, is
it appropriate to reconfigure the mtrr tables by hand (I assume that if
you misconfigure it ... you might crash your computer or worse)?
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more
** Summary changed:
- MTRR is not properly setup on Intel Northbridge Chipset (P35,X38) and with
Memory Remapping Enabled
+ MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping Enabled
--
MTRR is not properly setup on Intel
37 matches
Mail list logo
