Problems connecting Samsung YP-S3 Ogg Vorbis Player

**Rabenschwinge** · August 2nd, 2008

Hello,

since I had I accidently gave my last Ogg Vorbis player a ride in the washing machine I bought a new one - Samsung, same as last. But somehow udev does not seem to handle it correctly, while I can see it in lsusb it does not mount automatically. Is there anyway to enforce this, or to mount it manually?

syslog excerpts:

Code:

Aug  2 15:31:02 schatten kernel: [ 3020.537210] usb 2-10: new high speed USB device using ehci_hcd and address 7
Aug  2 15:31:02 schatten kernel: [ 3020.670203] usb 2-10: configuration #1 chosen from 1 choice
Aug  2 15:31:02 schatten NetworkManager: <debug> [1217683862.858713] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4e8_5091_363f4618000000d9'). 
Aug  2 15:31:02 schatten NetworkManager: <debug> [1217683862.887365] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_4e8_5091_363f4618000000d9_if0').

lsusb -v output:

Code:

Bus 002 Device 007: ID 04e8:5091 Samsung Electronics Co., Ltd 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x04e8 Samsung Electronics Co., Ltd
  idProduct          0x5091 
  bcdDevice            1.00
  iManufacturer           1 Samsung Electronics Co.,Ltd.
  iProduct                2 S3
  iSerial                 3 363f4618000000d9
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      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     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     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               2
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:     0x0001
  Self Powered

**stoneater** · August 13th, 2008

The Samsung S3 is an MTP-only device.

The problem is the mtp support over linux.
MTP is an extension of the USB standard, and it is made by Microsoft.
As a result MTP support on linux is not complete.
I've been searching a lot to solve this problem.
The only way for me was to setup a virtual machine with windows inside linux....
I think we have to wait a new firmware by samsung enabling UMS support (it works just like and usb drive) or wait for a better MTP support on Linux
Anyway I saw there is a new firmware there:
http://www.anythingbutipod.com/forum...ad.php?t=32690
but I didn't test it.

Regards
Stoneater

**mlaverdiere** · August 30th, 2008

Here's what I did to have the Samsung YP-S3 works perfectly in UMS mode with Ubuntu Hardy (after some digging, fumbling, try & error, etc.):

1. First, a functional UMS firmware must be installed on the S3. The one available right now is provided by Samsung Korea (See this page an updated and complete list of available firmwares. It has to be installed with the the proper config.dat file (description after) at the root of the device, then, after unplugging the device, the firmware upgrade/change will be performed automatically. Obviously, to be able to do this, the device has to be mounted first in MTP mode. I did this with Windows XP (with Windows Media Player, version 10 or superior installed). It's probably possible to do it with Ubuntu by now, after having installed mtpfs (sudo apt-get install mtpfs) and fumbling around with config files. Here's some more info:

The config.dat file has to be created, with the following content:

YP-S3
KR KO UMS

With this file, you will have the Korean language activated, but you'll be able to switch to your preferred language in the /settings/language menu (I think I have managed once to perform the upgrade by using "US US UMS" instead of "KR KO UMS" and then having English as the interface language, but I'm not sure; anyway, the "KR KO UMS" was suggested in one forum and for sure, it worked).
Other interesting ressources:
- For a complete liste of Samsung YP (and other DAP) firmwares, see this unofficial page
- For another description of the procedure, see this thread
- If yout want to try to have the S3 work in MTP mode under Linux/Ubuntu, see this and this; (Note: I didn't try seriously to make the S3 mount in MTP mode with Linux, so I'm not sure if it will work... but I think it could!)

