Launchpad has imported 17 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=43448.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-12-02T03:22:55+00:00 Marcaureleii wrote: Created attachment 54048 dmesg Dear, I try to get native 3D acceleration with my graphic card. I have a Dell Precision M6500 with Radeon FirePro M7740. The chipset (rv740) is rather well supported but I can't obtain native 3D acceleration. I have Linux Fedora 16, libmesa 7.11.1. I don't understand where is the problem... I attach my dmesg and LIBGL_DEBUG=verbose glxinfo. This last one indicates : "libGL error: failed to create dri screen" Please help me. Thanks a lot Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/0 ------------------------------------------------------------------------ On 2011-12-02T03:26:28+00:00 Marcaureleii wrote: Created attachment 54049 libgl verbose glxinfo Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/1 ------------------------------------------------------------------------ On 2011-12-02T14:07:09+00:00 agd5f wrote: Looks like you attached the wrong glxinfo output. Please attach your xorg log as well. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/2 ------------------------------------------------------------------------ On 2011-12-02T15:15:26+00:00 Marcaureleii wrote: Created attachment 54077 libgl verbose glxinfo Here is the correct output of LIBGL_DEBUG=verbose glxinfo Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/3 ------------------------------------------------------------------------ On 2011-12-02T15:20:40+00:00 Marcaureleii wrote: Created attachment 54078 xorg log And here is my xorg log. Thanks for your interest and sorry for the bad glxinfo log. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/4 ------------------------------------------------------------------------ On 2011-12-06T15:46:32+00:00 Michel-daenzer wrote: Looks like /usr/lib64/dri/r600_dri.so's dri2CreateNewScreen() hook fails, but it's not clear why. Maybe you can try running glxinfo in gdb, setting a breakpoint at dri2CreateNewScreen and tracing where the failure is coming from. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/5 ------------------------------------------------------------------------ On 2011-12-06T16:12:01+00:00 Airlied-freedesktop wrote: check mesa is built with radeon drm support. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/6 ------------------------------------------------------------------------ On 2011-12-25T10:25:42+00:00 Marcaureleii wrote: Dear, I use default version of mesa (7.11.2) on Fedora 16, so I think it is build with radeon drm support, yes. Tracing and debugging is not (yet) my skill level, but perhaps you can guide and help me. Here is what I get setting a breakpoint at dri2CreateNewScreen: (gdb) run Starting program: /usr/bin/glxinfo [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". name of display: :0 libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so Breakpoint 1, dri2CreateNewScreen (scrn=0, fd=8, extensions=0x614f30, driver_configs=0x7fffffffd980, data=0x6160b0) at ../common/dri_util.c:865 865 { (gdb) What else should I do ? Thanks a lot ! Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/7 ------------------------------------------------------------------------ On 2011-12-28T09:48:50+00:00 Michel-daenzer wrote: (In reply to comment #7) > What else should I do ? First of all, run 'finish' and check that the return value of dri2CreateNewScreen is 0 as suspected. If so, single-step through dri2CreateNewScreen and its callees with 'step' / 'next' to find out why it returns 0. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/8 ------------------------------------------------------------------------ On 2012-05-28T09:24:02+00:00 Freedesktop-n8 wrote: Hello, I think I have found a solution for this problem and another. I have the same notebook with that graphics card and had some problems with it in the past months whenever I tried the open source driver from Debian unstable. It worked about a year ago but then I bought a 27" monitor which was only usable with its native resolution of 2560x1440 with the fglrx driver (which had some other problems by the way). I regularly tried the open source driver when new versions show up in Debian but since some months the XServer crashed immediately after the start with a segfault. In newer versions it became more graceful with the following log messages: (EE) RADEON(0): radeon_surface_best failed (EE) RADEON(0): radeon_setup_kernel_mem failed After debugging like suggested in bug #48138 I found out that there is missing a case in r6_init_hw_info for setting num_banks. While there are cases for 0 and 1 the FirePro M7740 has a value of 2 at some bits of the tiling_config so it returns with -EINVAL from the default case. First I did not know on what to set num_banks in that case but tried something and the XServer started successfully with that change. Then I saw in /var/log/Xorg.0.log that the 3D acceleration was not working like described in this bug report: (EE) AIGLX error: Calling driver entry point failed (EE) AIGLX: reverting to software rendering I tried to debug that too, following the above hints and ended up in r600_interpret_tiling in src/gallium/drivers/r600/r600_pipe.c in the MESA code and found exactly the same reason as above, a missing case 2. In the meantime I checked out the source of xserver-xorg-video-ati too and sensitized by the above findings made a grep over all three source trees (libdri, mesa, xserver-xorg-video-ati): grep "num_banks.*=" -rsn . -B 2 -A 1 There I found another missing case 2 in r600_interpret_tiling in src/radeon_kms.c and somewhere else an existing case 2 with num_banks = 16. So I patched all found asymmetries regarding case 2 and the 3D acceleration began to work again. I append all three patches I made. Maybe someone can check them and add them if they are reasonable so future versions can incorporate the fixes. Best regards Stefan Kanarski PS: Now my only problem is the resolution of 2560x1440 with my Fujitsu P27T-6. Via DVI I only get 1280x1440 (every second pixel column missing, looks like single-link although the cable should be dual-link) and via DisplayPort the monitor is toggling between power save and a black screen. But that's another story for another day or two. If someone has an idea where to start looking I am glad to hear. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/13 ------------------------------------------------------------------------ On 2012-05-28T09:26:56+00:00 Freedesktop-n8 wrote: Created attachment 62157 Patch for branch debian-unstable in http://git.debian.org/pkg-xorg/lib/libdrm.git Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/14 ------------------------------------------------------------------------ On 2012-05-28T09:28:32+00:00 Freedesktop-n8 wrote: Created attachment 62158 Patch for branch debian-unstable in http://git.debian.org/pkg-xorg/lib/mesa.git Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/15 ------------------------------------------------------------------------ On 2012-05-28T09:30:44+00:00 Freedesktop-n8 wrote: Created attachment 62159 Patch for branch debian-unstable in http://git.debian.org/pkg-xorg/driver/xserver-xorg-video-ati.git Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/16 ------------------------------------------------------------------------ On 2012-05-29T22:43:11+00:00 agd5f wrote: Created attachment 62246 possible fix It's actually a kernel issue. The attached patch against Dave's drm- fixes branch should fix it. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/17 ------------------------------------------------------------------------ On 2012-06-06T08:37:53+00:00 Michel-daenzer wrote: Could libdrm_radeon also be made to deal gracefully with broken kernels? Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/19 ------------------------------------------------------------------------ On 2012-06-06T13:14:27+00:00 agd5f wrote: Created attachment 62672 libdrm fix This patch should do the trick. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/20 ------------------------------------------------------------------------ On 2012-06-06T13:26:50+00:00 agd5f wrote: Created attachment 62674 libdrm fix slightly improved version. Reply at: https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/1002562/comments/21 ** Changed in: xserver-xorg-driver-ati Status: Unknown => Confirmed ** Changed in: xserver-xorg-driver-ati Importance: Unknown => High -- 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/1002562 Title: no 3D with radeon driver, AIGLX error: Calling driver entry point failed To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1002562/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
