17 Oct
2017
17 Oct
'17
4:35 p.m.
I built a new PC and installed Ubuntu Studio 16.04.
The PC has a firewire card.
lsmod | grep fire
firewire_ohci 40960 0
firewire_core 65536 1 firewire_ohci
crc_itu_t 16384 1 firewire_core
ffado-diag claims these aren't there:
libraw1394 ....
libavc1394 ....
libiec61883 ...
libxml++-2.6 .
But, apt says they are.
jack_control fails to start the server if the firewire driver is selected.
But, starts ok if alsa is selected.
Not sure where to go from here. Any ideas/pointers appreciated.
My last 3 PC's, UBS 16.04, firewire, jack, just worked OOTB.
Mac
17 Oct
17 Oct
4:52 p.m.
Am Dienstag, den 17.10.2017, 10:34 -0400 schrieb Mac:
I built a new PC and installed Ubuntu Studio 16.04.
The PC has a firewire card.
lsmod | grep fire
firewire_ohci 40960 0
firewire_core 65536 1 firewire_ohci
crc_itu_t 16384 1 firewire_core
ffado-diag claims these aren't there:
libraw1394 ....
libavc1394 ....
libiec61883 ...
libxml++-2.6 .
But, apt says they are.
apt? Sure? I thought apt was just a package manager...
jack_control fails to start the server if the firewire
driver is
selected.
But, starts ok if alsa is selected.
Not sure where to go from here. Any ideas/pointers appreciated.
I had temporary trouble with an older ffado driver and took the alsa
driver in the meantime... If that's a problem, you can try a software
update. Aren't there Ubuntu studio versions 16.10 and 17.04?
Greets!
Mitsch
5:01 p.m.
Mac <ussndmac-xwVYE8SWAR3R7s880joybQ(a)public.gmane.org> writes:
I built a new PC and installed Ubuntu Studio 16.04.
The PC has a firewire card.
lsmod | grep fire
firewire_ohci 40960 0
firewire_core 65536 1 firewire_ohci
crc_itu_t 16384 1 firewire_core
ffado-diag claims these aren't there:
libraw1394 ....
libavc1394 ....
libiec61883 ...
libxml++-2.6 .
But, apt says they are.
jack_control fails to start the server if the firewire driver is selected.
But, starts ok if alsa is selected.
Not sure where to go from here. Any ideas/pointers appreciated.
A Firewire card is not able to play audio on its own. You have to
connect a Firewire soundcard or equivalent to it.
The purpose of ffado-diag is to create a bunch of useful information for
diagnosing someone's setup.
Posting its output (_after_ connecting a Firewire audio device) would
have been a lot more helpful than your information-scrubbed summary.
--
David Kastrup
6:15 p.m.
On Tue, 17 Oct 2017, Mac wrote:
I built a new PC and installed Ubuntu Studio 16.04.
The PC has a firewire card.
As firewire has been added to alsa, the alsa firewire drivers are loaded
instead. So you should be able to see your device as an alsa device (check
arecord -l). I have heard (though I have no FW HW) that the old FW drivers
may still be more stable, but to use them you need to blacklist the alsa
FW module(s) so that the old style FW kernel modules can load.
--
Len Ovens
www.ovenwerks.net
7:54 p.m.
Len Ovens <len-ODU3Ot18rIYsV2N9l4h3zg(a)public.gmane.org> writes:
On Tue, 17 Oct 2017, Mac wrote:
It depends. I can use Ffado fine for the Mackie Onyx mixer Firewire
card even though Alsa also offers to access it (through snd_ox I think).
I had to blacklist the (not properly functioning for this card) snd_dice
driver for Ffado to be able to access an Alesis iO|14.
In general, when sound hardware is old enough to have been supported in
the heydey of Ffado, the Alsa drivers are more likely to be of
"afterthought" quality in my experience.
--
David Kastrup
I built a new PC and installed Ubuntu Studio
16.04.
The PC has a firewire card.
As firewire has been added to alsa, the alsa firewire drivers are
loaded instead. So you should be able to see your device as an alsa
device (check arecord -l). I have heard (though I have no FW HW) that
the old FW drivers may still be more stable, but to use them you need
to blacklist the alsa FW module(s) so that the old style FW kernel
modules can load.
2597
days inactive
2597
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
David Kastrup -
Len Ovens -
Mac -
Michael Jarosch