Results 1 to 2 of 2

Thread: Firewire Audio Driver, M-audio Firewire 410, Firewire Utilities

  1. #1

    Default Firewire Audio Driver, M-audio Firewire 410, Firewire Utilities

    I'm running a current version of Tumbleweed and would like to use my M-audio Firewire 410 audio interface with it.
    I realize that it's an older interface, but when it's working it does what I need it to do, and it does it rather well. For these reasons I'd like to keep using it.
    The problem that I have is that the device requires a bit of a kick-start before the current drivers will work. If I can get some information on implementing this kick start then all will be good.

    The box has BeBob hardware and requires that the firmware be loaded at boot time. Originally it required that the firmware be uploaded every time, but the last version of the M-audio driver for Windows allowed the firmware to be stored on the device even while powered off, but it still needs to have a signal sent to it at boot time to get it to load that firmware into the operational memory. I should mention that if I boot the machine into Windows the box works just fine and if I reboot from Windows into Tumbleweed without powering off the machine then the box also works in Tumbleweed, so I know that the hardware works with the current Linux drivers.

    Here is the relevant page from the ffado mailing lists that describes the kick-start that I need to do.
    https://sourceforge.net/p/ffado/mail...sage/30807938/
    In particular, what I need to accomplish is given as follows:
    2. Send magic bytes to device with jujuutils
    $ ./firewire-request /dev/fw1 write 0xFFFFC8021000 010000000000110100000000
    I did a lot of searching and it would appear that jujuutils was renamed to linux-firewire-utils as per this link, but that package is not available on OpenSUSE.
    https://github.com/cladisch/linux-firewire-utils

    It's somewhat frustrating because this one small detail seems to be all that prevents this device from working.
    Is there another way to send these magic bytes to the unit? As I mentioned before, the driver seems to work when the firmware is in place.

    These are nice little audio boxes that have great sound and are quite inexpensive these days because of their age. At present I'm not using it for real-time audio work in Linux, but I do have some studio monitor speakers connected to it for high quality sound.

    Any suggestions are welcome. Any working suggestions are even better!
    Thanks

  2. #2

    Default Re: Firewire Audio Driver, M-audio Firewire 410, Firewire Utilities

    I think I have made some progress of a sort on this issue.
    It would seem that newer versions of ALSA support the M-Audio Firewire 410. I came across this posting that doesn't exactly describe my problem, but does indicate that the support should be there.

    https://github.com/takaswie/snd-fire...rove/issues/21

    There's also this that confirms the support.
    http://mailman.alsa-project.org/pipe...il/075885.html

    and this.
    https://ieee1394.wiki.kernel.org/ind...3.x#Linux_3.16

    A long time ago I wrote a bit of code, and these days I like to mess around with my Linux machines, but solving this problem is getting a bit too complex for me.
    If I understand the above posting correctly then things should work for me as I'm running Tumbleweed and that should be up to date with drivers. But perhaps I'm missing something.

    This is the output of 'dmesg | fw' after bootup.

    [ 3.932162] firewire_core 0000:03:00.0: created device fw0: GUID 78563412000000f5, S800
    [ 7.161073] firewire_core 0000:03:00.0: created device fw1: GUID 000d6c01109dc17a, S400
    [ 9.867909] snd-bebob fw1.0: Failed to send a cue to load firmware
    [ 9.867929] snd-bebob: probe of fw1.0 failed with error -5

    I think fw0 is the Firewire controller card and fw1 is the M-Audio 410.

    Perhaps someone with a better understanding of the current audio drivers can help me out here. Has the support listed in the above links just not made it into the current kernel yet? The output of dmesg seems to indicate that it is configured to send the cue to load the firmware and that should get the unit working, but it was unsuccessful for some reason.

    Any suggestions for troubleshooting?

    Thanks in advance.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •