LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-24-2005, 07:05 AM   #1
systematicni
LQ Newbie
 
Registered: Dec 2005
Posts: 4

Rep: Reputation: 0
Question sony ericsson v600i usb-storage


I have just got a vodafone branded sony ericsson v600i phone and am struggling to work out how to transfer files (photos and mp3s) over the usb cable. I am running ubuntu linux on the desktop.

When I plug in the usb cable to the phone and my linux box (ubuntu) I can see the tty serial (modem) device in the /var/log/messages but no mention of usb-storage.

I ran lsusb -v and got the device and manufacturer ids 0fce:d017 then I opened the file /lib/modules/2.6.10-5-386/modules.usbmap and add the line

usb-storage 0x003 0x0fce 0xd017 0x0000 0x0000 0x000 0x00 0x00 0x00 0x00 0x00

If I then plug in the usb cable again and tail /var/log/messages then the usb-storage module is loaded (or I get a message that it is already loaded). There is still nothing about scsi or sda or dev.... ie there is no storage device recognised....

a) has anyone got a v600 or k600 phone to work with linux over usb?
b) how did you do it?
c) any ideas on where I should look next to get a mountable device?


Thanks
 
Old 12-29-2005, 11:24 AM   #2
ankscorek
Member
 
Registered: Mar 2003
Distribution: Slackware10.2,SUSE,FC,RHL,Vector Linux,WHAX,PHLAK,bt4,ubuntu,debian,aptosid,backtrack,blackbuntu
Posts: 529

Rep: Reputation: 31
type

#tail -f /var/log/messages

plug in your mass storage device

and now give ht eo/p of the log
 
Old 12-29-2005, 12:13 PM   #3
systematicni
LQ Newbie
 
Registered: Dec 2005
Posts: 4

Original Poster
Rep: Reputation: 0
Hi ankscorek, thanks for the response. I have just plugged in the usb cable and tailed the /var/log/messages. I also included the lsusb output, which seems to show a number of available interfaces....

Thanks for your advice.

# tail -f /var/log/messages

Code:
Dec 29 17:02:46 localhost kernel: usb 3-1: new full speed USB device using uhci_hcd and address 2
Dec 29 17:02:47 localhost usb.agent[7256]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7298]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7355]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7351]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7340]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7319]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7235]:      cdc-acm: loaded successfully
Dec 29 17:02:47 localhost usb.agent[7277]:      cdc-acm: loaded successfully
Dec 29 17:02:47 localhost usb.agent[7277]:      usb-storage: already loaded
Dec 29 17:02:47 localhost usb.agent[7235]:      usb-storage: already loaded
Dec 29 17:02:47 localhost kernel: cdc_acm 3-1:1.1: ttyACM0: USB ACM device
Dec 29 17:02:47 localhost kernel: cdc_acm 3-1:1.3: ttyACM1: USB ACM device
Dec 29 17:02:47 localhost kernel: usbcore: registered new driver cdc_acm
Dec 29 17:02:47 localhost kernel: drivers/usb/class/cdc-acm.c: v0.23:USB Abstract Control Model driver for USB modems and ISDN adapters
#lsusb
Code:
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0fce:d017 Sony Ericsson Mobile Communications AB
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 06b9:4061 Alcatel Telecom Speed Touch ISDN or ADSL Modem
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 03f0:3b11 Hewlett-Packard
Bus 001 Device 003: ID 050d:0050 Belkin Components
Bus 001 Device 001: ID 0000:0000
#lsusb -v -s 003:002
Code:
Bus 003 Device 002: ID 0fce:d017 Sony Ericsson Mobile Communications AB
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0fce Sony Ericsson Mobile Communications AB
  idProduct          0xd017
  bcdDevice            0.00
  iManufacturer           1
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          239
    bNumInterfaces          8
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower               20mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass         2 Communications
      bInterfaceSubClass      8 Wireless Handset Control
      bInterfaceProtocol      0
      iInterface              4
      CDC Header:
        bcdCDC               1.10
      UNRECOGNIZED:  05 24 11 00 01
      UNRECOGNIZED:  0b 24 08 00 01 02 03 04 05 06 07
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              5
      CDC Header:
        bcdCDC               1.10
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         2
      CDC Call Management:
        bmCapabilities       0x03
          call management
          use DataInterface
        bDataInterface          2
      CDC ACM:
        bmCapabilities       0x07
          sends break
          line coding and serial state
          get/set/clear comm features
      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              16
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0
      iInterface              6
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 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     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              7
      CDC Header:
        bcdCDC               1.10
      CDC Union:
        bMasterInterface        3
        bSlaveInterface         4
      CDC Call Management:
        bmCapabilities       0x03
          call management
          use DataInterface
        bDataInterface          4
      CDC ACM:
        bmCapabilities       0x07
          sends break
          line coding and serial state
          get/set/clear comm features
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              16
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0
      iInterface              8
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 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     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass         2 Communications
      bInterfaceSubClass     11 OBEX
      bInterfaceProtocol      0
      iInterface              9
      CDC Header:
        bcdCDC               1.10
      UNRECOGNIZED:  05 24 15 00 01
      CDC Union:
        bMasterInterface        5
        bSlaveInterface         6
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass        10 Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0
      iInterface             10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass        10 Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0
      iInterface             11
      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     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        7
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      9 Device Management
      bInterfaceProtocol      1
      iInterface             12
      CDC Header:
        bcdCDC               1.10
      UNRECOGNIZED:  07 24 14 00 01 00 08
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              16
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
 
