kane@xanadu:~$ lsusb | grep EDIROL
Bus 001 Device 005: ID 0582:007d Roland Corp. EDIROL UA-101
This option is in sound.conf in /etc/modprobe.d, which if understood correctly set explicitly the order of the internal HDA and the EDIROL:
kane@xanadu:/etc/modprobe.d$ cat sound.conf
options snd cards_limit=2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel index=0
alias snd-card-1 snd-ua101
alias sound-slot-1 snd-ua101
options snd-ua101 index=1 vid=0x0582 pid=0x007d
So if I'm not mistaken with "vid" and "pid" you can define exactly the device you want, as in the snd-usb-audio, at http://alsa.opensrc.org/index.php/MultipleUSBAudioDevices
So, in my case it doesn't seem to work. After I commented it out, the module seems to load:
kane@xanadu:/etc/modprobe.d$ lsmod | grep snd
snd_hda_codec_si3054 3440 1
snd_hda_codec_realtek 217980 1
snd_hda_intel 22107 2
snd_usb_audio 86704 1
snd_hda_codec 87552 3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel
snd_ua101 13972 0
snd_pcm 71475 5 snd_hda_codec_si3054,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_ua101
snd_hwdep 5040 2 snd_usb_audio,snd_hda_codec
snd_usbmidi_lib 17413 2 snd_usb_audio,snd_ua101
snd_seq_midi 4588 0
snd_rawmidi 17783 2 snd_usbmidi_lib,snd_seq_midi
snd_seq_midi_event 6047 1 snd_seq_midi
snd_seq 47174 2 snd_seq_midi,snd_seq_midi_event
snd_timer 19067 2 snd_pcm,snd_seq
snd_seq_device 5744 3 snd_seq_midi,snd_rawmidi,snd_seq
snd 49006 19 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_ua101,snd_pcm,snd_hwdep,snd_usbmidi_lib,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 880 1 snd
snd_page_alloc 7120 2 snd_hda_intel,snd_pcm
and I finally have sound! Jack detects all the inputs and outputs and the card is working fine.
EXCEPT that after some time and quite randomly (can be 1hr or 1min) the computer loses connection to the PC (the USB light on the card goes off), something which never happens in windows for example, so I guess it's a driver issue...
Any ideas about that?
Regards,
Akis
On 22 September 2010 13:10, Arxontis Politis <deadflagblue@xxxxxxxxx> wrote:
Hm, yes that makes sense, that should be the alsa-base (or alsa-base.conf) file in /etc/modprobe.d ...I'll check it when I'm back from work, thanx a lot...On 22 September 2010 12:51, John Haxby <jch@xxxxxxxxxxxxxxx> wrote:
On 22/09/10 09:46, Arxontis Politis wrote:I think you have a bad modprobe config file somewhere. I forget where
>
> ---------------------------------------------------------------
> kane@xanadu:~/Music$ dmesg | grep snd
> [ 34.098749] snd_ua101: Unknown parameter `vid'
> [ 34.107709] snd_ua101: Unknown parameter `vid'
> [ 34.164993] snd_ua101: Unknown parameter `vid'
> [ 34.368494] usbcore: registered new interface driver snd-usb-audio
> --------------------------------------------------------------
>
>
Ubuntu keeps its modprobe options, but I suspect that somewhere you have
a file that says something like
options snd_ua101 vid=xyzzy
instead of
oprions snd_ua101 id=xyzzy
(I don't know what the id should be, but the parameter name is "id" not
"vid")
jch
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
