|
From: Jonathan W. <jw...@ju...> - 2017-03-28 22:53:42
|
Hi Marc
On Tue, Mar 28, 2017 at 09:32:29PM +0000, Marc Cayouette wrote:
> Hello Jonathan. I did some reading on redirection in Linux and figured it
> out. I had to use sudo to get it to work.
There's something wrong with your system if that's the case. Every user
should be able to create files in /tmp. The only common reason why this
might not work is if some other user has already created a file of the same
name. If
ffado-diag >& /tmp/ffado-diag.log
does not produce the file "ffado-diag.log" in the /tmp directory then it
seems that there is a problem with your /tmp directory.
Moving on to the ffado-diag output, we see
> /dev/fw* permissions:
> crw------- 1 root root 245, 0 Mar 28 08:30 /dev/fw0
I assume you had your FA-66 plugged in and turned on when you ran
ffado-diag. If not, please repeat after doing this. If you did then this
indicates that the FA-66 was not seen by your system.
Checking your earlier ffado-diag output post, we see
> User IDs:
> uid=1000(marcc) gid=1000(marcc)
> groups=1000(marcc),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),
> 113(lpadmin),128(sambashare)
You definitely need to be a member of the "audio" group if ffado is to work.
As per one of my emails yesterday, please add your "marcc" user to the
"audio" group.
For future reference, when posting log files to the list please use text
format rather than proprietary binary formats. Using text makes it much
easier for people to look at the content and respond to it.
> I have attached my files on ffadoListDevices as well as ffado-diag. It
> appears my FA-66 is not being seen by the system.
Agreed.
> Possibly my interface card is bad? Is ORICO USB 3.0 PCI Express Card Hub
> Controller supported by ffado?
FFADO only supports devices through the firewire bus. The USB devices in
your system are not relevant to FFADO and are in fact completely ignored by
FFADO.
If you are using the firewire bus, possible problems could be a bad firewire
controller (as you suggested), a bad firewire socket (either on the host
controller or the FA-66), a bad firewire cable or even an issue with the
FA-66 itself. We are probably getting ahead of ourselves though. At this
stage the following steps should be taken.
* Add your user to the "audio" group.
* Esure that the FA-66 is connected and plugged in, run ffado-diag as your
user ("marcc", NOT root), and post the resulting output.
> I shall try and get the PKG_CONFIG_PATH directories added today - did some
> investigation on how to add it today however your assistance would be
> appreciated.
As explained in my earlier email today, this should not be necessary for the
moment - you should not need to recompile FFADO. If you do want to pursue
this for your own interest, look for the "-devel" packages corresponding to
the respective libraries (with names resembling jack-devel,
libraw1394-devel, and so on).
Regards
jonathan
|