Hello, I'm "suddenly" (after a couple months of disuse) unable to start jack in real-time mode, making ardour unable to take advantage of it. I've had more or less the same setup for more than 10 years, so I've really forgotten if there is anything else than the below that I could investigate. Tue Jan 23 20:21:51 2024: Starting jack server... Tue Jan 23 20:21:51 2024: JACK server starting in realtime mode with priority 10 Tue Jan 23 20:21:51 2024: self-connect-mode is "Don't restrict self connect requests" Tue Jan 23 20:21:51 2024: Acquired audio card Audio2 Tue Jan 23 20:21:51 2024: creating alsa driver ... hw:MobilePre|hw:MobilePre|128|3|48000|0|0|nomon|swmeter|-|32bit Tue Jan 23 20:21:51 2024: configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 3 periods Tue Jan 23 20:21:51 2024: ALSA: final selected sample format for capture: 16bit little-endian Tue Jan 23 20:21:51 2024: ALSA: use 3 periods for capture Tue Jan 23 20:21:51 2024: ALSA: final selected sample format for playback: 16bit little-endian Tue Jan 23 20:21:51 2024: ALSA: use 3 periods for playback Tue Jan 23 20:21:51 2024: ERROR: Cannot use real-time scheduling (RR/10) (1: Operation not permitted) Tue Jan 23 20:21:51 2024: ERROR: AcquireSelfRealTime error # ls -l /dev/rtc0 crw-rw---- 1 root audio 253, 0 Jan 10 20:00 /dev/rtc0 # grep audio /etc/security/limits.conf @audio - rtprio 99 @audio - memlock unlimited My user is a member of the audio group. This is a pure ALSA system, so there is no pulseaudio that could be the culprit. pipewire is installed, but have not been running at any time, although there might be something there? As far as I've figured, when it last worked I was on a 6.4.x kernel, I've been through a 6.5.x and have now had this problem on a few different 6.6.x kernels. >From what I can gather, I've not changed anything that I can see. All help welcome. Regards, Arve _______________________________________________ Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx
