Picture frame 1de1:1101 does not work in mass storage mode

[Petr Kubánek]

Hi,

I get picture frame from Hama, with USB id 1de1:1101. It works under
Windows XP, fails under Linux. Find bellow dmesg and lsusb -v. Any idea
what can be wrong?

Thanks

Petr

[ 4096.873219] usb 2-1.7: USB disconnect, device number 37
[ 4099.633266] usb 2-1.8: new high-speed USB device number 38 using ehci_hcd
[ 4099.726001] usb 2-1.8: New USB device found, idVendor=1de1, idProduct=1101
[ 4099.726006] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4099.726008] usb 2-1.8: Product: \x01
[ 4099.726011] usb 2-1.8: Manufacturer: action
[ 4099.726013] usb 2-1.8: SerialNumber:
[ 4099.726013] V1.00.3333
[ 4099.727898] scsi16 : usb-storage 2-1.8:1.0
[ 4100.774630] scsi 16:0:0:0: Direct-Access GENERIC DPF NAND 1.00 PQ: 0 ANSI: 0 CCS
[ 4100.776339] scsi 16:0:0:1: Direct-Access GENERIC DPF SD/MMC/XD 1.00 PQ: 0 ANSI: 0 CCS
[ 4100.776628] sd 16:0:0:0: Attached scsi generic sg7 type 0
[ 4100.776756] sd 16:0:0:1: Attached scsi generic sg8 type 0
[ 4100.782353] sd 16:0:0:0: [sdg] 3770368 512-byte logical blocks: (1.93 GB/1.79 GiB)
[ 4100.784725] sd 16:0:0:0: [sdg] Write Protect is off
[ 4100.784730] sd 16:0:0:0: [sdg] Mode Sense: 00 12 00 00
[ 4100.785849] sd 16:0:0:1: [sdh] Attached SCSI removable disk
[ 4100.786598] sd 16:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4100.795915] ldm_validate_partition_table(): Disk read failed.
[ 4100.795933] Dev sdg: unable to read RDB block 0
[ 4100.795957] sdg: unable to read partition table
[ 4100.803224] sd 16:0:0:0: [sdg] Attached SCSI removable disk
[ 4100.804117] sd 16:0:0:0: [sdg] Synchronizing SCSI cache
[ 4100.809756] scsi 16:0:0:0: rejecting I/O to offline device
[ 4100.809760] scsi 16:0:0:0: killing request


Bus 002 Device 041: ID 1de1:1101 Actions Microelectronics Co. Generic Display Device (Mass storage mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1de1 Actions Microelectronics Co.
idProduct 0x1101 Generic Display Device (Mass storage mode)
bcdDevice 1.00
iManufacturer 1 action
iProduct 2 ^A
iSerial 3
V1.00.3333
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 self-powered
bmAttributes 0xc0
Self Powered
MaxPower 20mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 5 SFF-8070i
bInterfaceProtocol 80
iInterface 5 Mass Storage
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 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 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1

[Alan Stern]

On Mon, 24 Dec 2012, Petr [ISO-8859-1] Kub�nek wrote:

> Hi,
>
> I get picture frame from Hama, with USB id 1de1:1101. It works under
> Windows XP, fails under Linux. Find bellow dmesg and lsusb -v. Any idea
> what can be wrong?

There's no way to tell just from this information. Can you provide a
usbmon trace showing what happens when the picture frame is plugged in?
Instructions are in the kernel source file Documentation/usb/usbmon.txt

Alan Stern

[Petr Kubánek]

Hi Alan,

please find it attached. Let me know if you need more help/other
output/.... Dmesg claimed:

[ 9100.300027] scsi 9:0:0:0: Direct-Access GENERIC DPF NAND 1.00 PQ: 0 ANSI: 0 CCS
[ 9100.301723] scsi 9:0:0:1: Direct-Access GENERIC DPF SD/MMC/XD 1.00 PQ: 0 ANSI: 0 CCS
[ 9100.302155] sd 9:0:0:0: Attached scsi generic sg2 type 0
[ 9100.302330] sd 9:0:0:1: Attached scsi generic sg3 type 0
[ 9100.308599] sd 9:0:0:0: [sdc] 3770368 512-byte logical blocks: (1.93 GB/1.79 GiB)
[ 9100.310579] sd 9:0:0:0: [sdc] Write Protect is off
[ 9100.310584] sd 9:0:0:0: [sdc] Mode Sense: 00 12 00 00
[ 9100.312846] sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9100.318947] sd 9:0:0:1: [sdd] Attached SCSI removable disk
[ 9100.323474] ldm_validate_partition_table(): Disk read failed.
[ 9100.323494] Dev sdc: unable to read RDB block 0
[ 9100.323519] sdc: unable to read partition table
[ 9100.352934] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[ 9100.353059] sd 9:0:0:0: [sdc] Synchronizing SCSI cache
[ 9100.358341] scsi 9:0:0:0: rejecting I/O to offline device
[ 9100.358346] scsi 9:0:0:0: killing request
[ 9112.486330] usb 1-1.2: USB disconnect, device number 7

