Quatafire 610

Support Status: 
Full Support
Manufacturer: 
ESI

Comments

I can't get any jack application to discover my quatafire. although everything looks fine, jackd is started with freebob.
I can connect to jackd in Ardour and it reports the sample rate as being 44100 khz but in the inputs of ardour i see only ALSA and ARDOUR ...
BTW is the samplerate of 96 khz supported ?

Thanks
Tellurium

As you said, jackd is started with freebob. It has to start with ffado (known as the "firewire"-backend) to get a chance to detect the quatafire. And I even think you need developers trunk version of libffado...

I installed Ubuntu Studio 10.10 on a portable with a Firewire PC Card connected to an ESI Quatafire 610.
The ffado mixer "see" my Quatafire, and I can configure the firewire interface in the jackd setup.
But unfortunately, I can't get any sound out from the Ubuntu player (I configure it to use jack).
The Quatafire works very well when connected to Windows :-(
I don't know what to do to fix the problem !
Which configuration file or error log to check ?
Thanks for any help
Pascal

I'm trying to make work my quatafire 610 on Dream Studio, based on ubuntu 12.04 amd64.

When I try to run on terminal ffado-mixer, I have:

logginghandler: Could not communicate with the FFADO DBus service...

when I did:

sudo apt-get install ffado-mixer-qt4 jackd2-firewire
(jackd2-firewire was installed)

sudo gedit /etc/modules
(then I added the line: raw1394) (I restarted the system)

then:
sudo gedit /etc/udev/rules.d/50-raw1394.rules

(added: KERNEL=="raw1394", GROUP="audio" )

now:
gksudo modprobe raw1394sudo
ln /dev/fw0 /dev/raw1394
sudo ffado-mixer

Now the ffado-mixer can run but I have: not supported device found

:(

What's wrong?

I have no direct experience with the Quantafire 610 or Ubuntu 12.04. What follows are some generic suggestions. Others may chime in with more specific suggestions.

logginghandler: Could not communicate with the FFADO DBus service...

This tends to suggest that for some reason ffado-mixer was unable to start ffado-dbus-server. It would be interesting to know what happens if you try to run "ffado-dbus-server" in a terminal: does it run, or does it exit with an error?

then I added the line: raw1394

With the new firewire stack (which Ubuntu 12.04 uses) there should be no need to have the raw1394 kernel module installed. When the new firewire stack is used, /dev/raw1394 should not be used; instead /dev/fw0 and /dev/fw1 will be. If /dev/fw* are not present automatically it suggests that the firewire modules are not being loaded on your system for some reason. "lsmod" may shed some light on the subject. Amongst many other things you should see modules named "firewire_core" and "firewire_ohci" within the list. If not, we probably need to work out why your system is not loading these.

sudo ffado-mixer

It should not be necessary to run ffado-mixer as root: it is designed to be run as an ordinary user. In none of the components of FFADO should be run as root.

not supported device found

This may be collateral damage due to the appropriate firewire drivers not being loaded (see above). We need to clarify this before going further as described above. If it turns out that this message is shown even with the right drivers loaded, we will need to look into some other possibilities (incorrect permissions on /dev/fw*, a version of FFADO that's too old and doesn't know about the Quantafire interface, and so on).

First, a lot of thanks for replying.

Well.. until load the raw1394 module, I did not have fw0.. I know this because I tryied to create the raw1394 link first and I had fw0 not found.

And even managed to create the fw0 device, I can't load ffado-mixer or ffado-dbus-server without error.

When I try ffado-dbus-server I have:

esteban@Tattoine:~$ ffado-dbus-server
-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

Discovering devices...
20612505092: Fatal (devicemanager.cpp)[ 191] initialize: No firewire adapters (ports) found.
20612505238: Error (ffado-dbus-server.cpp)[ 277] main: Could not initialize device manager

Some ideas?

I'll reply to both your recent posts together.


[ 3.818281] firewire_ohci 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.818289] firewire_ohci 0000:07:00.0: setting latency timer to 64
[ 3.893266] firewire_ohci: Added fw-ohci device 0000:07:00.0, OHCI v1.10, 4 IR + 4 IT contexts, quirks 0x10
[ 4.395911] firewire_core: created device fw0: GUID 00241b001451ba01, S400
[20209.725886] firewire_core: skipped bus generations, destroying all nodes
[20210.227221] firewire_core: rediscovered device fw0

This shows a few interesting things. Firstly, your system is definitely loading firewire_core and firewire_ohci. That's good. We also see that it is creating the fw0 node (I'm assuming GUID 00241b001451ba01 is the Quantafire). So far so good, although if the Quantafire is turned on I would have expected to see the creation of both fw0 and fw1 (one of these being the Quantafire, the other being the firewire host controller).

