oops, sorry, now i mistyped!
I meant: echo "base=xxx size=yyy type=write-combining" >| /proc/mtrr
:)
-Bartek
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification because you are a member of Ubuntu
Bugs, whi
@ste: please read the instructions more carefully, the command is:
echo "base=xxx size=write-combining" >| /proc/mtrr
the pipe is important, so is the space. Also, if the base address you
posted above does not work, try removing the extra zero after the x.
Or you could try my script in the post
@ste: please read the instructions more carefully, the command is:
echo "base=xxx size=write-combining" >| /proc/mtrr
the pipe is important, so is the space. Also, if the base address you
posted above does not work, try removing the extra zero after the x.
Or you could try my script in the post
@ste: please read the instructions more carefully, the command is:
echo "base=xxx size=write-combining" >| /proc/mtrr
the pipe is important, so is the space. Also, if the base address you
posted above does not work, try removing the extra zero after the x.
Or you could try my script in the post
I get the same error as Gem on comment #29
(https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/314928/comments/29) running the command below:
r...@miniderfel:~# echo "base=0x03f60 size=0x1000
type=write-combining"> /proc/mtrr
bash: echo: write error: Invalid argument
oops, sorry no, of course it wouldn't... hmm, ok how about so
** Attachment added: "check whether mtrr range has been set up, move 0x
prefixes to echo"
http://launchpadlibrarian.net/26193373/fixmtrr.sh
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.
@Iain: that wouldn't quite work because the base is prefixed with
another zero in the /proc/mtrr output (and I'm not sure whether this is
always the case), but changing the grep argument to just $address should
work. Thank you.
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
ht
Can I suggest that the script is changed so that if that address is
already present in the mtrr then it doesn't add it (otherwise, each time
you add it a count variable is incremented). I'm not sure if this could
realistically happen if you're running it only when x starts and x
clears it when it s
@molecule-eye: What I mean by automate is that one does not have to manually
hunt for the correct base address and size. With some tweaks it could probably
be packaged as a workaround until the drivers are fixed.
The script should be run by the display manager (ie gdm) to ensure persistence.
--
@Bartek: I haven't looked at the script, but it's extremely easy to add
the "echo..." line to your (probably empty) /etc/rc.local file, which
will automate the process for you (as already recommended by sunken).
However, as noted by Francois, the mtrr entry is reset if you kill X
(e.g. by logging o
Is this an acceptable automatic hack for the missing MTRR range? I
realise there might be a problem when two VGA controllers are present,
but at least it does not require user interaction (if run as root).
** Attachment added: "fixmtrr.sh"
http://launchpadlibrarian.net/26188260/fixmtrr.sh
--
Guys, I think this explains why 2.6.30RC2 performance is hugely better
for me than 2.6.28-11.
I currently have two kernels installed.
2.6.30-020630rc2-generic
2.6.28-11.42-generic
Under the 30RC2 kernel, I see the following in kern.log (good news, I assume!)
Apr 27 10:40:39 vademecum kernel: [
Looks like there is more than enough information here to send this to
the intel driver developers.
I strongly recommend that someone who experiences this bug and
understands the issues opens a high quality bug report at
http://bugs.freedesktop.org/ (file against xorg and set component field
to Dri
I've had a good, long hack away at getting the fix above to stick
whenever you log into x (surely there must be a way of doing it through
/etc/X11/xinit?) but I can't get it to stay.
My solution has been to create a script containing the above, add that
script to sudoers, then make gnome run that
lspci -v
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated
Graphics Controller (rev 02)
Subsystem: Dell Device 01da
Flags: bus master, fast devsel, latency 0, IRQ 2300
Memory at dfe0 (32-bit, non-prefetchable) [size=1M]
Memory at c
After a little reading around, I think this might be something to do
with the acer bios: apparently it acquires all of the mtrr registers for
itself (I've set the mtrr cleanup kernel option and now there are only 4
in /proc/mtrr)
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
I'm using Jaunty (UNR) but my /proc/mtrr looks quite different. Not sure
if this is something that's been configured by the UNR people or if it's
generated by the ubuntu installer, but I have 8 registers defined!
> cat /proc/mtrr
reg00: base=0x0fffe ( 4095MB), size= 128KB, count=1: write-prot
Sorry, forgot to mention that I'm using a GM945/Acer Aspire One. And I
haven't modified /proc/mtrr at all.
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Gem: provide your lspci -v output (by typing "lspci -v" in the console)
for the VGA Compatible Controller.
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification because you are a member of Ubuntu
Bugs, which i
It's been three months - what's the plan to fix this (esp. given all the
other performance problems [intel] graphics users are having) ?
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification because you are a m
I also don't understanding how to fix the bug for me.
this is my lspci
00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev
02)
00:01.0 PCI bridge: Intel Corporation 82Q963/Q965 PCI Express Root Port (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q9
This fixes Bug #346289 for me:
Choppy Flash playback in full screen.
https://bugs.launchpad.net/ubuntu/+bug/346289
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification because you are a member of Ubuntu
Bugs,
@Guido: You can do exactly what I did. Type the following in terminal.
sudo -s
echo "base=0xc000 size=0x1000 type=write-combining" > /proc/mtrr
The size=0x1000 parameter specifies (in hex) 256MB.
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchp
Excuse me but I don't understanding how to fix the bug for me!
this is my lspci
Region 0: Memory at b008 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 1800 [size=8]
Region 2: Memory at c000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at b000 (32-bit, non-prefet
how did I fix this?
settings/preferences/compiz config settings manager in the general tab uncheck
Unredirect fullscreen windows and that is it, no more choppy full screen video
on youtube. hope this helps. marjan.
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs
I can also confirm very choppy fullscreen flash playback and that the
fix provided in the original bug report works.
Here is my /proc/mtrr before the fix:
reg00: base=0x0 (0MB), size= 1024MB, count=1: write-back
reg01: base=0x03f70 ( 1015MB), size=1MB, count=1: uncachable
reg0
This bug affect the MSI Wind too:
uptodate Jaunty:
% lspci -vvnn
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller [8086:27ae] (rev 03)
Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
Control: I/O+ Me
I've fixed issues with my intel VGA adding VideoRam option in xorg.conf
http://ubuntuforums.org/showpost.php?p=7121605&postcount=34
I did not touch /proc/mtrr
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notificati
Francois - similar thread
(http://ubuntuforums.org/showpost.php?p=7078262&postcount=35) with one
answer I devised - if you find a simpler method please let everyone
know. Thanks
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received
I can confirm that
echo "base=0xe000 size=0x1000 type=write-combining" > /proc/mtrr
fixes choppy fullscreen flash issues on an Intel Corporation Mobile
GME965/GLE960 Integrated Graphics Controller in Ubuntu Jaunty 9.04
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
h
@Sunkem. Thanks. But that only works for your first xorg session. If you
kill the X server (or log out/back in), the mtrr setting disappears.
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification because you ar
When you've found the line that works best for your system you could add
it to /etc/rc.local
In my case:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to
One thing to do is to add the echo line to /etc/rc.local
2009/4/20 Francois Rigaut
> Thanks for the fix. Got the same problem with a GM945, and this seems to
> fix it.
> I've read somewhere in this thread that the new line in /proc/mtrr gets
> wiped out after a reboot (or X restart?). Do any of
Thanks for the fix. Got the same problem with a GM945, and this seems to fix it.
I've read somewhere in this thread that the new line in /proc/mtrr gets wiped
out after a reboot (or X restart?). Do any of you have any advice on how to
implement this fix so that it survives reboots?
I mean, it's a
On my aspire one 110L running jaunty (freshly updated) this doesn't work:
# echo "base=0x6000 size=0x1000 type=write-combining" > /proc/mtrr
bash: echo: erro de escrita: Dispositivo sem espaço livre
(which is the translation for "write error:device full", I think)
lspci -vvnn:
00:02.0 VGA
Bryce & others,
It seems this issue is relevant to many (if not all?) Intel chipset
users. I have access to three systems with integrated graphics - a
900GMA desktop, 865G desktop and 855GM laptop - and none of these
systems setup write-combining MTRR ranges properly.
Although this causes issues
Thanks, fixed video playing/youtube problems on my Toshiba Tecra A8 (i945 GM).
Seems this problem affects many Intel GPU...
Detailed:
#lspci -vvnn
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
ok, the here proposed fix really helps, thank u so much, so what i did was this:
first checked for the region:
lspci -vvnn:
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04)
Subsystem: Uniwill Computer Corp
hello there,
i landed here after a long www odysee related to that new choppy flash in
fullscreen issue in jaunty alpha.
onboard chip i915gm
typing this into terminal: cat /proc/mtrr
gives me those quite minimal info...
reg00: base=0x0 (0MB), size= 2048MB, count=1: write-back
reg01:
I can confirm this on a DELL Inspiron 510m laptop & Jaunty, with all the
latest updates. The most notable problem I experience is stuttering
video through Totem (using the standard GStreamer backend, Xv output)
and other media players.
Relevant lspci -vvnn output:
00:02.0 VGA compatible controlle
** Summary changed:
- [915GM] MTRR entry missing since jaunty - is this intentional?
+ [i915GM] MTRR entry missing since jaunty - is this intentional?
--
[i915GM] MTRR entry missing since jaunty - is this intentional?
https://bugs.launchpad.net/bugs/314928
You received this bug notification beca
41 matches
Mail list logo
