*** This bug is a duplicate of bug 345542 ***
https://bugs.launchpad.net/bugs/345542
** This bug has been marked a duplicate of bug 345542
linux-image-2.6.28-5-powerpc has ioremap fault with radeon drm module
--
[rv350] DRI fails; drm module complains about agp ioremap
I'm tagging this as regression-release, per the reports in the forum
thread (http://ubuntuforums.org/showthread.php?p=7178402) which have
confirmed that this is a regression from intrepid to jaunty.
** Tags added: regression-release
--
[rv350] DRI fails; drm module complains about agp ioremap
== Regression details ==
Discovered in version: Jaunty (2.6.28-6.20): main/devel
Last known good version: Intrepid (2.6.25-2.3): main/devel
--
[rv350] DRI fails; drm module complains about agp ioremap
https://bugs.launchpad.net/bugs/359839
You received this bug notification because you are a
== Regression details ==
Discovered in version: Jaunty (2.6.28-6.20): main/devel
Last known good version: Intrepid (2.6.25-2.3): main/devel
--
[rv350] DRI fails; drm module complains about agp ioremap
https://bugs.launchpad.net/bugs/359839
You received this bug notification because you are a
I think my issue may be down to the lack of support for i865 based graphics
cards in Jaunty.
I hope this is addressed in some future release.
compiz-check:
Distribution: Ubuntu 9.04
Desktop environment: GNOME
Graphics chip: Intel Corporation 82865G Integrated Graphics
I am also seeing a failure of compiz after the upgrade from 8.10 to
9.04. It was all working fine on 8.10 and remained working until I did a
restart.
Checking for Xgl: not present.
xset q doesn't reveal the location of the log file. Using fallback
/var/log/Xorg.0.log
Detected PCI ID for VGA:
To check to see if your issue is similar (it's not going to be exactly
the same because I have a radeon card, instead of intel), look in your
dmesg (type 'dmesg' into a terminal to see this) for this line (or
something similar):
[ 31.423017] [drm:radeon_do_init_cp] *ERROR* could not find
I checked Xorg.0.log and that's exactly what it reports; thanks for
looking it over and explaining the discrepancy. I don't really
understand why it's a kernel bug, though, rather than a xserver-xorg-
driver-ati bug.
Would attempting a downgrade (or reinstalling) to collect log output on
a
