Edirol FA-66 and Ricoh Host Controller

stefan · Post by **stefan** » Sun Feb 13, 2011 8:24 pm

Hi,

I just bought a Edirol FA-66 to be attached to my Dell Latitude E4300. However, I get error messages when i start 'ffado-debus-server' and run the 'ffado-mixer'. The mixer gui starts allright, but 'ffado-debus-server' barfs errors:

Code: Select all

08731159904: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731188176: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731216470: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731284916: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731312600: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731340147: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731368084: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
08731397199: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug

Then I head over to subversion.ffado.org and reads the document Some notes on good/bad host controllers. Here they say that the Ricoh Host Controller generally is a bad one! I check my lspci and find:

Code: Select all

~$ lspci | grep FireWire
02:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)

What does this mean? Should I buy a new soundcard, buy a new laptop, or what? plz help me decipher this!

tia // s

Havoc · Post by **Havoc** » Sun Feb 27, 2011 12:05 pm

First the good news, I have here an Edirol FA-66 running on a Dell Vostro 1700 with the same Ricoh chip and it works. Caveat: I did not test it very hard, playback for a couple of hours, recording some stereo tracks like I mostly work.

Slightly worse news, I haven't an idea what that means. But I do use the FA-66 with Jack and QJackCtl so I have no experience of ffdao-debus-derver (are you sure it isn't ffado-dbus-server?). OTOH I see that ffado-mixer that is present on my pc does just nothing, it never runs. But that can be related to Jack.

What I propose is that you:
- list a step-by-step of how you start things, including the commands so I can try the same here
- the output of lsmod

Pablo · Post by **Pablo** » Sun Feb 27, 2011 10:18 pm

Hi,

And run

ffado-diag

You need the ffado-tools package

stefan · Post by **stefan** » Mon Feb 28, 2011 8:30 am

I've run ffado-diag and realTimeConfigQuickScan.pl and to the best of my knowledge, they do not report any problems. And since my entire setup works fine, I can live without the ffado-mixer. However, before I decided to file the issue under 'strange computer behaviour that doesn't effect my life', I took closer look at the problem I saw that the card was hanging on a pretty crowded irq.

Code: Select all

~$ cat /proc/interrupts
...
19:      16996       3417   IO-APIC-fasteoi   ata_piix, ata_piix, ohci1394
...

Somehow I thought that the mixer couldn't 'reach' the device since it shared its irq with other devices. I came to this conclusion after realTimeConfigQuickScan.pl reported that it couldn't proceed with extended scan due to crowded irq.

So I ran out and bought an ExpressCard to firewire (Texas Instruments chipset). But the only result was that I found out that the expresscard also docked into the 19th irq. So I blame the buses on my Dell Latitude 4300. The strange thing was that I expected to find a 'yenta' entry in /proc/interrupts, but the 'ohci1394' popped up twice...

Code: Select all

~$ cat /proc/interrupts
...
19:      16996       3417   IO-APIC-fasteoi   ata_piix, ata_piix, ohci1394, ohci1394
...

That's pretty much it. The mixer still reports errors, but my setup works fine. If anyone have a solution for this I'll be very greatful (and impressed!).

This is the commands I run before I get to work:

Code: Select all

sudo cpufreq-set -c 0 -g performance
sudo cpufreq-set -c 1 -g performance
sudo /sbin/sysctl -w vm.swappiness=10
sudo /etc/init.d/rtirq start
sudo mount -t tmpfs none /tmp
/usr/bin/jackd -P70 -p512 -dfirewire -r48000 -p128 -n3 & j2amidi_bridge &

This is the output that ffado-diag outputs:

Code: Select all

~$ ffado-diag

FFADO diagnostic utility 0.1
============================
(C) 2008 Pieter Palmers


=== CHECK ===
 Base system...
  kernel version............ 2.6.31-11-rt
FIXME: implement test for RT kernel
   RT patched............... False
  old 1394 stack present.... True
  old 1394 stack loaded..... True
  old 1394 stack active..... True
  new 1394 stack present.... True
  new 1394 stack loaded..... False
  new 1394 stack active..... False
  /dev/raw1394 node present. True
  /dev/raw1394 permissions.. True
 Prerequisites (dynamic at run-time)...
   gcc................ gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3
   g++................ g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3
   PyQt............... Python User Interface Compiler 3.18.1 for Qt version 3.3.8b
   jackd.............. jackd version 0.118.0 tmpdir /dev/shm protocol 24
     path............. /usr/bin/jackd
     flags............  -ljack -lpthread -lrt  
   libraw1394......... 2.0.4
     flags............  -lraw1394  
   libavc1394......... 0.5.3
     flags............  -lavc1394 -lrom1394 -lraw1394  
   libiec61883........ 1.2.0
     flags............  -liec61883 -lraw1394  
   libxml++-2.6....... 2.30.0
     flags............ -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0  
   dbus-1............. 1.2.16
     flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include  -L/lib -ldbus-1 -lpthread -lrt  
 Prerequisites (static at compile-time)...
   gcc................ gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3
   g++................ g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3
   PyQt............... sh: pyuic: not found
   jackd.............. sh: jackd: not found
     path............. 
     flags............ Package jack was not found in the pkg-config search path.
   libraw1394......... 2.0.4
     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.26.1
     flags............ -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0  
   dbus-1............. 1.2.16
     flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include  -L/lib -ldbus-1 -lpthread -lrt  
 Hardware...
   Host controllers:
