On Mon, 2005-02-07 at 22:53 +0100, [EMAIL PROTECTED] wrote: > Now it is working. > > BUT it seems that this is related to my attempt yesterday to install directly > from sources since my user needs to be in the ifp group instead of the > plugdev group to be able to use ifp (whereas the mpm-common package is > supposed to bypass this), being or not being in plugdev group has no effect. > > As a matter of fact dmesg gives > usb 1-1: new full speed USB device using address 4 > and ls -l in /proc/bus/usb/001 shows > -rw-rw-r-- 1 root ifp 50 2005-02-07 22:16 004 > so that it seems that a user really need to be in the ifp group to be able to > access the pmp.
There is no 'ifp' group on a Debian system, even with pmp-common installed. You broke something when you tried to install it from the package and the source at the same time. > --------------------------------- > A little bit of testing > I have just renamed /etc/hotplug/usb.usermap into > /etc/hotplug/usb.usermap.bkp > and apt-get remove pmp-common ifp-line. This is the closer I can do to come > back to a clean state as before my compiling the source. > > Then I apt-get install pmp-common and ifp-line -> the problem reappears : > Device is busy. (I was unable to claim its interface.) > > To make it work again (still with my user in ifp group instead of plugdev > group) I have had to rename /etc/hotplug/usb.usermap.bkp > into /etc/hotplug/usb.usermap. It seems that without > this /etc/hotplug/usb/ifpdev is never executed (as a cat > file I have added > in it shows) so that /proc/bus/usb/001 never chgrp ifp. Your system is all messed up. Please restore it to a pristine state by removing ifp-line and pmp-common *and* all the files installed by your source attempt, then try to replicate this bug. -- Joe Wreschnig <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
