• [deleted]

  • Post #2

I have the exact same stuff put into the same file. I think I never did anything with pam. On my system it works.

Have you logged out and back in? It should work OOTB. Changes with limits require a logout to take effect.

Here's what I did, following the instructions on http://jackaudio.org/faq/linux_rt_config.html:
Put

@realtime - rtprio 99
@realtime - memlock unlimited

in etc/security/limits.d/99-realtime.conf

and

Create a “realtime” group (as root)

groupadd realtime
usermod -a -G realtime yourUserID

Logout and back in...

Edit: After re-reading your post, I realized that you basically did the same thing already. Should read more carefully 🤦‍♂️

13 days later

[deleted] Could you elaborate ?
Because jack package already install a limits.conf file with the same values and users are in the audio group by default.
So I don't get what's the difference between the out of the box settings and the instructions on the link you provide... they look the same to me, unless I missed something ???

      • [deleted]

      • Post #7

      kyrios Oh, you're right

        a year later

        I am sorry to be posting here quite some time since this is active, but I think that I have found the root cause. The wiki page for jack was updated not that long ago about information regarding kernels that have CONFIG_RT_GROUP_SCHED enabled. This will probably need to be fixed with one of the solutions mentioned in https://github.com/jackaudio/jackaudio.github.com/wiki/Cgroups because it looks like linux-current has the option enabled.

          5 months later

          Jacalz So, it does seem to be related to the CONFIG_RT_GROUP_SCHED flag. I recompiled a linux-current kernel package without it and I now can start jack with realtime support without problem. This seems odd and as far as I can tell it may be an issue with upstream (jack). I'll report with upstream and see if anything comes up.

              mefistofeles
              Thank you so much for looking in to it. I never managed to solve it myself. Would be amazing to finally get JACK real-time working properly 🙂

                mefistofeles I might be wrong, but I think there might be a rule to not share .eopkg files in the forums, but I might be wrong.

                Anyway, have you reached out to upstream to see if the issues could be resolved there? I think that the config option is useful for Docker and other things, if I remember correctly. But other distros might not be using it if they have real-time JACK working, so I am a bit confused as to how they have it working and not us. It worked for a while sometime back though and I wonder if later kernel releases broke it, or if we just turned on the config around the same time.

                    Jacalz I know archlinux is not using that option and JACK + realtime works fine there. Fwiw. I tried reaching the JACK people via IRC and haven't got a response. I may try reporting an issue in their github repository, though.
                    Sorry about the eopkg files, hope it isn't much of a problem.

                        mefistofeles We all make mistakes. I think you should be fine 🙂

                        Looking forward you seeing if we can finally get this fixed. Is I’ll be great 👍

                          3 months later

                          Has this issue been solved?
                          I ended up fixing the RT issue on my end by fixing the spacing in the limits.conf.

                          I've reported it here