[Bug 44099] Big Image in Firefox crashes X server in
https://bugs.freedesktop.org/show_bug.cgi?id=44099 Karl Tomlinson changed: What|Removed |Added CC||bugs.freedesk...@karlt.net -- You are receiving this mail because: You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 69683] [r600g][GLAMOR] Crash when viewing a movie full screen with mplayer
https://bugs.freedesktop.org/show_bug.cgi?id=69683 --- Comment #5 from Zhigang Gong --- Thanks to report bug. It seems taht something bad happen when glamor try to fallback to sw path. It failed to find a matched format for the following formats. And the formats value are not valid formats. [ 71790.287] (II) fail to get matched format for 7893d260 [ 71790.287] (II) fail to get matched format for 7893d260 As I don't have a machine ready to run glamor now, I can't reproduce here. If possible, could you set env variable GLAMOR_DEBUG=2 before you start the X to log more debug information and may give more hints of the root cause. (In reply to comment #3) > GLAMOR: xorg-x11-glamor-0.5.1-1.20130921git29c0907.fc19.x86_64 > > Custom compiled from git master + patch from > http://lists.freedesktop.org/archives/glamor/2013-September/000386.html but > this doesn't change this. -- You are receiving this mail because: You are on the CC list for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#724264: xserver-xorg-video-radeon: X server crashes in multiple programs attempting to view a jpg file
On Mon, Sep 23, 2013 at 12:21:33 +0930, Arthur Marsh wrote: > Package: xserver-xorg-video-radeon > Version: 1:7.2.0-1+b1 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? > > Viewing a particular jpg file in pqiv, gthumb, midori > This looks similar to https://bugs.freedesktop.org/show_bug.cgi?id=44099 (thanks to Michel for the pointer). > [ 274.222] Backtrace: > [ 274.306] 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7f012e34f72d] > [ 274.306] 1: /usr/bin/X (0x7f012e1e2000+0x1713a9) [0x7f012e3533a9] > [ 274.307] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f012d504000+0xf210) > [0x7f012d513210] > [ 274.307] 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7f012c348000+0x8c8fb) > [0x7f012c3d48fb] > [ 274.307] 4: /usr/lib/xorg/modules/drivers/radeon_drv.so > (0x7f0129eda000+0x27087) [0x7f0129f01087] > [ 274.307] 5: /usr/lib/xorg/modules/libexa.so (0x7f0129ab6000+0x82dc) > [0x7f0129abe2dc] > [ 274.307] 6: /usr/bin/X (0x7f012e1e2000+0x1059e9) [0x7f012e2e79e9] > [ 274.307] 7: /usr/bin/X (0x7f012e1e2000+0x481a9) [0x7f012e22a1a9] > [ 274.307] 8: /usr/bin/X (0x7f012e1e2000+0x4b1f1) [0x7f012e22d1f1] > [ 274.307] 9: /usr/bin/X (0x7f012e1e2000+0x3ae65) [0x7f012e21ce65] > [ 274.307] 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) > [0x7f012c369995] > [ 274.307] 11: /usr/bin/X (0x7f012e1e2000+0x3b13b) [0x7f012e21d13b] > [ 274.307] > [ 274.307] Bus error at address 0x7f0117a82000 > [ 274.307] > Fatal server error: > [ 274.307] Caught signal 7 (Bus error). Server aborting > [ 274.307] Cheers, Julien ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#720329: xserver-xorg-video-radeon: Screen keeping black at start but for the cursor
On Son, 2013-09-22 at 12:15 +0200, Samuel Hym wrote: > > I finally tried setting the proposed kernel options, with the same > result (or slightly worse, the cursor got blurred or something). I > imagine the real problem is the fact that my card is not supported by > the kernel anyway, since the (attached) log shows the same > > [KMS] drm report modesetting isn't supported. That just means the kernel radeon driver didn't initialize with KMS. We really need to see the corresponding dmesg output. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 69683] [r600g][GLAMOR] Crash when viewing a movie full screen with mplayer
https://bugs.freedesktop.org/show_bug.cgi?id=69683 Michel Dänzer changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org |zhigang.g...@gmail.com QA Contact|xorg-t...@lists.x.org | CC||xorg-driver-ati@lists.x.org Component|Driver/Radeon |Driver/glamor --- Comment #4 from Michel Dänzer --- There doesn't seem to be anything radeon specific about the crash. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 69684] [r600g][GLAMOR] Crash when trying to play a game in WINE
https://bugs.freedesktop.org/show_bug.cgi?id=69684 --- Comment #1 from Michel Dänzer --- Looks like it's trying to use GLX indirect rendering, make sure you have 32-bit Mesa properly set up for Wine. -- You are receiving this mail because: You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Latest radeon driver with 7670M
Hello, On 24.09.2013 22:18, Alex Deucher wrote: > On Tue, Sep 24, 2013 at 3:31 PM, Vedran Furač wrote: >> Hi All, >> >> Fglrx 2D is dead slow for me so I'm wondering if my 7670M (Turks on Dell >> 5520 laptop, hybrid with Intel) is supported with latest 7.2 free Radeon >> driver. I've spent few hours googling with no luck. I'll really >> appreciate any help to get this working. Seems it's not detecting any >> outputs, but I have an external LCD connected via hdmi along with >> laptop's lvds1. With default xorg.conf I'm getting: >> > > Remove your xorg.conf. The radeon has no displays attached to it. So > it can only be used for rendering. You have to use the intel driver > for driving your displays. If you have a recent enough kernel and > xserver 1.14 or newer, you can use the radeon for rendering while the > intel driver handles the displays. See this page for how to handle > this: Thanks, that did the trick. Here's a reference for others if needed: Xorg.conf: Section "Device" Identifier "Radeon" Driver "radeon" BusId "PCI:1:0:0" Screen 1 Option"AccelMethod" "glamor" # Doesn't seem to be used EndSection Section "Device" Identifier "Intel" Driver "intel" BusId "PCI:0:2:0" Screen 0 Option "AccelMethod" "sna" # Unsure if this works EndSection # lsmod|grep radeon radeon694017 2 $ xrandr --setprovideroffloadsink radeon Intel $ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x77 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 1 name:Intel Provider 1: id: 0x50 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 1 outputs: 0 associated providers: 1 name:radeon $ DRI_PRIME=0 glxinfo|grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.2.0 $ DRI_PRIME=1 glxinfo|grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TURKS OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.2.0 OpenGL shading language version string: 1.30 Now I wonder if it's possible to start display manager and X with DRI_PRIME=1? Or that doesn't make sense? Regards, Vedran ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
