Ticket #289 (closed bug: worksforme)

Opened 10 years ago

Last modified 9 years ago

the old firewire stack (raw1394) seems required

Reported by: cedricr Assigned to: arnonym
Priority: minor Milestone: FFADO 2.x
Component: generic Version: FFADO SVN (trunk)
Keywords: Cc:
The device the bug applies to:

Description

Dear All,

When I launch ffado-diag it returns "This stack is not supported by FFADO. Please use the old stack". Could you help me please ?

Thank you in advance for you help.

Regards,

C├ędric

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

CHECK

Base system...

kernel version............ 2.6.34-ARCH

FIXME: implement test for RT kernel

RT patched............... False

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

Prerequisites (dynamic at run-time)...

gcc................ gcc (GCC) 4.5.0 20100610 (prerelease) g++................ g++ (GCC) 4.5.0 20100610 (prerelease) PyQt?............... sh: pyuic : commande introuvable jackd.............. no message buffer overruns

path............. /usr/bin/jackd flags............ -ljack

libraw1394......... 2.0.5

flags............ -lraw1394

libavc1394......... 0.5.3

flags............ -lavc1394 -lrom1394 -lraw1394

libiec61883........ 1.2.0

flags............ -liec61883 -lraw1394

libxml++-2.6....... 2.30.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.24

flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 -lpthread -lrt

Prerequisites (static at compile-time)...

gcc................ gcc (GCC) 4.5.0 20100610 (prerelease) g++................ g++ (GCC) 4.5.0 20100610 (prerelease) PyQt?............... sh: pyuic : commande introuvable jackd.............. sh: jackd : commande introuvable

path............. which: no jackd in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core) flags............ Package jack was not found in the pkg-config search path.

libraw1394......... 2.0.5

flags............ -lraw1394

libavc1394......... 0.5.3

flags............ -lavc1394 -lrom1394 -lraw1394

libiec61883........ 1.2.0

flags............ -liec61883 -lraw1394

libxml++-2.6....... 2.30.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.24

flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 -lpthread -lrt

Hardware...

Host controllers:

09:03.1 FireWire? (IEEE 1394) [0c00]: Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller [104c:803a] (prog-if 10 [OHCI])

Subsystem: Sony Corporation Device [104d:9005] 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: 32 (750ns min, 1000ns max), Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 17 Region 0: Memory at fc102000 (32-bit, non-prefetchable) [size=2K] Region 1: Memory at fc104000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: firewire_ohci Kernel modules: firewire-ohci

CPU info:

processor : 0 vendor_id : GenuineIntel? cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz stepping : 13 cpu MHz : 1995.083 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida tpr_shadow vnmi flexpriority bogomips : 3991.42 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:

processor : 1 vendor_id : GenuineIntel? cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz stepping : 13 cpu MHz : 1995.083 cache size : 2048 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida tpr_shadow vnmi flexpriority bogomips : 3991.24 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:

Configuration...

IRQ information

Hardware Interrupts:


IRQ 0: PID: None, count: [240629, 240629], Sched None (priority None), drivers: timer? IRQ 1: PID: None, count: [2453, 2453], Sched None (priority None), drivers: i8042? IRQ 8: PID: None, count: [0, 0], Sched None (priority None), drivers: rtc0? IRQ 9: PID: None, count: [2689, 2689], Sched None (priority None), drivers: acpi? IRQ 12: PID: None, count: [64, 64], Sched None (priority None), drivers: i8042? IRQ 14: PID: None, count: [10843, 10843], Sched None (priority None), drivers: ata_piix? IRQ 15: PID: None, count: [0, 0], Sched None (priority None), drivers: ata_piix? IRQ 16: PID: None, count: [65337, 65337], Sched None (priority None), drivers: ['uhci_hcd:usb3', 'yenta', 'nvidia'] IRQ 17: PID: None, count: [68, 68], Sched None (priority None), drivers: firewire_ohci? IRQ 18: PID: None, count: [7, 7], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb7', 'tifm_7xx1'] IRQ 19: PID: None, count: [25893, 25893], Sched None (priority None), drivers: uhci_hcd:usb6? IRQ 21: PID: None, count: [0, 0], Sched None (priority None), drivers: uhci_hcd:usb4? IRQ 23: PID: None, count: [1, 1], Sched None (priority None), drivers: ['ehci_hcd:usb2', 'uhci_hcd:usb5'] IRQ 29: PID: None, count: [38675, 38675], Sched None (priority None), drivers: ahci? IRQ 30: PID: None, count: [6022, 6022], Sched None (priority None), drivers: sky2? IRQ 31: PID: None, count: [0, 0], Sched None (priority None), drivers: iwlagn? IRQ 32: PID: None, count: [298, 298], Sched None (priority None), drivers: hda_intel?

