Announcement

Collapse
No announcement yet.

RadeonSI / GLAMOR Support Still M.I.A. From Ubuntu 13.10

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • AnonymousCoward
    replied
    Originally posted by AnonymousCoward View Post
    I tried it out on my APU + 7730M system and it does appear to work when not forcing glamor in xorg.conf. Anyway its definitely slower and more glitchy with the dedicated card with Prime, at least when running Unigine Heaven 3.0; which is fairly unsurprising given the immature driver, the overhead from Prime, and the card itself not being much faster than the APU.

    EDIT: It's definitely running on the dedicated card as I can load Skyrim now, which uses too much VRAM at 1080p to even launch with the APU. Cool, but it's far too slow to be playable, even with CSMT. Tried gallium-nine and it's a bit faster, but still 10-15 fps and it crashed.

    I'll try out that earlier mentioned patch as well.
    I was already using this patch: http://cgit.freedesktop.org/xorg/dri...168b719243bcd2

    Which results in a black screen with both cards using glamor.

    Leave a comment:


  • AnonymousCoward
    replied
    Originally posted by CalcProgrammer1 View Post
    If I remove my forcing of glamor in xorg.conf.d still with the Oibaf PPA which does not have the change mentioned above, the corruption is gone. I can even use DRI_PRIME for glxgears though performance from the DRI_PRIME card is god awfully slow (even though it says it's rendering thousands of fps). If I run it on the r600 APU's GPU it runs fine but still is choppy like it's always been on EXA. If I run Steam with DRI_PRIME, it crashes trying to view any 3D stuff in TF2 (the item menu or loading a map/server) but if I run Steam without DRI_PRIME on the r600 it works perfectly fine.
    I tried it out on my APU + 7730M system and it does appear to work when not forcing glamor in xorg.conf. Anyway its definitely slower and more glitchy with the dedicated card with Prime, at least when running Unigine Heaven 3.0; which is fairly unsurprising given the immature driver, the overhead from Prime, and the card itself not being much faster than the APU.

    EDIT: It's definitely running on the dedicated card as I can load Skyrim now, which uses too much VRAM at 1080p to even launch with the APU. Cool, but it's far too slow to be playable, even with CSMT. Tried gallium-nine and it's a bit faster, but still 10-15 fps and it crashed.

    I'll try out that earlier mentioned patch as well.
    Last edited by AnonymousCoward; 03 November 2013, 11:27 AM.

    Leave a comment:


  • CalcProgrammer1
    replied
    If I remove my forcing of glamor in xorg.conf.d still with the Oibaf PPA which does not have the change mentioned above, the corruption is gone. I can even use DRI_PRIME for glxgears though performance from the DRI_PRIME card is god awfully slow (even though it says it's rendering thousands of fps). If I run it on the r600 APU's GPU it runs fine but still is choppy like it's always been on EXA. If I run Steam with DRI_PRIME, it crashes trying to view any 3D stuff in TF2 (the item menu or loading a map/server) but if I run Steam without DRI_PRIME on the r600 it works perfectly fine.

    Leave a comment:


  • Melcar
    replied
    An Asus HD7850 arrived fresh in the mail today. Kubuntu 13.10 + 3.12 kernel + Oibaf ppa. Get OpenGL2.1 enabled hw acceleration. Kwin effects seem to work fine (except translucency). Games work too, though I have not tested anything in Wine or Source based games. Been watching some movies with VDPAU and that works. DPM works too, thank God, because those little fans on the DirectCU II unit really whine.

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by Nimbrant View Post
    Has anyone else confirmed this? I can't seem to get glamor to work. I even tried compiling it myself and X fails to start.
    I'm not sure what im doing wrong or where the correct place to submit a bug report is.
    After installing saucy on my Radeon HD 7850 computer, I saw GLAMOR being loaded, and had acceleration.

    (Dota 2 was terribly slow though)

    Leave a comment:


  • agd5f
    replied
    Originally posted by CalcProgrammer1 View Post
    Update!

    I just installed the newest stuff from Oibaf's PPA on my laptop and now both GPU's are initializing with glamor! So, problem solved? No! Now the corruption issue occurs on my laptop just as it does on my desktop (which I haven't updated yet). Could the corruption be caused by simply two glamor contexts being initialized at once? I can't test DRI_PRIME to see if it works since my terminal doesn't show text but I assume it is working since the Xorg log shows both cards as being acceleration enabled. I'll get a log from the laptop and post it here soon. So now it seems r600+r600 = corruption AND r600+radeonsi = corruption. Anyone else want to verify this?
    Make sure your ddx has this patch:

    Leave a comment:


  • CalcProgrammer1
    replied
    Update!

    I just installed the newest stuff from Oibaf's PPA on my laptop and now both GPU's are initializing with glamor! So, problem solved? No! Now the corruption issue occurs on my laptop just as it does on my desktop (which I haven't updated yet). Could the corruption be caused by simply two glamor contexts being initialized at once? I can't test DRI_PRIME to see if it works since my terminal doesn't show text but I assume it is working since the Xorg log shows both cards as being acceleration enabled. I'll get a log from the laptop and post it here soon. So now it seems r600+r600 = corruption AND r600+radeonsi = corruption. Anyone else want to verify this?

    Leave a comment:


  • Nimbrant
    replied
    Turns out I had some old libdrm_radeon and mesa libGL files being loaded from a manual install a while ago.
    I compiled glamor from git but the packaged glamor would probably work fine.

    I am using a radeon 7750 with ubuntu 13.10 and gnome3. I haven't done much besides open a browser to write this post, but I will give an update if I notice any screen corruption.

    Code:
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE
    OpenGL version string: 2.1 Mesa 9.2.1
    OpenGL shading language version string: 1.30

    Leave a comment:


  • Tyler_K
    replied
    Originally posted by Tyler_K View Post
    Tested this myself tonight. Like yourself, glamor is found to initialize properly on both of the r600 class adapters, but I too get correuption city. Switching back and forth from console seems to clear up a tiny bit of that, such that you can begin to make a few things out (such as a portion of the background wallpaper image), but the desktop (KDE) is still completely unusable in this state.
    Just saw a recent X log of a person using intel + SI(glamor) and it was error free. No info on any screen corruption issues.

    But it would be good to know if, say, intel(glamor) + radeon(SI or r600)(glamor) borks too.

    Leave a comment:


  • Nimbrant
    replied
    Originally posted by CalcProgrammer1 View Post
    Nope, not the case anymore. The latest packages definitely have glamor support enabled.
    Has anyone else confirmed this? I can't seem to get glamor to work. I even tried compiling it myself and X fails to start.
    I'm not sure what im doing wrong or where the correct place to submit a bug report is.

    EDIT: I should also mention that from the Xorg.0.log it does appear that glamor and glamoregl are being loaded, which means that glamor is enabled. But there still appears to be an issue with glamor.

    This is taken from the end of my Xorg.0.log after X fails to start.
    Code:
    Fatal server error:
    [     5.190] (EE) (EE) BUG: triggered 'if (f[f_idx])'
    [     5.190] (EE) BUG: ../../os/log.c:464 in pnprintf()
    [     5.190] (EE) Unsupported printf directive '#'
    [     5.190] (EE) 
    [     5.190] (EE) Backtrace:
    [     5.190] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7fd129f7602d]
    [     5.190] (EE) 1: /usr/bin/X (LogVMessageVerbSigSafe+0x87d) [0x7fd129f818ad]
    [     5.190] (EE) 2: /usr/bin/X (FatalError+0xd5) [0x7fd129f81b75]
    [     5.190] (EE) 3: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (0x7fd126151000+0x25caf) [0x7fd126176caf]
    [     5.190] (EE) 4: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (0x7fd126151000+0x25e0e) [0x7fd126176e0e]
    [     5.190] (EE) 5: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (glamor_create_pixmap+0x298) [0x7fd1261551c8]
    [     5.190] (EE) 6: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fd123a38000+0x4ba33) [0x7fd123a83a33]
    [     5.190] (EE) 7: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (glamor_glyphs_init+0x16d) [0x7fd12615cdcd]
    [     5.190] (EE) 8: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fd123a38000+0x4b5f8) [0x7fd123a835f8]
    [     5.190] (EE) 9: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fd123a38000+0x4444e) [0x7fd123a7c44e]
    [     5.190] (EE) 10: /usr/bin/X (0x7fd129dd4000+0xc6bde) [0x7fd129e9abde]
    [     5.190] (EE) 11: /usr/bin/X (0x7fd129dd4000+0x44426) [0x7fd129e18426]
    [     5.190] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fd127b10de5]
    [     5.190] (EE) 13: /usr/bin/X (0x7fd129dd4000+0x448af) [0x7fd129e188af]
    [     5.190] (EE) 
    [     5.190] destination is framebuffer incomplete: unsupported [%#x]
    [     5.191] (EE) 
    [     5.191] (EE)
    Last edited by Nimbrant; 20 October 2013, 06:11 PM.

    Leave a comment:

Working...
X