> I see in your attached debdiff something like...
>
> # MidiSport 2x2
> -ACTION=="add", SUBSYSTEM=="usb_device", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1001", RUN+="@fxload@ -s @firmwaredir@/MidiSportLoader.ihx -I @firmwaredir@/MidiSport2x2.ihx"
> +ACTION=="add", SUBSYSTEM=="usb_device", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1001", RUN+="@fxload@ -s @firmwaredir@/MidiSportLoader.ihx -I @firmwaredir@/MidiSport2x2.ihx" -d $env{DEVNAME}
>
> PLEASE, PLEASE, it is not correct!!!
>
> the '-d $env{DEVNAME}' MUST be inside the quote commas. And the '-d' should be an upper case.
Right, sorry about that. Fixed version attached.
> It is interesting to know also that I have compiled from the source available on the sourceforge.net on an official Debian Etch and the original
> '42-midisport-firmware.rules.in' as ALSO the proposed modified one both work.
> But on Ubuntu (both Feisty and Gutsy) the only way to make it work is with the above code, whether with -D $env{DEVNAME} or -D $tempnode.
Yes, I think this is due to some Ubuntu-specific udev/kerenl stuff, although I don't really know enough about that to be sure.
> I see in your attached debdiff something like... ="usb_device" , ATTRS{idVendor} =="0763" , ATTRS{idProduct }=="1001" , RUN+="@fxload@ -s @firmwaredir@ /MidiSportLoade r.ihx -I @firmwaredir@ /MidiSport2x2. ihx" ="usb_device" , ATTRS{idVendor} =="0763" , ATTRS{idProduct }=="1001" , RUN+="@fxload@ -s @firmwaredir@ /MidiSportLoade r.ihx -I @firmwaredir@ /MidiSport2x2. ihx" -d $env{DEVNAME}
>
> # MidiSport 2x2
> -ACTION=="add", SUBSYSTEM=
> +ACTION=="add", SUBSYSTEM=
>
> PLEASE, PLEASE, it is not correct!!!
>
> the '-d $env{DEVNAME}' MUST be inside the quote commas. And the '-d' should be an upper case.
Right, sorry about that. Fixed version attached.
> It is interesting to know also that I have compiled from the source available on the sourceforge.net on an official Debian Etch and the original firmware. rules.in' as ALSO the proposed modified one both work.
> '42-midisport-
> But on Ubuntu (both Feisty and Gutsy) the only way to make it work is with the above code, whether with -D $env{DEVNAME} or -D $tempnode.
Yes, I think this is due to some Ubuntu-specific udev/kerenl stuff, although I don't really know enough about that to be sure.
Thanks,
Forest