Hi Chris
AFAICS, it doesn’t really tell us anything more then what we already know. But thanks anyway. (its not a big deal regardless)
I can not find a repo in the Community Repositories list. Where would one be please? I did find the source code for Xorg on a mirror at http://mirror.csclub.uwaterloo.ca/x.org/X11R7.7/ but I would be very uncomfortable in compiling.
No, no, don’t bother with that … you’d zypper dup from here: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Leap_42.2/
How do I switch to glamor please?
Sorry, It’s not quite straight forward for you because of the multiple gpus (and from different vendors) …
For radeon:
- if you have v7.8.0 of xf86-video-ati driver (which I don’t think Leap has naitively), then it will enable DRI3 by provided
that X server version is >= 1.18.3 and glamor is enabled … when that is the case, then your Xorg log should report that DRI3 is enabled … note that it may appear that there is some conflicting info returned by glamor about it using DRI2. The latter can be ignored. And you can verify that DRI3 is indeed being utilised by the output of one of the aforementioned tests listed above in the thread (glxgears, glxinfo). - Glamor, itself, is not yet enabled by default (though should be enabled in v7.8.1 of the radeon xorg driver). So, by default, the driver, will still be using EXA, and hence only provide DRI2
- To enable glamor in older driver versions, just add an Acel option for it (glamor) to the Device section in /etc/X11/Xorg.conf.d …(see “man radeon”)
- To enable DRI3 in older driver versions, aside from the glamor caveat, just add a DRI option for it (DRI) in the Device section in /etc/X11/Xorg.conf.d … (see “man radeon”)
Got that? lol! … Oh, but wait, there’s more: the Intel side ! Leaving alone anything about its 2D Accel handling and DRI3 support, You want to bring things together by having both devices listed in the Device snipet file and then both in the Screen snipet file. Respectively like:
Section "Device"
Identifier "Radeon Device"
Driver "radeon"
BusID "PCI:1:0:0"
Option "AccelMethod" "glamor"
# Option "DRI" "3"
EndSection
Section "Device"
Identifier "Intel Device"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
and
Section "Screen"
Identifier "Default Screen"
Device "Intel Device"
Device "Radeon Device"
EndSection
If that works, know that you likely will get some glitching with glamor. v1.19 of the Xserver sees a number of glamor improvements, so I expect that to go away. Also note that when you get v7.8 of the radeon driver, there is potential you might also experience the error that I discuss in that other thread.
You may even wish to change the Intel driver to use UXA or, alternatively, don’t use the intel Xorg driver, but use the generic modesetting driver for the Intel device instead … both of which may provide help with your Plasma problems. See: https://forums.opensuse.org/showthread.php/521519-Screen-Freeze-on-Leap-42-2-only-option-is-reboot
In blender’s manual it states the following crieria which my card does not meet -
[QUOTE]OpenCL is supported for GPU rendering with AMD graphics cards. We only support graphics cards with GCN architecture (HD 7xxx and above). Not all HD 7xxx cards are GCN cards though, you can check if your card is here[QUOTE]Oh well, at least I now why now. Time to look at building a box with a NVidia GTX900 series card (or two
.[/QUOTE]
[/QUOTE]Ahh, yes, as expected, it was in relation to openCL. And so, in that regard, in terms of options, don’t overlook the obvious (a supported GCN device) … you might want to also keep an eye on, or consider, the ROCm develpements too:
chris@linux-4j2s:~> dmesg | grep -i dpm
3.618727] [drm] radeon: dpm initialized
…
Please ignore that previous screenshot of mine of the vgaswitcheroo settings. I did a “stupid” thing and somehow managed to get both cards powered. It is now as it should be.
linux-4j2s:/home/chris # cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynOff:0000:01:00.0
1:IGD:+:Pwr:0000:00:02.0
Ahh, very good; indeed, as it should be … Perhaps that “mishap” would account for the unexpected and poor performance behaviour mentioned previously
Happy to return the favour. You want me to do this in Plasma5 or LXDE? I do switch from the Desktop to a tty ‘semi regularly’ already. I usually use an external monitor connected via HDMI with the laptop LCD turned off. In Plasma5 sometimes the screen would go blank or I would loose the task bar at the bottom. LXDE has been ROCK SOLID! I’ll will switch back to Plasma5 and use the tty’s. If(when) it crashes what logs do you want?
Whatever DE you prefer (the error I encounter is with the server side of things, and is agnostic about the desktop/type of user session). You don’t have to provide any log if it crashes – just have a look through the xorg log for the crashed session (which, would then be “Xorg.0.log.old”, and not the now current instance … you’d likely be able to find the old one in systemd journaling anyway, if you know the time it occurred, in any case) … just be on the lookout for error messages along the lines of "failed to set mode: No space left on device " and “EnterVT failed for gpu”
I’m not expecting you to notice such though under or with your current environment. As I mentioned, that may change it you get adventurous and update. Thanks.
