Confirming this bug, and the solution to getting the card driver to properly load being as documented above. I have a different interface (TASCAM US-122L) but the same exact issues and errors. Creating ~/.pulse/client.conf with the line "autospawn = no", stopping JACK and issuing a "sudo alsa reload". The only other significant difference is that I'm using a core2 duo machine not an AMD one, with the i386 install of Ubuntu Studio. Since the issue is the same and the diagnostic outputs are identical though, I don't believe this to be relevant.
I will add, however, that any apps I'd started which attempted to use ALSA were stuck in the background and had to be manually killed (identified by the warnings issued by the alsa reload), and then an additional alsa reload worked. I've been documenting my experiences in a reddit thread at http://www.reddit.com/r/WeAreTheMusicMakers/comments/a4861/where_to_start_with_linux_music_apps/ but there's not really more pertinent info, just a little more description. I can post whatever diagnostics people wish, but they're identical to the ones listed above. -- [karmic] Failed to load module "module-alsa-card": initialization failed https://bugs.launchpad.net/bugs/382440 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