The "skipped bus generations" is unexpected; I've not seen that before. However, I notice that this corresponds with a fairly substantial timestep on your system (from around 4.4 seconds since boot up to 20209.7 seconds after boot). As such this may be an unrelated transient fault which self-corrected, but it would be worth keeping this in mind. "Destroying all nodes" is not a bad thing and is in fact what needs to happen in this situation. After the nodes are destroyed the bus is rescanned for devices which are present and any required nodes will be recreated (as we see happening at the 20120.2 mark).

This issue with the raw1394 kernel module has me confused. raw1394 is a part of the old firewire stack, and is not needed if the new stack (comprising in your case of firewire_core and firewire_ohci) is in use. Even more curious is the fact that - if I understand correctly - loading the raw1394 module made /dev/fw0 appear. That doesn't make sense.

At this point the best thing to do is probably the following. After a fresh boot, have the Quantafire plugged into your firewire bus and turned on. Then run "ffado-diag", which will produce a large amount of information about your system. Please post that information here; it may provide some clues as to what's going on.

Also, can you determine (perhaps from the package manager) which version of FFADO has been installed on your system by Ubuntu 12.04?

Ok... That's the outputs:

esteban@Tattoine:~$ ffado-diag

FFADO diagnostic utility 2.999.0-
============================
(C) 2008 Pieter Palmers
2009-2010 Arnold Krille

