[Long posting!] Re: [PlanetCCRMA] Self-configuring system Was:*Solved* Midisport8x8/s Was:Chasing my tail with ALSA

[Mark Knecht]

On Tue, 2004-02-17 at 19:12, Michael wrote:
> Due to this long posting, look/search for @@@ at the begining of my 
> comments.... I have to agree with you, I think about the firmware not 
> running, but why is it I can get it to run after pushing the system 
> through a configuration manually, but lose it on reboot? Is that right?

I would guess that you are able to load firmware by hand, but that
hotplug may not know what firmware to load when it's happening
automatically. 

I don't understand exactly what makes this stuff fly, but on my system
the file /etc/hotplug/usb.usermap has some entries where the Vendor ID
(0x763) matches my Midisport. When I plug it in on this system I see
this using tail -f /varlog/messages:

Feb 17 19:42:08 Wizard kernel: hub.c: new USB device 00:10.0-2, assigned
address 3
Feb 17 19:42:08 Wizard kernel: usb.c: USB device 3 (vend/prod
0x763/0x1001) is not claimed by any active driver.
Feb 17 19:42:08 Wizard /etc/hotplug/usb/ezusbmidi: load
/usr/share/usb/ezusbmidi/ezusbmidi2x2.ihx for 763/1001/1 to
/proc/bus/usb/001/003
Feb 17 19:42:08 Wizard kernel: usb.c: USB disconnect on device 00:10.0-2
address 3
Feb 17 19:42:08 Wizard /etc/hotplug/usb/ezusbmidi: load
/usr/share/usb/ezusbmidi/ezusbmidi2x2.ihx for 763/1001/1 to
/proc/bus/usb/001/003
Feb 17 19:42:09 Wizard kernel: hub.c: new USB device 00:10.0-2, assigned
address 4
Feb 17 19:42:09 Wizard kernel: usb.c: USB device 4 (vend/prod
0x763/0x1110) is not claimed by any active driver.
Feb 17 19:42:09 Wizard kernel: usb.c: registered new driver
snd-usb-audio
Feb 17 19:42:09 Wizard usb.agent[21764]: ... can't load module
snd-usb-audio
Feb 17 19:42:09 Wizard usb.agent[21764]: missing kernel or user mode
driver snd-usb-audio 

(This is NOT the system I would use this on, so I don't have the right
usb-audio driver built here I guess.)

Anyway, I think the point is that the firmware gets loaded 1) BEcause
hotplug sees the event, 2) because it sees a Vendor ID/Product ID it
understands, and 3) because it has a firmware file I can load.

If those 3 things aren't true on your system then it isn't going to
work.

1) Since you can get the firmware loaded by hand the firmware must be
there somewhere.

2) IF you don't get at least some event in /var/log/messages when you
plug the device in the hotplug must not be doing it's job.


> 
> @@@ In /etc/hotplug, I have:
> 
> #
> # Listing a module here prevents the hotplug scripts from loading it.
> # Usually that'd be so that some other driver will bind it instead,
> # no matter which driver happens to get probed first.  Sometimes user
> # mode tools can also control driver binding.
> #
> # Syntax:  driver name alone (without any spaces) on a line. Other
> # lines are ignored.
> #
> 
> # uhci ... usb-uhci handles the same pci class
> usb-uhci
> 
> # tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
> de4x5
> # At least 2.4.3 and later xircom_tulip doesn't have that conflict
> # xircom_tulip_cb
> dmfe
> # Fernando's suggestions to get my machine going again.... 02-14-04
> audio
> usb-midi

Here's mine. Yours looks good to me:

# uhci ... usb-uhci handles the same pci class
usb-uhci
# usbcore ... module is loaded implicitly, ignore it otherwise
usbcore

# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
de4x5
# At least 2.4.3 and later xircom_tulip doesn't have that conflict
# xircom_tulip_cb
dmfe

usb-midi
audio


> @@@ For var/log/messages, I have: (one more comment below....)
> 
> Feb 17 20:45:47 localhost syslogd 1.4.1: restart.
> Feb 17 20:45:47 localhost syslog: syslogd startup succeeded
<SNIP>
> Feb 17 20:51:28 localhost su(pam_unix)[1793]: session opened for user 
> root by mikes(uid=500)

I Didn't spot anything of real interest in there, but maybe I missed it.

> 
> @@@ For dmesg, I have: (see below) Take note of "usb.c: registered new 
> driver snd-usb-audio" located 14th from the bottom....
> 
<SNIP>
> usb.c: registered new driver snd-usb-audio
<SNIP>
This is just the driver getting loaded and not hotplug doing it's job.

Do you have hotplug enabled? chkconfig --show or whatever that command
is...

- Mark