** Tags removed: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215572
Title:
[saucy] c++config.h missing in i386
To manage notifications about this bug go to:
A few details might be relevant here. The directory searched for some of
C/C++ standard headers (libstdc++) is wrong for i386/i686 (it should
search /usr/include/c++/4.8 and /usr/include/i386-linux-gnu/c++/4.8);
(1) /usr/include/c++/4.8 is searched
(2) /usr/include/i386-linux-gnu/c++/4.8 is
I've decided to check-out the source package and check that the patches (from
debian/dkms/patches) have already been applied. I did the following:
[code]apt-get source fglrx-installer-updates[/code]
From patch/fix-build-issue-on-i386-where-TS_USEDFPU-is-no-longe.patch there
are two changes:
#1
Hardware:
Asus A8Jm (Core Duo T2400)
With a GeForce 7600 Go
I was able to use two external monitors (had to turn off the laptop
display) with twinview and 11.04. However in 11.10, when I attempt to
enable twinview on the second external monitor, nvidia-settings crashes.
Attached in the
Works Now: If I set the laptop monitor to disabled first, before trying
to enable twinview (but didn't apply any setting changes). Then enable
twinview on both monitors (a warning was output, but nvidia-settings
didn't crash and can currently use both external monitors).
--
You received this bug
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
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'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:
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).
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).
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
I think this bug and https://bugs.launchpad.net/ubuntu/+source/linux-
restricted-modules-2.6.24/+bug/224404 might be the same (however this
one is related to the mtrr issue with a fglrx driver). However, if one
use the desktop kernel from ubuntu and memory mapping enabled combined
with an ATi card
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
Okay. When you reboot an ubuntu machine it (often) will moves the output
of an important log file that was generated during the last session to a
new file. So for example:/var/log/Xorg.0.log might become
/var/log/Xorg.0.log.old . You might have to boot into recovery mode to
get a hold of the file.
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
Could you post your Xorg.0.log associated with the failed Xsession?
Could you also what glxinfo returns if you boot without loading X?
--
GDM won't load, or maybe X? With fglrx on radeon 9700 mobile. Ubuntu 8.04
https://bugs.launchpad.net/bugs/222861
You received this bug notification because
This looks similar to the issue documented in this bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/224404
--
kernel crashes on X startup with fglrx
https://bugs.launchpad.net/bugs/229467
You received this bug notification because you are a member of
I think we might need to remove the ASUS part of the title of this bug
report. Because it looks like its not restricted to just ASUS
motherboards.
** Summary changed:
- MTRR is not properly setup on Intel Northbridge Chipset (P35) and Asus
Motherboard with Memory Remapping Enabled
+ MTRR is not
Is this the same/similar to: https://bugs.launchpad.net/ubuntu/+source
/linux-restricted-modules-2.6.24/+bug/224404
--
X server won't start with 4 Gigs of ram
https://bugs.launchpad.net/bugs/226672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm going to attempt running the X server through gdb and see if I can
get a backtrace.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35,X38) and with
Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received this bug notification because you are a member of
Okay. So running /usr/bin/Xorg through gdb failed (I was unable to get a
backtrace). I was following instructions from
https://wiki.ubuntu.com/DebuggingXorg . I ran it through strace and used
the output option (it is attached to this message).
** Attachment added: strace_xorg.log
Here is the updated dmesg for the new kernel (first line is uname -a).
** Attachment added: dmesg_remapping_enabled
http://launchpadlibrarian.net/14859670/dmesg_remapping_enabled
--
MTRR is not properly setup on Intel Northbridge Chipset (P35,X38) and with
Memory Remapping Enabled
cat /proc/mtrr is attached (with memory remapping enabled)
** Attachment added: mtrr_new_kernel_memory_remapping_enabled
http://launchpadlibrarian.net/14859687/mtrr_new_kernel_memory_remapping_enabled
--
MTRR is not properly setup on Intel Northbridge Chipset (P35,X38) and with
Memory
With memory remapping disabled:
[EMAIL PROTECTED]:~$ cat /proc/mtrr
reg00: base=0x ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x8000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc000 (3072MB), size= 256MB: write-back, count=1
Attached is dmesg with memory
Is this the same problem as this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/224404
--
fglrx halts on Radeon HD 3850
https://bugs.launchpad.net/bugs/211586
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The wireless card that you are using is actually over the usb interfaces
(I've got this same issue). Try using lsusb -v.
--
rtl8187 drops connection
https://bugs.launchpad.net/bugs/182473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: xorg-driver-fglrx
In Hardy Heron (8.04). MTRR is improperly configured and causes a hard lock of
X and the entire computer (I can't use force the kernel into Raw Keyboard Input
Mode) when it attempts to use the display driver - fglrx (when using
This question has the same problem (but with different graphics card):
https://answers.launchpad.net/ubuntu/+question/31200
--
MTRR is not properly setup on Intel Northbridge Chipset (P35) and Asus
Motherboard with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received
** Attachment added: dmesg without memory remapping enabled
http://launchpadlibrarian.net/14025450/dmesg_without_memory_remapping
--
MTRR is not properly setup on Intel Northbridge Chipset (P35) and Asus
Motherboard with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You
** Attachment added: dmesg with memory remapping enabled
http://launchpadlibrarian.net/14025431/dmesg-remapping
--
MTRR is not properly setup on Intel Northbridge Chipset (P35) and Asus
Motherboard with Memory Remapping Enabled
https://bugs.launchpad.net/bugs/224404
You received this bug
31 matches
Mail list logo