02:01.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05) (prog-if 10)
	Subsystem: Dell Device [1028:024d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (500ns min, 1000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at f65ff800 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME+
	Kernel driver in use: ohci1394
	Kernel modules: firewire-ohci, ohci1394

   CPU info:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     P9600  @ 2.53GHz
stepping	: 10
cpu MHz		: 800.000
cache size	: 6144 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority
bogomips	: 5053.47
clflush size	: 64
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     P9600  @ 2.53GHz
stepping	: 10
cpu MHz		: 2535.000
cache size	: 6144 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority
bogomips	: 5053.72
clflush size	: 64
power management:

 Configuration...
  IRQ information
Hardware Interrupts:
--------------------
 IRQ    0: PID:  None, count:         [130, 130], Sched None (priority None), drivers: ['timer']
 IRQ    1: PID:  None, count:           [14, 14], Sched None (priority None), drivers: ['i8042']
 IRQ    8: PID:  None, count:             [1, 1], Sched None (priority None), drivers: ['rtc0']
 IRQ    9: PID:  None, count:         [404, 404], Sched None (priority None), drivers: ['acpi']
 IRQ   12: PID:  None, count:           [76, 76], Sched None (priority None), drivers: ['i8042']
 IRQ   17: PID:  None, count:           [43, 43], Sched None (priority None), drivers: ['eth1']
 IRQ   18: PID:  None, count:             [0, 0], Sched None (priority None), drivers: ['mmc0']
 IRQ   19: PID:  None, count:     [18214, 18214], Sched None (priority None), drivers: ['ata_piix', 'ata_piix', 'ohci1394']
 IRQ   20: PID:  None, count:         [176, 176], Sched None (priority None), drivers: ['ehci_hcd:usb2', 'uhci_hcd:usb3', 'uhci_hcd:usb6']
 IRQ   21: PID:  None, count:         [451, 451], Sched None (priority None), drivers: ['uhci_hcd:usb4', 'uhci_hcd:usb7', 'HDA Intel']
 IRQ   22: PID:  None, count:           [35, 35], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb5', 'uhci_hcd:usb8']
 IRQ   27: PID:  None, count:         [336, 336], Sched None (priority None), drivers: ['eth0']
 IRQ   28: PID:  None, count:     [13301, 13301], Sched None (priority None), drivers: ['i915']

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


=== REPORT ===
FireWire kernel drivers:
[PASS] Kernel modules present and correctly loaded.
[PASS] /dev/raw1394 node present and accessible.

autostatic · Post by **autostatic** » Mon Feb 28, 2011 12:55 pm

How does your /etc/default/rtirq file look like? Did you add ohci1394 to it? And it now shows up two times because you have to controllers probably. Is it possible to disable the onboard one? And it's not necessary to mount /tmp to tmpfs.

Best,

Jeremy

stefan · Post by **stefan** » Mon Feb 28, 2011 1:19 pm

Here's my rtirq:

Code: Select all

~$ cat /etc/default/rtirq
RTIRQ_NAME_LIST="rtc0 ohci1394 snd usb i8042"
RTIRQ_PRIO_HIGH=90
RTIRQ_PRIO_DECR=5
RTIRQ_RESET_ALL=0
RTIRQ_NON_THREADED="rtc0 ohci1394 snd"

And Yes, I can disable the onboard firewire port via BIOS. The only diff is that (again) the 'ohci1394' shows up once. It's still on he 19th irq, though. And no 'yenta' entry... Maybe I'm a bit hung up the 'yenta' thingy, but all the posts I've came across on the topic mention this.

If I remember correctly, the ffado-mixer still reports error if I disable the onboard fw and run off the ExpressCard (I'm at work now, and can't verify it).

Is my assumption that the onboard fw and the ExpressCard slot is wired to the same bus wrong?

Pablo · Post by **Pablo** » Mon Feb 28, 2011 2:06 pm

Hi, try raising the prio of mmc0, instead of yenta which you don't have. IIRC, that did the trick in a friends' laptop with a FA-66.

stefan · Post by **stefan** » Mon Feb 28, 2011 2:10 pm

Thanks Pablo. I'll try it this evening and report back...

autostatic · Post by **autostatic** » Mon Feb 28, 2011 2:41 pm

stefan wrote:
Code: Select all
RTIRQ_NAME_LIST="rtc0 ohci1394 snd usb i8042"

Ok, looks good.

stefan wrote:Maybe I'm a bit hung up the 'yenta' thingy, but all the posts I've came across on the topic mention this

Afaik yenta is a cardbus controller module. Unless you have such a cardbus controller you don't need to prioritize it.

stefan wrote:If I remember correctly, the ffado-mixer still reports error if I disable the onboard fw and run off the ExpressCard (I'm at work now, and can't verify it).

That's probably because the samplerate set in ffado-mixer doesn't match with the samplerate of the device. But does ffado-mixer start? And can you set the samplerate in there? And the most important thing: does your FA-66 work with JACK?

stefan wrote:Is my assumption that the onboard fw and the ExpressCard slot is wired to the same bus wrong?

No, it's right.

Best,

Jeremy

autostatic · Post by **autostatic** » Mon Feb 28, 2011 2:47 pm

Pablo wrote:Hi, try raising the prio of mmc0, instead of yenta which you don't have. IIRC, that did the trick in a friends' laptop with a FA-66.

That's weird, mmc0 is the (multimedia) cardreader on your system, it has nothing to do with FireWire controllers/soundcards or ExpressCards.

Best,

Jeremy

stefan · Post by **stefan** » Mon Feb 28, 2011 4:12 pm

Ok... I'm back at home. To sum things up.

1. The onboard fw is disabled. I run from the ExpressCard.

2. I boot into my RT kernel and start the ffado-dbus-server, then ffado-mixer. Same error. And I can't set the sample rate in the mixer. And whatever samplerate I set in my FA-66, the errors keep coming. And yes, I restart the FA-66 between tries.

3. I can't seem to find any 'mmc0' from ps -eLo...

4. When I run ffado-dbus-server I get:

Code: Select all

-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.0.0
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

 Discovering devices...
 Starting DBUS service...
 Running... (press ctrl-c to stop & exit)

Then it halts. So I open up a new terminal end run ffado-mixer:

Code: Select all

~$ ffado-mixer

I fires up, but the ffado-dbus-server prints:

Code: Select all

00709354900: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709368680: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709382706: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709397838: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709432833: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709447776: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709462763: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug
00709476614: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug

The mixer starts (see attached screenshot) and I can adjust the up and down knobs (don't know the term, sorry). But I can't change 'sample rate' or 'clock source'.The six 'knobs' are grouped with the label 'monitor input mixer'. I really don't know how this is supposed to look, or how I am supposed to test the mixer.

5. Yes. To the best of my knowledge, jack and my FA-66 plays nicely. That is,

Code: Select all

jackd -P70 -p512 -dfirewire -r48000 -p128 -n3

does not throw any errors...

autostatic · Post by **autostatic** » Mon Feb 28, 2011 4:22 pm

stefan wrote:5. Yes. To the best of my knowledge, jack and my FA-66 plays nicely. That is,
Code: Select all
jackd -P70 -p512 -dfirewire -r48000 -p128 -n3
does not throw any errors...

And what if you start the mixer after having started JACK? And I just checked this: http://www.roland.com/products/en/FA-66 ... e_03_L.jpg so indeed, you can't change the samplerate in ffado-mixer, you have to do it on the device itself.
Up and down knobs = faders.

stefan · Post by **stefan** » Mon Feb 28, 2011 5:10 pm

Well, if I start ffado-dbus-server, then run:

Code: Select all

jackd -P70 -p512 -dfirewire -r48000 -p128 -n3

Then start ffado-mixer the errors keep coming, but the two drop-downs in the mixer gui are grayed out. However, when I start the mixer without jack, the drop-downs are 'active' but there are only one option. Nothing to change.

autostatic · Post by **autostatic** » Mon Feb 28, 2011 8:52 pm

And what if you start JACK first and then the FFADO stuff?

Best,

Jeremy

stefan · Post by **stefan** » Wed Mar 02, 2011 5:34 am

Sorry for the absence... stupid business trips!

It doesn't matter if I start jack first or not. The only diff is the one described above (controls being 'grayed out'). So,

1. Starting jackd -> ffado-dbus-server -> ffado-mixer = error plus controls in the mixer not grayed out.

2. Starting ffado-dbus-server -> ffado-mixer = error plus controls grayed out.

LinuxMusicians

Edirol FA-66 and Ricoh Host Controller

Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller

Re: Edirol FA-66 and Ricoh Host Controller