(In reply to Marek Olšák from comment #30)
> The patch is correct from the LE perspective. It simply adds ARGB support
> and was tested thoroughly on LE. The side effect is that BE can use the
> format now too, but there may be other issues with BE.
Makes sense. Maybe we can use bug 43698 to
That piglit sanity is failing with the patch may confirm my suspicion
that something doesn't add up yet I'm afraid: Since the kernel driver
and xf86-video-ati EXA code are using the same hardware formats for
display/rendering with BE & LE, I was wondering how the patch could
result in both display
Elimar, Nathan or anyone else, can you try if the piglit sanity tests
pass with this patch?
Also, do OpenGL compositing managers such as gnome-shell show correct
colours?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
*** Bug 91923 has been marked as a duplicate of this bug. ***
--
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/1443456
Title:
Xorg crashed with SIGABRT in fbBltOne()
To manage
Please attach all relevant information (at least dmesg, Xorg.0.log and
the screenshot) here directly.
--
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/1441687
Title:
Screen
Sounds like the crashes are fixed.
The wrong colours are probably (related to) the well-known Gallium
driver endianness bugs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-fbdev in Ubuntu.
Please attach the Xorg log file.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1314587
Title:
Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7
(14.04 and 14.10)
To manage
(In reply to Alberto Salvia Novella from comment #6)
It also happens to me using Ubuntu 14.10 with xorg 7.7.
Please attach the full /var/log/Xorg.0.log and output of dmesg
corresponding to that here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
You seem to be using a very old version of Ubuntu and in particular the
Linux kernel. Can you try newer versions? Current versions of the kernel
radeon driver support DPM.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
(In reply to cvillelk from comment #24)
It looks like (per Alex Oranges previous comment) the fix for this issue is
already submitted and commited to the master branch of xserver
See 2014-10-27 fb: Fix Bresenham algorithms for commonly used small
segments.
Resolving this report
(In reply to comment #11)
Big-endian patches are in mesa git now. Is this still an issue?
Yes. The infrastructure changes are mostly complete now, but the
hardware drivers still haven't been adapted to them.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
(In reply to comment #5)
X-Plane Demo fails to start with the following error:
BTW, beware that X-Plane is a 32-bit executable, so if you're using a
64-bit distro, make sure your 32-bit r300_dri.so is up to date.
--
You received this bug notification because you are a member of Ubuntu-X,
which
(In reply to comment #3)
I get this bug with Mutter and Compiz when I try to use a dual monitor setup
for a combined resolution of 3200x2000.
Note that even if you get the exact same messages, they might not be
caused by the same problem for you as for Anton. It's probably better if
you file
Please attach the output of dmesg after the crash.
Can you get a backtrace of the crash with gdb?
Note that there is no EXA support for Southern Islands and newer
Radeons, Option AccelMethod EXA just disables all hardware
acceleration with those.
--
You received this bug notification because
This is really weird: As you can see, tile_split is not 0, so the
division by 0 must be about stencil_tile_split. But I don't see how
eg_surface_best can not set stencil_tile_split to non-0 for a
depth/stencil surface...
--
You received this bug notification because you are a member of Ubuntu-X,
Can you run
print *surf
at the gdb prompt when the problem occurs, and attach the output?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1257612
Title:
divide by zero error in
(In reply to comment #26)
If a patch to xorg-video-ati fixes a bug while using fglrx, that would be
surprising indeed.
The component field of this report says Radeon. It's unlikely for fglrx
and radeon to be affected by one and the same bug. It's possible that
fglrx has a similar bug though.
(In reply to comment #26)
If a patch to xorg-video-ati fixes a bug while using fglrx, that would be
surprising indeed.
The component field of this report says Radeon. It's unlikely for fglrx
and radeon to be affected by one and the same bug. It's possible that
fglrx has a similar bug though.
(In reply to comment #24)
Nope, don't think so
Why not? Have you tried the fix for that?
--
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/195051
Title:
[RV350 9600] [Needs
(In reply to comment #24)
Nope, don't think so
Why not? Have you tried the fix for that?
--
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/108527
Title:
X freezes when compiz
(In reply to comment #22)
This usually occurs using compiz when the monitors go into ACPI power save
mode.
If it only happens at DPMS power save, it's probably not this bug but
bug 49761.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to comment #22)
This usually occurs using compiz when the monitors go into ACPI power save
mode.
If it only happens at DPMS power save, it's probably not this bug but
bug 49761.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to comment #21)
Disabling compositing alone doesn't solve the tearing problem, it only works
with enabled EXAVSync.
For some reason, Ubuntu seem to have patched their metacity to enable
automatic (server side) compositing even when client side compositing is
disabled in the metacity
*** Bug 55723 has been marked as a duplicate of this bug. ***
--
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/1010794
Title:
Graphics/text corruptions in some applications with nouveau
commit 1ca096d5e07221025c4c4110528772b7d94f15ee
Author: Michel Dänzer michel.daen...@amd.com
Date: Mon Oct 29 12:57:54 2012 +0100
EXA: Track source/mask pixmaps more explicitly for Composite
fallback regions.
--
You received this bug notification because you are a member of Ubuntu-X,
(In reply to comment #20)
Radeon 7570 card - PCI identifier 675D
That's a different card from the one this bug report is about.
libdrm-radeon1 libdrm2: 2.4.33-1
Support for your card was only added in libdrm_radeon 2.4.34.
--
You received this bug notification because you are a member of
(In reply to comment #17)
It's been suggested that my problem is related to the bug documented here. To
those more knowledgable than I - does this seem likely?
Yes.
If the patches listed here are relevant, could someone explain - would ONE of
the patches address the problem, or would they
According to Dave Airlie this isn't (easily) fixable completely. Current
xf86-video-ati Git bails in this case, and then the next X server
startup should work properly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
According to bug 38694 there can be problems when changing the number of
PCIe lanes. Does disabling that as described there help for this
problem?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
Resolving per comment #14, reopen if you're still seeing the problem
with the fix.
--
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/929960
Title:
Mouse cursor corruption when
Created attachment 57853
Restrict offset for legacy hardware cursor.
Does this kernel patch fix the problem?
--
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/929960
Title:
Created attachment 58066
Verbose test patch
In order to facilitate testing, here's another version of the fix which
prints a message
[drm] Fixing large cursor offset 0x = 0x0800
when the suspected problem would have occurred. So if such a message
appears in dmesg but the cursor is
Created attachment 58436
Submitted fix
(In reply to comment #11)
[...] I haven't had the mouse corruption issue on this patched driver, and the
message appears in dmesg:
Okay, so an unpatched driver probably would use too large offsets
sometimes, which would definitely explain the corrupted
(In reply to comment #7)
I got the source for xserver-xorg-video-ati from the Ubuntu repositories and
tried to apply the patch to it.
That can't work, as the patch is for the kernel, not the X driver.
You should be able to get the source for your running kernel with
apt-get source
Created attachment 58312
Verbose test patch with crash fixed
(In reply to comment #9)
This patch causes my computer to crash at login. However, it's not a super bad
crash because I was able to ssh in and check dmesg.
Sorry about that, here's another test patch which shouldn't crash.
--
You
(In reply to comment #18)
I have not yet applied Alex's patch, [...]
Have you been able to test it in the meantime? It doesn't seem very
likely it'll help, but...
However, setting the vramlimit to 64 seems (2 reboots later) to clear up the
corruption.
vramlimit of 128, 256, and 0 (0 is
(In reply to comment #98)
I have this problem with my Radeon 9600XT
No, you probably don't. This problem is (was? Looks like this report can
be resolved now?) specific to RS690 chipsets.
Please file your own report with the usual information attached, i.e. at
least Xorg.0.log and the output of
37 matches
Mail list logo
