I've made a kernel with the latest fix available in this PPA:
https://launchpad.net/~brian-rogers/+archive/graphics-fixes-testing
If it gets good feedback, I'll copy it to my regular graphics-fixes PPA.
This kernel is based on Natty's 2.6.37 kernel, has the changes in drm-
intel-next applied
Hardeep, you should file a new bug report for that. It's not related to
this bug.
--
ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in
Maverick
https://bugs.launchpad.net/bugs/626974
You received this bug notification because you are a member of Ubuntu-X,
which is
Maverick now defaults to using the fbdev xorg driver by default instead
of intel for i8xx chips, and this should work around the freezing bug.
--
MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
https://bugs.launchpad.net/bugs/541492
You received this bug notification
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
This appears to be the same problem as bug 541492. It's just that most
people weren't hitting the bug with any degree of frequency until Lucid.
Duping.
** This bug has been marked a duplicate of bug 541492
Yeah, ubuntu-bug won't upload a bug report on an unofficial package
version. It also gathers and attaches the output of glxinfo in its
graphics-related bug reports, so it's pretty useless when the bug report
is glxinfo crashes X. :)
Do you have a machine to SSH into the affected system from? I
** Summary changed:
- X server crash with intel driver when using shadow option
+ [xorg-edgers] X server crash with intel driver when using shadow option
--
[xorg-edgers] X server crash with intel driver when using shadow option
https://bugs.launchpad.net/bugs/640058
You received this bug
Yeah, that's the xorg-edgers version. Do you still have Option Shadow
True in the device section of your xorg.conf? Because with shadow
buffer mode enabled, OpenGL isn't supposed to work (but it shouldn't
crash, it should just revert to software rendering).
If glxinfo says direct rendering: Yes,
*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511
I'm going to dupe this against the master bug report for i855 freezing
issues, and follow up on the periodic freezing issue there.
** This bug has been marked a duplicate of bug 541511
MASTER: [i855] GPU
A real fix was posted for the invisible cursor issue, so I incorporated
it into linux-image-2.6.35-ppa21+v9patch-generic (building now).
As for the periodic freezing issue, that is covered by this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=29536
The patches there don't apply cleanly to
My shadow branch PPA is now obsolete because the code was committed
upstream. So now you only need xorg-edgers and the xorg.conf changes to
enable a shadow buffer.
Jean-Marie, do you observe the glxinfo-triggered segfault if you remove
my shadow branch PPA and switch the xserver-xorg-video-intel
://launchpad.net
/~brian-rogers/+archive/graphics-fixes
To use this fixed kernel, run the following commands:
sudo apt-add-repository ppa:brian-rogers/graphics-fixes
sudo apt-get update
sudo apt-get dist-upgrade
- sudo apt-get install linux-image-2.6.35-ppa20+v9patch-generic
+ sudo apt-get
The invisible cursor fix will be sent to stable and make it into
Maverick that way. I don't know if it will make it in before release,
though.
As for the stability fix, Daniel Vetter has said the following:
I haven't upstreamed the patch for a few reasons:
- It's an extremely ugly approach,
In Fedora's kernel package:
http://pkgs.fedoraproject.org/gitweb/?p=kernel.git;a=tree;h=refs/heads/f13/master;hb=f13/master
I see drm-intel-big-hammer.patch. That's a patch that improved stability
somewhat, but didn't quite solve the problem. My testcase could still
kill the system. It also
The kernels in the experimental PPA are all outdated. The new kernels
are in graphics-fixes: https://launchpad.net/~brian-rogers/+archive
/graphics-fixes
Try linux-image-2.6.35-ppa20+v9patch-generic. If X starts but the cursor
is invisible, then try linux-image-2.6.35-ppa20+v9+cursorfix-generic
I'd like to point out that this isn't just an nvidia bug. It was
originally filed for an ati card, and I'm seeing the problem with intel
graphics. It's most likely a kernel/VT bug.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You
2.6.35-20 blacklists KMS on the problematic cards. X is then supposed to
fall back to vesa. If it doesn't, a bug should be filed for that. If
falling back to vesa has enough problems of its own, that decision might
be reversed.
i915.modeset=1 will override the blacklist, so you can always turn
Also, to catch up with an older comment...
John, Intrepid's driver can't be built for a newer system. I'm also not
sure it would solve the problem if someone forward-ported it. As far as
I can tell, the driver has always been broken for these chipsets, but
was being used in just the right
Yeah, a separate bug should be filed because it means either the system
failed to fallback to vesa when KMS wasn't available or the vesa driver
didn't work right.
--
MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
https://bugs.launchpad.net/bugs/541492
You received this bug
David, I just uploaded a new kernel (currently building for both Lucid
and Maverick) that reverts the commit that caused the invisible cursor
regression. That way you or anyone else experiencing this bug isn't
stuck on an RC kernel until there's a proper fix.
The new kernel is
Can you get a dmesg from after the screen freezes? You might have to ssh
in from another computer to do it.
--
Maverick screen freeze with shadow intel driver
https://bugs.launchpad.net/bugs/628556
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
You mean that it freezes temporarily, then resumes, like a stuttering
behavior? In that case, do new messages appear in dmesg after a freeze?
--
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of
://launchpad.net
/~brian-rogers/+archive/graphics-fixes
To use this fixed kernel, run the following commands:
sudo apt-add-repository ppa:brian-rogers/graphics-fixes
sudo apt-get update
sudo apt-get dist-upgrade
- sudo apt-get install linux-image-2.6.35-v9patch+19-generic
+ sudo apt-get install
Does adding
Option UseEvents True
into your xorg.conf's Device section help?
That option has always improved things for me.
--
nVidia card : X won't start since 1.9 update, no screens found
https://bugs.launchpad.net/bugs/616023
You received this bug notification because you are a member of
I found a bug report for the invisible cursor issue. It's bug 614176
here and upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=29413
When there's a fix, I'll put up a new kernel including it. I'll be
providing maverick kernels soon as well, so once the cursor bug is
fixed, maverick
Yeah, the shadow buffer mode does disable OpenGL. I forgot to mention
it. It's a sort of safe mode that's a more functional alternative to the
vesa driver.
I'm refreshing the kernels in my graphics-fixes PPA, since
2.6.35-v9patch1 is getting kind of stale. There have been relevant fixes
in the
://launchpad.net
/~brian-rogers/+archive/graphics-fixes
To use this fixed kernel, run the following commands:
sudo apt-add-repository ppa:brian-rogers/graphics-fixes
sudo apt-get update
sudo apt-get dist-upgrade
- sudo apt-get install linux-image-2.6.35-v9patch1-generic
+ sudo apt-get install
John, comments like yours aren't useful. If you don't want to test
something that might solve your problem, you're completely free to keep
quiet.
--
MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
https://bugs.launchpad.net/bugs/541492
You received this bug notification
Developer Chris Wilson has published a branch of xserver-xorg-video-
intel which accesses the graphics card differently and avoids the kinds
of operations that cause problems with the old chipsets.
I created a PPA for it: https://launchpad.net/~brian-rogers/+archive
/intel-shadow
This branch
Developer Chris Wilson has published a branch of xserver-xorg-video-
intel which accesses the graphics card differently and avoids the kinds
of operations that cause problems with the old chipsets.
I created a PPA for it: https://launchpad.net/~brian-rogers/+archive
/intel-shadow
This branch
Skip, if you haven't wiped your 10.04 system yet, what happens if you
remove the 'Option Shadow True' part? I'm curious if the shadow
buffer mode is introducing a new problem or just not fixing an existing
problem. If normal 10.04 fails to even show the login screen, then how
did you get that
://launchpad.net
/~brian-rogers/+archive/graphics-fixes
To use this fixed kernel, run the following commands:
sudo apt-add-repository ppa:brian-rogers/graphics-fixes
sudo apt-get update
sudo apt-get dist-upgrade
- sudo apt-get install linux-image-2.6.34-v9patch-generic
+ sudo apt-get install
Sorry, the instructions at the top of this bug were outdated and
referenced an older version of the patched kernel. I fixed that now.
Here's the command to install the newest kernel in my PPA:
sudo apt-get install linux-image-2.6.35-v9patch1-generic
If you're still on 9.04 these instructions
** Changed in: xserver-xorg-video-intel
Remote watch: freedesktop.org Bugzilla #29054 = freedesktop.org Bugzilla
#28573
--
[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 Ubuntu-X,
which is
I just uploaded some new kernels:
linux-image-2.6.35rc4-131+ge467e10+nopatch-generic
linux-image-2.6.35rc4-131+ge467e10+v9patch-generic
Julien, do these kernels help the suspend issue?
--
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug
://launchpad.net
/~brian-rogers/+archive/graphics-fixes
To use this fixed kernel, run the following commands:
sudo apt-add-repository ppa:brian-rogers/graphics-fixes
sudo apt-get update
sudo apt-get dist-upgrade
- sudo apt-get install linux-image-2.6.34-52-generic
+ sudo apt-get install linux
upstream at
http://bugs.freedesktop.org/show_bug.cgi?id=26345 . For now, we mark all
automatically reported GPU lockups as duplicates of this unless there is
a reason not to.
A fixed kernel is available at https://launchpad.net/~brian-
rogers/+archive/graphics-fixes
To use this fixed
Julien, did you try linux-image-2.6.34-v9patch-generic from ppa:brian-
rogers/graphics-fixes ? It's based on the final 2.6.34, so should have
some bug fixes. But if it doesn't work as well as 2.6.34rc7-51-generic,
then there's some sort of regression and we'll try to hunt it down.
--
MASTER:
- with this patch for others to test, that would be nice.
+ to.
+
+ A kernel with the proposed fix is available at https://launchpad.net
+ /~brian-rogers/+archive/graphics-fixes
+
+ To use this fixed kernel, run the following commands:
+
+ sudo apt-add-repository ppa:brian-rogers/graphics-fixes
+ sudo apt-get
I just updated the bug description to point at my PPA containing a
kernel with the proposed fix. I would advise people to try this kernel,
because it has had plenty of positive feedback so far. Then people can
report how it goes, and we can aggregate the data and report it
upstream.
--
MASTER:
current kernel
and includes Ubuntu-specific patches, unlike a typical upstream kernel
build. The 32-bit build is building right now and should be available
within a few hours.
The PPA is here: https://launchpad.net/~brian-rogers/+archive/graphics-
fixes
This PPA also contains a fix for a 3D-specific
://launchpad.net/~brian-rogers/+archive/graphics-fixes
+ To use this fixed kernel, run the following commands:
+ sudo apt-add-repository ppa:brian-rogers/graphics-fixes
+ sudo apt-get update
+ sudo apt-get dist-upgrade
+ sudo apt-get install linux-image-2.6.34-52-generic
+
+ NOTE: As of May 26th, 3:54 PM PST
upstream at
http://bugs.freedesktop.org/show_bug.cgi?id=26345 . For now, we mark all
automatically reported GPU lockups as duplicates of this unless there is
a reason not to.
- A fixed kernel is available at
https://launchpad.net/~brian-rogers/+archive/graphics-fixes
+ A fixed kernel is available
That's the information page for the PPA. You'll find instructions for
adding it there.
But my 'experimental' PPA with a patched kernel is a better option:
https://launchpad.net/~brian-rogers/+archive/experimental
To add it, add this to your sources: ppa:brian-rogers/experimental
Then after
Is there 64-bit capable hardware with i8xx graphics? I just assumed it
was too old for that. I'm going to post a 2.6.34 (final release) kernel
with the latest patch for this bug to my PPA. If there are i8xx machines
with 64-bit, I'll make sure to include a 64-bit build.
--
MASTER: [i855] GPU
If Ubuntu releases were held up by this kind of bug, Karmic wouldn't be
out yet. I helped reinstall Jaunty for someone with an i845 that was
locking up on Karmic, for example. And in retrospect, that system had
graphical issues even before Jaunty, such as freezing on the splash
screen until a VT
They did blacklist KMS support for i8xx in an attempt to fix this, but
that didn't work for everyone. I believe reverting to vesa was
considered, but that has its own regressions including bad performance,
lack of multi-monitor support, and often even a lack of support for a
laptop's native
The kernel patch from this bug might help:
https://bugs.freedesktop.org/show_bug.cgi?id=27187
I placed a kernel with the newest version of the patch in my experimental PPA:
https://launchpad.net/~brian-rogers/+archive/experimental
If it helps, you can provide feedback in the upstream bug
Alban, there is warning of this bug in the release notes:
http://www.ubuntu.com/getubuntu/releasenotes/1004#Intel%208xx%20X%20freezes/crashes
It's also a bug in the upstream code that every distro pulls from, so
it's going to affect every linux distro in existence. You can't escape
it by
I have a kernel available in this PPA that might help:
https://launchpad.net/~brian-rogers/+archive/experimental
--
MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
https://bugs.launchpad.net/bugs/541492
You received this bug notification because you are a member of Ubuntu-X
For those who need it, I have a kernel with Daniel Vetter's patch in my
experimental PPA: https://launchpad.net/~brian-
rogers/+archive/experimental
--
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member
FYI, the fix I was referring to in the earlier comment has since been
included in Lucid and therefore I removed the package from my PPA. The
kernel in there is a new, different fix from an upstream bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=27187
Glad to hear it helps.
Anyway, a
I don't expect disabling KMS to help overall. The nature of this bug is
that it's timing-dependent, so just about any change can affect the
stability for better or worse. On an affected system, I would often get
a repeatable freeze on bootup after upgrading an unrelated package just
because the
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
Gdk-WARNING is just a toolkit warning, so it's not a sign of any GPU-
related problems.
--
[i845G] Lucid Beta 2.6.32-17 browsing Lucid forum screen went black no keyboard
I recommend trying the experimental kernel with xorg-edgers. Or if not
that, the standard packages.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Released = Confirmed
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
I have a kernel for people to try in my experimental PPA:
https://launchpad.net/~brian-rogers/+archive/experimental
It contains the gtt chipset flush v7 patch from
http://bugs.freedesktop.org/show_bug.cgi?id=27187 on top of linux
2.6.34-rc3. This patch has managed to stabilize the system for some
Flabdablet, can you try Lucid + xorg-edgers? The upstream driver has
additional bugfixes that may be relevant.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is
OK, at this point, I recommend the xorg-edgers PPA for testing. It now
has the newest xserver-xorg-video-intel driver, as well as libdrm and
Xorg. Updating just the first part may have caused some stability
issues. Does xorg-edgers experience the freezing issue?
--
[i845g] Karmic stops
Oh, here is the link:
https://launchpad.net/~xorg-edgers/+archive/ppa
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
There are potential fixes for this in the upstream development version. I
uploaded it for Lucid to the following PPA:
https://launchpad.net/~brian-rogers/+archive/experimental
I can't simply upload this version for Karmic because it requires new
versions of support libraries, but I can backport
There are potential fixes for this in the upstream development version. I
uploaded it for Lucid to the following PPA:
https://launchpad.net/~brian-rogers/+archive/experimental
I can't simply upload this version for Karmic because it requires new
versions of support libraries, but I can backport
Can you try Jaunty's kernel on Karmic and Karmic's kernel on Jaunty, to
see if the difference in stability is due to the kernel versions?
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a
That's interesting because those are essentially the same versions that
were unstable for you in Karmic. Can you attach /var/log/Xorg.0.log for
both Karmic and Jaunty running graphics-testing?
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
Flabdablet, any console switching issues are most likely separate bugs
that have already been fixed in newer versions. Only random freezing
during general use is important. Do you see that with my current Jaunty
PPA packages?
crazybyte, the best workaround is probably using nomodeset and setting
OK, I have libdrm 2.4.11 for Jaunty and a rebuild of the Intel driver
queued up.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
I think the 2.6.32-50 kernel I uploaded for Lucid might perform better. If you
want to try it in Karmic, you can get it directly here:
https://launchpad.net/~brian-rogers/+archive/graphics-fixes/+build/1534570/+files/linux-image-2.6.32-50-generic_2.6.32-50.22_i386.deb
--
[i845g] Karmic stops
I could lower the delay, but if it froze we wouldn't know if that was
because a delay doesn't fix the problem or because the delay was too
short.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you
I'm preparing post-Jaunty versions of libdrm and the intel driver, so we
can step forward and find the first broken version, hopefully with fewer
problems than running these old versions in Karmic.
--
[i845g] Karmic stops responding a few minutes after log in
If you never added my PPA, does that mean you never downgraded libdrm or
mesa? That might be a factor in being able to reproduce the freeze in
such old xserver-xorg-video-intel versions.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You
OK, I see where you specify libdrm 2.4.14-1ubuntu1. You could be getting
freezes because of a libdrm bug in the newer version.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of
I have a kernel patch for people to try. It works around the x11perf
freeze, and I'm curious if it prevents random freezing as well. Kernels
with this patch, for both Karmic and Lucid, are available in a separate
PPA of mine, graphics-fixes:
https://launchpad.net/~brian-rogers/+archive/graphics
Yeah, that's definitely a GPU hang. 2.7.0 has been uploaded and should
build eventually. If you have problems getting this version to run at
all, you may have to boot with i915.modeset=0 in your kernel parameters.
--
[i845G] Karmic stops responding a few minutes after log in
We've gone back so far now that we've nearly gone back to the Jaunty
version. When you get back to this testing, you may want to do a Jaunty
install and see if that suffers from the bug. If it doesn't, we have our
good version and it might be easier to step forward from there with
newer versions
Yeah, a new video card will bypass the problem, since you won't be using
the i845.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
Based on the reports from Flabdablet, I have backed up a bit to a build
between 2.8.0-8-g12c5aec and 2.8.0-47-ge903b3e. 2.8.0-27-g926c7e7 is now
uploaded.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification
The system deletes old packages after a while, so that one isn't
available any more. But now I sent in a build of 2.8.0, which will get
built when it works its way through the queue.
You've been having a lot of luck reproducing the hang, which is good,
but I want to double-check that you're
2.8.99.901-16-g7e7db7a just got done building. If you could verify if
that version also freezes, it'd be a good sanity check.
I'm going to upload a version between 2.8.99.901-5-g57fc09c and
2.8.99.901-12-g2cc1f3c now, and it might take an hour or so to build.
--
[i845G] Karmic stops responding
Version 2.8.99.901-5-g57fc09c is now available.
To speed things up I'm going to wait less for feedback now. It could
take us down a wrong path if a bad version happens to run stably for a
while, but we'll backtrack if that happens.
--
[i845G] Karmic stops responding a few minutes after log in
The package has to be built for Lucid so it can tie into the Lucid
versions of its dependencies. Older versions of xserver-xorg-video-intel
were failing to build on Lucid, and it looked like it may have taken
some work, so I just left that for later when we found a good version
that's new enough
Just search for xserver-xorg-video-intel in synaptic. If you have the
Lucid version from my PPA, it will say 7:2.8.99.901-5-g57fc09c+lucid in
the Installed version column. If you select it and go to the package
menu and choose force version you will be able to select between
available versions.
Apparently there's a generic X memory corruption bug triggered by the
x11perf command I gave (I can crash Xephyr with it). When X crashes out
rather than freezing, it's because of that. So it turns out this isn't a
good test of the driver.
I did witness freezing in some scenarios with this
manually, type
sudo dpkg -i filename
The file you want might still be in /var/cache/apt/archives. If not, here is
the archive of past versions:
https://launchpad.net/~brian-rogers/+archive/graphics-testing/+packages?field.name_filter=field.status_filter=field.series_filter=karmic
It's good to save
OK, version 2.8.0-8-g12c5aec is up.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
I found another way to freeze the system. For me, the following command
will usually trigger a freeze before it completes:
x11perf -range copywinpix10,comppixwin500 -time 1 -repeat 1
I'd like to find out if that freeze is connected to this one. If it is,
then we have a good, reproducible test
shadetree, what version of libdrm, mesa, and xserver-xorg-video-intel is
that result for? Did you get 2.8.1-1 to start without crashing? Or did
you revert to an earlier version, or to standard Karmic?
--
[i845G] Karmic stops responding a few minutes after log in
OK, xserver-xorg-video-intel 2.8.1-1 has now been posted.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
When this bug is resolved, we'll be able to go back to the new driver
with the bugfix added, and things will be fast again as well as stable.
One reason I just realized for why graphics-testing is slower is that by
reverting libdrm but not mesa, I broke opengl acceleration. It was just
silently
OK, I've uploaded a plain 2.8.1 build, no additional patches on top of
it this time.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
Have you tried those versions along with also booting with 'nomodeset'
in the kernel options? Otherwise that version of the driver probably
won't do the right thing.
--
[i855] [karmic] X freezes with intel 855GM videocard
https://bugs.launchpad.net/bugs/476817
You received this bug notification
Due to an ABI change in Xorg 1.7, the older binary packages built
against 1.6 won't work, so new packages have to be recompiled for 1.7.
And unfortunately I wasn't able to easily compile the older driver
versions on Lucid.
I didn't investigate yet how much work it'd take to work around this
OK, with two reports of stability, that version does appear to be good.
I've now uploaded 2.8.0-2-gb0aa94f.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the
Since most people are getting the freeze randomly, it's possible for it
to seem stable purely by chance and not because you're running a good
version. I believe that happened with 2.8.0.901, which has now been
reported as both good and bad.
So it helps to have as many testers as possible. We want
That's excellent news!
We've now identified a good and bad version with only a handful of code
changes between them. At this point, we have just a few tests to go.
I've now uploaded 2.8.0.901.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
Olie, try it with KMS enabled and any AccelMethod setting in xorg.conf
deleted. It's possible it won't freeze with that setup.
If it still freezes, also try installing this version:
https://launchpad.net/~brian-rogers/+archive/graphics-
testing/+build/1437394/+files/xserver-xorg-video
Confirmed. I had a chance to do the Bejeweled test with that version and
it passed. The next version also passed: 2.7.99.902+git20090720.bb300738
They worked with and without KMS. We're in pretty good shape here. This
means the bug didn't exist since the beginning of UXA and there's a
pretty good
Actually, I just saw there are no code changes between the git snapshot
I tested and 2.8.0, so I'll bump us forward one more version for now, to
2.8.1.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because
OK, the next version is up. I had to patch it to get it to build against
the final X Server release. If my patch isn't right, the driver will
most likely crash on startup. If it starts correctly, I'm interested in
the results both with and without KMS. If this version freezes, is it
only with KMS,
Thanks for the report. It appears the fact that old kernels prevented
the freeze was just a red herring: without a recent kernel, the newer
userspace driver couldn't enable some features related to the crash.
The real problem is probably in the Xorg driver. To narrow down when the
problem
I set up a PPA for Karmic that will roll libdrm and xserver-xorg-video-intel
back to the Jaunty versions:
https://launchpad.net/~brian-rogers/+archive/graphics-testing
It will be interesting if the older X driver works without problems on
the newer kernel. I haven't had a chance to try
Also, yes Adam, I did see X crashing (not the window manager) during
Firefox use on a system where I reverted to a kernel version that
doesn't freeze. It makes running an older kernel not a viable workaround
for this problem...
--
[i845G] Karmic stops responding a few minutes after log in
1 - 100 of 107 matches
Mail list logo
