Currentlty I'm favouring patch4. Possible random crashes maybe with
patch3.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch
Sorry about the delay, I've been trying to figure out if there is a
difference between the performance of the two patches.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Right, the above patches should be correct now (he says hopefully). I
don't know which is the best to use.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch
Do I need to raise an explicit SRU request or is this bug report good
enough?
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Okay, stupid question alert - how do I assign 'canonical-x' because it
won't let me?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch
This patch removes commit b5093063b5d76ff31519a2daf85ea32808f1afe6 and
replaces it with the old 215_glx_drawable_refcounting.diff
** Attachment added: patch3
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3637039/+files/patch3
** Bug watch added:
This should be basically the patch here
https://bugs.freedesktop.org/show_bug.cgi?id=28181#c40
** Attachment added: patch4
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3637040/+files/patch4
** Patch removed: Remove upstream commit and re-apply
Apologies, reviewing those patches I seem to have sucked in a random
nouveau line or two. I'll check them some more and re-submit.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1160903
** Attachment added: Remove upstream commit and re-apply
215_glx_drawable_refcounting.diff
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3600793/+files/patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
Hello,
This bug affects oneiric and precise. Previous versions of Ubuntu used
to carry a patch 215_glx_drawable_refcounting.diff . This came about
because of this upstream bug report
https://bugs.freedesktop.org/show_bug.cgi?id=28181 .
The patch was removed in oneiric
** Attachment added: Log of a crash
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3600792/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Attachment added: Refreshed comment 40 patch
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3600794/+files/patch2
** Tags added: precise
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch 215_glx_drawable_refcounting.diff for precise (12.04)
To manage notifications about
I opened a new bug about the kwin crashing with patches to fix it here
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/946677
PowerPC + radeon + Kernel Mode Setting (KMS) has problems with AGP. If
you force pci mode radeon.agpmode=-1 does this help?
Userspace mode setting with radeon was dropped after Ubuntu 12.04/Debian
wheezy so you have to use KMS in 12.10 onwards. KMS on PowerPC is
something that really needs
I just tried Xubuntu without the composting manager and see this problem
also. The only exception is the terminal program which has the correct
colours. If I disable the composite extension in an xorg.conf then this
also has messed up colours. Some sort of endian problem in the radeon
driver?
I also should add that in addition to this problem, there are a few
colour issues with radeon KMS. A lot of fixes have gone in, and it is
much better than it was, but last time I tried I was still getting this
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
ati/+bug/1052619 . If
@John thanks that's another confirmation of this bug. Unity/compiz
won't work with the fbdev xorg driver (...or more correctly it is
supposed to work with llvmpipe, but there are still issues). If you
want to try KMS which may work with unity then you can define an
xorg.conf like I did
Bug 1066435 is what I referred to in post 24. Turns out it was a
problem with the snd-powermac module. 2blue, I think you just needed to
use ctrl-alt-f1 to get to a command login prompt.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
There seems to be a new problem - the kernel is currently screwed when
using KMS. It won't even boot. I think this is the problem you were
hitting 2blue. A serious regression just at the end of testing. I
don't think 12.10 should be released in this state.you can only
stretch workarounds
Also, you haven't turned off just 3d acceleration, but ALL acceleration
from what I understand. To turn off 3d you'd have to disable DRI or
turn off AIGLX so that the software rasteriser is used. Something like
that anyway. I think your problem is possibly EXA related, but FYI if
you wish you
@Ron thanks that confirms my problem in that the radeon card is not
detected and the Xorg server is not starting. It seems for you,
additionally, the radeondrmfb is not working correctly (hence the blank
screen).
@2blue thanks for trying to help out, but those logs have nothing to do
with this
** Tags removed: precise
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1058753
Title:
Radeon driver nolonger works on PowerPC without drm
To manage notifications about this
It's probably worth pointing out that you had to define an xorg.conf
because you got No devices detected in the Xorg.0.log. A similar
problem to what is currently happening to some (all?) radeon cards with
PowerPC at the moment since the latest update to the radeon driver - bug
1058641 .
--
You
@2blue I don't understand. Either you have mis-typed or there is
something weird happening with your foreign keyboard.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1058641
@2blue, the boot parameter is 'video=ofonly', not offonly. The radeon
xorg driver will only work in 12.10 on PowerPC if you disable the
radeonfb framebuffer.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
Please post your Xorg.0.log (in the /var/log directory) when using the
video=ofonly parameter.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1058641
Title:
No devices
Maarten, thanks for the comment, although I am not sure I follow it (!)
I know UMS has been dropped. I know it is never coming back. And I'm
not suggesting for one minute that it should (the last version of radeon
with UMS was largely broken from what I can gather).
I just need confirmation
@wxl and lars. You are not understanding this bug report.
video=radeonfb:1024x768-32 etc is using the fbdev driver. It is not
using the radeon xorg driver.
If you are on PowerPC and you want to test for this bug then you need to
turn off radeonfb using the video=ofonly (or video=radeonfb:off).
Note, in all the logs I've disabled the radeonfb framebuffer (still
built in on PowerPC) to allow KMS. You do this either via the
video=ofonly or video=radeonfb:off boot parameters on PowerPC.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Another thing that is possibly worth a mention is if I don't have the
line:
BusID PCI:0:16:0
then the computer seems to freeze. (Obviously the value you write is
computer dependant)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
In the 12.04 Xorg.0.log I have the line
[39.624] (II) RADEON(0): Color tiling enabled by default
If it was using KMS then it should be (*I think*) something like ths:
[98.582] (II) RADEON(0): KMS Color Tiling: disabled
[98.582] (II) RADEON(0): KMS Pageflipping: enabled
This is why
*** This bug is a duplicate of bug 1044180 ***
https://bugs.launchpad.net/bugs/1044180
** This bug has been marked a duplicate of bug 1044180
Screen Freeze on Bootup - Lubuntu 12.10 PPC Alternate Aug 30 Build
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
Testing the quantal daily/live ISOs I've noticed a regression with the
radeon driver. The last ISO I tested was from the 19th of Sept and that
was fine. Yesterdays live/desktop ISO (28/9/2012) fails to start the
Xorg server. It reports that no devices are detected.
** Attachment added: No xorg.conf
https://bugs.launchpad.net/bugs/1058641/+attachment/3355290/+files/Xorg.0.log-no-xorg-conf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Attachment added: With xorg.conf
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058641/+attachment/3355291/+files/Xorg.0.log-with-xorg-conf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
Just for completeness I'll add the Xorg.0.log using the previous version
of the ati/radeon driver. It boots fine without any xorg.conf.
** Attachment added: Xorg.0.log-6.99.99~git20120713.6ef1ad6a-0ubuntu1
Public bug reported:
Hi, I'm trying to find out the best radeon setup for PowerPC in quantal
and need some advice! The PowerPC kernel is currently setup with KMS
enabled, BUT the legacy framebuffer radeonfb is still built in.
Although this is obviously not an ideal setup it seemed to work okay
Under 12.04:
dmesg | grep drm
[ 38.849798] [drm] Initialized drm 1.1.0 20060810
[ 39.102286] [drm] radeon defaulting to kernel modesetting.
[ 39.102301] [drm] radeon kernel modesetting enabled.
** Attachment added: 12.04 default Xorg.0.log
** Attachment added: 12.10 Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058753/+attachment/3356097/+files/Xorg.0.log-default
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
Looking at the various logs that are spread out over the various bug
reports I'm guessing that under 12.04 the radeon driver was using UMS
despite it saying it was using KMS. Once somebody with expertise can
confirm this then we can push to have the kernel config and PowerPC boot
message updated
** Description changed:
Hi, I'm trying to find out the best radeon setup for PowerPC in quantal
and need some advice! The PowerPC kernel is currently setup with KMS
enabled, BUT the legacy framebuffer radeonfb is still built in.
Although this is obviously not an ideal setup it seemed
*** This bug is a duplicate of bug 1040526 ***
https://bugs.launchpad.net/bugs/1040526
Most of these comments refer to Bug #1040526 and as such I'm making it a
duplicate of that bug. There are known and working solutions for the
live/desktop ISOs (although a change to the kernel config and
Not just a ubiquity problem. I notice the network applet windows do
something similar.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1046951
Title:
No desktop environment or
The radeon driver no longer supports UMS. Because of the current
PowerPC kernel config (radeonfb is built in) KMS drm cannot be
activated. You are falling back to the fbdev driver in 8 bit mode (hence
the poor colors).
One way to activate KMS is using the video=ofonly parameter (this
disables
I'm not sure why ubiquity can't cope with 8 bit colours.possibly
something that might be worth looking into?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1046951
Title:
This is the bug for ubiquity
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1040544
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1046951
Title:
No desktop
I've found a better way to deal with the unmiminising crashing with
Kwin. In System Settings Desktop Effects Advanced there is a settng
for Keep window thumbnails. If you change that to Always (Breaks
minimization) then it cures the crashing. It still allows
minimistation, but (from a bit of
For anybody experiencing these problems: To overcome the resize
crashings I used the plugins to draw a rectangle instead of the 'normal'
resize mode.
The unminimising crashes can be overcome in kwin by creating a rule to
disable minimising. This is not so extreme as it sounds - I believe
gnome
Argh.kwin had gone to Xrender. Sigh.
Just resizing windows in kwin and compiz is now causing crashings.
Things are getting worse!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/946677
Hi Tormod and Bryce, thanks for the interest in this. Sorry I've been a
bit long getting back to you about this - I don't check this email
address often enough!!
I don't know if I can help much with the details of the mesa-legacy
package setup, but I am always up for testing stuff. Is it
Thanks Robert for the qick reply! Is this a can't fix/won't fix
situation then? I remember reading on phoronix (
http://www.phoronix.com/scan.php?page=news_itempx=OTg0Mg ) that large
chunks of code were being deleted, is this the case with r200? Or is it
possible for the user just to tweak some
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/946677
Title:
UMS dri support missing for r200
To manage notifications about this bug go to:
Public bug reported:
Hi,
I'm currently testing 12.04 on my PowerPC iBook. It is reverting to the
software rasterizer. Here is the relevant bit of the xorg log:
[29.603] (II) AIGLX: Screen 0 is not DRI2 capable
[29.603] drmOpenDevice: node name is /dev/dri/card0
[29.603]
54 matches
Mail list logo
