You are not logged in.
I assume there is no way of getting opengl higher than 3.0 on a Radeon HD 6770 with mesa (?
Offline
your OpenGL core profile should be OpenGL3.3 , but i assume you want OpenGL 4.1 ?
A few R600 chipsets do expose OpenGL 4.x support, but you'll need llvm 3.9 or later to get that.
For time being easiest way is to install mesa-git & llvm-svn , check arch discussion topic about mesa-git .
disclaimer : i have no idea if your chipset is one of those few.
Last edited by Lone_Wolf (2016-10-10 13:52:01)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi,
anyone having trouble run gdm after today update to 3.22?
Oct 12 16:59:14 etnyx-work systemd[1005]: Started Sound Service.
Oct 12 16:59:21 etnyx-work dbus[503]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Oct 12 16:59:21 etnyx-work systemd[1]: Starting Locale Service...
Oct 12 16:59:21 etnyx-work gnome-shell[1121]: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory)
Oct 12 16:59:21 etnyx-work dbus[503]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 12 16:59:21 etnyx-work systemd[1]: Started Locale Service.
Oct 12 16:59:22 etnyx-work dbus[503]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
Oct 12 16:59:22 etnyx-work systemd[1]: Starting Location Lookup Service...
Oct 12 16:59:22 etnyx-work polkitd[674]: Registered Authentication Agent for unix-session:c4 (system bus name :1.32 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Oct 12 16:59:22 etnyx-work gnome-shell[1121]: JS LOG: No permission to trigger offline updates: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered
Oct 12 16:59:22 etnyx-work dbus[503]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Oct 12 16:59:22 etnyx-work systemd[1]: Starting WPA supplicant...
Oct 12 16:59:23 etnyx-work dbus[503]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Oct 12 16:59:23 etnyx-work systemd[1]: Started WPA supplicant.
Oct 12 16:59:23 etnyx-work wpa_supplicant[1285]: Successfully initialized wpa_supplicant
Oct 12 16:59:23 etnyx-work dbus[503]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Oct 12 16:59:23 etnyx-work systemd[1]: Started Location Lookup Service.
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): EDID vendor "DEL", prod id 16475
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Using hsync ranges from config file
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Using vrefresh ranges from config file
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Printing DDC gathered Modelines:
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
Oct 12 16:59:23 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
Oct 12 16:59:24 etnyx-work dbus[503]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 12 16:59:24 etnyx-work systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 12 16:59:24 etnyx-work gnome-session-binary[1091]: Entering running state
Oct 12 16:59:24 etnyx-work dbus[503]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Oct 12 16:59:24 etnyx-work systemd[1]: Starting Hostname Service...
Oct 12 16:59:24 etnyx-work xbrlapi.desktop[1300]: openConnection: connect: No such file or directory
Oct 12 16:59:24 etnyx-work xbrlapi.desktop[1300]: cannot connect to braille devices daemon brltty at :0
Oct 12 16:59:24 etnyx-work dbus[503]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 12 16:59:24 etnyx-work systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 12 16:59:24 etnyx-work dbus[503]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 12 16:59:24 etnyx-work systemd[1]: Started Hostname Service.
Oct 12 16:59:24 etnyx-work gnome-settings-[1274]: g_task_return_error: assertion 'error != NULL' failed
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: Shader compilation failed:
Vertex shader failed to compile with the following errors:
ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
ERROR: error(#273) 1 compilation errors. No code generated
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: Shader compilation failed:
Fragment shader failed to compile with the following errors:
ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
ERROR: error(#273) 1 compilation errors. No code generated
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: Failed to link GLSL program:
Vertex and Fragment shader(s) were not successfully compiled before glLinkProgram() was called. Link failed.
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:796: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:819: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:823: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:827: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:831: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-opengl.c:748: GL error (1280): Invalid enumeration value
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: Shader compilation failed:
Vertex shader failed to compile with the following errors:
ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
ERROR: error(#273) 1 compilation errors. No code generated
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: Shader compilation failed:
Fragment shader failed to compile with the following errors:
ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
ERROR: error(#273) 1 compilation errors. No code generated
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: Failed to link GLSL program:
Vertex and Fragment shader(s) were not successfully compiled before glLinkProgram() was called. Link failed.
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:384: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:399: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:409: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:796: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:819: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:823: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:827: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:831: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Oct 12 16:59:25 etnyx-work gnome-shell[1121]: driver/gl/cogl-buffer-gl.c:198: GL error (1282): Invalid operation
Oct 12 16:59:28 etnyx-work dbus[503]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Oct 12 16:59:28 etnyx-work dbus[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Oct 12 16:59:30 etnyx-work dbus[503]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Oct 12 16:59:30 etnyx-work dbus[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) AIGLX: Suspending AIGLX clients for VT switch
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Backup framebuffer data.
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) fglrx(0): Backup complete.
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) systemd-logind: got pause for 13:68
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) systemd-logind: got pause for 13:65
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) systemd-logind: got pause for 13:69
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) systemd-logind: got pause for 13:67
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) systemd-logind: got pause for 13:66
Oct 12 17:00:39 etnyx-work /usr/lib/gdm/gdm-x-session[1013]: (II) systemd-logind: got pause for 13:64
Oct 12 17:00:39 etnyx-work systemd[1]: Started Getty on tty2.
After some diging google point me back to 3.18 update situation in this thread, so maybe it similar to this problem,... according to aur discus catalyst-fix-gdm fail on install,...
Should someone confirm this? or have some solution?
Offline
In my case, for my card AMD HD6570, I get slightly better performance with the modesetting driver and glamor than with the xf86-video-ati. Forcing dri3 and glamor improves the performance for xf86-video-ati but it is still slightly better with the generic modesetting driver; particularly for 2D acceleration (gtkperf or cat <very long text file> in an xterm). This is worth mentioning because this generic driver is a really viable and sometimes better solution. We have really two opensource drivers now.
I have tried catalyst in the past, but have had problems with it, 2D acceleration was terrible and 3D was only marginally better. I have not retried recently but it is really a pain to maintain and force to downgrade Xorg, so I will stick with the open source solution.
Last edited by olive (2016-10-13 04:10:36)
Offline
Hi,
anyone having trouble run gdm after today update to 3.22?
After some diging google point me back to 3.18 update situation in this thread, so maybe it similar to this problem,... according to aur discus catalyst-fix-gdm fail on install,...
Should someone confirm this? or have some solution?
I can confirm. Ran into this after updating. Black screen with white dots, some problem with cogl again. No solution, sorry to say.
Gave up on catalyst finally and switched to radeon while waiting for amdgpu to improve. My only complaint is that 144hz doesn't work with 1440p and hawaii (only <= 120hz does). Someone reported this already, hopefully this gets fixed at some point.
Offline
After some diging google point me back to 3.18 update situation in this thread, so maybe it similar to this problem,...
Sorry for late answer, I'm still recovering after some crazy flu virus attack. It's also the reason of why packages weren't updated to support 4.8 kernel (btw for this kernel no additional patch is needed, it only needs simple dependency version bump)
But let's get back to gdm/gnome: Quick look at the problem didn't return positive results. You traced well, it's similar but more complicated and previous patch isn't fixing it anymore. I will look at this closer on tomorrow's evening.
BTW catalyst-fix-gdm@aur was used to cover other problem, it's not needed anymore.
Last edited by Vi0L0 (2016-10-16 20:07:28)
Offline
@Vi0L0, where is the source code for your xserver (1.17)? I need to patch it, but I'm having problems with it.
If you can take a look here, I'd appreciate: https://bbs.archlinux.org/viewtopic.php?id=216766
Cheers
EDIT: Nevermind, got the sources from Arch itself, seems to be working https://git.archlinux.org/svntogit/pack … 470e4b32f7
Last edited by Amanda S (2016-10-17 05:00:23)
If it ain't broke, you haven't tweaked it enough...
Offline
So it looks like I got working gnome. Still no sign of life from gdm, it's unable to map MMIO register space, error looks like this:
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (**) fglrx(0): NoAccel = NO
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (**) fglrx(0): AMD 2D Acceleration Architecture enabled
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (--) fglrx(0): Chipset: "AMD Radeon R9 200 Series" (Chipset = 0x67b0)
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (--) fglrx(0): (PciSubVendor = 0x1462, PciSubDevice = 0x3080)
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (--) fglrx(0): Linear framebuffer (phys) at 0xe0000000
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (--) fglrx(0): MMIO registers at 0xf7b00000
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (--) fglrx(0): I/O port at 0x0000e000
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (==) fglrx(0): ROM-BIOS at 0x000c0000
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE) fglrx(0): failed to map MMIO register space!(EE) fglrx(0): MapMMIO failed
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE) fglrx(0): PreInitAdapter failed
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE) fglrx(0): PreInit failed
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) fglrx(0): === [xdl_xs117_atiddxPreInit] === end
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) UnloadModule: "fglrx"
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) UnloadSubModule: "fglrxdrm"
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) Unloading fglrxdrm
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) UnloadSubModule: "vgahw"
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) Unloading vgahw
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (II) UnloadSubModule: "fglrxdrm"
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE) Screen(s) found, but none have a usable configuration.
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE)
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: Fatal server error:
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE) no screens found(EE)
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: (EE)
paź 17 21:03:30 xaos /usr/lib/gdm/gdm-x-session[1056]: Please consult the The X.Org Foundation support
As for the gnome to get it work (via sddm) I have not only to use known patch to cover glsl version on cogl package, but also on mutter package, which does contain separate copy of cogl and compiles it to make it work lol
I lost at least 2 hours to figure it out, Im probably getting old. Don't have time to update repo, also tomorrow I'm working for whole day so no update tomorrow as well, but maybe wednesday is the day.
For now you can get sources and x86_64 packages from this location: https://drive.google.com/open?id=0B-S6e … 1Jwbjh4Z1U
Let me just paste patches here, i used Ashley Sommer cogl patch as the base:
cogl patch:
--- 1222/cogl/driver/gl/gl/cogl-driver-gl.c 2016-10-17 18:16:05.638995324 +0200
+++ 1222b/cogl/driver/gl/gl/cogl-driver-gl.c 2016-10-17 18:23:58.703175772 +0200
@@ -416,9 +416,14 @@
&ctx->glsl_minor);
}
- if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 2))
- /* We want to use version 120 if it is available so that the
- * gl_PointCoord can be used. */
+
+ if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 5))
+ ctx->glsl_version_to_use = 150;
+ else if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 4))
+ ctx->glsl_version_to_use = 140;
+ else if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 3))
+ ctx->glsl_version_to_use = 130;
+ else if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 2))
ctx->glsl_version_to_use = 120;
else
ctx->glsl_version_to_use = 110;
mutter patch:
--- mutter3221/cogl/cogl/driver/gl/gl/cogl-driver-gl.c 2016-10-17 20:43:31.283749432 +0200
+++ mutter3221b/cogl/cogl/driver/gl/gl/cogl-driver-gl.c 2016-10-17 20:47:44.000000000 +0200
@@ -416,9 +416,13 @@
&ctx->glsl_minor);
}
- if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 2))
- /* We want to use version 120 if it is available so that the
- * gl_PointCoord can be used. */
+ if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 5))
+ ctx->glsl_version_to_use = 150;
+ else if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 4))
+ ctx->glsl_version_to_use = 140;
+ else if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 3))
+ ctx->glsl_version_to_use = 130;
+ else if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 2))
ctx->glsl_version_to_use = 120;
else
ctx->glsl_version_to_use = 110;
edit: just checked and amdgpu driver does work well on those patched packages - good.
btw probably oftopic: convert bin (owned by imagemagick) was eating a lot of my cpu resources - making spikes on all cores every second, every second process was killed and the new one was born for a second and so on. Force removed imagemagick xD it will probably harm my system but oh well ;P no spikes anymore...
Last edited by Vi0L0 (2016-10-17 20:03:36)
Offline
Are you guys able to use AMDGPU-PRO with GCN 1.0 cards such as the R9 270X?
If it ain't broke, you haven't tweaked it enough...
Offline
Are you guys able to use AMDGPU-PRO with GCN 1.0 cards such as the R9 270X?
You have to wait for Kernel 4.9 for that and I don't know if it will be experimental or not.
Offline
Amarildo wrote:Are you guys able to use AMDGPU-PRO with GCN 1.0 cards such as the R9 270X?
You have to wait for Kernel 4.9 for that and I don't know if it will be experimental or not.
I did try AMDGPU-PRO with 4.9-wip. It's interesting that AMDGPU alone works, but AMDGPU-PRO doesn't.
If it ain't broke, you haven't tweaked it enough...
Offline
So I may had a lucky shot 2 pages ago when saying "280x is rebranded Radeon HD 7970 GHz Edition, gcn 1.0, and AFAIK it's not supported by amdgpu. Heard rumor that it will be added to 4.9 kernel, but then I _believe_ AMD would have to realase new amdgpu-pro libs to cover support on this (blob) side."
BTW @Amarildo: what error does -pro throw?
Last edited by Vi0L0 (2016-10-19 06:53:13)
Offline
ChemBro wrote:Amarildo wrote:Are you guys able to use AMDGPU-PRO with GCN 1.0 cards such as the R9 270X?
You have to wait for Kernel 4.9 for that and I don't know if it will be experimental or not.
I did try AMDGPU-PRO with 4.9-wip. It's interesting that AMDGPU alone works, but AMDGPU-PRO doesn't.
Oh sorry, I didn't read the "PRO" part...
Offline
I've updated aur and repos (also uploadded cogl and newer mutter there).
+ just to let you know - yesterday I recompiled amd-staging-4.7 kernel once more and found its amdgpu driver stable and fast on 290x (after weeks of beeing unstable). If you want you can check my x86_64 build [1], it comes with DAL, experimental CONFIG_DRM_AMDGPU_CIK and CONFIG_DRM_AMDGPU_SI support, so basically covers all GCN cards.
[1] https://drive.google.com/open?id=0B-S6e … ENsX3ljZDQ
Last edited by Vi0L0 (2016-10-19 20:24:49)
Offline
BTW @Amarildo: what error does -pro throw?
A bunch of core dumping and library errors. Sorry, I don't remember right now.
I tried using AMDGPU-PRO in two ways:
- Using the latest 4.9-wip (it's constantly updated by AMD and a few Xorg developers) with AMDGPU Kernel Driver, Mesa-git, LLVM-SVN, etc. AMDGPU (OSS) works with Mesa, though performance is terrible. AMDGPU-PRO with this Kernel Driver doesn't work. I didn't install the KMS package for AMDGPU-PRO in this case. Also, when I removed 'xserver-xorg-amdgpu-pro' (and used 'xf86-video-amdgpu' instead) the whole system hangs forcing me to solve things via LiveCD;
- Using the entire AMDGPU-PRO package from the AUR;
None work.
If it ain't broke, you haven't tweaked it enough...
Offline
Just re-checked AMDGPU (4.9-wip). Performance is AMAZING! Much better than Radeon, and then obviously crushes FGLRX.
While on ETS2 I got 15-30 FPS on Radeon and FGLRX, I'm getting 30-60 on AMDGPU.
CSGO performance is the same across all 3 drivers.
X-Plane is 5-25 FPS (Ultra) on Catalyst, 35-40 on Radeon and ADMGPU, with custom scenery as well.
CSS is the same on Radeon and AMDGPU.
Mouse lag no longer happens.
https://i.imgur.com/kg5wkJH.png
I guess only thing left now is OpenCL on AMDGPU. Other than that, and the horrible TF2 hang bug [1], AMDGPU is a much better driver.
[1] https://bugs.freedesktop.org/show_bug.cgi?id=93649
Last edited by Amanda S (2016-10-20 04:09:57)
If it ain't broke, you haven't tweaked it enough...
Offline
Hello,
Yesterday I’ve tried to install catalyst on my freshly installed new PC (AMD A10 with A88 chipset). I pass over all my problems of pacman.conf and xorg issues.
Finally I’ve installed xorg thru [xorg18] repository, first problem : No valid gpg key for xorg package. No problem with other package from the repository so I guess the gpg keys are well installed. --> Ok bypassed temporally by adding ‘’SigLevel = Never’’ in my pacman.conf.
On a second time I couldn’t install catalyst-hook as it require linux<4.7. Linux has been updated to 4.8 yesterday! Ok I have downgrade from 4.8.1-1 to 4.7.6-1 from pacman cache. BTW it is not enough… Do I have to downgrade to 4.6.5 (july 2016) or do you plan to upgrade catalyst-hook soon? If I have to downgrade linux, where can I find the old package?
Last edited by lesebas (2016-10-20 10:14:09)
Offline
Finally I’ve installed xorg thru [xorg18] repository, first problem : No valid gpg key for xorg package. No problem with other package from the repository so I guess the gpg keys are well installed. --> Ok bypassed temporally by adding ‘’SigLevel = Never’’ in my pacman.conf.
There's something wrong there. You don't need an xorg 1.18 repo because that's already in [Extra]. You need the xorg 117 repo. And to add Vi0l0's gpg key to pacman, you only need to check his user page at the wiki:
pacman-key --keyserver pgp.mit.edu --recv-keys 0xabed422d653c3094
pacman-key --lsign-key 0xabed422d653c3094
This is how the repos look to me:
[xorg117]
Server = http://catalyst.wirephire.com/repo/xorg117/$arch
## Mirrors, if the primary server does not work or is too slow:
#Server = http://mirror.hactar.xyz/Vi0L0/xorg117/$arch
[catalyst]
Server = http://mirror.hactar.xyz/Vi0L0/catalyst/$arch
Put them before/above [Core] then do a "pacman -Suu" to downgrade your xorg.
On a second time I couldn’t install catalyst-hook as it require linux<4.7. Linux has been updated to 4.8 yesterday! Ok I have downgrade from 4.8.1-1 to 4.7.6-1 from pacman cache. BTW it is not enough… Do I have to downgrade to 4.6.5 (july 2016) or do you plan to upgrade catalyst-hook soon? If I have to downgrade linux, where can I find the old package?
It is not enough only if you don't make pacman ignore "linux" and "linux-headers" (see Wiki, get used to it).
Vi0l0 had already updated his repo and I could successfuly build catalyst-hook on linux 4.8.
Cheers.
If it ain't broke, you haven't tweaked it enough...
Offline
@lesebas: like Amarildo said + let me explain: wirephire mirror is working but I don't have access to it anymore and so I'm unable to update, just switch to hactar.xyz mirror
@Amarildo: amd-staging-4.7 contains newer amd patches than 4.9-wip, those patches were merged to 4.10-wip, so they are now head-to-head while 4.9-wip is lagging behind. The main difference is I believe in the base - staging is basing on stable 4.7 kernel while wip are basing on still-unreleased kernels, also I believe that latest staging is most fresh when it comes to amd patches.
Last edited by Vi0L0 (2016-10-20 11:03:52)
Offline
There's something wrong there. You don't need an xorg 1.18 repo because that's already in [Extra]. You need the xorg 117 repo. And to add Vi0l0's gpg key to pacman, you only need to check his user page at the wiki:
pacman-key --keyserver pgp.mit.edu --recv-keys 0xabed422d653c3094
pacman-key --lsign-key 0xabed422d653c3094
Argg!!! I've missed 1.8 and 1.18! you're right 1.17 should work!
I've already imported the gpg key... but I think that old package with 1.8 version are not correctly signed.
It is not enough only if you don't make pacman ignore "linux" and "linux-headers" (see Wiki, get used to it).
Vi0l0 had already updated his repo and I could successfuly build catalyst-hook on linux 4.8.
Cheers.
It's means that version 4.7.6 works with catalyst or to I have to downgrade to 4.6.5?
Offline
@Amarildo: amd-staging-4.7 contains newer amd patches than 4.9-wip, those patches were merged to 4.10-wip, so they are now head-to-head while 4.9-wip is lagging behind. The main difference is I believe in the base - staging is basing on stable 4.7 kernel while wip are basing on still-unreleased kernels, also I believe that latest staging is most fresh when it comes to amd patches.
Thanks, I will try amd-staging. At the time I compiled my 4.9, latest commit was ~50 mins so I thought that was the latest.
Argg!!! I've missed 1.8 and 1.18! you're right 1.17 should work!
I've already imported the gpg key... but I think that old package with 1.8 version are not correctly signed.
Why would you want the old 1.8 package? Go with 1.17.
It's means that version 4.7.6 works with catalyst or to I have to downgrade to 4.6.5?
4.7.6 already worked, and there's no need for 4.6.5. Go with 4.8 if you want, it works.
If it ain't broke, you haven't tweaked it enough...
Offline
@Vi0L0 can you add the patch from https://aur.archlinux.org/packages/mutter-catalyst to your mutter build too?
It still applies for 3.22 but now also needs the cogl patch, so i thought it to be an unnecessary duplication to still have the aur pkg separately.
Offline
@Amarildo: amd-staging-4.7 contains newer amd patches than 4.9-wip, those patches were merged to 4.10-wip, so they are now head-to-head while 4.9-wip is lagging behind. The main difference is I believe in the base - staging is basing on stable 4.7 kernel while wip are basing on still-unreleased kernels, also I believe that latest staging is most fresh when it comes to amd patches.
I assume you are talking about linux kernels here. If so, do I make them with the Arch Build System, or are there PKGBUILDS you can get to build them?
Offline
I assume you are talking about linux kernels here. If so, do I make them with the Arch Build System, or are there PKGBUILDS you can get to build them?
Yes I'm talking about Linux kernels.
I build them with PKGBUILD's and the other files. I built 4.10 by downloading 'linux-git' from the AUR and editing the PKGBUILD and the config files to fit my needs. See here: https://github.com/amarildojr/linux-4.1 … .10.tar.gz
But for some reason the PKGBUILD still identifies the Kernel as '4.8.0-rc8-10', which is not true. I couldn't identify what's causing this =p
EDIT: I think it's the "set localversion to git commit" and "get kernel version" parts.
Last edited by Amanda S (2016-10-22 11:08:42)
If it ain't broke, you haven't tweaked it enough...
Offline
@Vi0L0 can you add the patch from https://aur.archlinux.org/packages/mutter-catalyst to your mutter build too?
I don't have a laptop, but will test this patch and if it will work well with my 290x I will add it to my mutter.
Edit: works well, repos were updated
It still applies for 3.22 but now also needs the cogl patch, so i thought it to be an unnecessary duplication to still have the aur pkg separately.
I believe that leaving aur version is good idea, it will make patch easily accessible for others, who may also need it. Though it would be good to update it to the newest version and add cogl patch.
Last edited by Vi0L0 (2016-10-24 19:56:24)
Offline