Cannot load frebob or firewire drivers

13 replies [Last post]
nickyrugg
User offline. Last seen 2 years 12 weeks ago. Offline
Joined: 2009-11-05

Hello I have a Mackie Onyx I'm trying to configure in Jack. When I plug the device in it appears to be recognized "ieee1394: Node added: ID:BUS[0-01:1023]". When I go into Jack and try to switch from alsa to either "firewire" or "freebob" I get the following:

loading driver ..
SSE2 detected
13243805598: (ffado.cpp)[ 92] ffado_streaming_init: libffado 1.999.43 built Sep 17 2009 20:06:09
firewire ERR: Error creating FFADO streaming device
cannot load driver module firewire

Any ideas?

Thanks,

peder
User offline. Last seen 1 week 1 day ago. Offline
Joined: 2007-05-08

I don't have any personal experience with firewire cards but first of all, unless it's a Onyx Mixer, the FFADO support doesn't seem that great (http://www.ffado.org/?q=devicesupport/list&page=1).

And second; shouldn't you select ffado in jack, if that's what you're running?

DrG
User offline. Last seen 2 years 11 weeks ago. Offline
Joined: 2008-01-05

(peder) Jack refers to FFADO as firewire.

Have you checked the permissions of /dev/raw1394? Your user needs to have read/write permission, most distributions don't permit this by default as it can be a security risk, apparently. How you achieve this can depend on which distribution you are running - the best method is to make /dev/raw1394 owned by a group that your user is a member of. You may be able just to chgrp it but on *buntu distributions it's necessary to create a udev rule. I can look mine up if you need it.

nickyrugg
User offline. Last seen 2 years 12 weeks ago. Offline
Joined: 2009-11-05

thanks for the reply "/dev/raw1394 " doesn't exist on my box. Where do I go from here?

Thanks,

roaldz
User offline. Last seen 18 weeks 5 days ago. Offline
Joined: 2008-11-12

It could be in /dev/.static/raw1394

Danni
Danni's picture
User offline. Last seen 11 weeks 3 days ago. Offline
Joined: 2006-07-05

the command

sudo modprobe raw1394

would be my first step if that results in you seeing a /dev/raw1394 device
then you should add the line

raw1394

to the /etc/modules

if I remember correctly.. This forces the raw firewire interface to be loaded at boot.

GMaq
GMaq's picture
User offline. Last seen 1 hour 44 min ago. Offline
Joined: 2007-12-11

Hello,

Have you tried this?

sudo adduser YOURUSERNAME disk

Linux looks at firewire as a hard disk interface primarily, adding yourself to the disk group usually addresses the permissions issue (on Debian anyway).

nickyrugg
User offline. Last seen 2 years 12 weeks ago. Offline
Joined: 2009-11-05

Hi, I tried both but still not working.

kurviak
User offline. Last seen 9 weeks 1 day ago. Offline
Joined: 2009-11-02

did /dev/raw1394 exist in your system ? if not do a modprobe raw1394 to "create" it

nickyrugg
User offline. Last seen 2 years 12 weeks ago. Offline
Joined: 2009-11-05

I tried "sudo modprobe raw1394" it did not create "/dev/raw1394" but did not indicate error either.

Motrax
User offline. Last seen 1 year 27 weeks ago. Offline
Joined: 2009-05-11

have you tried this on root: "chmod 777 /dev/raw1394" ?

peder
User offline. Last seen 1 week 1 day ago. Offline
Joined: 2007-05-08

nickyrugg, you seriously need to get on IRC to get help with this.

Is it an Onyx Mixer or something else? As I stated in my first reply FFADO doesn't seem to support any other Mackie stuff but that one.

nickyrugg
User offline. Last seen 2 years 12 weeks ago. Offline
Joined: 2009-11-05

Yes it is the Onyx Mixer, I'll try to jump on irc later.

Thanks

midiholic
User offline. Last seen 1 year 50 weeks ago. Offline
Joined: 2010-02-19

I've got the same problem and after several tries it solved
try this
type in terminal
$ ffado-dbus-server

-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 1.999.43
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

01594487264: (ffado-dbus-server.cpp)[ 269] main: Discovering devices...
01594540667: Debug (devicemanager.cpp)[ 332] discover: Starting discovery...
01594540796: Debug (devicemanager.cpp)[ 639] discover: Discovery finished...
01594540810: Debug (devicemanager.cpp)[1184] showDeviceInfo: ===== Device Manager =====
01594540836: Debug (Element.cpp)[ 121] show: Element DeviceManager
01594540849: Debug (devicemanager.cpp)[1192] showDeviceInfo: --- IEEE1394 Service 0 ---
Iso handler info:
Dumping IsoHandlerManager Stream handler information...
State: 2
01594540902: Debug (devicemanager.cpp)[1192] showDeviceInfo: --- IEEE1394 Service 1 ---
Iso handler info:
Dumping IsoHandlerManager Stream handler information...
State: 2
01594540990: (ffado-dbus-server.cpp)[ 312] main: Starting DBUS service...
01594557429: (ffado-dbus-server.cpp)[ 328] main: Running... (press ctrl-c to stop & exit)
01594557483: Debug (ffado-dbus-server.cpp)[ 331] main: dispatching...

------
Watch out at this line:
01594540849: Debug (devicemanager.cpp)[1192] showDeviceInfo: --- IEEE1394 Service 0 ---
Iso handler info:
Dumping IsoHandlerManager Stream handler information...
State: 2
01594540902: Debug (devicemanager.cpp)[1192] showDeviceInfo: --- IEEE1394 Service 1 ---

Service 0 means hw:0
Service 1 means hw:1

-----
just change your jackd command into this....
jackd -R -P70 -dfirewire -dhw:1 -r44100 -p128 -n3

where -dhw:1 is to tell jackd where is your firewire port
you can change into -dhw:0

or

go to qjackctl
setup ---> write into interface label hw:0 or hw:1 or hw:2 whatever....

goodluck.....