Old 12-29-2005, 07:54 PM   #4
ankscorek
Member
 
Registered: Mar 2003
Distribution: Slackware10.2,SUSE,FC,RHL,Vector Linux,WHAX,PHLAK,bt4,ubuntu,debian,aptosid,backtrack,blackbuntu
Posts: 529

Rep: Reputation: 31
build in the scsi device support in your kernel
 
Old 12-30-2005, 02:46 AM   #5
systematicni
LQ Newbie
 
Registered: Dec 2005
Posts: 4

Original Poster
Rep: Reputation: 0
Thanks for the advice but I believe there is scsi support in the kernel..... when I plug in my Olympus camera using the usb cable it is mounted, and cards inserted into my HP all in one device are also mounted. I have included tails of the log files below.

I wonder if the phone is using some non-standard method to access its storage device which is not recognised by the linux kernel? I see in the lsusb -v output that there are bulk storage devices listed but then I cannot get to them. I have no idea how the device is meant to be recognised so no idea how to test/debug.

I also see there is an Obex device listed...I wonder can I use some obexftp (bluetooth?) software over the usb cable to manage file transfers? Again this is an untested idea and I have never used any obex software, so there is a fair amount of learning /trail and error down that path too...

Thanks again for your advice.

Code:
Dec 30 07:19:36 localhost kernel:   Vendor: OLYMPUS   Model: C150,D390         Rev: 1.00
Dec 30 07:19:36 localhost kernel:   Type:   Direct-Access                      ANSI SCSI revision: 00
Dec 30 07:19:36 localhost kernel: SCSI device sdb: 127945 512-byte hdwr sectors (66 MB)
Dec 30 07:19:36 localhost kernel: sdb: Write Protect is off
Dec 30 07:19:36 localhost kernel: SCSI device sdb: 127945 512-byte hdwr sectors (66 MB)
Dec 30 07:19:36 localhost kernel: sdb: Write Protect is off
Dec 30 07:19:36 localhost kernel:  /dev/scsi/host2/bus0/target0/lun0:
Dec 30 07:19:36 localhost kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
Dec 30 07:19:36 localhost scsi.agent[10923]:      sd_mod: loaded sucessfully
Similarly if I put a memory cardinto the HP 1350 psc all-in-one printer/scanner/card-reader the card is mounted correctly:

Code:
Dec 30 07:27:08 localhost kernel: SCSI device sda: 128000 512-byte hdwr sectors (66 MB)
Dec 30 07:27:08 localhost kernel: sda: Write Protect is off
Dec 30 07:27:08 localhost kernel: SCSI device sda: 128000 512-byte hdwr sectors (66 MB)
Dec 30 07:27:08 localhost kernel: sda: Write Protect is off
Dec 30 07:27:11 localhost kernel:  /dev/scsi/host1/bus0/target0/lun0: p1
 
Old 12-30-2005, 06:02 AM   #6
ankscorek
Member
 
Registered: Mar 2003
Distribution: Slackware10.2,SUSE,FC,RHL,Vector Linux,WHAX,PHLAK,bt4,ubuntu,debian,aptosid,backtrack,blackbuntu
Posts: 529

Rep: Reputation: 31
yeah u r right ......

it is taking as sda

is your pendrive working fine in Windows XP
 
Old 01-04-2006, 02:02 PM   #7
systematicni
LQ Newbie
 
