Mbox 2 Pro (Factory)

Support Status: 
Unknown
Manufacturer: 
Digidesign

Comments

I own a M-Audio / AVID MBox Pro:

http://www.avid.com/US/products/Mbox-Pro#TechSpecs

- kernel 3.7.10
- FFADO 2.1.0 and current devel sources
[ 2141.273761] firewire_core 0000:04:00.0: phy config: new root=ffc1, gap_count=5
[ 2149.502049] firewire_core 0000:04:00.0: phy config: new root=ffc1, gap_count=5
[ 2151.808243] firewire_core 0000:04:00.0: created device fw1: GUID 00a07e0401000000, S400

which seems recognized but not accessible/working under FFADO so far.
=== 1394 PORT 0 ===
Node id GUID VendorId ModelId Vendor - Model
0 0x00a07e0401000000 0x0000A07E 0x00000004 Avid - Mbox Pro

gongo ~ # ffado-test Discover
-----------------------------------------------
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Version: 2.1.9999-Unversioned directory
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

02178964635: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
02178964725: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
02178964749: Error (bebob_avdevice.cpp)[ 96] probe: Number of channels command failed
02179018039: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
02179018114: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
02179089190: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
02179089225: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
02179089235: Error (avc_avdevice.cpp)[ 89] probe: Subunit info command failed
no message buffer overruns

If i can help to test, investigate or anything other feel free to contact me.

(I tried to add it to the device list but got ac "access denied" here?)

best regards,

Niels.
nd@syndicat.com

---
Niels Dettenbach
Syndicat
Internet & Open Source
http://www.syndicat.com

Yes, that would be correct. At this point in time we do not know how to communicate with these devices. Since the protocol is proprietary, we would require information from the manufacturer or the results from an extensive protocol analysis effort in order to support these.