On Sunday 05 Jun 2011 13:53:49 [email protected] wrote: > 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?
Yes. They ought to show in dmesg when the module is loaded and the device
probed. Sometimes they also show if you run modprobe with -v and the debug
module parameter is switched to verbose (only some modules have this
parameter).
They also show conveniently under alsa-info (since we're talking here about a
sound module):
!!Module: snd_usb_audio
async_unlink : Y
device_setup : 0,0,0,0,0,0,0,0
enable : Y,Y,Y,Y,Y,Y,Y,Y
(this is the array we were talking about and it is enabled)
id : (null),(null),(null),(null),(null),(null),(null),(null)
ignore_ctl_error : N
(this is the ignore ctl error and is not ignored, so you could switch this to
yes and see if it makes a difference)
index : -1,-1,-1,-1,-1,-1,-1,-1
nrpacks : 8
pid : -1,-1,-1,-1,-1,-1,-1,-1
vid : -1,-1,-1,-1,-1,-1,-1,-1
> 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....
Ideally, you should not need to tweak anything to be honest. This mechanism
is to tune some modules in case there are conflicts between devices, or you
want to switch on a hardware functionality which may be switched off by
default (e.g. QoS, debugging, etc).
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
