Sorry about that guys, should have made the script more robust - looks like the kernel source & module directories change every update
Paste this into a .sh file and it will do the trick - I just updated mine too.
Here is the compile output. It’s normal for it to complain that modules are in use - it won’t affect anything. After a reboot you should see the new modules loaded…
linux-source-3.13.0/samples/seccomp/bpf-direct.c
linux-source-3.13.0/samples/seccomp/Makefile
(Stripping trailing CRs from patch; use --binary to disable.)
patching file quirks-table.h
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 386 with fuzz 1.
CC [M] /usr/src/linux-source-3.13.0/sound/usb/card.o
LD [M] /usr/src/linux-source-3.13.0/sound/usb/snd-usb-audio.o
LD [M] /usr/src/linux-source-3.13.0/sound/usb/snd-usbmidi-lib.o
Building modules, stage 2.
MODPOST 8 modules
LD [M] /usr/src/linux-source-3.13.0/sound/usb/snd-usb-audio.ko
LD [M] /usr/src/linux-source-3.13.0/sound/usb/snd-usbmidi-lib.ko
rmmod: ERROR: Module snd_usb_audio is in use
building file list ... done
./
snd-usb-audio.ko
snd-usbmidi-lib.ko
sent 293,691 bytes received 57 bytes 587,496.00 bytes/sec
total size is 574,864 speedup is 1.96
Well, doesn’t work anymore. I don’t know what happened. Suddenly, Ubuntu ask me for a password where it didn’t ask for it before (like restart, mounting partitions). And my UR-22 doesn’t work anymore…
I tried to re-do what I did to make it work, but it doesn’t. I can’t see the UR-22 in Ubuntu settings. Only Dummy Output.
Got it working again. After doing all the steps listed by KgwgK again, I purged ALSA drivers and reinstalled them. So now I can see the UR-22 in the Gnome audio settings.
I bought UR22 recently hoping it will work with ubuntu. I also tried all the steps mentioned above in this thread but still can not see it in the gnome GUI. Does anybody has any new idea?
That’s strange - make sure you’re running the script as root, otherwise the rsync step may have some problems.
I pasted the script here - http://pastebin.com/mVxFZVhY
If you’ve already got a snd-usb-audio driver being loaded, the script won’t be able to uninstall it, so after running it, you will have to reboot, and it should get picked up on the next boot.
Can you paste the script output here to help debug? By the way, the patch is in the upstream kernel, but Ubuntu hasn’t picked it up yet
So after some effort I managed to push my UR22 to work. It is not the smartest solution but it works at the time. I noticed that I boot to 3.13.0-40 kernel version and the patch refers to 3.13.0-32…So i had to find the way to boot to older kernel version. Now it works fine. I am still interested how to make it work with 3.13.0-40 though…
The script here http://pastebin.com/mVxFZVhY should do the trick if you run it as root. I generalized it so it always pulls the latest kernel. The source tree it downloads may be labeled differently than the ubuntu build number, but we’re not rebuilding the entire kernel for this, only the snd-usb-audio driver, and it’ll point to the official ubuntu headers so the kernel version ends up matching up after all is said and done.
I have a Steinberg UR44 and tried the same procedure in Ubuntu 14.10. When that didn’t help, I edited the quirks-table.h in analogy to KgwgK’s patch file and thereby duplicated the UR22 entry, replacing the idProduct for 0x150e (which I took from lsusb). Then I repeated the steps of KgwgK’s bash script (make, disabling snd-usb-audio, rsync, enabling snd-usb-audio). Unfortunately, even after reboot the device is still not listed as a sound input device in Settings > Sound. Any idea what went wrong?
I have a Steinberg UR44 and tried the same procedure in Ubuntu 14.10. When that didn’t help, I edited the quirks-table.h in analogy to KgwgK’s patch file and thereby duplicated the UR22 entry, replacing the idProduct for 0x150e (which I took from lsusb). Then I repeated the steps of KgwgK’s bash script (make, disabling snd-usb-audio, rsync, enabling snd-usb-audio). Unfortunately, even after reboot the device is still not listed as a sound input device in Settings > Sound. Any idea what went wrong?
However, apparently it did indeed work but the device is only recognized if it’s connected at system start. Reconnecting it later (including off/on) is of no use. Another caveat is that in Settings > Audio it’s only listed as an output device while, luckily, Audacity lists it as both input and output. A fast test showed that with a six-track recording the microphone input in channel 4 is detected correctly.