Hallo! Ich versuche, mein Smartphone per MTP an meinen Linuxrechner anzuschließen, doch es funktioniert nicht. Ich habe mtpfs, mtp-tools (mtp-detect), jmtpfs, go-mtpfs und go-mntfs ausprobiert, und ich bekomme immer den gleichen Fehler:
~ $ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 6 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ~ $ mtpfs /mnt/android/ Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 6 Attempting to connect device ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 ~ $ jmtpfs /mnt/android/ Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Unable to open ~/.mtpz-data for reading, MTPZ disabled.Abgebrochen ~ $ go-mtpfs /mnt/android/ 2013/12/14 04:28:10 OpenSession failed: LIBUSB_ERROR_IO; attempting reset 2013/12/14 04:28:11 Configure failed: OpenSession after reset: LIBUSB_ERROR_IO Das Gerät wird bei jedem Kommando von oben gefunden, doch der Versuch eine Verbindung/Session herzustellen, schlägt fehl. dmesg liefert die folgenden Meldungen. In /var/log/messages und /var/log/kern.log steht das gleiche: ... [ 7409.768040] usb 2-1.1: usbfs: process 3815 (ThreadWeaver::T) did not claim interface 0 before use [ 7409.768224] usb 2-1.1: usbfs: process 4924 (jmtpfs) did not claim interface 0 before use [ 7438.781863] usb 2-1.1: usbfs: process 4934 (go-mtpfs) did not claim interface 0 before use [ 7438.872199] usb 2-1.1: reset high-speed USB device number 6 using xhci_hcd [ 7438.889206] xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801fadebc00 ... [ 7438.889239] xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802254bb140 [ 7438.891734] cdc_acm 2-1.1:1.1: This device cannot do calls on its own. It is not a modem. [ 7438.891850] cdc_acm 2-1.1:1.1: ttyACM0: USB ACM device [ 7438.893224] usb 2-1.1: usbfs: process 3815 (ThreadWeaver::T) did not claim interface 0 before use [ 7439.894969] usb 2-1.1: usbfs: process 4934 (go-mtpfs) did not claim interface 0 before use Ich habe jetzt ein paar Stunden gegoogelt, doch ich habe nichts passendes über die auftretenden Fehlermeldungen zutage gefördert. Hat jemand eine Ahnung, was hier schief läuft? Ich bin mit meinem neuen Smartphone eigentlich sehr zufrieden, wenn nur der Massenspeichermodus unterstützt würde. Wenn ich MTP nicht zum laufen bringe, muß ich das Ding vielleicht rooten. Das möchte ich vermeiden, wenn es geht. Viele Grüße, Volker -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5956320.AO4KUtyL0e@debian
