Menu
▾
▴
Re: [FFADO-user] [I'm a user and need support] QJACKCTL not showing interface options
|
From: Marc C. <mca...@st...> - 2017-03-24 15:26:57
|
I re-installed Ubuntu 16:04 LTD amd64 on my system.
As requested I ran a ffado-diag. The system responded that I needed to install the tool kit which I did. I then re-ran the ffado-diag and this is what I obtained.
I also changed the driver option from alsa to firewire. When I tried to start the Jack server it returned an error "D-BUS: Jack server could not be started. Sorry"
Here is what I obtained from the ffado-diag:
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 ............ Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found
flags ........... Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found
Prerequisites (static at compile-time)...
gcc ............... gcc (Ubuntu 5.2.1-27ubuntu1) 5.2.1 20151129
g++ ............... g++ (Ubuntu 5.2.1-27ubuntu1) 5.2.1 20151129
PyQt4 (by pyuic4) . Python User Interface Compiler 4.11.4 for Qt version 4.8.6
jackd ............. sh: 1: jackd: not found
path ............
flags ........... Package jack was not found in the pkg-config search path.
libraw1394 ........ 2.1.1
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.40.1
flags ........... -std=c++11 -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.10.4
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1
uname -a...
Linux marcc-desktop 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Hardware...
Host controllers:
03:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (prog-if 10 [OHCI])
Subsystem: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fe403000 (32-bit, non-prefetchable) [size=2K]
Region 1: Memory at fe402000 (32-bit, non-prefetchable) [size=128]
Region 4: Memory at fe401000 (32-bit, non-prefetchable) [size=128]
Region 5: Memory at fe400000 (32-bit, non-prefetchable) [size=128]
Capabilities: <access denied>
Kernel driver in use: firewire_ohci
Kernel modules: firewire_ohci
CPU info:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Model name: Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz
Stepping: 7
CPU MHz: 2797.692
CPU max MHz: 3200.0000
CPU min MHz: 1600.0000
BogoMIPS: 5786.95
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
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 aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx lahf_lm epb tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [17, 0, 0, 0], Sched None (priority None), drivers: ['2-edge timer']
IRQ 1: PID: None, count: [2, 0, 0, 0], Sched None (priority None), drivers: ['1-edge i8042']
IRQ 5: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['5-edge parport0']
IRQ 8: PID: None, count: [1, 0, 0, 0], Sched None (priority None), drivers: ['8-edge rtc0']
IRQ 9: PID: None, count: [4, 0, 0, 0], Sched None (priority None), drivers: ['9-fasteoi acpi']
IRQ 12: PID: None, count: [4, 0, 0, 0], Sched None (priority None), drivers: ['12-edge i8042']
IRQ 16: PID: None, count: [27, 0, 0, 0], Sched None (priority None), drivers: ['16-fasteoi ehci_hcd:usb1']
IRQ 18: PID: None, count: [1, 0, 0, 0], Sched None (priority None), drivers: ['18-fasteoi firewire_ohci']
IRQ 23: PID: None, count: [1358, 0, 0, 9523], Sched None (priority None), drivers: ['23-fasteoi ehci_hcd:usb2']
IRQ 24: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['458752-edge PCIe PME']
IRQ 25: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['462848-edge PCIe PME']
IRQ 26: PID: None, count: [47, 0, 217, 0], Sched None (priority None), drivers: ['409600-edge eno1']
IRQ 27: PID: None, count: [6365, 0, 9722, 0], Sched None (priority None), drivers: ['512000-edge ahci']
IRQ 28: PID: None, count: [267, 1798, 0, 0], Sched None (priority None), drivers: ['32768-edge i915']
IRQ 29: PID: None, count: [12, 0, 0, 0], Sched None (priority None), drivers: ['360448-edge mei_me']
IRQ 30: PID: None, count: [653, 83, 0, 0], Sched None (priority None), drivers: ['442368-edge snd_hda_intel:card0']
Software Interrupts:
--------------------
=== REPORT ===
FireWire kernel drivers:
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).
marcc@marcc-desktop:~$
-----Original Message-----
From: Jonathan Woithe [mailto:jw...@ju...]
Sent: March-22-17 10:02 PM
To: Marc Cayouette <mca...@st...>
Cc: ffa...@li...
Subject: Re: [FFADO-user] [I'm a user and need support] QJACKCTL not showing interface options
Hi Marc
Your message has been forwarded to the ffado-user mailing list for feedback.
Please subscribe to this list to ensure your communication is not delayed by moderation. Instructions describing the subscription process are available on our website in the "Contact" section.
On Wed, Mar 22, 2017 at 09:59:42AM -0700, mca...@st... wrote:
> I am a new Linux user. I have installed Ubuntu 16:04LTS many times on my
> system hoping to get my Edirol FA-66 to work. When I open QJACKCTL in
> setup, I do not get a option for interface selection. I tried installing
> Ubuntu Studio yet with same problem arising - no interface selection.
What interface options do you see in qjackctl? The FA-66 will not be mentioned by name. Instead you will want to select the "firewire" option.
> I tried install the 32 bit version of Ubuntu - same problem.
Whether you run 32-bit or 64-bit won't matter. The jackd/ffado software combination works fine on both.
> I tried install ffado (with my limited Linux knowledge) yet it did not
> seem to rectify my problem.
Ubuntu Studio is probably the best distribution to use when getting started with audio and video tasks under Linux since it comes with most things configured and ready to use. It includes ffado so you would have no need to install it yourself.
I am not sure whether plain Ubuntu installs ffado by default. I suspect it does not, in which case you need to use the Ubuntu package manager to install it for you. This is not a difficult task, in and of itself, but there would be other adjustments you'll need to do down the track to obtain a smoothly running system. As a result, of the distributions mentioned above I would suggest running with Ubuntu Studio.
> I have tried another distro of Linux for audio - but cannot see the
> Edirol FA-66.
There are other audio-focused distros around besides Ubuntu Studio and these should be equally suitable.
> I am not sure if this is a firewire issue however any assistance would
> be greatly appreciated.
In the first instance the problem may be a case of looking for "FA-66" in qjackctl rather than "firewire". Look into this and see if that is your issue.
Failing that we can do some simple diagnostics on your system. With the
FA-66 plugged in to the firewire bus and turned on, run
ffado-diag
and post the results. This will give us an overview of how your system is set up, and will also allow us to confirm that your FA-66 is visible to the system. We can then take things from there.
Regards
jonathan
|