Registered: Dec 2005
Posts: 4

Original Poster
Rep: Reputation: 0
some success ...

ankscorek thanks for your advice and prompts, I now believe that the phone does not expose a usbstorage device. i know that it can be accessed over the usb cable using the software from SonyEricsson - but I think it uses weird drivers...

I can now transfer files eg mp3s onto the phone and pictures off the phone...

but I have not managed to get a useful file system access..so there is room for improvement.

What I did was buy a bluetooth usb dongle (from usbtech in uk delivered next day with free develiery!). I then installed the ubuntu bluez-utils and obexserver packages using aptitude.

Push files from pc to phone using gnome-obex-send. The phone puts them in the right directory based on the extension (.mp3, .gif, .jpg etc). I found that if I right click a file and then choose Open With and then select command and enter "gnome-obex-send" then that option is quickly available if i want to send a file of the same type... room for improvement but better than typing!

Push files from phone to PC... I could not get gnome-obex-server to work, however I can get obexserver to run. Unfortunately you have to start obexserver at the commandline before each transfer. After much angst I discovered that you can enter a directory on the phone and then mark all the files, and then send them all over bluetooth... so I have transferred all my phootos while having dinner! again not perfect but I have most of the funtionality I need.


For future reference of anyone interested: here is a working command sequence

Code:
root@linuxserver:/home/paul # /etc/init.d/bluez-utils stop
 * Stopping Bluetooth services...                                        [ ok ]
root@linuxserver:/home/paul # hcid
root@linuxserver:/home/paul # sdpd
root@linuxserver:/home/paul # sdptool add --channel=10  OPUSH
OBEX Object Push service registered
root@linuxserver:/home/paul # obexserver
Waiting for connection...

...................................................... ...................................................... ................................................HEADER _LENGTH = 158073
Filename = DSC00026.JPG
Wrote /tmp/DSC00026.JPG (158073 bytes)


root@linuxserver:/home/paul # obexserver
Waiting for connection...

...................................................... ...................................................... ...................................................... HEADER_LENGTH = 164747
Filename = DSC00024.JPG
Wrote /tmp/DSC00024.JPG (164747 bytes)


root@linuxserver:/home/paul # obexserver
Waiting for connection...

...................................................... ...................................................... ...................................................... ..........HEADER_LENGTH = 174135
Filename = DSC00023.JPG
Wrote /tmp/DSC00023.JPG (174135 bytes)


root@linuxserver:/home/paul # obexserver
Waiting for connection...

........HEADER_LENGTH = 7724
Filename = City.jpg
Wrote /tmp/City.jpg (7724 bytes)

..........................................HEADER_LENGT H = 42461
Filename = Yellow Flower.jpg
Wrote /tmp/Yellow Flower.jpg (42461 bytes)

...........HEADER_LENGTH = 10850
Filename = Windsurfer.jpg
Wrote /tmp/Windsurfer.jpg (10850 bytes)

.........HEADER_LENGTH = 8785
Filename = Sunset.jpg
Wrote /tmp/Sunset.jpg (8785 bytes)
Before transfering the files I went to Settings/Connectivity/Bluetooth/MyDevices on the phone deleted the previous attempt to pair the device. Enetered the commands above to start obexserver, then on the phone Settings/Connectivity/Bluetooth/MyDevices "Add new" device found the PC, search services found Obex Push. When prompted for passwords on the Phone and PC enter whatevver you put in /etc/bluetooth/pin.

Then I went to my Camera Pictures folder , right click select Mark/MarkAll, then Send/Bluetooth and hey presto.... dinner time.

I have not managed to pull files from the phone (ie to get something off the phone I have to send it from the phone over iR or Bluetooth). I did get obexftp (compiled from source) to get a directory listing from the phone over the usb cable. obexftp also pushed files to the phone over the usb cable.

Hope this gives inspiration to someone!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Sony Ericsson P900 Meriadoc Linux - Laptop and Netbook 4 06-29-2009 09:57 AM
Sony Ericsson Z500a Matir Linux - Hardware 2 08-08-2006 07:27 PM
how to auto-mount usb storage mirto Slackware 7 01-05-2006 11:48 AM
Sony Ericsson T230 Themes kamransoomro84 General 0 03-12-2005 07:19 PM
Syncing my Sony Ericsson T610 johnnycakes79 Linux - Laptop and Netbook 7 12-12-2004 07:06 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration