Ok, so I'll start with replying to the last post on my previous thread here.
Hold on that till I get back to the studio. These steps are probably where I should have started though... read on to get amused with how far I went chasing this last night.raboof wrote: When you insert the device, does anything show up in /var/log/messages? When it is connected, what does 'lsusb' output? What do 'aplay -l' and (as slowpick mentions) 'cat /proc/asound/cards' tell you?
Good point. I used to have two other Motu 8x8 interfaces that I was trying to get working in linux a few years ago, a parallel MTPAV and MIDI express XT. I just sold them a year back in exchange for one USB MTPAV. So my methodology for getting the USB MTPAV is from legacy experience.raboof wrote:
I said:How do you know? http://www.alsa-project.org/main/index. ... dule-mtpav doesn't mention anything about usb, might be it only supports PCI.The alsa driver is MTPAV.ko
I suppose it doesnt help that there seems to be a good bit of outdated info on the alsa-project site, especially on the page you refer to. Lots of legacy info on there so it didn't seem too odd that the USB version wasn't mentioned.
You're probably right that I'm making an incorrect assumption.
After discussing this a bit on the other thread I went home yesterday, determined to try to get a little further with getting the MTPAV USB working. Here are my notes:
Started with a fresh Ubuntu Studio 10.04 install, no additional software, just the base install.
apt-get installed linux-backports-modules-alsa for the kernel installed (I believe it was 2.6.32-22)
at the root of the file system I did a locate mtpav and found several instances located in:
great so no need to compile anything (still thinking mtpav.ko is what I'm after)
sudo modprobe snd_mtpav
FATAL: Error inserting snd_mtpav (/lib/modules/<kernel number>/ubuntu/sound/alsa-driver/drivers/snd-mtpav.ko): No such device
I thought this was odd, the mtpav.ko file was exactly at the path given in the "FATAL" error.
So I opened one terminal to display the syslog with tail -f /var/log/syslog, then opened another terminal window to modprobe snd_mtpav again.
the syslog showed:
ALSA sound/drivers/mtpav.c:590: MTVAP port 0x378 is busy
snd_mtpav: probe of snd_mtpav failed with error -16
which as far as I can interpret was telling me that either the device isn't attached, or the port 0x378 which indeed is the ioport the MTPAV is connected to (verified in bios) is busy with something else.
I then unloaded a few modules that were not in use:
sudo modprobe -r ppdev
sudo modprobe -r lp
sudo modprobe -r parport_pc
sudo modprobe -r parport
bingo, I could then modprobe snd-mtpav successfully.
cat /proc/interrupts confirmed:
Motu MidiTimePiece on parallel port irq: 7 ioport: 0x378
I then opened Qjackctl, confirmed I was using the "raw" MIDI driver (seems illogical to set this to none, please explain that... maybe later?)
I started the JACK server, went to connections, MIDItab and holy crap I saw MOTU MTPAV Parallel port 1, all the way through port 8. I thought it was odd that it said "parallel" for every port but still figured I was in luck!! Ran out to have a victory smoke and came back in to realize that was where my success ended. I was not able to get any MIDI IO from any synth connected to my MTPAV or to any synth fromsay renoise (my sequencer of choice , the MTPAVs LEDs confirmed this. No activity.
I rebooted, once again unloaded ppdev, lp, parport_pc, parport and pp5-1-doodoo. the later gave me an error but I expected that.
Once again did a modprobe snd-mtpav and seemed to have success loading the driver, connections appear in jack's, Patchage, Renoise, etc but no activity.
I then realized that even with the MTPAV turned OFF I was seeing these connections... leading me to see the clouds part enough for me to realize I was chasing down a rabbit hole and came to the same question you brought up about the mtpav alsa driver being the "correct" driver to use for the USB MTPAV.
Then I started questioning my selling the LPT/parallel Motus... Frustrated, I called it a night and went to bed.
So. Back to your question. "How do I know"? I don't. I now am clueless as to what driver I need to load in order to get the MTPAV USB working.
I will try tonight loading the trusty ubuntu studio 8.04, as far as my research went, since karmic ubuntu has shipped with mtpav already compiled into the kernel - but maybe it isn't mtpav.ko that I want after all.