Re: [FFADO-user] [I'm a user and need support] QJACKCTL not showing interface options

[Jonathan W. <jw...@ju...>]

Hi Marc

Please subscribe to ffado-user to prevent your replies being delayed by
moderation.

On Fri, Mar 24, 2017 at 03:11:37PM +0000, Marc Cayouette wrote:
> I re-installed Ubuntu 16:04 LTD amd64 on my system.

Ok.

> As requested I ran a ffado-diag.   The system responded that I needed to
> install the tool kit which I did.

Ok, that makes sense.

> I then re-ran the ffado-diag and this is what I obtained.
>
> 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
> :

The top part of the output appears to be missing.  Could you run ffado-diag
again and ensure the full output is captured?  There is a chance that the
top section went beyond your terminal's scrollback storage.  The easiest way
to avoid this is to redirect the output to a file and then put that file's
content into a post.  For example:

  ffado-diag >& /tmp/ffado-diag.log

You will find the output in the /tmp/ffado-diag.log file, which you can then
cut and paste into an email.

>  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

Down the track you will almost certainly want to install a so-called
"preempt" or "low-latency" kernel, which is available through the Ubuntu
package manager.  This is required to obtain reliable operation with ffado
due to its soft realtime requirements.  We don't need to pursue this right
now since we're just trying to establish a basic system.

>  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]

JMicron firewire interfaces have been known to give trouble in the past. 
Again, this is not an issue right now but might be later depending on how
you use the system.

> CPU MHz:               2797.692
> CPU max MHz:           3200.0000
> CPU min MHz:           1600.0000

Having the CPU speed change randomly can cause issues when jackd/ffado is
running.  When we get this far it would be advantageous for you to disable
power saving and set the CPU to its fastest speed.

>  IRQ   18: PID:  None, count:       [1, 0, 0, 0], Sched None (priority None), drivers: ['18-fasteoi   firewire_ohci']

This is good: the firewire interrupt is not shared with anything else.

> 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"

We need to determine that your firewire bus is working and that the PC can
see your FA-66.  The output from the start of ffado-diag will help us with
this.  You could also run

  ffado-test ListDevices

and see if the FA-66 is reported.  If it is, try running 

  jackd -R -P70 -dfirewire -p512 -n3 -v3

and post the resulting output.  This may indicate the general problem which
is preventing jackd (the Jack server) starting with the "firewire" backend. 
In case you're wondering about how all this fits together, the "firewire"
jack backend uses FFADO to do its job.

Regards
  jonathan