I reported this bug at the Debian Bug Tracker (http://bugs.debian.org/559342) and under their recommendation, I forward this report here. The issue is the following: I own a Samsung SGH-L760V mobile phone, which can be mounted via USB as a normal USB massive storage device. This device worked with Linux under 2.6.28 (Debian 5.0 "Lenny"), but stopped doing so after the upgrade into the testing "Squeeze" release. This is the output at /var/log/messages when connecting the device. As you can see, it recognizes it, but doesn't mount it: May 2 14:48:00 UGI kernel: [ 8742.164099] usb 7-2: new full speed USB device using uhci_hcd and address 12 May 2 14:48:00 UGI kernel: [ 8742.324214] usb 7-2: New USB device found, idVendor=04e8, idProduct=5a0f May 2 14:48:00 UGI kernel: [ 8742.324220] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 2 14:48:00 UGI kernel: [ 8742.324224] usb 7-2: Product: SGH-L760V May 2 14:48:00 UGI kernel: [ 8742.324228] usb 7-2: Manufacturer: SAMSUNG MTP Device May 2 14:48:00 UGI kernel: [ 8742.324231] usb 7-2: SerialNumber: A353666023139976 May 2 14:48:00 UGI kernel: [ 8742.324374] usb 7-2: configuration #1 chosen from 1 choice There's more information at the link provided. I'll be pleased to hand out any further help I may be able to offer. Cheers, Eugenio
Recategorised to USB, marked as a regression.
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sun, 2 May 2010 13:03:36 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=15894 > > Summary: Mobile phone not being mounted as USB flash memory > Product: Drivers > Version: 2.5 > Kernel Version: 2.6.30 - 2.6.32 (Debian testing "Squeeze") > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Flash/Memory Technology Devices > AssignedTo: dwmw2@infradead.org > ReportedBy: emvigo@gmail.com > Regression: No It's a regression. > > I reported this bug at the Debian Bug Tracker (http://bugs.debian.org/559342) > and under their recommendation, I forward this report here. > > The issue is the following: I own a Samsung SGH-L760V mobile phone, which can > be mounted via USB as a normal USB massive storage device. This device worked > with Linux under 2.6.28 (Debian 5.0 "Lenny"), but stopped doing so after the > upgrade into the testing "Squeeze" release. > > This is the output at /var/log/messages when connecting the device. As you > can > see, it recognizes it, but doesn't mount it: > > May 2 14:48:00 UGI kernel: [ 8742.164099] usb 7-2: new full speed USB device > using uhci_hcd and address 12 > May 2 14:48:00 UGI kernel: [ 8742.324214] usb 7-2: New USB device found, > idVendor=04e8, idProduct=5a0f > May 2 14:48:00 UGI kernel: [ 8742.324220] usb 7-2: New USB device strings: > Mfr=1, Product=2, SerialNumber=3 > May 2 14:48:00 UGI kernel: [ 8742.324224] usb 7-2: Product: SGH-L760V > May 2 14:48:00 UGI kernel: [ 8742.324228] usb 7-2: Manufacturer: SAMSUNG MTP > Device > May 2 14:48:00 UGI kernel: [ 8742.324231] usb 7-2: SerialNumber: > A353666023139976 > May 2 14:48:00 UGI kernel: [ 8742.324374] usb 7-2: configuration #1 chosen > from 1 choice > > There's more information at the link provided. I'll be pleased to hand out > any > further help I may be able to offer. >
Am 05.05.2010 18:09, schrieb Alan Stern: > It's strange that this thing calls itself an MTP device and not a > mass-storage device. What shows up in the "lsusb -v" entry for the > phone? Eugenio, when you do the "lsusb -v", make sure you have the phone switched to mass storage mode. I read in your report that you switched modes during your trials. Josua Dietze
On Tue, 4 May 2010, Andrew Morton wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=15894 > > > > Summary: Mobile phone not being mounted as USB flash memory > > The issue is the following: I own a Samsung SGH-L760V mobile phone, which > can > > be mounted via USB as a normal USB massive storage device. This device > worked > > with Linux under 2.6.28 (Debian 5.0 "Lenny"), but stopped doing so after > the > > upgrade into the testing "Squeeze" release. > > > > This is the output at /var/log/messages when connecting the device. As you > can > > see, it recognizes it, but doesn't mount it: > > > > May 2 14:48:00 UGI kernel: [ 8742.164099] usb 7-2: new full speed USB > device > > using uhci_hcd and address 12 > > May 2 14:48:00 UGI kernel: [ 8742.324214] usb 7-2: New USB device found, > > idVendor=04e8, idProduct=5a0f > > May 2 14:48:00 UGI kernel: [ 8742.324220] usb 7-2: New USB device strings: > > Mfr=1, Product=2, SerialNumber=3 > > May 2 14:48:00 UGI kernel: [ 8742.324224] usb 7-2: Product: SGH-L760V > > May 2 14:48:00 UGI kernel: [ 8742.324228] usb 7-2: Manufacturer: SAMSUNG > MTP > > Device It's strange that this thing calls itself an MTP device and not a mass-storage device. What shows up in the "lsusb -v" entry for the phone? Alan Stern
Thanks for your replies! First of all, I am using the "Multimedia Device" option at the phone, which previously allowed me to use the phone as it were a regular USB stick. The other option is the one that allows the use of Samsung's PC Studio software. Not choosing anything on the menu that pops up at it when plugged in renders the phone (and it works) as a GSM broadband modem. lsusb -v output shows: Bus 007 Device 003: ID 04e8:5a0f Samsung Electronics Co., Ltd MTP Device Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04e8 Samsung Electronics Co., Ltd idProduct 0x5a0f MTP Device bcdDevice 0.00 iManufacturer 1 SAMSUNG MTP Device iProduct 2 SGH-L760V iSerial 3 A353666023139976 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 96 Device Status: 0x0000 (Bus Powered)
(Sorry, my last comment was done through the web interface... here I copy the message again) Thanks for your replies! First of all, I am using the "Multimedia Device" option at the phone, which previously allowed me to use the phone as it were a regular USB stick. The other option is the one that allows the use of Samsung's PC Studio software. Not choosing anything on the menu that pops up at it when plugged in renders the phone (and it works) as a GSM broadband modem. lsusb -v output shows: Bus 007 Device 003: ID 04e8:5a0f Samsung Electronics Co., Ltd MTP Device Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04e8 Samsung Electronics Co., Ltd idProduct 0x5a0f MTP Device bcdDevice 0.00 iManufacturer 1 SAMSUNG MTP Device iProduct 2 SGH-L760V iSerial 3 A353666023139976 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 96 Device Status: 0x0000 (Bus Powered)
On Wed, 5 May 2010, Eugenio M. Vigo wrote: > Thanks for your replies! First of all, I am using the "Multimedia Device" > option at the phone, which previously allowed me to use the phone as it were > a regular USB stick. The other option is the one that allows the use of > Samsung's PC Studio software. Not choosing anything on the menu that pops up > at it when plugged in renders the phone (and it works) as a GSM broadband > modem. > > lsusb -v output shows: This is for the "Multimedia Device" setting? Maybe you got the settings mixed up. Have you tried the other setting? > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 6 Imaging > bInterfaceSubClass 1 Still Image Capture > bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) That's very clear. It is not a mass-storage interface, so with this setting the phone cannot be mounted like a regular disk. You have to access it using an appropriate program, like gphoto2, Gnomad2, Rhythmbox, or Amarok. Alan Stern
2010/5/5 Alan Stern <stern@rowland.harvard.edu> > > On Wed, 5 May 2010, Eugenio M. Vigo wrote: > (...) > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 0 > > bAlternateSetting 0 > > bNumEndpoints 3 > > bInterfaceClass 6 Imaging > > bInterfaceSubClass 1 Still Image Capture > > bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) > > That's very clear. It is not a mass-storage interface, so with this > setting the phone cannot be mounted like a regular disk. You have to > access it using an appropriate program, like gphoto2, Gnomad2, > Rhythmbox, or Amarok. Ok, that was it: I was expecting the device to act like something it shouldn't; maybe the previous behaivor of mass storage-like mounting was the bug and not this one. Yes, using Rhythmbox and gphoto2 work flawlessly. I'm very sorry for all the inconveniences; I just hate to make people lose their time like this. I apologize. So, this can be considered to be closed. I'll report this back to the Debian BTS. Thanks for everything!
On Thu, 6 May 2010, Eugenio M. Vigo wrote: > > That's very clear. It is not a mass-storage interface, so with this > > setting the phone cannot be mounted like a regular disk. You have to > > access it using an appropriate program, like gphoto2, Gnomad2, > > Rhythmbox, or Amarok. > > Ok, that was it: I was expecting the device to act like something it > shouldn't; maybe the previous behaivor of mass storage-like mounting > was the bug and not this one. Yes, using Rhythmbox and gphoto2 work > flawlessly. > > I'm very sorry for all the inconveniences; I just hate to make people > lose their time like this. I apologize. > > So, this can be considered to be closed. I'll report this back to the > Debian BTS. Okay, closing out the bug report. Alan Stern