Chargement...
 
Skip to main content

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


Fire wire ,HP EliteBook 8440p [RESOLU]

Bonjour,


J'avais creer un homme studio avec une tours avant, tout fonctionnait (Librazik, Ardour, et autres logciels , table ONYX 1620i et les musicos !!)

Pour des raison pratique, J'ai fais l'achat d'un HP EliteBook 8440p, pour son FIREWIRE, pour brancher sur table de mixage ONYX 1620i.

et voila le hic, je n'y arrive pas, j'ai mème pensé au cordon (croisé , droit)..
je passe les détails des essais...

Copy to clipboard
root@neufdegres:/home/neufdegres# cat /proc/asound/cards 0 [MID ]: HDA-Intel - HDA Intel MID HDA Intel MID at 0xd4720000 irq 31


Copy to clipboard
root@neufdegres:/home/neufdegres# aplay -l **** Liste des Périphériques Matériels PLAYBACK **** carte 0: MID [HDA Intel MID], périphérique 0: 92HD75B3X5 Analog [92HD75B3X5 Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: MID [HDA Intel MID], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: MID [HDA Intel MID], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: MID [HDA Intel MID], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 root@neufdegres:/home/neufdegres#


Cecque QtlJack renvoi
Copy to clipboard
18:51:39.555 Journalisation démarrée --- sam. sept. 28 18:51:39 2019 --- 18:51:39.645 Réinitialisation des statistiques. 18:51:39.655 Changement des connexions ALSA. Cannot connect to server socket err = Aucun fichier ou dossier de ce type Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 18:51:39.777 Changement du graphe des connexions ALSA. qjackctlAlsaGraph::updateItems() 18:51:42.617 Script de démarrage... 18:51:42.617 pulseaudio --start Cannot connect to server socket err = Aucun fichier ou dossier de ce type Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock N: [pulseaudio] main.c: Serveur configuré par l'utilisateur sur {c189928e5c154026b9bc325866c8f86e}unix:/run/user/1000/pulse/native, qui semble être local. Analyse plus précise en cours. 18:51:43.035 Script de démarrage terminé avec succès. 18:51:43.035 JACK démarre... 18:51:43.035 /usr/bin/jackd -v -P70 -dfirewire -r48000 -p512 -n3 -i1 -o1 18:51:43.039 JACK a été démarré avec le PID=2276. no message buffer overruns no message buffer overruns no message buffer overruns jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 70 self-connect-mode is "Don't restrict self connect requests" Jack: JackPosixThread::StartImp : create non RT thread Jack: JackPosixThread::ThreadHandler : start Jack: JackDriver::Open capture_driver_name = Jack: JackDriver::Open playback_driver_name = Jack: Check protocol client = 8 server = 8 Jack: JackEngine::ClientInternalOpen: name = system Jack: JackEngine::AllocateRefNum ref = 0 Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 Jack: JackEngine::NotifyAddClient: name = system Jack: JackGraphManager::SetBufferSize size = 512 Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackDriver::SetupDriverSync driver sem in flush mode Jack: JackSocketServerChannel::Open Jack: JackServerSocket::Bind : addr.sun_path /dev/shm/jack_default_1000_0 Jack: JackSocketServerChannel::BuildPoolTable size = 1 Jack: JackEngine::Open Jack: JackClientSocket::Connect : addr.sun_path /dev/shm/jack_default_1000_0 Jack: JackEngine::ClientInternalOpen: name = freewheel Jack: JackEngine::AllocateRefNum ref = 1 Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_freewheel val = 0 Jack: JackEngine::NotifyAddClient: name = freewheel Jack: JackDriver::ClientNotify ref = 1 driver = system name = freewheel notify = 0 Jack: JackDriver::ClientNotify ref = 0 driver = freewheel name = system notify = 0 Jack: JackConnectionManager::DirectConnect first: ref1 = 1 ref2 = 1 Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 1 ref2 = 1 Jack: JackDriver::SetupDriverSync driver sem in flush mode Jack: JackFFADODriver::Attach fBufferSize 512 fSampleRate 48000 1569689503206483: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.4.1 built Apr 19 2018 20:03:01 firewire ERR: FFADO: Error creating virtual device Cannot attach audio driver Jack: JackDriver::Close Jack: JackConnectionManager::DirectDisconnect last: ref1 = 1 ref2 = 1 Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 1 ref2 = 1 Jack: JackEngine::ClientInternalClose ref = 1 Jack: JackEngine::ClientCloseAux ref = 1 Jack: JackGraphManager::RemoveAllPorts ref = 1 Jack: JackDriver::ClientNotify ref = 1 driver = system name = freewheel notify = 1 Jack: JackEngine::Close Jack: JackClientSocket::Close Jack: JackServerSocket::Close /dev/shm/jack_default_1000_0 Jack: JackDriver::Close Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackEngine::ClientInternalClose ref = 0 Jack: JackEngine::ClientCloseAux ref = 0 Jack: JackGraphManager::RemoveAllPorts ref = 0 Jack: no message buffer overruns Jack: JackPosixThread::Stop Jack: JackPosixThread::ThreadHandler : exit JackServer::Open failed with -1 Jack: Succeeded in unlocking 82280346 byte memory area Jack: JackShmMem::delete size = 0 index = 0 Jack: ~JackDriver no message buffer overruns Jack: ~JackDriver Jack: Succeeded in unlocking 1187 byte memory area Jack: JackShmMem::delete size = 0 index = 1 Jack: Cleaning up shared memory Jack: Cleaning up files Jack: Unregistering server `default' Failed to open server 18:51:43.230 JACK a été arrêté qjackctlJackGraph::clearItems() 18:51:45.083 Impossible de connecter le serveur JACK comme client. - L'opération a échoué. - Incapable de se connecter au serveur. Veuillez consulter la fenêtre des messages pour plus d'informations. Cannot connect to server socket err = Aucun fichier ou dossier de ce type Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock qjackctlJackGraph::clearItems() qjackctlJackGraph::clearItems()


