LinuxQuestions.org - [SOLVED] Ryzen 2400g / 3400g and Slackware 14.2 support

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Ryzen 2400g / 3400g and Slackware 14.2 support (https://www.linuxquestions.org/questions/slackware-14/ryzen-2400g-3400g-and-slackware-14-2-support-4175658439/)

Quote:

Originally Posted by tramtrist (Post 6025341)

I wasn't aware Ryzen GPU acceleration/support was available pre-5.x Kernel...

It's in the later 4.x series, but it's MASSIVELY improved in 5.x

Quote:

Originally Posted by tramtrist (Post 6025341)

I wasn't aware Ryzen GPU acceleration/support was available pre-5.x Kernel...

I think the 4.15 kernel is what introduced kernel support for the newer GPUs and then support has just gotten better since then. I'm not doing much with my APU, but it does work fine for the GPU video decoding and whatever the default effects are in KDE4 using -current from May (including the stock 4.19.x kernel at that time). I haven't really tried any gaming on it.

Writing from 3400g

Hi to all, and sorry for the long delay (I have been on holiday)

I had some troubles trying to make this APU work with stock slackware-current.

It seems that, even if the vega cores are the same and in the same number as in the 2400g, the 3400g changed enough inner things to not work (outside for vesa) with stock 4.19.66 -current kernel.

It took me quite a while to figure out (the other pc that I build (2400g) works great with a less updated mesa-18.2 and 4.19 kernel on MX linux), until I stumbled on a random comment from a arch linux guy who said that in it's configuration (kernel 5.X) worked great in reply to another user with my same problem (but on arch)

since arch and -current share the same mesa version, I decided to just upgrade the kernel and check if it worked.

Long story short, it worked, but the amdgpu driver failed to recon my monitor correctly, so at boot my console was all blurred and extremely low resolution (640x480 I think), and X start in the same way as the console (even with a xorg.conf file) because of KMS...

So I added the "video=1280x1024" bit to the append line in /boot/efi/EFI/Slackware/elilo.conf

Now both the console and X start with the correct resolution (and without xorg.conf)

direct rendering works great, and both games and video render correctly (game performance are very good, both in wine's and native's linux games)

But running current has it's own set of problem of course....

So I need your help once again, since I new to this spin of Slackware.

I downloaded sbotools and tried to use it (I think it uses the 14.2 branch of slackbuild tree, but I used it for so long, that it was worth a try) expecting the worst, but instead it worked for MOST of my required packages, with few exceptions.

Then I downloaded sbopkg, read the docs, pointed to ponce git repository, and tried to install the missing packages.

Some of them installed correctly, others didn't

Code:

vhba needed by cdemu failed with "cc1: error: incompatible gcc/plugin versions"



steamos-xpad failed with "cc1: error: incompatible gcc/plugin versions"



thunar-media-tags-plugin failed with "checking for thunarx-2 >= 1.0.1... not found

*** The required package thunarx-2 was not found on your system.

*** Please install thunarx-2 (atleast version 1.0.1) or adjust

*** the PKG_CONFIG_PATH environment variable if you

*** installed the package in a nonstandard prefix so that

*** pkg-config is able to find it."



arc-theme-red failed with  "configure: error: Invalid GNOME version: 3.24" (note: arc-theme worked instead)



mu64py failed with lots of python errors with the last line being "ValueError: PyCapsule_GetPointer called with incorrect name"

another thing: I require portaudio-32bit for pcsx2, however I have failed to find a way to use sbopkg to build a 32bit version of a package. Is there a way that I missed?
Then I tried to build it manually with the normal Slackbuild (from ponce git) using the ". /etc/profile.d/32-dev.sh" and then start the build. It worked, but the package contained /lib64 directories, and convert32pkg refused to convert it.... what I'm doing wrong?

Sorry for the monumental post!

portaudio solved

ok, as for portaudio I managed to compile and install it.

I forgot (it was such a long time since I manually compiled a slackbuild!) to set ARCH=i486 after sourcing 32dev.sh.
so in order I had to

Code:

#. /etc/profile.d/32dev.sh

#export ARCH=i486

#sbopkg -i portaudio

However it FAILED anyway... then I figured the reason, I have set the jobs nr in the sbopkg.conf file.
Most build succeeded normally, but some, like this, fail.
Commenting that line in sbopkg.conf solved the issue, and a conversion of the resulting 32bit packages closed the deal.
So one problem less. PCSX2 then compiled succesfully (and WITH the -j8 line in sbopkg.conf enabled)

*) vhba module and steamos-xpad, however seems to suffer from a gcc<->kernel compatibility problem. No idea on where to start with it. Any clues?

*) for thunar-media-tags-plugin I tried to point the PKG_CONFIG_PATH to both /usr/lib64/pkgconfig/ to no avail, and then to /usr/lib64/pkgconfig/thunarx-3.pc directly, but it still end with the same "checking for thunarx-2 >= 1.0.1... not found".... I do have thunarx-3, it SHOULD be higher version than thunarx-2, no?

*) m64py still fail with

Code:

m64py-0.2.2/src/m64py/core/defs.py

m64py-0.2.2/src/m64py/core/vidext.py

running install

running build

running build_qt

Traceback (most recent call last):

  File "setup.py", line 322, in <module>

    ("share/applications", ["xdg/m64py.desktop"]),

  File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup

    dist.run_commands()

  File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands

    self.run_command(cmd)

  File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command

    cmd_obj.run()

  File "/usr/lib64/python2.7/distutils/command/install.py", line 563, in run

    self.run_command('build')

  File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command

    self.distribution.run_command(command)

  File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command

    cmd_obj.run()

  File "setup.py", line 287, in run

    self.run_command("build_qt")

  File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command

    self.distribution.run_command(command)

  File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command

    cmd_obj.run()

  File "setup.py", line 62, in run

    self.compile_ui(join(dirpath, filename))

  File "setup.py", line 38, in compile_ui

    uic.compileUi(ui_file, fp, from_imports = True)

  File "/usr/lib64/python2.7/site-packages/PyQt4/uic/__init__.py", line 173, in compileUi

    winfo = compiler.UICompiler().compileUi(uifile, pyfile, from_imports, resource_suffix)

  File "/usr/lib64/python2.7/site-packages/PyQt4/uic/Compiler/compiler.py", line 55, in __init__

    CompilerCreatorPolicy())

  File "/usr/lib64/python2.7/site-packages/PyQt4/uic/uiparser.py", line 183, in __init__

    self.factory = QObjectCreator(creatorPolicy)

  File "/usr/lib64/python2.7/site-packages/PyQt4/uic/objcreator.py", line 97, in __init__

    self._cwFilters.append(plugin_locals["getFilter"]())

  File "<string>", line 22, in getFilter

ValueError: PyCapsule_GetPointer called with incorrect name

even after changing jobs count... no idea on that one too, i've no experience with python...

SOLVED and moved to another thread the other problems

Hi to all again, I'll mark this thread as solved, since Ryzen 5 3400g works well with -current as long as a 5.2 kernel is installed, and to answer myself on one of my first posts, yes, VESA do works out of the box (to a max of 800x600) with -current stock kernel. Only acceleration and higher resolutions, require compiling a 5 kernel.

So, I'll move the rest of the questions to THIS thread instad, to make things easier for everyone.

Also, I haven't read it anywhere (probably my fault) but SBOTOOLS do works with current, in /etc/sbotools/sbotools.conf it's enough to set the SLACKWARE_VERSION= to current, then it will automagically use Ponce-Git as a source.

In the meanwhile, thanks to everyone that answered here!