This is a master bug report, and no more logs are required despite the
automated message. Besides, the upstream bug report has been closed as
FIXED RESOLVED.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu Lucid)
Status: Incomplete =
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/605124
Title:
[965gm] No screens on
Note that the upstream 845G bug report has been reopened. It turned out
that the fixes (which are contained in Brian's PPA kernel) are
insufficient to fix the 845G-specific problem completely. The kernel
will probably improve stability on 845G, but I think adding results from
845G to the upstream
I have previously used the instructions at
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . Instead of getting
the vanilla upstream kernel in #2, I would use the drm-intel-next head
from git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git.
Then you would need to apply the patch
There is a (yet another) new kernel patch in the upstream bug report that has
the potential to fix this bug once and for all:
https://bugs.freedesktop.org/show_bug.cgi?id=27187#c281
I don't have the resources (full hard drive and other limitations) to
build a Ubuntu kernel package with this
Note that the new patch upstream fixes the 845G-specific part of this
bug. The 845G also suffers from the same i8xx incoherency that the 855GM
suffers from (LP bug 541511). There is a patch for that as well at
https://bugs.freedesktop.org/show_bug.cgi?id=27187#c281, but this has
not been commited
For completeness, I should add that the upstream fix introduces another
bug which may cause some corruption. This one is fixed in this commit:
commit dc3bfebcf77d943b7e8495d30d0ee3d01b3042a5
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Thu Dec 30 18:02:21 2010 +
drm/i915: Don't
Why was this closed. Because you hope it's fixed?
Same issue on Fedora 12:
I do hope it is fixed, but that was not the reason I closed the bug
report.
It is an unfortunate reality that there is not enough people with
enough time to handle ubuntu and specifically xserver-xorg-video-intel
bug
I agree that it is not worth the trouble putting this through as an SRU.
--
Failsafe X displays variable name instead of file name for debugging tarball
https://bugs.launchpad.net/bugs/596819
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
On Mon, Aug 9, 2010 at 1:59 AM, Warren E. Downs wrote:
Regarding ppa kernel.ubuntu.com/~kernel-ppa/mainline/, I tried adding
the source but it wasn't recognized. I noticed that there is no 'dists'
directory under it like apt expects. Is there another source or do I
have to install the kernel
** Summary changed:
- [IGDgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003)
+ [pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003)
** Tags added: pineviewgm
--
[pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003)
https://bugs.launchpad.net/bugs/609717
You received this bug notification
** Summary changed:
- [IGDgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003)
+ [pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003)
** Tags added: pineviewgm
--
[pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003)
https://bugs.launchpad.net/bugs/607207
You received this bug notification
** Tags added: 915gm
** Summary changed:
- Dual monitor instability - reverts to low graphics mode
+ [915gm] Dual monitor instability - reverts to low graphics mode
--
[915gm] Dual monitor instability - reverts to low graphics mode
https://bugs.launchpad.net/bugs/608434
You received this bug
** Tags added: 945gm
--
[i945gm] GPU lockup d0c69edf
https://bugs.launchpad.net/bugs/611951
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
___
Mailing list:
Running intel_error_decode on the attached i915_error_state.txt shows
that there is a page table error and that the ringbuffer is completely
empty:
Time: 1280551135 s 109870 us
PCI ID: 0x27a2
EIR: 0x0010
PGTBL_ER: 0x0001
INSTPM: 0x
IPEIR: 0x
IPEHR: 0x
** Tags added: resume suspend
--
[i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001)
https://bugs.launchpad.net/bugs/611951
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
I have forwarded this bug the intel developers at
https://bugs.freedesktop.org/show_bug.cgi?id=29345 . Please register at
bugs.freedesktop.org, add yourself to the CC: field of that bug report,
and respond to any requests made by the intel developers. If you need
help with fulfilling any of these
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Triaged
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = Low
--
[i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001)
https://bugs.launchpad.net/bugs/611951
You received this bug notification because
** Summary changed:
- Lucid - Intel Integrated Graphics freezes when external monitor is plugged in
+ [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor
is plugged in
--
[arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is
plugged in
** Tags added: arrandale dual-head freeze
** Tags removed: freezing monitor syncmaster
--
[arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is
plugged in
https://bugs.launchpad.net/bugs/610387
You received this bug notification because you are a member of Ubuntu-X,
Great troubleshooting, Corona! I don't know enough kernel stuff to know
if this means that the dell-wmi is the troublemaker or it simply needs
an update to silence an innocent message. Hopefully the kernel people
know that better, so I think it's time that I send this over there. I am
not sure if
** Description changed:
Binary package hint: xserver-xorg-video-intel
I cannot hook up an external monitor or beamer to my Dell Latitude E6510
using the VGA port. When I open the monitors dialogue, the screen goes black
if there is a VGA cable plugged in. Only alt-sysrq-REISUB works to
Following upstream and closing this bug report.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Released
--
[gm45] system locks up at random intervals, except mouse
https://bugs.launchpad.net/bugs/469820
You received this bug notification because you are a member
- When I plug in the VGA cable and switch to VT1, the screen goes black,
even when I don't run `xrandr -q` first, so that doesn't give any
additional info.
What if you switch to VT1 and then plug in the monitor? Possibly it
will hang when you switch back to X. If that is the case, what if you
Chris, good to see that this is on your radar. I wasn't aware that you
were also following Ubuntu bug reports. I was simply hoping that the
kernel triagers would know better how to extract some useful information
about the black screen (which takes down the ssh connection) before
forwarding it
*** This bug is a duplicate of bug 604885 ***
https://bugs.launchpad.net/bugs/604885
Marking this as a duplicate to bug 604855, since this is troubleshooting
information for that bug report.
** This bug has been marked a duplicate of bug 604885
No main text between the two lateral frames
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel
developers are still scratching their head about this. This is what
Chris Wilson writes:
We have big issues with GEM on i8xx. i845 is even
** Summary changed:
- VGA port not working on Dell Latitude E6510 (arrandale, Intel Core i5)
+ [arrandale] VGA port not working on Dell Latitude E6510
** Tags added: arrandale dual-head
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Confirmed
** Changed in:
In addition to bug 596082, there is also bug 599626 which is very similar. In
that case I gave up and moved to the linux package, since I couldn't find a way
to extract relevant logs. That hasn't been touched for the last two weeks,
though, but I'm afraid this may go the same way eventually.
Dmitry, the Ubuntu bug already has status 'Fix Released'. The upstream
task should be updated automatically from the upstream task.
Btw, I don't think it was the commit you mentioned that fixed this
particular bug, since it has also been working in Maverick before that
commit. That commit
Robert, with the upgrade to kernel 2.6.35-8.13, xorg doesn't have problems, but
the kernel oops still happens. Results from testing with 2.6.35-8.13:
vesafb=fubar doesn't seem to change anything (it still get kernel oops
sometimes, but not always)
gfxpayload=text seems to stop the problems. I
Corona, most bug reports will never be assigned to anyone. After
screening and finding the most relevant symptoms, we report in to the
upstream developers who then look at and hopefully fix the bug. Then the
fix is pulled into ubuntu, either by a regular driver update or a patch.
This bug report
Thank you, takashi. I have reopened the upstream bug report and copied
your comment and dmesg there. There will probably be more questions in
the upstream bug report. Please answer those there directly.
--
[i945] X Freezes when compiz enabled
https://bugs.launchpad.net/bugs/475429
You received
Tomas, the question in comment #59 was meant for the original reporter
of the bug, takashi torigoe (sorry for not specifying that). These kind
of bugs may look exactly the same but have totally different underlying
causes, so your freeze may be an unrelated bug.
If you are the experiencing
Following upstream and closing since patches can't be tested.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Invalid
--
[i945G] Samsung TV not detected on VGA output (no screens)
https://bugs.launchpad.net/bugs/379157
You received this bug notification because you are
** Bug watch added: freedesktop.org Bugzilla #29048
http://bugs.freedesktop.org/show_bug.cgi?id=29048
** Also affects: xserver-xorg-video-intel via
http://bugs.freedesktop.org/show_bug.cgi?id=29048
Importance: Unknown
Status: Unknown
--
[965gm] No screens on startup:
The patch that fixed (or rather worked around) this problem in Lucid has
not been applied upstream because the developers figure it is not
necessary anymore due to some other fixes. The Maverick kernel has been
without this patch for quite some time now. Could someone that was
affected with this
Thank you for testing Nicolò. I will close the upstream bug report.
--
[gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the
laptop lid)
https://bugs.launchpad.net/bugs/535640
You received this bug notification because you are a member of Ubuntu-X,
which is the
I can now confirm this myself. I have installed a Maverick partition and
got a no screens when booting with an external monitor attached and X
in low-graphics mode. Thanks to Glen for already finding out where the
failsafeX-backup-tar went.
** Description changed:
Binary package hint: xorg
The problem is in line 177 of debian/local/Failsafe/failsafeXinit. There
is an \ before the $ in $xorg_backup_file which shouldn't be there.
Since there is an eval_gettext at the beginning, the varable name was
probably supposed to be part of the preceding string. So either remove
the \ or do
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I just installed Maverick on a partition yesterday. Sometimes (i.e. 2
out of 5 or 6 times so far) when booting with an external monitor
attached I get a no screens error in the log and get xorg in low-
graphics mode. I haven't
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51880252/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/51880253/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51880254/Dependencies.txt
**
** Attachment added: dmesg with 0x04 when the problem does not occur
http://launchpadlibrarian.net/51882987/dmesg-fine.txt
--
[965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor
https://bugs.launchpad.net/bugs/605124
You received this bug notification
** Attachment added: Xorg.0.log from when the problem does not occur
http://launchpadlibrarian.net/51883077/Xorg.0.log.old
--
[965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor
https://bugs.launchpad.net/bugs/605124
You received this bug notification
It turns out that this can happen also without an external monitor
attached, so I will remove that part of the description. I will upload
dmesg and Xorg.0.log, for a bad and fine session.
** Attachment added: dmesg with 0x04 without problem and without external
monitor
** Attachment added: Xorg.0.log without external monitor and without problem
http://launchpadlibrarian.net/51883838/Xorg.0.log
--
[965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor
https://bugs.launchpad.net/bugs/605124
You received this bug notification
** Attachment added: dmesg with 0x04 with problem and without external monitor
http://launchpadlibrarian.net/51885206/dmesg-noexternal-bug.txt
--
[965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor
https://bugs.launchpad.net/bugs/605124
You received this
** Attachment added: Xorg.5.log without external monitor with problem
http://launchpadlibrarian.net/51885483/Xorg.5.log
--
[965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor
https://bugs.launchpad.net/bugs/605124
You received this bug notification because
** Attachment added: /var/log/gdm/:5.log with problem
http://launchpadlibrarian.net/51885543/%3A5.log
--
[965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file
descriptor
https://bugs.launchpad.net/bugs/605124
You received this bug notification because you are a member
** Description changed:
Binary package hint: xserver-xorg-video-intel
I just installed Maverick on a partition yesterday. Sometimes (i.e. 2
out of 5 or 6 times so far) when booting with an external monitor
attached I get a no screens error in the log and get xorg in low-
graphics
I saw the line
Pid: 343, comm: plymouthd Not tainted 2.6.35-7-generic #12-Ubuntu
7764CTO/7764CTO
in the dmesg output, so I tried to remove the kernel options quiet splash,
but to no avail. dmesg looks the same to me, but is attached.
** Attachment added: dmesg with drm.debug=0x04 without quiet
** Description changed:
Binary package hint: xserver-xorg-video-intel
I just installed Maverick on a partition yesterday. Sometimes (i.e. 2
- out of 5 or 6 times so far) when booting with an external monitor
- attached I get a no screens error in the log and get xorg in low-
- graphics
Robert Hooker wrote in comment #3:
It looks like our friend bug #535640 is back as the patch fixing that is not
upstream yet.
I suppose we talk about:
SAUCE: drm/i915: don't change DRM configuration when releasing load detect pipe
It looks like that patch is not going to end up upstream. See
According to the upstream bug report, two commits to the kernel should
fix this bug. The commits are included in the current Maverick kernel.
Could you verify that this now works in Maverick?
--
[i945] X Freezes when compiz enabled
https://bugs.launchpad.net/bugs/475429
You received this bug
If the GPU locks up, the output of intel_error_decode is often more
interesting than intel_gpu_dump (unless the kernel hasn't noticed yet).
If X is able to restart properly, it indicates that the GPU is working
which may be because its state has been reset. dmesg is most interesting
with
** Summary changed:
- Xorg freeze
+ [arrandale] Xorg freeze
** Tags added: arrandale
--
[arrandale] Xorg freeze
https://bugs.launchpad.net/bugs/601366
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
Andreas, with the script /usr/share/apport/apport-gpu-error-intel.py we
are (ab)using the crash report system to automatically collect
information about a GPU error. So it is not really the application
apport-gpu-error-intel.py that has crashed.
Often a GPU error will cause the computer to freeze
I think Bryce adds those tags automatically, so he may not see this.
However, it's partly correct:
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.32-21-generic
This is the Lucid kernel running on a Maverick system. I guess Bryce's
script looks at the kernel to
Looking a little closer at the timing, I notice something strange. In the
automatically collected information there is:
Date: Tue Jul 6 21:01:05 2010
which is when the GPU error happened and the logs should have been collected.
You reported the bug the next day (2010-07-07 - doesn't say what time
I take it that the original problem is now fixed, and I therefore close
this bug report.
The missing effects in KWin may be a bug in KWin, mesa, and others and
you may file a new bug report for that.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = High
** Changed in:
Bonne, try to be very explicit in your comments. When you say in comment
#15 but it gives exactly the same results I interpret that as same
results as with the current Ubuntu kernel, not same result as the
LiveCD. I hope that is correct.
There have been cases before where a problem does not occur
Good to hear that this is now working with the new kernel. I'm not sure
which of the patches listed in the changelog could have fixed it.
PGTBL_ER being anything but zero means that the graphics hardware has
detected a page table error, i.e. some kind of corruption in the table
that maps GPU
The newest Ubuntu kernels (2.6.35-7) are based on -rc4 and therefore
include the eDP patch. Could you verify that the display problem is gone
with this kernel? If this kernel introduces the keyboard and trackpad
problem, please file a new bug report for that.
** Changed in:
Good that the display now lights up. If I understand you correctly you
have a working computer if you use an external mouse and keyboard. The
mouse/keyboard problem is probably unrelated to the original problem. It
may be related to using a daily build (it is possible that the mainline
build of
It seems that you tested the mainline build of 2.6.35-rc1, while 2.6.35-rc3 was
the newest at that point (now it's -rc4). That could be the source of the other
problems. There was a discussion on the intel-gfx mailing list about
hibernation causing memory corruption on intel hardware last week.
Never mind the acpi_osi option, since I see that you already use that
(and acpi_backlight).
--
[pineviewgm] Backlight changes at random, brightness applet doesn't work
https://bugs.launchpad.net/bugs/596742
You received this bug notification because you are a member of Ubuntu-X,
which is
Yorkim, I just got an EEE PC 1005P which had a similar issue. It
happened both in Windows 7 and Ubuntu 10.04. Updating the BIOS from
version 901 to 1103 fixed the problem. You may try to update the BIOS
and see if it fixes the problem. On bug 513921 there are some
suggestions for how to override
I thought I would have to get a patched kernel image built for you to
test this, but v4 of the patch is now commited and has found its way to
the latest daily ubuntu mainline build already [1] (see [2] for more
information about the mainline builds). It will also be included when
2.6.35-rc4 is
Bonne, what exactly do you mean by it worked the second time? Do you
mean that there was no freeze or that it froze but did not bring the
network down? If it froze, the logs show that this is not a GPU hang as
I first suspected.
Do you connect to the computer via wireless? The wireless networking
Thank you for finding out what the real problem was. I will close this
bug report.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Invalid
--
[g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ]
https://bugs.launchpad.net/bugs/592044
You received this bug
Good!
There are a few more things I am a little confused about.
I assume the files from comment #1 are uploaded from the NX-session.
Is the XorgLog.txt from an X-session that you run in the NX-client or
a non-working X-session that should have displayed on the VGA monitor?
Usually when the
** Tags added: arrandale freeze
** Summary changed:
- X freezes after plugging in external monitor and selecting
SystemPreferencesMonitors
+ [arrandale] X freezes after plugging in external monitor and selecting
SystemPreferencesMonitors
** Tags added: dual-head regression-update
--
** Summary changed:
- Xorg freeze Intel 945GM
+ [945GM] Xorg freeze
--
[945GM] Xorg freeze
https://bugs.launchpad.net/bugs/599149
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
** Tags added: gm45
** Summary changed:
- Xorg freeze
+ [gm45] 2x Print-Screen makes individual windows or whole desktop freeze
--
[gm45] 2x Print-Screen makes individual windows or whole desktop freeze
https://bugs.launchpad.net/bugs/599047
You received this bug notification because you are a
** Summary changed:
- Xorg freeze on Firefox on one particular page
+ [gm45] Xorg freeze on Firefox on one particular page
** Tags added: freeze gm45
--
[gm45] Xorg freeze on Firefox on one particular page
https://bugs.launchpad.net/bugs/599017
You received this bug notification because you
** Summary changed:
- x.org crash while watching flash video
+ [945gm] x.org crash while watching flash video
** Tags added: 945gm
** Tags added: freeze
** Tags removed: 945gm
--
[945gm] x.org crash while watching flash video
https://bugs.launchpad.net/bugs/599690
You received this bug
** Tags added: arrandale
** Tags added: flicker
--
[Intel Arrandale] Screen flickers
https://bugs.launchpad.net/bugs/599360
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
There has been some progress upstream with respect to GPU hangs after
Lucid was released. We would like to find out if this is one of those
bugs or if it is still present in the latest code. In the former case we
may test patches and see if it is possible to find one or more that
fixes the
There has been some progress upstream with respect to GPU hangs after
Lucid was released. We would like to find out if this is one of those
bugs or if it is still present in the latest code. In the former case we
may test patches and see if it is possible to find one or more that
fixes the
There has been some progress upstream with respect to GPU hangs after
Lucid was released. We would like to find out if this is one of those
bugs or if it is still present in the latest code. In the former case we
may test patches and see if it is possible to find one or more that
fixes the
There has been some progress upstream with respect to GPU hangs after
Lucid was released. We would like to find out if this is one of those
bugs or if it is still present in the latest code. In the former case we
may test patches and see if it is possible to find one or more that
fixes the
There has been some progress upstream with respect to GPU hangs after
Lucid was released. We would like to find out if this is one of those
bugs or if it is still present in the latest code. In the former case we
may test patches and see if it is possible to find one or more that
fixes the
There has been some progress upstream with respect to GPU hangs after
Lucid was released. We would like to find out if this is one of those
bugs or if it is still present in the latest code. In the former case we
may test patches and see if it is possible to find one or more that
fixes the
zvaral, the output of dmesg in comment #4 is without drm.debug=0x04. You
can see the boot parameter at the end of like 4 in that file:
[0.00] Command line: BOOT_IMAGE=/vmlinuz-2.6.35-6-generic
root=UUID=abc11909-dd1a-460a-ba4c-53c7c1ebbdb8 ro
There should have been a drm.debug=0x04 in
The initial kernel patch broke another laptop with eDP panel, so there
is still some discussion on the mailing list about how to fix this.
There is a version 2 of the patch out, but that didn't fix it on another
computer which was fixed by version 1. I hope they sort it out soon, and
then we can
** Summary changed:
- 3D Poor graphics performance on Intel GM45 Express
+ [GM45] 3D Poor graphics performance
** Tags added: gm45 performance
--
[GM45] 3D Poor graphics performance
https://bugs.launchpad.net/bugs/598948
You received this bug notification because you are a member of Ubuntu-X,
** Summary changed:
- video unusable after 10.04 installation
+ [i815] video unusable after 10.04 installation
** Tags added: i815
--
[i815] video unusable after 10.04 installation
https://bugs.launchpad.net/bugs/598481
You received this bug notification because you are a member of Ubuntu-X,
There is a kernel patch on the intel-gfx mailing list that may fix this.
http://lists.freedesktop.org/archives/intel-gfx/2010-June/007216.html .
Unfortunately, it is quite involved to patch the kernel and respin a new
iso-image in order to test it. Would you have the possibility to install
** Tags added: gm45
--
[gm45] xorg intel crashing when screensaver starts
https://bugs.launchpad.net/bugs/595182
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
___
** Tags added: q35
** Summary changed:
- compiz causes SDL surfaces to stop animating
+ [q35] compiz causes SDL surfaces to stop animating
--
[q35] compiz causes SDL surfaces to stop animating
https://bugs.launchpad.net/bugs/597094
You received this bug notification because you are a member of
** Summary changed:
- xorg intel crashing when screensaver starts
+ [gm45] xorg intel crashing when screensaver starts
--
[gm45] xorg intel crashing when screensaver starts
https://bugs.launchpad.net/bugs/595182
You received this bug notification because you are a member of Ubuntu-X,
which is
zvaral, could you boot with the kernel parameter drm.debug=0x04 and
remove quiet splash just to simplify the boot process. Then upload the
output of dmesg. We would also like the output of intel_reg_dumper and a
video bios dump taken according to
1 - 100 of 1626 matches
Mail list logo
