[Expired for alsa-tools (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-tools (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to alsa-tools in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1245096

Title:
  usx2yloader fails - wrong path to firmware

Status in alsa-tools package in Ubuntu:
  Expired

Bug description:
  I'm having trouble with a tascam US-122. In raring, it worked fine,
  but on upgrading to saucy, I ran into problems. First of all, the
  firmware is no longer available, since medibuntu no longer exists. I
  installed the package from alsa-project.org manually though, and made
  a symlink from /usr/local/share/alsa/firmware/ to
  /usr/share/alsa/firmware/, since that's where the old package
  installed the files.

  Then when I plug the device in, it seems to load the initial firmware
  just fine - the syslog shows that it detected the 2nd device and ran
  the tascam_fpga script. However, the usx2yloader program fails.

  When I run it manually, (usx2yloader -c 1) I get the following error
  message: usx2yloader: cannot open the index file
  /lib/firmware/usx2yloader/us122.conf

  Of course, that's not where the us122.conf file is located, but that
  path seems hardcoded in usx2yloader. When I made a symlink from sudo
  ln -s /usr/local/share/alsa/firmware/usx2yloader/ to /lib/firmware/,
  it seems to load the firmware just fine.

  I think the issue is with the path hardcoded into the utility. it
  should be changed to
  /usr/local/share/alsa/firmware/usx2yloader/us122.conf, since that's
  where the old package expected the file to be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1245096/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to     : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

Reply via email to