|
From: Jonathan W. <jw...@ju...> - 2017-03-29 02:00:45
|
Hi Marc On Wed, Mar 29, 2017 at 01:47:43AM +0000, Marc Cayouette wrote: > Here is my last ffado-diag. Thanks for this. In this output we see > /dev/fw* permissions: > crw------- 1 root root 245, 0 Mar 28 19:47 /dev/fw0 > User IDs: > uid=1000(marcc) gid=1000(marcc) > groups=1000(marcc),4(adm),24(cdrom),27(sudo),29(audio),30(dip),46(plugdev), > 113(lpadmin),128(sambashare) The "User IDs" section shows that you're now in the audio group. We will confirm the effect of this later, but it should eliminate the memory lock and realtime scheduling failures when running jackd and give that a much better chance of working. We note, however, that the only /dev/fw* device mentioned is /dev/fw0. This is your firewire card. The lack of a /dev/fw1 indicates that for some reason your system is not seeing the FA-66. Could you please run dmesg | grep fire and post the result? This should show kernel messages related to the firewire bus; in particular, whether the bus is seeing something and just unable to work with it, or if it's completely blind to the bus devices. > I had to use the "~" option. Cannot use the other option - doe not work > without "sudo". What error do you get when using the other option? What happens if you run touch /tmp/foo Does this give an error too? If so, what is it? If it gives an error, what is the output of ls -ld /tmp Regards jonathan |