Software Interrupts:


REPORT

FireWire? kernel drivers:

The new FireWire? kernel stack is loaded. This stack is not supported by FFADO. Please use the old stack.

Attachments

ffado-diag.txt (7.0 kB) - added by cedricr on 06/27/10 07:02:56.
ffado-diag.txt

Change History

06/27/10 07:02:56 changed by cedricr

  • attachment ffado-diag.txt added.

ffado-diag.txt

06/27/10 08:17:05 changed by arnonym

  • owner set to arnonym.
  • priority changed from blocker to minor.
  • status changed from new to assigned.
  • milestone changed from FFADO 2.x to FFADO 2.1.

Yeah, thats just an old relict. Will remove that anytime soon.

But it will _not_ stop ffado from working with the new stack :-)

06/28/10 00:53:39 changed by cedricr

I am happy to learn about it! Please, let me know when I must to test it. If I can help you do not hesitate.

See you,

07/07/10 12:50:51 changed by cedricr

  • version changed from FFADO 2.0.1 to FFADO SVN (trunk).
  • milestone changed from FFADO 2.1 to FFADO 2.x.

If it can help you, I have this error message when I launch ffado-mixer directly from console:

[cedric@Linux-LPT bin]$ ./ffado-mixer


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


00685741771: (ffado-dbus-server.cpp)[ 270] main: Discovering devices... 00685790834: Fatal (devicemanager.cpp)[ 191] initialize: No firewire adapters (ports) found. 00685790881: Error (ffado-dbus-server.cpp)[ 277] main: Could not initialize device manager 00685791038: Debug (ffado-dbus-server.cpp)[ 202] exitfunction: Debug output flushed... no message buffer overruns 23:47:32 logginghandler ERROR Could not communicate with the FFADO DBus service...

(follow-up: ↓ 5 ) 07/07/10 13:43:51 changed by adi

This means you don't have rw access to the device node in question. With the old stack, it was /dev/raw1394, with the new stack, it's probably /dev/fw1, given that /dev/fw0 is your controller.

Try chmod 666 on the device node, if this helps, you can write an udev rule to make this change permanent. There's a mail by Stefan Richter on ffado-devel asking for device IDs, so we can ship an appropriate udev rule with FFADO.

HTH

(in reply to: ↑ 4 ) 07/08/10 07:22:47 changed by stefanr

Device file permissions and udev rules are off-topic to this bug. Such issues are best discussed on the linux1394-user mailinglist since they are most certainly not FFADO specific at all. https://ieee1394.wiki.kernel.org/index.php/Contact

03/27/12 03:59:30 changed by jwoithe

  • status changed from assigned to closed.
  • resolution set to worksforme.

In the 18 months since the last addition to this ticket, the new kernel firewire stack has completely displaced the old (and in fact the old stack is no longer in the stock kernel.org kernels). Reports from users with many different interfaces on varied computers indicate that the new stack is now working just as well as the old, if not better. Finally, the ffado-diag output noted at the start of this ticket was updated in r2053. As a result, I don't believe the issues raised by this ticket are relevant anymore - the old firewire stack is no longer required by FFADO.

If anyone has problems which seem related to the kernel stack, please create a new ticket specifically for the issue concerned.