Hello, since the kernel update to 4.4.1 (I'm on Arch Linux x86_64), I cannot use the jack server in duplex mode or record only mode anymore (playback only still works) using the internal sound card (an Intel HDA manufactured by NVidia) of my Apple MacBook Pro 7,1. Up until kernel 4.3.3, this was possible without any issues. JACK seems to start formally, but fails after a multi-second timeout as soon as one tries to connect any client to it, giving the following error messages: Sun Feb 7 15:02:32 2016: Starting jack server... Sun Feb 7 15:02:32 2016: JACK server starting in realtime mode with priority 10 Sun Feb 7 15:02:32 2016: self-connect-mode is "Don't restrict self connect requests" Sun Feb 7 15:02:32 2016: Acquired audio card Audio0 Sun Feb 7 15:02:32 2016: creating alsa driver ... hw:NVidia|hw:NVidia|512|2|48000|0|0|nomon|swmeter|-|32bit Sun Feb 7 15:02:33 2016: configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 2 periods Sun Feb 7 15:02:33 2016: ALSA: final selected sample format for capture: 32bit integer little-endian Sun Feb 7 15:02:33 2016: ALSA: use 2 periods for capture Sun Feb 7 15:02:33 2016: ALSA: final selected sample format for playback: 32bit integer little-endian Sun Feb 7 15:02:33 2016: ALSA: use 2 periods for playback Sun Feb 7 15:02:38 2016: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out Sun Feb 7 15:02:38 2016: ERROR: Driver is not running Sun Feb 7 15:02:38 2016: ERROR: Cannot open client name = dbusapi Sun Feb 7 15:02:38 2016: ERROR: failed to create dbusapi jack client Sun Feb 7 15:02:38 2016: ERROR: Unknown request 4294967295 Sun Feb 7 15:02:38 2016: ERROR: CheckSize error size = 0 Size() = 12 Sun Feb 7 15:02:38 2016: ERROR: CheckRead error I already filed bug reports against the JACK sound server package on Arch Linux... https://bugs.archlinux.org/task/48073 ...where at least one other user was able to reproduce (though he did not specify his hardware configuration), and I filed an issue for the JACK developers on Github... https://github.com/jackaudio/jack2/issues/186 ...where further investigation has shown that it seems to be related to the HDA hardware, as I can start JACK successfully in all modes using an external USB audio interface. Markus Seeber has pointed me to an older issue report against JACK... https://github.com/jackaudio/jack2/issues/116 ...where a genuine Intel HDA card in a Lenovo laptop showed the exact same symptoms, but obviously using an older kernel. Output of alsa-info.sh on the MacBook Pro is here: http://www.alsa-project.org/db/?f=4f288b556984d50e322fc85d2cfd73fb03b7e0cd I'm interested in getting the device to work again in all modes as it used to. Best, Johannes ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
