The problem I'm facing now is that qjackctl output shows, no matter what settings I use, the message "ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory)".
Here is the complete output:
Code: Select all
03:37:44.924 Statistics reset.
03:37:44.928 ALSA connection change.
03:37:44.975 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
03:37:44.985 ALSA connection graph change.
03:37:57.966 D-BUS: JACK server is starting...
03:37:57.978 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sun Aug 11 03:37:57 2019: Starting jack server...
Sun Aug 11 03:37:57 2019: JACK server starting in realtime mode with priority 10
Sun Aug 11 03:37:57 2019: self-connect-mode is "Don't restrict self connect requests"
Sun Aug 11 03:37:57 2019: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory)
Sun Aug 11 03:37:57 2019: Acquired audio card Audio1
Sun Aug 11 03:37:57 2019: creating alsa driver ... hw:K6|hw:K6|64|2|44100|0|0|nomon|swmeter|-|32bit
Sun Aug 11 03:37:57 2019: configuring for 44100Hz, period = 64 frames (1.5 ms), buffer = 2 periods
Sun Aug 11 03:37:57 2019: ALSA: final selected sample format for capture: 32bit integer little-endian
Sun Aug 11 03:37:57 2019: ALSA: use 2 periods for capture
Sun Aug 11 03:37:57 2019: ALSA: final selected sample format for playback: 32bit integer little-endian
Sun Aug 11 03:37:57 2019: ALSA: use 2 periods for playback
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:capture_1'
Sun Aug 11 03:37:57 2019: New client 'system' with PID 0
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:capture_2'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:capture_3'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:capture_4'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:capture_5'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:capture_6'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:playback_1'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:playback_2'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:playback_3'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:playback_4'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:playback_5'
Sun Aug 11 03:37:57 2019: graph reorder: new port 'system:playback_6'
Sun Aug 11 03:37:57 2019: New client 'PulseAudio JACK Sink' with PID 2353
Sun Aug 11 03:37:57 2019: Connecting 'PulseAudio JACK Sink:front-left' to 'system:playback_1'
Sun Aug 11 03:37:57 2019: Connecting 'PulseAudio JACK Sink:front-right' to 'system:playback_2'
Sun Aug 11 03:37:58 2019: New client 'PulseAudio JACK Source' with PID 2353
Sun Aug 11 03:37:58 2019: Connecting 'system:capture_1' to 'PulseAudio JACK Source:front-left'
Sun Aug 11 03:37:58 2019: Connecting 'system:capture_2' to 'PulseAudio JACK Source:front-right'
Sun Aug 11 03:37:59 2019: Saving settings to "/home/palmiro/.config/jack/conf.xml" ...
03:38:00.044 JACK connection change.
03:38:00.045 Server configuration saved to "/home/palmiro/.jackdrc".
03:38:00.045 Statistics reset.
03:38:00.046 Client activated.
03:38:00.046 Patchbay deactivated.
03:38:00.054 JACK connection graph change.
Sun Aug 11 03:38:00 2019: New client 'qjackctl' with PID 11746
After research in this forum, I checked what seem to be the usual suspects, and they have been discarded:
1) There exists indeed an "audio" group, to which I belong.
2) As far as I can tell, the memory allocation parameters in /etc/security/limits.d/audio.conf and /etc/security/limits.conf are correct:
Code: Select all
cat /etc/security/limits.d/audio.conf
# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
# dpkg-reconfigure -p high jackd
@audio - rtprio 95
@audio - memlock unlimited
#@audio - nice -19
Code: Select all
cat /etc/security/limits.conf
# /etc/security/limits.conf
#
#Each line describes a limit for a user in the form:
#
#<domain> <type> <item> <value>
#
#Where:
#<domain> can be:
# - a user name
# - a group name, with @group syntax
# - the wildcard *, for default entry
# - the wildcard %, can be also used with %group syntax,
# for maxlogin limit
# - NOTE: group and wildcard limits are not applied to root.
# To apply a limit to the root user, <domain> must be
# the literal username root.
#
#<type> can have the two values:
# - "soft" for enforcing the soft limits
# - "hard" for enforcing hard limits
#
#<item> can be one of the following:
# - core - limits the core file size (KB)
# - data - max data size (KB)
# - fsize - maximum filesize (KB)
# - memlock - max locked-in-memory address space (KB)
# - nofile - max number of open file descriptors
# - rss - max resident set size (KB)
# - stack - max stack size (KB)
# - cpu - max CPU time (MIN)
# - nproc - max number of processes
# - as - address space limit (KB)
# - maxlogins - max number of logins for this user
# - maxsyslogins - max number of logins on the system
# - priority - the priority to run user process with
# - locks - max number of file locks the user can hold
# - sigpending - max number of pending signals
# - msgqueue - max memory used by POSIX message queues (bytes)
# - nice - max nice priority allowed to raise to values: [-20, 19]
# - rtprio - max realtime priority
# - chroot - change root to directory (Debian-specific)
#
#<domain> <type> <item> <value>
#
#* soft core 0
#root hard core 100000
#* hard rss 10000
#@student hard nproc 20
#@faculty soft nproc 20
#@faculty hard nproc 50
#ftp hard nproc 0
#ftp - chroot /ftp
#@student - maxlogins 4
# End of file
My computer has 16Gb RAM, so I don't think there's a problem of RAM shortage either.
Other things I've tried have been: changing the rtprio value to from 95 to 90 (as that is the value that appears in the documentation example - https://wiki.linuxaudio.org/wiki/system ... faudioconf), and uncommenting the line #@audio - nice -19 at the end of audio.conf. None of them have had any effect on that unexplainable "cannot lock down memory" message.
What could be causing this error? In addition to the aforementioned settings, is there any other configuration I should check, that could be obstructing the computer from using real time mode? Or maybe this is a normal thing and shouldn't worry me as long as I don't get xruns? Thank you in advance for any suggestion.