On Thu, Aug 22, 2019 at 12:32:20PM +0200, Florian Zieboll wrote:
> Am 22. August 2019 10:32:01 MESZ schrieb Joel Roth via Dng 
> <dng@lists.dyne.org>:
> > I previously used jmtpfs to mount an android phone connected
> > via usb.  Now having issues mounting a recently acquired
> > nokia 6 with android pie. 
> > 
> > First issue was missing /lib/udev/mtp-probe in dmesg output.
> > That was resolved by installing libmtp-runtime. 
> > 
> > Now I get:
> > 
> > [ 2501.994664] usb 2-1.5: new high-speed USB device number 5 using
> > ehci-pci
> > [ 2502.104236] usb 2-1.5: New USB device found, idVendor=0489,
> > idProduct=c001, bcdDevice= 3.18
> > [ 2502.104242] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [ 2502.104245] usb 2-1.5: Product: Android
> > [ 2502.104248] usb 2-1.5: Manufacturer: Android
> > [ 2502.104251] usb 2-1.5: SerialNumber: PLEGAR2812101035
> > [ 2502.105172] usb-storage 2-1.5:1.0: USB Mass Storage device detected
> > [ 2502.105264] scsi host6: usb-storage 2-1.5:1.0
> > [ 2503.108002] scsi 6:0:0:0: CD-ROM            Linux    File-CD Gadget
> >   0318 PQ: 0 ANSI: 2
> > [ 2503.108959] sr 6:0:0:0: Power-on or device reset occurred
> > [ 2503.110700] sr 6:0:0:0: [sr1] scsi-1 drive
> > [ 2503.110909] sr 6:0:0:0: Attached scsi CD-ROM sr1
> > [ 2503.110984] sr 6:0:0:0: Attached scsi generic sg2 type 5
> > 
> > mount /dev/sr1 /mnt/test fails with 
> > 
> >    mount: no medium found on /dev/sr1
> > 
> > jtmpfs reports "No mtp devices found."
> > 
> > file /dev/sr1 reports 
> > 
> >    /dev/sr1: block special (11/1)
> > 
> > 
> > lsusb -v -s 2:5
> > 
> >    Bus 002 Device 005: ID 0489:c001 Foxconn / Hon Hai
> >    Device Descriptor:
> >      bLength                18
> >      bDescriptorType         1
> >      bcdUSB               2.00
> >      bDeviceClass            0 (Defined at Interface level)
> >      bDeviceSubClass         0
> >      bDeviceProtocol         0
> >      bMaxPacketSize0        64
> >      idVendor           0x0489 Foxconn / Hon Hai
> >      idProduct          0xc001
> >      bcdDevice            3.18
> >      iManufacturer           1 Android
> >      iProduct                2 Android
> >      iSerial                 3 PLEGAR2812101035
> >      bNumConfigurations      1
> >      Configuration Descriptor:
> >        bLength                 9
> >        bDescriptorType         2
> >        wTotalLength           55
> >        bNumInterfaces          2
> >        bConfigurationValue     1
> >        iConfiguration          0
> >        bmAttributes         0x80
> >          (Bus Powered)
> >        MaxPower              500mA
> >        Interface Descriptor:
> >          bLength                 9
> >          bDescriptorType         4
> >          bInterfaceNumber        0
> >          bAlternateSetting       0
> >          bNumEndpoints           2
> >          bInterfaceClass         8 Mass Storage
> >          bInterfaceSubClass      6 SCSI
> >          bInterfaceProtocol     80 Bulk-Only
> >          iInterface              4 Mass Storage
> >          Endpoint Descriptor:
> >            bLength                 7
> >            bDescriptorType         5
> >            bEndpointAddress     0x81  EP 1 IN
> >            bmAttributes            2
> >              Transfer Type            Bulk
> >              Synch Type               None
> >              Usage Type               Data
> >            wMaxPacketSize     0x0200  1x 512 bytes
> >            bInterval               0
> >          Endpoint Descriptor:
> >            bLength                 7
> >            bDescriptorType         5
> >            bEndpointAddress     0x01  EP 1 OUT
> >            bmAttributes            2
> >              Transfer Type            Bulk
> >              Synch Type               None
> >              Usage Type               Data
> >            wMaxPacketSize     0x0200  1x 512 bytes
> >            bInterval               1
> >        Interface Descriptor:
> >          bLength                 9
> >          bDescriptorType         4
> >          bInterfaceNumber        1
> >          bAlternateSetting       0
> >          bNumEndpoints           2
> >          bInterfaceClass       255 Vendor Specific Class
> >          bInterfaceSubClass     66
> >          bInterfaceProtocol      1
> >          iInterface              7 ADB Interface
> >          Endpoint Descriptor:
> >            bLength                 7
> >            bDescriptorType         5
> >            bEndpointAddress     0x02  EP 2 OUT
> >            bmAttributes            2
> >              Transfer Type            Bulk
> >              Synch Type               None
> >              Usage Type               Data
> >            wMaxPacketSize     0x0200  1x 512 bytes
> >            bInterval               0
> >          Endpoint Descriptor:
> >            bLength                 7
> >            bDescriptorType         5
> >            bEndpointAddress     0x82  EP 2 IN
> >            bmAttributes            2
> >              Transfer Type            Bulk
> >              Synch Type               None
> >              Usage Type               Data
> >            wMaxPacketSize     0x0200  1x 512 bytes
> >            bInterval               0
> >    Device Qualifier (for other device speed):
> >      bLength                10
> >      bDescriptorType         6
> >      bcdUSB               2.00
> >      bDeviceClass            0 (Defined at Interface level)
> >      bDeviceSubClass         0
> >      bDeviceProtocol         0
> >      bMaxPacketSize0        64
> >      bNumConfigurations      1
> >    Device Status:     0x0000
> >      (Bus Powered)
> > 
> > I upgraded from 4.9 kernel to 4.19 and continue to have this issue. 
> > 
> > According to apt-cache search, udev is a transitional package for
> > eudev. So does that mean I have an issue with eudev?
> > 
> > Grateful for any advice toward diagnosing or resolving this
> > issue!
> > 
> 
> Do you have the device specific udev rule under /etc/udev/rules.d/ ? The 
> following line works for me, with $VENDORID and $PRODUCTID replaced by the 
> actual output of lsusb:
> 
> SUBSYSTEM=="usb", ATTR{idVendor}=="$VENDORID", ATTR{idProduct}=="$PRODUCTID", 
> SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", 
> ENV{ID_MEDIA_PLAYER}="1"
> 
> See also http://cheatsheet.zwischenspeicher.info/2018/02/16-2018-02-12/ 