2. Once the UMS firmware is correctly installed, plug the S3 and you should have 2 new removable USB media storage devices recognized, one big (3.7 GB) for the data (music, video, etc,) and another one small (40 MB) that appears to be reserved for the S3 ROM, with system and config files; If, like me, you just want the data partition (the big 3.7 GB one) to be automounted and visible, you can add this line in your fstab file (make sure that the UUID corresponds to the one allocated to the S3 system/config partition on your system

UUID=0000-CCCC vfat rw,nosuid,nodev,relatime,uid=1000,fmask=0077,dmask =0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,noauto 0 0

3. In Ubuntu Hardy, the S3 (with the UMS firmware) is recognized as a regular USB device, instead of a Digital Audio Player (DAP). It doesn't prevent you to move music (or other) files on the S3 with Nautilus (or other file manager) and play them, but it may be annoying since audio application, like Rhythmbox, won't be able to recognize the device correctly; To have the S3 recognized as a DAP, see the solution provided in this bug report (in fact, this is not really a bug, since the S3 is quite new; this report has been made with the hope that future Ubuntu versions will automatically recognize the S3 as a DAP).

In order to have the modification effective, don't forget to run the following command: sudo /etc/init.d/hal restart

Hope this helps.

**whitmad** · September 16th, 2008

Splendid - this worked just fine for me with only one small alteration - the root directory of my S3 when connected to Windows XP was not writeable, but copying the S3.ROM and config.dat files to the Data directory had the desired effect.

Many thanks

**agoodno** · November 16th, 2008

I've followed all the directions posted by mlaverdiere and my device is showing now Korean firmware (Settings->System->About reports Firmware Version 1.50c KR) and I've switched back to English language. The problem is now Hardy is not mounting it. Using dmesg, I've verified that it is being recognized but is saying:

[98473.127162] usb 4-6: new high speed USB device using ehci_hcd and address 4
[98473.260194] usb 4-6: configuration #1 chosen from 1 choice

I've read up on udev and udevinfo and think I need to manually mount but don't know which device to use. So,

sudo mount /dev/<usb46?> /mnt/usb

So, how do I find the device name and why is it not automounting?

Andy

**mlaverdiere** · November 16th, 2008

Hum, it should mount automatically, like any other UMS USB device...

Anyway, you can try the following command to figure out what's going on and try to manually mount your S3:

1. Just after you have plugged the S3, type the following command:

dmesg

You should see something like this, at the end of the output:

[47260.132085] usb 2-3: new high speed USB device using ehci_hcd and address 5
[47260.269919] usb 2-3: configuration #1 chosen from 1 choice
[47260.270898] scsi12 : SCSI emulation for USB Mass Storage devices
[47260.273001] usb-storage: device found at 5
[47260.273046] usb-storage: waiting for device to settle before scanning
[47266.272633] usb-storage: device scan complete

If you don't see anything like this, it would probably mean that the kernel is not recognizing the S3 (it could be the case if you use a custom compile kernel).

2. Now use the following command

sudo fdisk -l

It should report something like this (sorry, my system is in French, but you should get the idea, i.e. the red part indicates that the S3 is mountable on /dev/sdc1, being a 4GB fat16 partition):

Disque /dev/sda: 250.0 Go, 250059350016 octets
255 heads, 63 sectors/track, 30401 cylinders
Units = cylindres of 16065 * 512 = 8225280 bytes
Identifiant disque: 0xb0016565

Périphérique Amorce Début Fin Blocs Id Système
/dev/sda1 * 1 4042 32467333+ 7 HPFS/NTFS
/dev/sda2 29158 30401 9988096 7 HPFS/NTFS
/dev/sda3 4043 29157 201736237+ 5 Extended
/dev/sda5 4043 28134 193518958+ 83 Linux
/dev/sda6 28135 29157 8217216 82 Linux swap / Solaris

Les entrées de la table de partitions ne sont pas dans l'ordre du disque

Disque /dev/sdc: 4030 Mo, 4030692864 octets
255 heads, 63 sectors/track, 490 cylinders
Units = cylindres of 16065 * 512 = 8225280 bytes
Identifiant disque: 0xffffffff

Périphérique Amorce Début Fin Blocs Id Système
/dev/sdc1 1 485 3893244 6 FAT16
Partition 1 a des débuts différents physique/logique (non Linux?):
phys=(1023, 254, 63) logique=(0, 0, 9)
Partition 1 a des fins différentes physique/logique:
phys=(1023, 254, 63) logique=(484, 175, 11)

3. Now, you should be able to mount the S3 as /dev/sdc1 (based on the above output - on your system, it may be different) as a vfat device, on a mounting point (directory) that you have manually created (let's say /media/S3) with the following command:

sudo mount -t vfat /dev/sdc1 /media/S3

Hope this helps.