=== CHECK ===
Base system...
kernel version............ 3.2.0-23-lowlatency
old 1394 stack present.... False
old 1394 stack loaded..... False
old 1394 stack active..... False
new 1394 stack present.... True
new 1394 stack loaded..... True
new 1394 stack active..... True
/dev/raw1394 node present. False
/dev/fw* permissions:
ls: impossível acessar /dev/fw*: Arquivo ou diretório não encontrado
User IDs:
uid=1000(esteban) gid=1000(esteban) grupos=1000(esteban),4(adm),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),44(video),46(plugdev),100(users),109(lpadmin),126(sambashare)
Prerequisites (dynamic at run-time)...
gcc ............... gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
g++ ............... sh: 1: g++: not found
PyQt4 (by pyuic4) . sh: 1: pyuic4: not found
jackd ............. jackdmp 1.9.8
path ............ /usr/bin/jackd
flags ........... -ljack
libraw1394 ........ Package libraw1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libraw1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libraw1394' found
flags ........... Package libraw1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libraw1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libraw1394' found
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
flags ........... Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
libiec61883 ....... Package libiec61883 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libiec61883.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libiec61883' found
flags ........... Package libiec61883 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libiec61883.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libiec61883' found
libxml++-2.6 ...... Package libxml++-2.6 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml++-2.6.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml++-2.6' found
flags ........... Package libxml++-2.6 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml++-2.6.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml++-2.6' found
dbus-1 ............ 1.4.18
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1 -lpthread -lrt
Prerequisites (static at compile-time)...
gcc ............... gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
g++ ............... g++ (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
PyQt4 (by pyuic4) . Python User Interface Compiler 4.9.1 for Qt version 4.8.1
jackd ............. jackdmp 1.9.8
path ............ /usr/bin/jackd
flags ........... -ljack
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
flags ........... Package libavc1394 was not found in the pkg-config search path.
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.34.1
flags ........... -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0
dbus-1 ............ 1.4.18
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1 -lpthread -lrt
Hardware...
Host controllers:
07:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (prog-if 10 [OHCI])
Subsystem: Lenovo Device [17aa:387d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci

CPU info:
Arquitetura: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) por núcleo: 1
Núcleo(s) por soquete:2
Soquete(s): 1
NUMA node(s): 1
ID do fabricante: GenuineIntel
CPU family: 6
Modelo: 23
Stepping: 10
CPU MHz: 1200.000
BogoMIPS: 4388.77
L1d cache: 32K
L1i cache: 32K
L2 cache: 2048K
NUMA node0 CPU(s): 0,1
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [528924, 528924], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [56, 56], Sched None (priority None), drivers: ['i8042']
IRQ 8: PID: None, count: [1, 1], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [3582, 3582], Sched None (priority None), drivers: ['acpi']
IRQ 10: PID: None, count: [0, 0], Sched None (priority None), drivers: ['ite-cir']
IRQ 12: PID: None, count: [72027, 72027], Sched None (priority None), drivers: ['i8042']
IRQ 16: PID: None, count: [4, 4], Sched None (priority None), drivers: ['uhci_hcd:usb3', 'mmc0', 'firewire_ohci', 'jmb38x_ms:slot0']
IRQ 18: PID: None, count: [73, 73], Sched None (priority None), drivers: ['uhci_hcd:usb8']
IRQ 19: PID: None, count: [0, 0], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb5', 'uhci_hcd:usb7']
IRQ 21: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb4']
IRQ 23: PID: None, count: [14, 14], Sched None (priority None), drivers: ['ehci_hcd:usb2', 'uhci_hcd:usb6']
IRQ 46: PID: None, count: [8292, 8292], Sched None (priority None), drivers: ['ahci']
IRQ 47: PID: None, count: [14412, 14412], Sched None (priority None), drivers: ['i915']
IRQ 48: PID: None, count: [20147, 20147], Sched None (priority None), drivers: ['iwlwifi']
IRQ 49: PID: None, count: [193, 193], Sched None (priority None), drivers: ['snd_hda_intel']
IRQ 50: PID: None, count: [2, 2], Sched None (priority None), drivers: ['eth0']

Software Interrupts:
--------------------

=== REPORT ===
FireWire kernel drivers:

The new FireWire kernel stack is loaded.
If running a kernel earlier than 2.6.37 and problems are experienced, either
try with the old Firewire kernel stack or upgrade to a newer kernel
(preferrably 2.6.37 or later).

The versions of packages installed:

esteban@Tattoine:~$ sudo apt-cache policy ffado-tools
ffado-tools:
Instalado: 2.0.99+svn2146-0~precise2
Candidato: 2.0.99+svn2146-0~precise2
Tabela de versão:
*** 2.0.99+svn2146-0~precise2 0
500 http://ppa.launchpad.net/kxstudio-team/ppa/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
2.0.99+svn2019-1ubuntu1 0
500 http://br.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
esteban@Tattoine:~$ sudo apt-cache policy ffado-dbus-server
ffado-dbus-server:
Instalado: 2.0.99+svn2146-0~precise2
Candidato: 2.0.99+svn2146-0~precise2
Tabela de versão:
*** 2.0.99+svn2146-0~precise2 0
500 http://ppa.launchpad.net/kxstudio-team/ppa/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
2.0.99+svn2019-1ubuntu1 0
500 http://br.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
esteban@Tattoine:~$ sudo apt-cache policy ffado-mixer-qt4
ffado-mixer-qt4:
Instalado: 2.0.99+svn2146-0~precise2
Candidato: 2.0.99+svn2146-0~precise2
Tabela de versão:
*** 2.0.99+svn2146-0~precise2 0
500 http://ppa.launchpad.net/kxstudio-team/ppa/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
2.0.99+svn2019-1ubuntu1 0
500 http://br.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

And confirming, I don't have /dev/fw0 until start raw1394, and that's work only when I have the card unplugged.

Thanks for the latest posts and I apologise for the over-zealous spam detector.

A few observations:

  1. I don't completely follow the package information at the end, but it seems that there are several different ffado-related packages installed on your system. I think it's saying that FFADO is at version 2.0.99+svn2146 and if this is correct then we should be fine. I am confused by the appearance of "2.0.99+svn2019" seemingly in connection with ffado-dbus-server (even though the more recent version was reported earlier in the output). I'm not sure what that means at present. I'm also not completely sure why FFADO appears to be split between two different packages (ffado-tools and ffado-dbus-server). Given the other issues though we can probably leave this to one side for the moment.
  2. ffado-diag confirms that /dev/fw* does not exist on your system even though the new kernel firewire stack is loaded. It's far from clear to me as to why these nodes aren't appearing. It's also extremely strange that loading raw1394 makes /dev/fw0 appear because the raw1394 kernel module has nothing to do with /dev/fw*. I'm wondering whether something is causing /dev/fw0 to be created as a symlink to /dev/raw1394 in this scenario. It's very odd, but I can't see what else could be happening. To investigate this possibility, could you load raw1394 on an otherwise fresh boot, and then do "ls -l /dev/raw1394 /dev/fw*" and post the result?

I expect the primary cause of your problems is the failure of the system to correctly create the /dev/fw* device nodes. Without those nodes being created the FFADO programs will not be able to access the device properly. Therefore this is what we should concentrate on first up.

esteban@Tattoine:~$ ls -l /dev/raw1394 /dev/fw*
ls: impossível acessar /dev/raw1394: Arquivo ou diretório não encontrado
crw------- 1 root root 251, 0 Set 16 10:30 /dev/fw0

well... I was needed to reinstall the system because I have some problems with video after one system atualization... :/

But the outputs are the same and now I have the /dev/fw0 .

Telling the truth, I initiate to think on the possibility of hardware problem.. In this case the QuataFire interface...

I was installed one temporary copy of windows vista, and using the driver of ESI, I can't finish the installation because the driver can't detect the interface.. :(

I try too connect it on mac osx 10.6.8, but the interface can't turn on the PWR green led, I try two firewire cables... This week I will test it again on another friend mac osx 10.6.8

If I have the same problem I will think it's something too wrong with this interface..

'll keep you informed! And I apreciate some new suggestion!

Your suggestion that there might be a problem with the Quantafire itself is consistent with the symptoms you report. That would certainly explain why you don't see both /dev/fw0 and /dev/fw1 when the Quantafire is plugged in and turned on (one of these is your host adapter, the other would be the Quantafire). Your conclusion also looks consistent given your experience under alternative operating systems.

Marginal firewire cables can certainly create problems like this so it's good you tried a second cable.

Clearly you've also tried it on a totally different computer (a mac) and had similar trouble. That pretty much rules out the firewire card in your PC.

Does the Quantafire have two firewire sockets? If so (and assuming you haven't tried this yet) it may be worth plugging into the second firewire slot on the off-chance that the problem is with the socket you've been using. Based on what you have reported though I would have to agree that at this stage it looks like the Quantafire itself may have a fault. If you are handy with a soldering iron (or know someone who is) it may be worth inspecting the solder pads of the firewire socket on the PCB; due to mechanical stresses it would not be unusual to find dry joints on these pads which would be easily resolved by retouching them. If this doesn't prove to the the cause then it's unlikely the fault will be identifiable without access to the device's service manual and internal test programs.

Thanks for the update and please do keep us informed of your future findings.

I have some problems to post the results... The Forum as flagged mu post like possible spam.. :(

I ran lspci -v and have this response:

07:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller (prog-if 10 [OHCI])
Subsystem: Lenovo Device 387d
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f4700800 (32-bit, non-prefetchable) [size=2K]
Memory at f4701000 (32-bit, non-prefetchable) [size=128]
Memory at f4700400 (32-bit, non-prefetchable) [size=128]
Memory at f4700000 (32-bit, non-prefetchable) [size=128]
Capabilities:
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci

I will try post the another results yet...

I run dmesg:

esteban@Tattoine:~$ sudo dmesg | grep -i 1394
esteban@Tattoine:~$ sudo dmesg | grep -i fire
[ 3.818281] firewire_ohci 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.818289] firewire_ohci 0000:07:00.0: setting latency timer to 64
[ 3.893266] firewire_ohci: Added fw-ohci device 0000:07:00.0, OHCI v1.10, 4 IR + 4 IT contexts, quirks 0x10
[ 4.395911] firewire_core: created device fw0: GUID 00241b001451ba01, S400
[20209.725886] firewire_core: skipped bus generations, destroying all nodes
[20210.227221] firewire_core: rediscovered device fw0
esteban@Tattoine:~$

"destroying all nodes"??? Is it bad?