You are not logged in.
Hi earlz, did you find a solution to this? I also get
[aaron@aaronsDesktop ~]$ alsa_in
connect(2) call to /dev/shm/jack-500/default/jack_0 failed (err=No such file or directory)
jackd 0.124.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
ATTENTION: The capture device "hw:0" is already in use. The following applications are using your soundcard(s) so you should check them and stop them as necessary before trying to start JACK again:
crrcsim (process ID 594)
jackd (process ID 874)
cannot load driver module alsa
connect(2) call to /dev/shm/jack-500/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-500/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-500/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-500/default/jack_0 failed (err=No such file or directory)
^CMODERATOR EDIT: split from https://bbs.archlinux.org/viewtopic.php?id=178888
Last edited by Trilby (2014-06-06 14:27:48)
Offline
pkgfile libffado.so.2Apparently it is missing.
Change your default sound card using the recommended method to PCH (use vid and pid for this). Or specify the output using:
alsa_in -d hw:PCH@AaronBrown I doubt that earlz still has this problem though. And in your case crrcsim and jackd block the sound card, otherwise to check run:
fuser -v /dev/snd/*Is the structure under /dev/shm in place?
Offline
Welcome to the forums Aaron. I've split your comment from the other thread as your problem does not relate in any way to the existing thread (completely different command, completely different error). Please don't hijack threads. You can always provide links to other threads if you think they might be relevant to an issue you are posting about.
EDIT: my appologies - on second look there may be some overlap between these issues. This still will be better as it's own thread though: if you are actively pursuing an issue it is best for you to be the thread OP.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline