Github messages for voidlinux
 help / color / mirror / Atom feed
From: VoidDuck <VoidDuck@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] jack cannot use realtime scheduling
Date: Sun, 15 Mar 2020 00:18:34 +0100	[thread overview]
Message-ID: <20200314231834.JMbxHMuIXffFRPPQ4KrM9lOzC4_5xCk2xuOkGu212nQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20051@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

Closed issue by VoidDuck on void-packages repository

https://github.com/void-linux/void-packages/issues/20051

Description:
Hello,

I tried many different settings but I definitely cannot get jack to run with realtime priority on Void, while it works fine on other distributions.

I checked everything described on https://jackaudio.org/faq/linux_rt_config.html and https://github.com/jackaudio/jackaudio.github.com/wiki/Cgroups but it still does not work.

Here is what I get when running `jackd -R -d alsa`:

> JACK server starting in realtime mode with priority 10
> self-connect-mode is "Don't restrict self connect requests"
> Cannot lock down 82280346 byte memory area (Cannot allocate memory)
> audio_reservation_init
> Acquire audio card Audio0
> creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
> ALSA: final selected sample format for capture: 32bit integer little-endian
> ALSA: use 2 periods for capture
> ALSA: final selected sample format for playback: 32bit integer little-endian
> ALSA: use 2 periods for playback
> Cannot use real-time scheduling (RR/10) (1: Operation not permitted)
> AcquireSelfRealTime error

### System
* xuname:  
  *Void 5.4.24_1 x86_64 GenuineIntel uptodate rF*
* package:  
  *jack-1.9.14_1*

  parent reply	other threads:[~2020-03-14 23:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 21:44 [ISSUE] " VoidDuck
2020-03-13 14:47 ` VoidDuck
2020-03-13 16:59 ` daniel-eys
2020-03-13 17:13 ` VoidDuck
2020-03-13 17:22 ` daniel-eys
2020-03-13 19:41 ` jrigg
2020-03-13 19:43 ` jrigg
2020-03-13 22:16 ` VoidDuck
2020-03-13 22:16 ` VoidDuck
2020-03-13 22:37 ` daniel-eys
2020-03-13 22:57 ` VoidDuck
2020-03-13 23:45 ` daniel-eys
2020-03-13 23:47 ` daniel-eys
2020-03-13 23:50 ` daniel-eys
2020-03-13 23:52 ` daniel-eys
2020-03-13 23:56 ` VoidDuck
2020-03-13 23:56 ` VoidDuck
2020-03-14  1:12 ` daniel-eys
2020-03-14  9:12 ` VoidDuck
2020-03-14 16:19 ` daniel-eys
2020-03-14 18:07 ` VoidDuck
2020-03-14 23:18 ` VoidDuck
2020-03-14 23:18 ` VoidDuck [this message]
2020-03-14 23:37 ` daniel-eys
2020-03-14 23:51 ` VoidDuck
2020-03-15  1:30 ` daniel-eys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200314231834.JMbxHMuIXffFRPPQ4KrM9lOzC4_5xCk2xuOkGu212nQ@z \
    --to=voidduck@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).