Merci pour votre aide
Bonsoir Florentdu19,

Pour essayer de cerner le problème, tu peux lancer dans un terminal la commande

Copy to clipboard
ffado-diag


qui va lister tout l'environnement firewire de ton pc. Vérifie bien que tes ports firewire apparaissent. S'ils n'étaient pas listés, vérifie dans le bios de ta machine et active le port firewire le cas échéant.

En lançant la commande

Copy to clipboard
ffado-test ListDevices


tu devrais voir ta carte firewire apparaître.

Ces commandes font partie du paquet ffado-tools sur debian stretch.
Bonjour dlb, et merci !

Copy to clipboard
root@neufdegres:/home/neufdegres# 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 (Debian 8.3.0-6) 8.3.0 g++ /usr/bin/g++ g++ (Debian 8.3.0-6) 8.3.0 pyuic4 None pyuic5 None jackd /usr/bin/jackd jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 pkg-config None Build time info /usr/lib/x86_64-linux-gnu/libffado/static_info.txt gcc /usr/bin/gcc gcc (Debian 7.3.0-17) 7.3.0 g++ /usr/bin/g++ g++ (Debian 7.3.0-17) 7.3.0 pyuic4 None pyuic5 /usr/bin/pyuic5 Python User Interface Compiler 5.10.1 for Qt version 5.10.1 jackd None pkg-config /usr/bin/pkg-config jack not found libraw1394 2.1.2 -lraw1394 libavc1394 not found libiec61883 1.2.0 -liec61883 -lraw1394 libxml++-2.6 2.40.1 -I/usr/include/libxml++-2.6 -I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lglib-2.0 -lsigc-2.0 dbus-1 1.12.8 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1 kernel version 4.19.0-6-amd64 Preempt (low latency) False RT patched False /dev/fw* ['/dev/fw0'] crw------- 1 root root 246, 0 Sep 30 21:07 /dev/fw0 User IDs uid=0(root) gid=0(root) groups=0(root) uname -a Linux neufdegres 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux lspci /usr/bin/lspci 44:06.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 06) (prog-if 10 [OHCI]) Subsystem: Hewlett-Packard Company R5C832 IEEE 1394 Controller [103c:172a] 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 20 Region 0: Memory at d0401000 (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 NoSoftRst- PME-Enable- DSel=0 DScale=2 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): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 37 Model name: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz Stepping: 5 CPU MHz: 2320.620 CPU max MHz: 2400.0000 CPU min MHz: 1199.0000 BogoMIPS: 4787.94 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 3072K NUMA node0 CPU(s): 0-3 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm pti tpr_shadow vnmi flexpriority ept vpid dtherm ida arat Hardware interrupts IRQ 0 PID count 34,0,0,0 Sched priority drivers IO-APIC,2-edge,timer IRQ 1 PID count 0,0,31,0 Sched priority drivers IO-APIC,1-edge,i8042 IRQ 5 PID count 0,0,0,0 Sched priority drivers IO-APIC,5-edge,parport0 IRQ 8 PID count 0,0,0,1 Sched priority drivers IO-APIC,8-edge,rtc0 IRQ 9 PID count 0,1522,0,0 Sched priority drivers IO-APIC,9-fasteoi,acpi IRQ 12 PID count 0,21796,0,0 Sched priority drivers IO-APIC,12-edge,i8042 IRQ 16 PID count 0,370,0,0 Sched priority drivers IO-APIC,16-fasteoi,ehci_hcd:usb1 IRQ 18 PID count 0,0,0,0 Sched priority drivers IO-APIC,18-fasteoi,ips IRQ 20 PID count 0,0,5001,0 Sched priority drivers IO-APIC,20-fasteoi,ehci_hcd:usb2,,firewire_ohci IRQ 22 PID count 0,0,0,6 Sched priority drivers IO-APIC,22-fasteoi,mmc0,,yenta,,pata_pcmcia[0.0] IRQ 23 PID count 0,0,0,0 Sched priority drivers IO-APIC,23-edge,lis3lv02d IRQ 24 PID count 0,0,0,0 Sched priority drivers PCI-MSI,458752-edge,PCIe,PME IRQ 25 PID count 0,0,0,0 Sched priority drivers PCI-MSI,460800-edge,PCIe,PME,,pciehp IRQ 26 PID count 0,0,0,0 Sched priority drivers PCI-MSI,464896-edge,PCIe,PME IRQ 27 PID count 3,4692,0,0 Sched priority drivers PCI-MSI,409600-edge,enp0s25 IRQ 28 PID count 29942,0,0,0 Sched priority drivers PCI-MSI,512000-edge,ahci[0000:00:1f.2] IRQ 29 PID count 0,623,6059,0 Sched priority drivers PCI-MSI,32768-edge,i915 IRQ 30 PID count 0,24,0,0 Sched priority drivers PCI-MSI,360448-edge,mei_me IRQ 31 PID count 0,0,1637,0 Sched priority drivers PCI-MSI,442368-edge,snd_hda_intel:card0 Software interrupts module directory /lib/modules/4.19.0-6-amd64 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 present firewire-core loaded firewire-ohci 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). root@neufdegres:/home/neufdegres#



et

Copy to clipboard
root@neufdegres:/home/neufdegres# 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 0 0x5566778811223344 0x00556677 0x00000000 Linux Firewire - no message buffer overruns root@neufdegres:/home/neufdegres#



je crois que je n'est pas les pilotes , d'ailleurs aussi l 'ordi est équipé de bluetouf,wifi, possibilité puce gsm , mais j'ai pas tout compris pour installer.

encore merci
Bonsoir Florentdu19,

Alors la commande ffado-diag montre que ton port firewire ( FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 ) est bien monté au niveau du bios, d'aute part, les modules firewire du noyau ( The new FireWire kernel stack is loaded.) sont bien présents, ça c'est bon.

Le retour de la commande ffado-test est moins probant ... La commande ne détecte que le port firewire de ton ordinateur. Ta carte aurait dû apparaître ... Elle ne semble pas détectée.

Vérifie quand même que ta carte Onyx est bien allumée, et donne le résultat de la commande

Copy to clipboard
lsmod


Le module snd-dice, ( ou snd-bebob ou snd-oxfw, la littérature est un peu floue sur le sujet ... ) devrait apparaître, l'un de ces trois modules devrait être monté pour piloter ta carte.
Bonjour dlb,

Lors du précédent poste , je n'avais pas la carte son a proximité, ce qui explique la non détection de celle-ci ..

j'ai lancer "Cadence" fait un forçage et oh bonheur , la table est apparu !!!
je ne sais pas ou j'ai buggé !

un grand merci !!

Résolu