From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hartmut Geissbauer Subject: Re: Creamware Noah, snd-usb-audio capable? Date: Mon, 16 Feb 2004 19:18:10 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <1076955490.2515.11.camel@chief.local> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: alsa-devel List-Id: alsa-devel@alsa-project.org Hi Clemens, Clemens Ladisch wrote: > Hartmut Geissbauer wrote: > > Clemens Ladisch wrote: > > > The problem is that the kernel automatically selects the first > > > configuration. Please try the patch below. > > > > drivers/usb/core/usb.c: usb_hotplug > > usb 1-2.4: configuration #1 chosen from 2 choices > > usb 1-2.4: registering 1-2.4:1.0 (config #1, interface 0) > > drivers/usb/core/usb.c: usb_hotplug > > snd-usb-audio 1-2.4:1.0: usb_probe_interface > > snd-usb-audio 1-2.4:1.0: usb_probe_interface - got id > > > > The device is not appearing in /proc/asound. > > Does the new configuration (the audio interfaces) show up in > /proc/bus/usb/devices? No. > What happens when you re-load snd-usb-audio > after that? > 'rmmod snd-usb-audio' does not return to the command prompt. A 'modprobe snd-usb-audio' on another xterm after the rmmod as well. dmesg shows me: drivers/usb/core/usb.c: deregistering driver snd-usb-audio I tried to connect the device via a hub and direct. No difference. > > Regards, > Clemens > Thank you for your answer, Hartmut -- Hartmut Geissbauer ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click