On Monday 02 September 2002 09:19, Clemens Ladisch wrote:
> Matt Walker wrote:
> > I am trying to get the midisport to do rawmidi - just sysex/librarian
> > stuff. The following leads me to believe that usb is working, and the
> > driver is getting loaded, but the 2 aren't making a connection....
> >
> > Other observations:
> > c) I used the modules.conf and hotplug script on the new card matrix php
> > thing. I put a logger line before the if's in /etc/hotplug/usb/ezusbmidi,
> > but it never appears in var/log/messages. Is there a trick to getting it
> > to run?
>
> The hotplug script would have output some messages if it had been run.
> Is it installed (/sbin/hotplug, from
> <http://linux-hotplug.sourceforge.net/>), and is CONFIG_HOTPLUG enabled in
> the kernel config?
>
> > I ended up running fxload manually; it didn't return an error, so I guess
> > it worked.
>
> Add -v to the other fxload parameters to see what it's doing.
> After uploading the firmware, fxload resets the device, so you should be
> able to see something in /var/log/messages.
>
>
> HTH
> Clemens
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Alsa-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/alsa-user
Kai --
Correct me if I'm wrong, but I assumed that since I'm trying to upload
firmware via hotplug, I wouldn't need ezusb2131....
Clemens --
I might have mistyped the device path when I tried fxload before, but as you
predicted, it reset everything and bound all the drivers. Rebooting, however,
wipes out everything. I know that hotplug isn't yours, but before I jump into
the software design wars between David Brownell and the rest of the hotplug
list ( ;-), do you know anything about this? usb.agent calls load_modules,
which appears to be the only path to get to /etc/hotplug/usb/ezusbmidi.
.
.
.
LISTER=`type -p ${TYPE}modules`
if [ "$LISTER" != "" ]; then
case $TYPE in
usb)
...blah -blah...
pci)
...blah-blah....
....
esac
fi
# do it with just shell scripts
if [ "$LISTER" = "" ]; then
${TYPE}_map_modules < $FILENAME
fi
if [ "$DRIVERS" = "" ]; then
return
fi
well, MY version of usbmodules (0.8) requires '--device' as an argument, and
when the thing hasn't been successfully set up, even sending it the right
device argument returns nothing, so... load_devices() returns before hitting
the code that would run the ezusbmidi script, and I don't see a scenario by
which it could ever load a driver. Am I missing something here? Do I have to
put "fxload --I blah blah.." in my .profile? ;-)
Thanks,
Matt Walker
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
