Configure Realtime Kernel to be Compatible with AMD driver

zabrielza · 2015-08-09 14:59:22

Hello,

I am new In ArchLinux world, about 6 months. (about 7-8 years in Linux Wolrd). I will explain the reasons I want to have both Realtime Kernel and A proprietary Graphics Card Driver. I study architecture ( so, I work with programs like blender, qcad, draftsight, freecad, gimp, Photoshop-via wine, Maya, Kdenlive, Nuke X etc) So I want my graphics card working 100% as expected and also I am interested in music production and work sometimes as DJ ( so, I want to work with Ardour and any other Ableton-related Application, But mainly I have to use Traktor-via wine- I have to run Jack server and connect it to wineasio) and for that reason a realtime kernel is useful in latency related problems.

My graphics Card is AMD Radeon HD4890 2Gb. I have Installed the amd legacy driver through Vi0L0 repository. In the past I have tried compiling Realtime Kernel and was successful to get it to work with my graphics card, But as I remember that was on Ubuntu Studio.So, I tried again on debian several months later and was successful too, after a lot of effort. So, 2 months before I tried to get it to work on Arch Linux (which is the best distro in my opinion, for the way I want to work on my computer) and was not successful. I tried installing from AUR linux-rt and linux-rt-lts. I think that I have tried to compile a kernel but I am a little bit confused about compiling in arch linux and would like some guidance.

If anyone would like to help me configure the system for my needs it would be greatly appreciated. Any suggestion about how to start or any explanation about why realtime kernel and amd driver cannot work together on my system, would be great.

EDIT: I have already ran a script realtimeconfigquickscan by raboof. I have set everything except the realtime kernel.

Info:

uname -a

Linux zabArch 4.1.4-1-ARCH #1 SMP PREEMPT Mon Aug 3 21:30:37 UTC 2015 x86_64 GNU/Linux

Thanks in advance

Last edited by zabrielza (2015-08-09 15:07:09)

Lone_Wolf · 2015-08-09 15:08:44

You will probably have to build the driver yourself against the rt-kernel to make it work.

All packages by Violo are in the aur, i think you'll need https://aur.archlinux.org/catalyst-total-hd234k.git/ .

Check wiki for AUR and makepkg if needed.

zabrielza · 2015-08-09 15:17:39

Lone_Wolf wrote:

You will probably have to build the driver yourself against the rt-kernel to make it work.
All packages by Violo are in the aur, i think you'll need https://aur.archlinux.org/catalyst-total-hd234k.git/ .
Check wiki for AUR and makepkg if needed.

So, I have to install the rt package from AUR instead of compiling one myself? The link you posted is 404 not valid.

Lone_Wolf · 2015-08-09 15:35:08

That's because i posted a .git link and browsers can't handle that, i should have posted this : https://aur.archlinux.org/packages/cata … al-hd234k/

You don't have to compile/install the rt-kernel from aur if you don't want to.

Your problem is the catalyst kernel MODULE needs to be build against a specific kernel to work with it.
The catalyst-total-hd234k pacakge from Violo's repo is build against archlinux stock kernel and doesn't understand how t deal with your rt-kernel
By building catalyst-total-hd234k on your machine against your kernel, you get a version that's tailored to your kernel.

clfarron4 · 2015-08-09 16:06:09

Lone_Wolf wrote:

The catalyst-total-hd234k pacakge from Violo's repo is build against archlinux stock kernel and doesn't understand how t deal with your rt-kernel
By building catalyst-total-hd234k on your machine against your kernel, you get a version that's tailored to your kernel.

Alternatively, there are the -hook and -generator packages which should allow you to install the pre-built package and then build all the modules you need with the catalyst_build_module command (I recommend -hook, because you can automate the process). You will find these in the repository, and provide a nice way of managing fglrx with multiple kernels installed on a system.

At least, that's what I do for the multitude of kernels (lqx, 312, tresor, [list continues]) I have installed on my system.

Last edited by clfarron4 (2015-08-09 16:14:35)

zabrielza · 2015-08-09 16:11:04

Lone_Wolf wrote:

