-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jack Wont Start After arch linux System Upgrade. #94
Comments
Does not seem an issue with jack, likely you just need to rebuild it.
implies that jack is not part of your system and built manually. so now the system libraries updated and created a mismatch of versions. |
I also run jack on archlinux and see the messages could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory I am still able to use jack as my audio driver in programs like Ardour and Hydrogen. So on my machine things work in spite of not having those shared libraries. I would guess the following diagnostic is pointing to your problem: open "hw:H1" (No such device) ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA: Cannot open PCM device alsa_pcm for playback. I am not familiar with the syntax 'hw:H1'. That does not work on my machine and I see a similar error message. If I instead use 'hw:1' things work. |
@ksralgp Do you mean i should change that string in the source, and recompile? thx |
I have no experience in qjackctl, but poking around it looks like you can set the device name in the "setup" menu. There is an "interface" box. I entered "hw:1" there and was able to start jackd. Alternatively it has a pull-down that shows you the devices it detected. Maybe you need to select something else there? |
Thx, i'll try that. So, the issue is a device is named that jack can't find? Does jack require any devices at all, to start? However, without doing that (or anything else different), I noticed sometimes jack runs, sometimes it doesn't. Seem intermittent, or only works under just-so conditions or sequence of events (which i can't tell yet). |
Not sure if i'm running jack1 or jack2.
Up to now, it's been running just fine.
I'm running alsa only. Pretty sure i do not have pulse installed.
Here's the error log from qjackctl:
The text was updated successfully, but these errors were encountered: