At Thu, 26 Sep 2002 10:20:25 +0200, Duncan Sands wrote: > > I have a usb webcam with audio plugged into my computer, > and a cs46xx sound card inside. > > When I boot the following sequence occurs: > > (1) the hotplug subsytem is started. This automatically > loads the snd-usb-audio module and the modules it > depends on. In particular /proc/asound/ is created. > > (2) the alsasound init script is run. It detects that > /proc/asound/ exists, and exits at once. In particular > it does not restore mixer levels for the cs46xx card. > > I solved this by commenting out the check for /proc/asound/ > in the init script. The problem goes deeper though, especially > when things like usb audio devices are around, which can be > hotplugged: maybe sound card modules should really be calling > the hotplug subsystem when they are initialize. The hotplug > script would then restore mixer settings etc... > > Thoughts?
i solved like the following: - add snd-usb-* (and oss audio module) to hotplug's blacklist to avoid to load them from the modules.usermap. - add a usermap for the usb audio devices to call its own start-up script. the script starts the alsasound init script inside before loading the snd-usb-audio module (if no /proc/asound exists), so that it asssures that the normal PCI devices are assigned prior to usb devices. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel