Skip to main content

1 - Le matériel et les pilotes ALSA, FFADO, ...


[RÉSOLU] Onyx Firewire Option Card

Bonjour à tous,

J'aimerais utiliser la Mackie Onyx 1640 avec Firewire Option Card sur Manjaro, mais elle n'est pas détectée.
Elle a pourtant l'air bien supportée http://www.ffado.org/?q=node/85
Comment savoir d'où vient le problème?

Merci pour votre aide

Carte mère : G33M-S2L

Quand je branche le cable:
Copy to clipboard
# journalctl -f fév 10 21:47:38 bob-pc kernel: firewire_ohci 0000:05:01.0: isochronous cycle inconsistent fév 10 21:47:39 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 35) fév 10 21:47:42 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 3e) fév 10 21:47:45 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 6) fév 10 21:47:49 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel c) fév 10 21:47:52 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 12) fév 10 21:47:55 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 18) fév 10 21:47:58 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 1e) fév 10 21:48:01 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 25) fév 10 21:48:05 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 2b) fév 10 21:48:08 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 32) fév 10 21:48:11 bob-pc kernel: firewire_core 0000:05:01.0: giving up on node ffc1: reading config rom failed: no ack fév 10 21:48:11 bob-pc kernel: firewire_core 0000:05:01.0: unsolicited response (source ffc1, tlabel 3a) fév 10 21:48:11 bob-pc kernel: firewire_core 0000:05:01.0: phy config: new root=ffc0, gap_count=5


Copy to clipboard
# ffado-test ListDevices ----------------------------------------------- FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org Version: 2.4.1 (C) 2008, Daniel Wagner, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY. ----------------------------------------------- === 1394 PORT 0 === Node id GUID VendorId ModelId Vendor - Model 1 0x001106664555858b 0x00001106 0x00000000 Linux Firewire - no message buffer overruns


Copy to clipboard
# ls -l /dev/fw* crw-rw-r-- 1 root video 243, 0 10 fév 18:20 /dev/fw0


Copy to clipboard
# ffado-diag FFADO diagnostic utility 2.4.1 (C) 2008 Pieter Palmers 2009-2010 Arnold Krille 2018 Nicolas Boulenguez, Jonathan Woithe gcc /usr/bin/gcc gcc (GCC) 8.2.1 20181127 g++ /usr/bin/g++ g++ (GCC) 8.2.1 20181127 pyuic4 None pyuic5 /usr/bin/pyuic5 Python User Interface Compiler 5.11.3 for Qt version 5.12.0 jackd /usr/bin/jackd jackd version 0.125.0 tmpdir /dev/shm protocol 25 pkg-config /usr/bin/pkg-config jack 0.125.0 -ljack -lpthread libraw1394 2.1.2 -lraw1394 libavc1394 0.5.4 -lavc1394 -lrom1394 -lraw1394 libiec61883 1.2.0 -liec61883 -lraw1394 libxml++-2.6 not found dbus-1 1.12.12 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 Build time info /usr/lib/libffado/static_info.txt gcc /usr/bin/gcc gcc (GCC) 8.1.1 20180531 g++ /usr/bin/g++ g++ (GCC) 8.1.1 20180531 pyuic4 None pyuic5 /usr/bin/pyuic5 Python User Interface Compiler 5.11.2 for Qt version 5.11.1 jackd /usr/bin/jackd jackd version 0.125.0 tmpdir /dev/shm protocol 25 pkg-config /usr/bin/pkg-config jack 0.125.0 -ljack -lpthread libraw1394 2.1.2 -lraw1394 libavc1394 0.5.4 -lavc1394 -lrom1394 -lraw1394 libiec61883 1.2.0 -liec61883 -lraw1394 libxml++-2.6 not found dbus-1 1.12.8 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 kernel version 4.18.16-rt9-MANJARO Preempt (low latency) False RT patched True /dev/fw* ['/dev/fw0'] crw-rw-r-- 1 root video 243, 0 Feb 10 18:20 /dev/fw0 User IDs uid=0(root) gid=0(root) groups=0(root) uname -a Linux bob-pc 4.18.16-rt9-MANJARO #1 SMP PREEMPT RT Mon Oct 29 18:36:52 UTC 2018 x86_64 GNU/Linux lspci /usr/bin/lspci 05:01.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 80) (prog-if 10 [OHCI]) Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] 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 (8000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=2K] Region 1: I/O ports at c000 [size=128] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: firewire_ohci Kernel modules: firewire_ohci lscpu /usr/bin/lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 36 bits physical, 48 bits virtual CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Model name: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz Stepping: 6 CPU MHz: 2025.351 BogoMIPS: 5335.31 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 6144K NUMA node0 CPU(s): 0,1 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 nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti tpr_shadow vnmi flexpriority dtherm Hardware interrupts IRQ 0 PID count 40,0 Sched priority drivers IO-APIC,2-edge,timer IRQ 1 PID count 3563,0 Sched priority drivers IO-APIC,1-edge,i8042 IRQ 7 PID count 0,0 Sched priority drivers IO-APIC,7-edge,parport0 IRQ 8 PID count 1,0 Sched priority drivers IO-APIC,8-edge,rtc0 IRQ 9 PID count 0,0 Sched priority drivers IO-APIC,9-fasteoi,acpi IRQ 16 PID count 11623,0 Sched priority drivers IO-APIC,16-fasteoi,uhci_hcd:usb3,,pata_jmicron IRQ 18 PID count 0,114071 Sched priority drivers IO-APIC,18-fasteoi,ehci_hcd:usb1,,uhci_hcd:usb5,,uhci_hcd:usb8,,i801_smbus IRQ 19 PID count 0,48800 Sched priority drivers IO-APIC,19-fasteoi,firewire_ohci,,ata_piix,,uhci_hcd:usb7,,ata_piix IRQ 21 PID count 0,0 Sched priority drivers IO-APIC,21-fasteoi,uhci_hcd:usb4 IRQ 23 PID count 0,137950 Sched priority drivers IO-APIC,23-fasteoi,ehci_hcd:usb2,,uhci_hcd:usb6 IRQ 24 PID count 47410,0 Sched priority drivers PCI-MSI,2097152-edge,enp4s0 IRQ 25 PID count 0,4203382 Sched priority drivers PCI-MSI,442368-edge,snd_hda_intel:card0 IRQ 26 PID count 639342,0 Sched priority drivers PCI-MSI,524288-edge,nvkm Software interrupts module directory /lib/modules/4.18.16-rt9-MANJARO Old 1394 stack ieee1394 not present ieee1394 not loaded ohci1394 not present ohci1394 not loaded raw1394 not present raw1394 not loaded stack active False statically linked False New 1394 stack firewire-core not present firewire-core loaded firewire-ohci not present firewire-ohci loaded stack active True statically linked False Kernel support: 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).

