Sorry, I haven't read your message completely and I thought it was a reiteration of Tim's original question. I think Tim will be alrite with the alsa-base.conf solution, but your problem is trickier.
Andras
2011/9/5 Ingo ingo@miamiwave.com
That's what I was thinking, too. But it doesn't work like this. The devices I create with udev show up in /dev. But the devices used by /etc/modprobe.d/alsa-base.conf :
snd-emu10k1 snd_intel8x0
do not show up in /dev.
That means the sound device names are created somewhere else. Names that I create with udev in /dev seem to be ignored by modprobe.d/alsa-base.conf.
So the question is where are these sound card IDs generated and how could I create such an ID with udev?
Ingo
On Sun, Sep 4, 2011 at 14:33, Ingo ingo@miamiwave.com wrote: Has anybody had any success with udev?
I need to use oss and have tried to create a udev.rule to connect two identical usb midi interfaces and identify them by the usb port.
I ended up creating the devices in /dev/ and /dev/snd/ and named them /dev/midi1, /dev/midi2 and/or /dev/snd/midiC1D0, /dev/snd/C2D0.
They show up correctly in the folder /dev/ but I don't know how to assign them to anything alsa-base.conf can use.
The first one that gets plugged in is always midi1 no matter where I plug
it
in. If I plug only one of them into the second usb port it will create midi1 and midi2. alsa-base.conf cannot seem to use the udev rules. It looks like something is assigning the soundcard numbers before or
after
udev.
Any ideas?
Ingo
More than udev it might be a modprobe thing. I have these rules in /etc/modprobe.d/alsa-base.conf :
options snd-emu10k1 index=0 options snd_intel8x0 index=1
...which make my Soundblaster card always be hw:0 and the motherboard
sound
card be hw:1.
Andras