Mick <michaelkintz...@gmail.com> [11-06-05 14:40]: > On Sunday 05 Jun 2011 04:51:54 meino.cra...@gmx.de wrote: > > > Hi Mick, > > > > I did a > > > > modinfo snd_usb_audio > > > > and git this: > > > > filename: /lib/modules/2.6.39.1/kernel/sound/usb/snd-usb-audio.ko > > license: GPL > > description: USB Audio > > author: Takashi Iwai <ti...@suse.de> > > alias: usb:v*p*d*dc*dsc*dp*ic01isc01ip* > > alias: usb:v*p*d*dc*dsc*dp*ic01isc03ip* > > alias: usb:v0DBAp1000d*dc*dsc*dp*ic*isc*ip* > [snip ...] > > > depends: snd-usbmidi-lib,snd-pcm,snd,snd-hwdep > > vermagic: 2.6.39.1 SMP preempt mod_unload > > parm: index:Index value for the USB audio adapter. (array of > > int) parm: id:ID string for the USB audio adapter. (array of > > charp) parm: enable:Enable USB audio adapter. (array of bool) > > parm: vid:Vendor ID for the USB audio device. (array of int) > > parm: pid:Product ID for the USB audio device. (array of int) > > parm: nrpacks:Max. number of packets per URB. (int) > > parm: async_unlink:Use async unlink mode. (bool) > > parm: device_setup:Specific device setup (if needed). (array > > of int) parm: ignore_ctl_error:Ignore errors from USB controller > > for mixer interfaces. (bool) > > > > I am unsure how to play with the params... > > > > For example: Is "snd_usb_audio enable=treu" correct? > > Well, "treu" wouldn't be correct, not even in French! ;-) > > > > Why it is an /array/ of bool? > > I think that this is used when there is more than one device/interface/etc. > where you will need to enable/disable each one. > > > > May be a last chance is with fiddling with this params? Can I > > rmmod/insmod snd_usb_audio while giving new params to it? How > > can I do that? Fortunately > > > > Module Size Used by > > ecryptfs 87672 3 > > snd_seq_dummy 1359 0 > > snd_seq_oss 30300 0 > > snd_seq_midi_event 5268 1 snd_seq_oss > > snd_seq 50559 5 > > snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_pcm_oss 43683 > > 0 > > snd_mixer_oss 14787 1 snd_pcm_oss > > microcode 6787 0 > > nvidia 10489149 28 > > snd_hda_codec_via 51530 1 > > *** snd_usb_audio 90398 0 > > snd_hda_intel 20832 0 > > snd_hda_codec 63752 2 snd_hda_codec_via,snd_hda_intel > > snd_pcm 73953 4 > > snd_pcm_oss,snd_usb_audio,snd_hda_intel,snd_hda_codec mt352 > > 5653 1 > > snd_hwdep 5940 2 snd_usb_audio,snd_hda_codec > > 8250_pci 23504 0 > > snd_timer 18685 2 snd_seq,snd_pcm > > snd_usbmidi_lib 18214 1 snd_usb_audio > > snd_rawmidi 18484 1 snd_usbmidi_lib > > snd_seq_device 5197 4 > > snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi dvb_bt8xx 11873 > > 0 > > bt878 7643 1 dvb_bt8xx > > bttv 112236 2 dvb_bt8xx,bt878 > > snd 55623 15 > > snd_seq_dummy,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_ > > via,snd_usb_audio,snd_hda_intel,snd_hda_codec,snd_pcm,snd_hwdep,snd_timer,s > > nd_usbmidi_lib,snd_rawmidi,snd_seq_device gspca_ov534 10121 0 > > gspca_main 22449 1 gspca_ov534 > > i2c_algo_bit 4928 1 bttv > > videobuf_dma_sg 7344 1 bttv > > videobuf_core 15263 2 bttv,videobuf_dma_sg > > btcx_risc 3171 1 bttv > > 8250 21264 1 8250_pci > > serial_core 18115 1 8250 > > pcspkr 1811 0 > > asus_atk0110 8206 0 > > tveeprom 13257 1 bttv > > k10temp 2715 0 > > snd_page_alloc 6793 2 snd_hda_intel,snd_pcm > > > > snd_usb_audio is not used by anything else... > > > > Years over years I had not a single problem with alsa and modules at > > all and this seems now be th revenge of the peace of all that years... > > Yes, I would definitely try switching some of these parameters on/off to see > if it will make a difference. > > I recommend you use modprobe -v instead of insmod. So this could be: > > modprobe -v -r snd_usb_audio > modprobe -v -n snd_usb_audio enable=yes > > If you don't get any horror warnings when you run it, then remove the "-n" > option and run it again. Also, try paremeter ignore_ctl_error=1 in case it > makes a difference. > > To make this permanent add a line in /etc/modprobe.d/alsa-base.conf > > options snd_usb_audio enable=yes > options snd_usb_audio ignore_ctl_error=1 > > and restart alsa (or reboot). > > However, the new openrc uses a new way to start modules and dictate their > configuration. So the above may not work for ever and you would need to add > at some point the module and its parameters in /etc/conf.d/modules. For now > I > though I would leave it in /etc/modprobe.d/alsa-base.conf > > Hope this helps. > -- > Regards, > Mick
Hi Mick, this is becoming interesting beyond the goal of solving the problem as such more and more ;) Is there a way to get the default settings of the listed parameters above when the module is loading without giving any additional params on the command line? If yes, I could exclude that default setting from the list of possible working setups and additionally -- may be -- I get a hint, what to twiddle first.... Best regards, mcc