That's because i posted a .git link and browsers can't handle that, i should have posted this : https://aur.archlinux.org/packages/cata … al-hd234k/
You don't have to compile/install the rt-kernel from aur if you don't want to.
Your problem is the catalyst kernel MODULE needs to be build against a specific kernel to work with it.
The catalyst-total-hd234k pacakge from Violo's repo is build against archlinux stock kernel and doesn't understand how t deal with your rt-kernel
By building catalyst-total-hd234k on your machine against your kernel, you get a version that's tailored to your kernel.

Ok, I am really trying to understand those words I have not yes installed any rt kernel. The one word that confuses me is "against".

I read from here here that in order to build catalyst for a custom kernel I have to do those things:

1. Obtain the PKGBUILD and catalyst.install files from Catalyst.
2. Editing the PKGBUILD. Two changes need to be made here:
1. Change pkgname=catalyst to pkgname=catalyst-$kernel_name, where $kernel_name is whatever you want (e.g. custom, mm, themostawesomekernelever).
2. Change the dependency of linux to $kernel_name.
3. Build your package and install; run makepkg -i or makepkg followed by # pacman -U pkgname.pkg.tar.gz

Is this similar to the word "against"?

zabrielza · 2015-08-09 16:14:22

clfarron4 wrote:

Lone_Wolf wrote:
The catalyst-total-hd234k pacakge from Violo's repo is build against archlinux stock kernel and doesn't understand how t deal with your rt-kernel
By building catalyst-total-hd234k on your machine against your kernel, you get a version that's tailored to your kernel.
Alternatively, there are the -hook and -generator packages which should allow you to install the pre-built package and then build the module yourself (I recommend -hook, because you can automate the process). You will find these in the repository, and provide a nice way of managing fglrx with multiple kernels installed on a system.
At least, that's what I do for the multitude of kernels (lqx, 312, tresor, [list continues]) I have installed on my system.

Does this mean that after I install The rt-kernel then with catalyst-hook it is recompiled for the specific kernel( rt-kernel) ?

clfarron4 · 2015-08-09 16:18:25

zabrielza wrote:

clfarron4 wrote:
Lone_Wolf wrote:
The catalyst-total-hd234k pacakge from Violo's repo is build against archlinux stock kernel and doesn't understand how t deal with your rt-kernel
By building catalyst-total-hd234k on your machine against your kernel, you get a version that's tailored to your kernel.
Alternatively, there are the -hook and -generator packages which should allow you to install the pre-built package and then build the module yourself (I recommend -hook, because you can automate the process). You will find these in the repository, and provide a nice way of managing fglrx with multiple kernels installed on a system.
At least, that's what I do for the multitude of kernels (lqx, 312, tresor, [list continues]) I have installed on my system.
Does this mean that after I install The rt-kernel then with catalyst-hook it is recompiled for the specific kernel( rt-kernel) ?

Pretty much. What's supposed to happen is that if you install catalyst-hook, then enable AND start the catalyst-hook.service, then you can install any kernel you like and it should build all the required fglrx modules when shutting down, so you can boot up and done. After that initial setup, you shouldn't have to think about fglrx again, unless it doesn't build for some reason or another

I'm a bit paranoid about this kind of stuff, so for good measure, I run the following after any kernel update:

sudo catalyst_build_module all

Last edited by clfarron4 (2015-08-09 16:19:18)

zabrielza · 2015-08-09 16:28:57

Pretty much. What's supposed to happen is that if you install catalyst-hook, then enable AND start the catalyst-hook.service, then you can install any kernel you like and it should build all the required fglrx modules when shutting down, so you can boot up and done. After that initial setup, you shouldn't have to think about fglrx again, unless it doesn't build for some reason or another
I'm a bit paranoid about this kind of stuff, so for good measure, I run the following after any kernel update:
sudo catalyst_build_module all

Ok, I am going to try this now. Have you any suggestion about which rt-kernel to install ? For example, linux-rt comes with 4.0.8 but linux-rt-lts with 3.18.18. Right now I have 4.1.4. I do not know if it matters. Or is it better to build one?

Last edited by zabrielza (2015-08-09 16:29:39)

zabrielza · 2015-08-09 16:43:28

I installed linux-rt-lts and after that

sudo catalyst_build_module all