Petr

Alan Stern píše v Po 24. 12. 2012 v 11:12 -0500:

[Alan Stern]

On Sat, 29 Dec 2012, Petr [ISO-8859-1] Kub�nek wrote:

> Hi Alan,
>
> please find it attached. Let me know if you need more help/other
> output/.... Dmesg claimed:
>
> [ 9100.300027] scsi 9:0:0:0: Direct-Access GENERIC DPF NAND 1.00 PQ: 0 ANSI: 0 CCS
> [ 9100.301723] scsi 9:0:0:1: Direct-Access GENERIC DPF SD/MMC/XD 1.00 PQ: 0 ANSI: 0 CCS
> [ 9100.302155] sd 9:0:0:0: Attached scsi generic sg2 type 0
> [ 9100.302330] sd 9:0:0:1: Attached scsi generic sg3 type 0
> [ 9100.308599] sd 9:0:0:0: [sdc] 3770368 512-byte logical blocks: (1.93 GB/1.79 GiB)
> [ 9100.310579] sd 9:0:0:0: [sdc] Write Protect is off
> [ 9100.310584] sd 9:0:0:0: [sdc] Mode Sense: 00 12 00 00
> [ 9100.312846] sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [ 9100.318947] sd 9:0:0:1: [sdd] Attached SCSI removable disk
> [ 9100.323474] ldm_validate_partition_table(): Disk read failed.
> [ 9100.323494] Dev sdc: unable to read RDB block 0

The usbmon trace shows that some program is trying to access the
pictuyre frame and is sending commands that the picture frame doesn't
handle correctly. When it gets these commands, the picture frame
crashes.

Unfortunately I don't know of any easy way to tell what program is
sending the bad commands. It may be some tool started by udev.

Alan Stern

[Petr Kubánek]

Hi Alan,

I found rule in udev, which called usb_modeswitch. This was apparently
mistake. Commenting it out makes the device working as expected.

Later, I will try to contact udev maintainer, to either explain or
remove this rule.

Petr

Alan Stern píše v Ne 30. 12. 2012 v 13:34 -0500:

> --
> You received this message because you are subscribed to the Google Groups "USB Mass Storage on Linux" group.
> To post to this group, send email to usb-s...@lists.one-eyed-alien.net.
> To unsubscribe from this group, send email to usb-storage...@lists.one-eyed-alien.net.
> For more options, visit this group at http://groups.google.com/a/lists.one-eyed-alien.net/group/usb-storage/?hl=en.
>

[Alan Stern]

On Sun, 20 Jan 2013, Petr [ISO-8859-1] Kub�nek wrote:

> Hi Alan,
>
> I found rule in udev, which called usb_modeswitch. This was apparently
> mistake. Commenting it out makes the device working as expected.
>
> Later, I will try to contact udev maintainer, to either explain or
> remove this rule.

First you should contact the usb_modeswitch maintainer: Josua Dietze
<digid...@draisberghof.de>.

Alan Stern

[linux.ren...@gmail.com]

Hello ,

Any news on this issue? Im having the same problem.

Thanks,
Daniel

[moresun]

My Hama 10SLP Digital Photo Frame did not work under Ubuntu 14.04
I used the command lsusb to and found the related entry:
Bus 001 Device 008: ID 1de1:1101 Actions Microelectronics Co. Generic Display Device (Mass storage mode)
Afterwards I checkt the file /lib/udev/rules.d/40-usb_modeswitch.rules and found an entry for the device:
# Philips PicoPix 1020 Projector
ATTR{idVendor}=="1de1", ATTR{idProduct}=="1101", RUN+="usb_modeswitch '%b/%k'"
I just removed the entry by adding a # and now the frame works like a usb-stick.
#ATTR{idVendor}=="1de1", ATTR{idProduct}=="1101", RUN+="usb_modeswitch '%b/%k'"

Greetings
moresun

[mar...@baders.eu]

Check the file  /lib/udev/rules.d/40-usb_modeswitch.rules  and remove the entry for 1de1:1101
It worked on my Ubuntu 14.04 with a Hama 10SLP Digital Photo Frame

Geetings
Markus

Am Dienstag, 15. September 2015 16:16:28 UTC+2 schrieb linux.ren...@gmail.com:

[sdown...@gmail.com]

Worked for me. Question is why is that rule in there if it does not work?

[Eddy Manuel Sanchez]

Just perfect, it worked for me too, I had this disk on my PC and the board damaged for som reason, and my disk was with all the information inaccessible, thank you.