|
From: Stefan R. <st...@s5...> - 2010-07-13 10:13:32
|
Biby wrote: >> On Monday 12 July 2010 20:30:07 Aaron Peart wrote: >>> I've been running ubuntu 10.04 and i just bought an edirol >>> FA-101 and I'm >>> having some problems getting jack to run. My >>> permissions are set up >>> properly, i've got my username in the audio >>> and video group, and jack is >>> set to use the firewire driver. >>> > audio/video/ and disk? Never add a normal user account to group disk. The block device files of all HDDs are normally owned by group disk, and any member of that group can overwrite disks with garbage. [...] > Finally what i'm doing for Edirol FA 101 working: in a console > > sudo chmod 777 /dev/raw1394 > > Some uses "sudo chmod 666 /dev/raw1394" This is not necessary if you simply add an udev rule for raw1394 that sets proper group ownership every time when /dev/raw1394 is created. This missing of a default raw1394 udev rule is a shortcoming of Ubuntu (and increasingly also of other distributions). It is going to be resolved in a future Ubuntu release when the newer firewire-core and firewire-ohci kernel drivers replace raw1394, ieee1394, ohci1394. https://help.ubuntu.com/community/Firewire https://help.ubuntu.com/community/FireWire https://bugs.launchpad.net/ubuntu/+source/kino/+bug/6290 https://ieee1394.wiki.kernel.org/index.php/FAQ#How_to_get_access_to_raw1394_as_unprivileged_user.3F Another solution is not to use Ubuntu if you want to use FireWire, since there is no Ubuntu release in which FireWire works out of the box. Alas I do not know which distributions (still) have proper udev rules. A while ago, the Ubuntu udev maintainer pushed his faulty ruleset to mainline udev and thus destroyed FireWire usability also on other distributions. This mistake could not be prevented in time because neither the Ubuntu udev maintainer nor upstream udev maintainer bothered to consult with FireWire driver/ library developers when they created that mess. -- Stefan Richter -=====-==-=- -=== -==-= http://arcgraph.de/sr/ |