I have an old netbook with AMD E-350 dual core CPU and HD6310 integrated GPU. It’s old but has 8GB RAM and one of the first 128 GB SSD, so it is not too shabby running oS 13.1 64-bit with KDE 4.11.5 with a few desktop effects enabled.
Since Mr. Friedmann posted that there will be no fglrx for 42.2, and once when I had to temporarily revert to the open source driver (radeon?), there were screen artifacts (pink stripes) and suspend/resume and heating issues, I’m wondering if LEAP 4.2 will work OK with the open source driver on this old GPU or if I should stick to 42.1.
If someone had already tried something similar or have some info on this, I’d be thankful.
On Sat 03 Dec 2016 04:26:02 PM CST, brunomcl wrote:
brunomcl;2802644 Wrote:
> Hi there,
>
> I have an old netbook with AMD E-350 dual core CPU and HD6310
> integrated GPU. It’s old but has 8GB RAM and one of the first 128 GB
> SSD, so it is not too shabby running oS 13.1 64-bit with KDE 4.11.5
> with a few desktop effects enabled.
>
> Since Mr. Friedmann posted that there will be no fglrx for 42.2, and
> once when I had to temporarily revert to the open source driver
> (radeon?), there were screen artifacts (pink stripes) and
> suspend/resume and heating issues, I’m wondering if LEAP 4.2 will
> work OK with the open source driver on this old GPU or if I should
> stick to 42.1.
>
> If someone had already tried something similar or have some info on
> this, I’d be thankful.
Given the implications on this http://tinyurl.com/hsxvdvf perhaps I
should leave 42.2 away from this netbook…
Comments, anyone?
TIA
Hi
No issues seen here with GNOME DE, think I might have a E-350 system
here with similar graphics, have to sort through the junk pile
I would grab a live Tumbleweed release and fire that up on it to see
how it goes with the radeon driver?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Just a follow up: both TW (from last week) and 42.2 (after updates) with the opensuse AMD driver have problems with KDE compositing. Transitions instead of being smooth look like a stroboscopic effect, screen repaint by blocks sometimes is quite slow, and only for brief intervals everything works. It’s bad to the point of being unusable.
I didn’t try with compositing disabled - it’s settings changed place in 42.2 and I wrongly assumed it was permanently on now. It probably would have worked OK for a no-bling desktop.
Thus I installed 42.1 and after updates and switch to the fglrx driver it works as it should, bling and all.
It seems I’ll have to forgo AMD graphics in my next devices, which is a pity as their onboard GPUs are miles ahead of Intel HD.
I remember the E-350s were problematic (i.e. similar anaemic performance as to what you’ve described) previously, but it was because of the default clocks being set really low until proper power management (DPM) was introduced.
What you’ve described sounds like that (but should have long since been corrected), or, an openGL related issue.
I wouldn’t give up on it, unless you’re just looking for a “it works out of the box and I don’t want to have to fiddle with it”. As, on the one hand, its good on you to have tried out two different releases, but on the other hand, what investigations under the hood (so to speak) did you perform and what were the results found? i.e. what is telling when you ran something like:
I don’t think so, sysinfo reports the correct idle and full load frequencies, and it worked OK with the previous oS 13.1+fglrx.
None really. This is a seldom used netbook, approaching EOL. To make things worse, the ENTER key stopped working. Perhaps I can find a replacement keyboard easily (or remap it to another key), else It’ll probably be consigned to the great hardware pile in the sky…
:~> glxinfo | grep version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 4.4.13416 Core Profile Context 15.302
OpenGL core profile shading language version string: 4.40
OpenGL version string: 4.5.13416 Compatibility Profile Context 15.302
OpenGL shading language version string: 4.40
:~>
Yeah, the fglrx stack had the proper power mgmt for them. The oss stack didn’t start getting proper dpm until kernel ~3.10 IIRC, and a number of adapters/apus took a while longer.
None really. This is a seldom used netbook, approaching EOL.
I hear ya
To make things worse, the ENTER key stopped working.
Ouch!
Perhaps I can find a replacement keyboard easily (or remap it to another key), else It’ll probably be consigned to the great hardware pile in the sky…
I see
:~> glxinfo | grep version...
Oops, sorry, while that does provide some useful info, its actually not the glxinfo command I was intending … in any regard, that looks like the GL info for the prop driver, as opposed to with oss/Mesa
What I had meant/intended was for you to run, with the oss driver stack, is the following :
LIBGL_DEBUG=verbose glxinfo -B
If you don’t have (or want to install TW again), you could always just test with a live CD version
