Linux MAO | [ABANDONNÉ] Pb install Presonus Firebox

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

[ABANDONNÉ] Pb install Presonus Firebox

Envoyé par jpa le Fri 13 Dec 2013 09:53

Bonjour à tous,

J'ai acheté d'occasion une Presonus Firebox firewire, devant enregistrer ma basse dans ardour2, etc...

Je suis en Debian Wheezy, j'ai vu sur linuxmao et ailleurs que la carte son fonctionne avec FFADO, que j'ai installé, grâce aux packages suivants:

Copy to clipboard

ii  ffado-dbus-server                      2.0.99+svn2171-2                   amd64        FFADO D-Bus server
  ii  ffado-mixer-qt4                        2.0.99+svn2171-2                   all          FFADO D-Bus mixer applets (QT4)
  ii  ffado-tools                            2.0.99+svn2171-2                   amd64        FFADO debugging and firmware tools
  ii  libffado2                              2.0.99+svn2171-2                   amd64        FFADO API

Le Firewire semble OK sur ma carte mère jusqu'au connecteur:

Copy to clipboard

$ lspci | grep Fire
05:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller

$ dmesg | grep firewire
[    1.086784] firewire_ohci 0000:05:00.0: setting latency timer to 64
[    1.154100] firewire_ohci: Added fw-ohci device 0000:05:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11
[ 1164.914066] firewire_core: created device fw0: GUID 001e8c0001dbb113, S400
[ 1516.084068] firewire_core: skipped bus generations, destroying all nodes
[ 1516.579714] firewire_core: rediscovered device fw0

[deux dernières lignes qui se répète à chaque fois que je connecte/déconnecte le cable firewire d'un côté ou de l'autre)

Mais voilà, on dirait que la carte n'est pas reconnue:

Copy to clipboard

$ sudo ffado-test ListDevices
-----------------------------------------------
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

=== 1394 PORT 0 ===
  Node id  GUID                  VendorId     ModelId   Vendor - Model
   0       0x001e8c0001dbb113  0x00001E8C  0x00000000   Linux Firewire - 
no message buffer overruns



$ sudo 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...
DBUS service running
press ctrl-c to stop it & exit

....

bien sûr ffado-mixer ne donne rien... pas mieux que jack & cie, même en le démarrant en mode firewire. Pas étonnant, puisque je pense qu'à ce stade, la carte devrait au moins être reconnue ?!!!

J'ajoute que le gars à qui je l'ai acheté ne l'a pas trop utilisée, voir pas du tout depuis longtemps... Faut la mettre à jour? (firmware??? possible????...)

J'avoue être completement planté à ce niveau.

Merci pour toute aide!!

===========

Pour la route: ffado-diag complet!

[+]

Copy to clipboard

$ sudo ffado-diag 


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


=== CHECK ===
 Base system...
  kernel version............ 3.2.0-4-amd64
    Preempt (low latency)... False
    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
  /dev/fw* permissions:
crw------- 1 root root 252, 0 déc.  13 09:18 /dev/fw0
  User IDs:
uid=0(root) gid=0(root) groupes=0(root)
 Prerequisites (dynamic at run-time)...
   gcc ............... gcc (Debian 4.7.2-5) 4.7.2
   g++ ............... g++ (Debian 4.7.2-5) 4.7.2
   PyQt4 (by pyuic4) . sh: 1: pyuic4: not found
   jackd ............. no message buffer overruns
     path ............ /usr/bin/jackd
     flags ........... Package jack was not found in the pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
   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.6.8
     flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  -ldbus-1  
 Prerequisites (static at compile-time)...
   gcc ............... gcc (Debian 4.7.1-2) 4.7.1
   g++ ............... g++ (Debian 4.7.1-2) 4.7.1
   PyQt4 (by pyuic4) . Python User Interface Compiler 4.9.1 for Qt version 4.8.1
   jackd ............. sh: 1: jackd: not found
     path ............ 
     flags ........... Package jack was not found in the pkg-config search path.
   libraw1394 ........ 2.0.9
     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.2
     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.6.0
     flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  -ldbus-1  
 uname -a...
   Linux deiphobe 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
 Hardware...
   Host controllers:
05:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] (prog-if 10 [OHCI])
	Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard [1043:8384]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-

Lectures: 5224

Messages: Tri: Rechercher :

Envoyé par jpa le Fri 13 Dec 2013 14:45

Hop,

Renseignement pris auprès de la communauté FFADO + ARDOUR (surtout!!).

Ça viendrait de mon chipset Firewire de ma carte mère (voir au dessus), qui est un VIA.

J'ai donc, sur les reccomandations de ces gens avisés, commandé une carte PCI interne à base de Texas Instruments, sur un site de vente de matos informatique qui assure que cette carte là -avec deux chipsets texas instruments- est vraiment parfaite pour les cartes son externes en firewire..

(en 400 bien sûr, pas besoin du 800 dans mon cas.)

Je reviendrai ici pour dire si ça résolu mon soucis ou pas, d'ici une semaine, le temps de recevoir la carte, la monter, faire des tests... etc..

A+ !!

Envoyé par olinuxx le Sun 02 Feb 2014 13:43 France

Salut jpa,
alors, ça marche maintenant ? On peut passer ce sujet en [RÉSOLU] ?
A+
Olivier

Aller au forum:

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

Thread actions

Contenu en relation