On Tue, 20 Apr 2004, Andy Green wrote: > Hi folks - > > >Apr 20 11:16:29 fastcat kernel: usbaudio: no idea what's going on..., > >contact [EMAIL PROTECTED] > > The mighty /var/log/messages - it which must be obeyed - has commanded me to > join this list and tell you my problem. > > I am very nearly a happy chappy. My Creative Audigy2 NX is working really > quite well with Alsa on 2.6.5 as rolled by Redhat on their current FC2 > development tree (currently their build 327). There is one exception -- the > kernel will not accept the device *until the PC is rebooted* if the device is > in during Linux boot. > > Although this has been going on for a while until today I figured that the > BIOS on this Inspiron 5150 was responsible for messing the USB host > controller up somehow if the Audigy was present at boot. But no, the problem > seems to be coming from Linux. If I remove the device, reboot the machine, > and add it back just as Linux begins its boot, the problem is present. > > So what does the problem look like? Here is the log: > > Apr 20 11:16:28 fastcat kernel: usb 3-1: new full speed USB device using > address 4 > Apr 20 11:16:28 fastcat kernel: usbaudio: device 4 audiocontrol interface 0 > has 1 input and 1 output AudioStreaming interfaces <snip>
Much of the omitted log is normal. The message above, for instance, will always appear when the usbaudio driver binds to a device. I don't know about the later error messages, though. > This same crapulence is generated no matter what I do to the Audigy, power it > down, remove it, curse at it.... if it was in during Linux boot, that is all > that happens and the device does not appear in /proc/asound/cards until the > PC is rebooted. > > If I hold off on inserting it until we are up in X, then the card comes up > perfectly in Alsa and I can use it just fine. The danger period for having > it plugged in runs from powerup, through Linux boot, at least up until my > initscripts bring up Postfix (which is quite late in the day). The danger is > past by the time X has changed video mode to start up, if I plug in then the > device will be recognized fine for the rest of the session. > > What is in the logs for a good connect? None of the debug stuff above, just > this. > > Apr 20 11:43:14 fastcat kernel: usb 3-1: new full speed USB device using > address 2 > Apr 20 11:43:17 fastcat kernel: usbcore: registered new driver audio > Apr 20 11:43:17 fastcat kernel: drivers/usb/class/audio.c: v1.0.0:USB Audio > Class driver The fact that you don't even see the first message from before means that the usbaudio driver isn't binding to the sound card. Some other driver is controlling it instead, maybe something loaded when you start X. > So long as the device was not plugged in during Linux boot, I can unplug it > and replug it perfectly successfully. > > If anyone has any ideas for getting more information, or advice, please fire > away :-) Seems like you need to prevent the usbaudio driver from loading at boot time. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