+ building fglrx module for 3.18.18-rt15-1-rt-lts kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
+ building fglrx module for 4.1.4-1-ARCH kernel ...
  ok.

--------
2015-08-09 19:34:51
Building fglrx module for 3.18.18-rt15-1-rt-lts kernel ...
--------
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
Warning:
kernel includes at /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include not found or incomplete
file: /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include/linux/autoconf.h

Warning:
kernel includes at /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include not found or incomplete
file: /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include/linux/autoconf.h

assuming default: MODVERSIONS=0
Warning:
kernel includes at /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include not found or incomplete
file: /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/arch/x86/include/asm/compat.h

md5sum: /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/Module.symvers: No such file or directory
make: Entering directory '/usr/lib/modules/3.18.18-rt15-1-rt-lts/build'
make: *** No rule to make target 'modules'.  Stop.
make: Leaving directory '/usr/lib/modules/3.18.18-rt15-1-rt-lts/build'

--------
2015-08-09 19:34:51
Building fglrx module for 4.1.4-1-ARCH kernel ...
--------
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /usr/lib/modules/4.1.4-1-ARCH/build/include/generated/autoconf.h says: SMP=1
file /usr/lib/modules/4.1.4-1-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
file /usr/lib/modules/4.1.4-1-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory '/usr/lib/modules/4.1.4-1-ARCH/build'
  CC [M]  /tmp/catalyst.RQqMxU/firegl_public.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_acpi.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_agp.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_debug.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_ioctl.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_io.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_pci.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_str.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_iommu.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl.o
  CC [M]  /tmp/catalyst.RQqMxU/kcl_wait.o
  LD [M]  /tmp/catalyst.RQqMxU/fglrx.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/catalyst.RQqMxU/fglrx.mod.o
  LD [M]  /tmp/catalyst.RQqMxU/fglrx.ko
make: Leaving directory '/usr/lib/modules/4.1.4-1-ARCH/build'
ok.

For the linux-rt package error again.

--------
2015-08-09 19:42:56
Building fglrx module for 4.0.8-rt6-2-rt kernel ...
--------
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
Warning:
kernel includes at /usr/lib/modules/4.0.8-rt6-2-rt/build/include not found or incomplete
file: /usr/lib/modules/4.0.8-rt6-2-rt/build/include/linux/autoconf.h

Warning:
kernel includes at /usr/lib/modules/4.0.8-rt6-2-rt/build/include not found or incomplete
file: /usr/lib/modules/4.0.8-rt6-2-rt/build/include/linux/autoconf.h

assuming default: MODVERSIONS=0
Warning:
kernel includes at /usr/lib/modules/4.0.8-rt6-2-rt/build/include not found or incomplete
file: /usr/lib/modules/4.0.8-rt6-2-rt/build/arch/x86/include/asm/compat.h

md5sum: /usr/lib/modules/4.0.8-rt6-2-rt/build/Module.symvers: No such file or directory
make: Entering directory '/usr/lib/modules/4.0.8-rt6-2-rt/build'
make: *** No rule to make target 'modules'.  Stop.
make: Leaving directory '/usr/lib/modules/4.0.8-rt6-2-rt/build'

Last edited by zabrielza (2015-08-09 16:53:11)

ooo · 2015-08-09 18:27:00

Did you install headers for the -rt kernel you installed. Afaik it is required to build any external modules.

zabrielza wrote:

But mainly I have to use Traktor-via wine- I have to run Jack server and connect it to wineasio

Sorry for off-topic, but have you tried using some linux native applications with traktor (there's at least mixxx and xwax)? I'd imagine latency would be much better compared to using anything with wine. I've been using traktor soundcard with xwax, and would be interested to know if you've made any comparisons :)

clfarron4 · 2015-08-09 20:41:57

ooo wrote:

Did you install headers for the -rt kernel you installed. Afaik it is required to build any external modules.

He has them installed. If he didn't, he'd have a message like following when I tried to build the lts312 fglrx module without headers.

--------
2015-08-09 19:02:18
Building fglrx module for 3.12.46-lts312 kernel ...
--------
Kernel header files are absent: directory /usr/lib/modules/3.12.46-lts312/build doesn't exist! Game over

@zabrielza: Hmm... Looks like we have a fun problem on our hands here.

zabrielza · 2015-08-09 21:42:20

ooo wrote:

Did you install headers for the -rt kernel you installed. Afaik it is required to build any external modules.
zabrielza wrote:
But mainly I have to use Traktor-via wine- I have to run Jack server and connect it to wineasio
Sorry for off-topic, but have you tried using some linux native applications with traktor (there's at least mixxx and xwax)? I'd imagine latency would be much better compared to using anything with wine. I've been using traktor soundcard with xwax, and would be interested to know if you've made any comparisons

Well, Actually no I had not installed them. I just installed them, and

+ building fglrx module for 3.18.18-rt15-1-rt-lts kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
+ building fglrx module for 4.0.8-rt6-2-rt kernel ...
  ok.
+ building fglrx module for 4.1.4-1-ARCH kernel ...
  ok.

2015-08-10 00:29:09
Building fglrx module for 3.18.18-rt15-1-rt-lts kernel ...
--------
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include/generated/autoconf.h says: SMP=1
file /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/include/generated/autoconf.h says: MODVERSIONS=1
file /usr/lib/modules/3.18.18-rt15-1-rt-lts/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory '/usr/lib/modules/3.18.18-rt15-1-rt-lts/build'
  CC [M]  /tmp/catalyst.U19nva/firegl_public.o
/tmp/catalyst.U19nva/firegl_public.c: In function ‘kcl_mem_pat_setup’:
/tmp/catalyst.U19nva/firegl_public.c:4182:15: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration]
         cr4 = read_cr4();
               ^
/tmp/catalyst.U19nva/firegl_public.c:4183:9: error: implicit declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration]
         write_cr4(cr4 & ~X86_CR4_PGE);
         ^
cc1: some warnings being treated as errors
scripts/Makefile.build:257: recipe for target '/tmp/catalyst.U19nva/firegl_public.o' failed
make[1]: *** [/tmp/catalyst.U19nva/firegl_public.o] Error 1
Makefile:1381: recipe for target '_module_/tmp/catalyst.U19nva' failed
make: *** [_module_/tmp/catalyst.U19nva] Error 2
make: Leaving directory '/usr/lib/modules/3.18.18-rt15-1-rt-lts/build'

So, what is going on with lts kernel?

About, the off topic, I meant traktor scratch pro, the app. I have a behringer sound card and on ubuntustudio( the successful configuration) I had minimal latency. I have tried Mixxx and is not like Traktor scratch pro at all. Much more futures in traktor. I havent use much native linux apps because i use traktor on my windows laptop ( the only reason I use windows). But I have tried ableton and traktor scrach on ubuntustudio and the latency was not something to worry about.

Arch Linux

#1 2015-08-09 14:59:22

Configure Realtime Kernel to be Compatible with AMD driver

#2 2015-08-09 15:08:44

Re: Configure Realtime Kernel to be Compatible with AMD driver

#3 2015-08-09 15:17:39

Re: Configure Realtime Kernel to be Compatible with AMD driver

#4 2015-08-09 15:35:08

Re: Configure Realtime Kernel to be Compatible with AMD driver

#5 2015-08-09 16:06:09

Re: Configure Realtime Kernel to be Compatible with AMD driver

#6 2015-08-09 16:11:04

Re: Configure Realtime Kernel to be Compatible with AMD driver

#7 2015-08-09 16:14:22

Re: Configure Realtime Kernel to be Compatible with AMD driver

#8 2015-08-09 16:18:25

Re: Configure Realtime Kernel to be Compatible with AMD driver

#9 2015-08-09 16:28:57

Re: Configure Realtime Kernel to be Compatible with AMD driver

#10 2015-08-09 16:43:28

Re: Configure Realtime Kernel to be Compatible with AMD driver

#11 2015-08-09 18:27:00

Re: Configure Realtime Kernel to be Compatible with AMD driver

#12 2015-08-09 20:41:57

Re: Configure Realtime Kernel to be Compatible with AMD driver

#13 2015-08-09 21:42:20

Re: Configure Realtime Kernel to be Compatible with AMD driver

Board footer