Copy to clipboard
# ffado-dbus-server ----------------------------------------------- FFADO Control DBUS service Part of the FFADO project -- www.ffado.org Version: 2.4.1 (C) 2008, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY. ----------------------------------------------- 1549836467070032: (ffado-dbus-server.cpp)[ 275] main: Discovering devices... 01376068039: Debug (devicemanager.cpp)[ 354] discover: Starting discovery... 01376074465: Debug (devicemanager.cpp)[ 398] discover: Could not read config rom from device (node id 1). Skip device discovering for this node 01376080861: Debug (devicemanager.cpp)[ 573] discover: Could not read config rom from device (node id 1). Skip device discovering for this node 01376080878: Debug (devicemanager.cpp)[ 661] discover: Discovery finished... 01376080883: Debug (devicemanager.cpp)[1258] showDeviceInfo: ===== Device Manager ===== 01376080912: Debug (Element.cpp)[ 121] show: Element DeviceManager 01376080915: Debug (devicemanager.cpp)[1266] showDeviceInfo: --- IEEE1394 Service 0 --- terminate called after throwing an instance of 'DBus::Error' what(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Abandon (core dumped)



Peut-être un problème de permissions?
Copy to clipboard
# /dev/fw0 permissions: bash: /dev/fw0: Permission non accordée


J'ai essayé ça
Copy to clipboard
# sudo chmod 777 /dev/fw0


Mais du coup
Copy to clipboard
/dev/fw0 permissions:
ne donne plus rien
France
As-tu la possibilité d'essayer un live-USB de LibraZiK-2 pour pouvoir comparer ?
Sur LibraZik-2, même messages d'erreurs.

Par contre j'ai trouvé une autre carte FireWire, et la Mackie est détectée!

Copy to clipboard
# lspci |grep FireWire 05:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 61)


Copy to clipboard
# ffado-test ListDevices ----------------------------------------------- FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org Version: 2.3.0-Unversioned directory (C) 2008, Daniel Wagner, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY. ----------------------------------------------- === 1394 PORT 0 === Node id GUID VendorId ModelId Vendor - Model 0 0x0030bd0000002f34 0x000030BD 0x00000000 Linux Firewire - 1 0x00000ff200000019 0x0000000F 0x00010065 Mackie - Onyx Firewire no message buffer overruns


Plus qu'à essayer avec Ardour.

Merci! 😎
France
Si c'est la même chose sous LibraZiK-2, alors probablement y a-t'il un soucis avec cette interface audio côté FFADO.

À en lire le fil de discussion que tu donnes dans ton message initial ici, certains modèles sont supportés, d'autres non. Aurais-tu un lien vers la fiche constructeur du modèle précis de cette interface audio ?

Édition : après avoir relu ton dernier message, je me demande si je l'ai bien compris. En tentant de le re-phraser, tu veux dire qu'avec une autre carte-contrôleur firewire, la même interface Mackie fonctionne à présent ? Si c'est bien ça, c'est très possible car j'ai lu maintes fois que certains contrôleurs firewire étant déficients avec l'utilisation d'une interface audio étant connectée dessus (sous linux, et même sous d'autres systèmes d'exploitation).
Oui, le soucis venait bien la carte pci firewire de l'ordi (VIA VT6307 rev 80).
Elle avait l'air de fonctionner pour certains: http://subversion.ffado.org/wiki/HostControllers

Sinon sur Manjaro quelques XRUNs, mais tourne nickel sur librazik2! 😎
France
OK, merci pour le retour. Et merci pour le [RÉSOLU] également.

Bonne musique à toi avec LibraZiK-2 à présent.