Re: [FFADO-user] [Alsa-user] edirol fa-66

[Stefan R. <st...@s5...>]

On Jan 26 Stefan Thomas wrote:
> Dear Stefan,
> I did, as You suggested.
> Should I have also typed modprobe firewire-ohci quirks=81 (not 17)?

Both 81 and 17 should have the same effect as they contain bits 1 and 16.
Bit 64 is not used.

> After dmseg I've got indeed a lot messages about firewire.

Good.

> In /sys/bus/firewire/devices/ is a folder, named fw0, but in this folder
> seems nothing named fa-66.

Bad.  I had expected that you got two further directories from the FA-66,
named
	/sys/bus/firewire/devices/fw1/
	/sys/bus/firewire/devices/fw1.0/
and some of the attribute files in them, which can be conveniently read
e.g. by
	grep . /sys/bus/firewire/devices/fw1*/*
would hint that this is some sort of AV device --- perhaps only through
certain numeric values, but more likely also with some human-readable
labels which identify the vendor and model of the device.

If you do "grep . /sys/bus/firewire/devices/fw0/*" instead, you get among
else a vendor_name "Linux Firewire" and a model_name "Juju", which is all
just from the controller itself (because fw0 is the so-called local node;
fw1 would typically be a remote node if any had been successfully
discovered by the kernel).

> After ffado-test ListDevices I get
> === 1394 PORT 0 ===
>   Node id  GUID                  VendorId     ModelId   Vendor - Model
>    0       0x08004603035126ed  0x00080046  0x00000000   Linux Firewire -
> no message buffer overruns

This too should show another node besides the Linux node.

Perhaps the dmesg log contains some hints what went wrong.  Could you post
it or copy it to a site like pastebin.com and post the link?
-- 
Stefan Richter
-=====-===-- ---= ==-=-
http://arcgraph.de/sr/