Thanks for this suggestion. I put in a udev rule as you
advise (see below). However no difference in the result.
Any other ideas??

$ cat rules.d/80-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", ATTR{idProduct}=="c001", 
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", 
ENV{ID_MEDIA_PLAYER}="1"

$ tail -13 /var/log/kern.log

Aug 31 10:07:14 sprite kernel: [822384.553598] usb 2-1.5: new high-speed USB 
device number 18 using ehci-pci
Aug 31 10:07:14 sprite kernel: [822384.662963] usb 2-1.5: New USB device found, 
idVendor=0489, idProduct=c001, bcdDevice= 3.18
Aug 31 10:07:14 sprite kernel: [822384.662968] usb 2-1.5: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Aug 31 10:07:14 sprite kernel: [822384.662971] usb 2-1.5: Product: Android
Aug 31 10:07:14 sprite kernel: [822384.662974] usb 2-1.5: Manufacturer: Android
Aug 31 10:07:14 sprite kernel: [822384.662977] usb 2-1.5: SerialNumber: 
PLEGAR2812101035
Aug 31 10:07:14 sprite kernel: [822384.664025] usb-storage 2-1.5:1.0: USB Mass 
Storage device detected
Aug 31 10:07:14 sprite kernel: [822384.664113] scsi host6: usb-storage 2-1.5:1.0
Aug 31 10:07:15 sprite kernel: [822385.674525] scsi 6:0:0:0: CD-ROM            
Linux    File-CD Gadget   0318 PQ: 0 ANSI: 2
Aug 31 10:07:15 sprite kernel: [822385.675279] sr 6:0:0:0: Power-on or device 
reset occurred
Aug 31 10:07:15 sprite kernel: [822385.676932] sr 6:0:0:0: [sr1] scsi-1 drive
Aug 31 10:07:15 sprite kernel: [822385.677127] sr 6:0:0:0: Attached scsi CD-ROM 
sr1
Aug 31 10:07:15 sprite kernel: [822385.677190] sr 6:0:0:0: Attached scsi 
generic sg2 type 5


> Regards,
> Florian
> 
> -- 
> Florian Zieboll

-- 
Joel Roth

"Welcome to the World Heat Bank, where we store your waste
energy and return it with interest."
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to