ubuntu-x-swat team mailing list archive

[Bryce Harrington <556782@xxxxxxxxxxxxxxxxxx>]

Hmm, looks like this bug has stalled.

First thing, for those looking for workarounds, you should be able to
install the classic (non-gallium) driver and still use the disable-KMS
workaround to get back to working 3D.  If you haven't located the
classic drivers, look in /usr/lib/dri-alternates.  You can use the
environment variable to set the path, ala:

 LIBGL_DRIVERS_PATH=/usr/lib/dri-alternates glxgears-info

If that works, you can set that option globally.  You guys may need to
experiment a bit to get an optimal workaround.

"""Sometimes I'm tempted to just shout "Help, help!", but I know it's just more noise. ..if *anyone* knows who to mail that:
1) can move this bug along, and
2) whom it wouldn't be rude to email about this, and
3) preferably actually *wants* to see this fixed,
please let me know!
"""

Here is a course of action I'd suggest.  I agree it's unfortunate the
upstream bug report got closed without actually being fixed.  Part of
the trouble is I think this bug report is a bit creakily old and has
conglomerated a few different issues which perhaps makes the issue
unclear to the developers.  So, I would first suggest breaking out a
separate bug report from this one, and keep it discrete to a specific,
reproducible problem; be very clear in your description, include a
reference to this bug report, and identify specific error messages,
screenshots, and so on that clearly define the problem.  Here's a good
way to start filing it:

 $ ubuntu-bug mesa

(In the dialog that pops up, pick the "yes, I was directed here"
option.)

Next, it looks to me like upstream wants this tested against current git
versions of things; they don't put much priority on issues reported
against released versions in distros typically.  Fortunately we provide
packaged versions of all the upstream stuff you need to test.  Here's
the links you need:

  * xorg-edgers:  https://launchpad.net/~xorg-edgers/+archive/ppa  -
this will give git versions of mesa, -ati, etc.

  * http://kernel.ubuntu.com/~kernel-ppa/mainline/ - includes drm-next
and .39 backports to natty

For this bug I doubt you need to install and test a newer kernel, I
think the newer mesa is the more important thing to test.  However, many
of these kinds of bugs do depend on stuff in the kernel, so if the new
mesa doesn't resolve the issue it would be wise to also test either the
drm-next kernel or a .39 kernel (like v2.6.39-rc4-natty).  For mesa,
make sure to only use natty builds.  For the kernel, either the oneiric
or natty kernels should work on natty, but the natty builds are more
likely to work properly.  You may need to experiment a bit.  Take good
notes.

In the case that you *do* find that the newer git builds work properly,
upstream will consider the issue solved, so no use bothering them
further.  However, if you think the issue still should be fixed in
natty, there's some additional testing work to do.  You can use a git
bisection procedure to narrow in on what patch fixed it.  See
https://wiki.ubuntu.com/Kernel/KernelBisection or
https://wiki.ubuntu.com/X/BisectingMesa or
https://wiki.ubuntu.com/X/Bisecting as appropriate.

In the case that you *don't* find any success from the newer git builds,
then upstream should care.  Forward the bug upstream to
bugs.freedesktop.org and file it against mesa (DRI/radeon).  Then link
it to your ubuntu bug report to the upstream bug via the "Also affects
project" link.  Upstream may give patches or request testing other
options or things; if you have the bug linked, we can keep an eye out
for you and give you a helping hand with package builds or whatnot if we
have time.

Anyway, hope this helps.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is a direct subscriber.
https://bugs.launchpad.net/bugs/556782

Title:
  [rs690m] Graphics corruption with ati x1200