From: Stefan R. <st...@s5...> - 2011-12-26 14:17:54
|
On Dec 26 ROY LEITH wrote: > Thank you, Stefan, > > That was a great help. Well, almost. See below. :-) > >________________________________ > > From: Stefan Richter <st...@s5...> > >To: r.m...@bt... > > > >On Dec 25 r.m...@bt... wrote: > > > >> With Ubuntu Studio 11.10, which, now, uses the XFCE window manager, I have > >> libraw1394-11 2.0.7.1 installed by default. > >> > >> I have the following port installed which has worked well, before. > >> > >> I have installed the Ubuntu Studio > >> Control which seems to work as well as in the past. > > > >So what do you get from "ffado-test ListDevices", run as the same user who > >runs jackd and from "ls -l /dev/fw*" while the Saffire is connected and > >powered? > > > roy@Laptop:~$ ffado-test ListDevices > Cannot create thread 1 Operation not permitted Perhaps there is indeed a permission problem. But if there really is one, it is not actually related to the firewire device files. > ----------------------------------------------- > FFADO test and diagnostic utility... > ----------------------------------------------- > > === 1394 PORT 0 === > Node id GUID VendorId ModelId Vendor - Model > 0 0x00130e0100060f3e 0x0000130E 0x00000006 Focusrite - Pro10IO See, the normal user account is able to access the Saffire just fine. > ERROR: messagebuffer not initialized: 00616777965: Error (configrom.cpp)[ 150] initialize: Could not parse config rom of node 1 on port 0 This is normal. Access to the "local node's" file (the /dev/fw* which belongs to the IEEE 1394 controller chip, not to any external 1394 node) is denied per default, and this is OK for FFADO except for some irritating error messages like the above one. > > [sudo] password for roy: > ----------------------------------------------- > FFADO test and diagnostic utility... > ----------------------------------------------- > > === 1394 PORT 0 === > Node id GUID VendorId ModelId Vendor - Model > 0 0x0090f5000048a072 0x000090F5 0x00000000 Linux Firewire - > 1 0x00130e0100060f3e 0x0000130E 0x00000006 Focusrite - Pro10IO > no message buffer overruns > > _____So, there is a permissions problem. No, FFADO does not need to have access to "Linux Firewire - ", only to "Focusrite - Pro10IO". > The rules file you noted is in place in /lib/udev/rules.d and I am a member of the audio group. (BTW, the file includes interesting info about my Mackie Onyx which is working well on a much older version of Ubuntu Studio atm.) > > roy@Laptop:~$ ls -l /dev/fw* > crw------- 1 root root 251, 0 2011-12-26 11:07 /dev/fw0 > crw-rw----+ 1 root audio 251, 1 2011-12-26 11:12 /dev/fw1 > > ______So, it is the first port which has the problem. These ownerships and permissions are fine. > 60-raw1394.rules: > > #This is a file for Ubuntu Studio Controls to write firewire access rules to > #it's advised that you do not manually edit this file. > > KERNEL=="raw1394", GROUP="audio" > > This is in /etc/udev/rules.d and is, obviously, out of date because raw1394 is no longer used for FFADO. Yes, you can leave this file there; it is only of importance with older kernels which still have the raw1394 driver. > The question is now what the KERNEL rule for port fw0 should be and where should it be put? There is none necessary. Please run $ jackd -dfirewire -v3 in a terminal window and post the result. -- Stefan Richter -=====-==-== ==-- ==-=- http://arcgraph.de/sr/ |