[ilvalle]

Dear all,
To some extent I can say that I successfully run a vodafone key 14.4, K3806-Z by using sakis3g scripts on a raspberry-pi powered by raspbian. This is the key:

Code: Select all

pi@raspberrypi ~ $ lsusb -s 7
Bus 001 Device 007: ID 19d2:1013 ZTE WCDMA Technologies MSM

The key works if I plug it when the raspberry is already running. In this case I can see from dmesg that automatically it has been switched, and with lsusb I can see that the product id is slictly different, from 19d2:1013 to 19d2:1015.

However, the key doesn't work if the raspberry boots with the key already attached. I tried:

Code: Select all

    pi@raspberrypi ~ $ sudo usb_modeswitch -W -v 19d2 -p 1013 -c /usr/share/usb_modeswitch/19d2:1013

    Reading config file: /usr/share/usb_modeswitch/19d2:1013

     * usb_modeswitch: handle USB devices with multiple modes
     * Version 1.2.3 (C) Josua Dietze 2012
     * Based on libusb0 (0.1.12 and above)

     ! PLEASE REPORT NEW CONFIGURATIONS !

    DefaultVendor=  0x19d2
    DefaultProduct= 0x1013
    TargetVendor=   0x19d2
    TargetProduct=  0x1015
    TargetClass=    not set
    TargetProductList=""

    DetachStorageOnly=0
    HuaweiMode=0
    SierraMode=0
    SonyMode=0
    QisdaMode=0
    GCTMode=0
    KobilMode=0
    SequansMode=0
    MobileActionMode=0
    CiscoMode=0
    MessageEndpoint=  not set
    MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
    NeedResponse=1
    ResponseEndpoint= not set

    InquireDevice enabled (default)
    Success check disabled
    System integration mode disabled


    usb_set_debug: Setting debugging level to 15 (on)
    usb_os_find_busses: Found 001
    usb_os_find_devices: Found 006 on 001
    skipped 1 class/vendor specific interface descriptors
    skipped 1 class/vendor specific interface descriptors
    usb_os_find_devices: Found 005 on 001
    usb_os_find_devices: Found 004 on 001
    usb_os_find_devices: Found 003 on 001
    usb_os_find_devices: Found 002 on 001
    usb_os_find_devices: Found 001 on 001
    error obtaining child information: Inappropriate ioctl for device
    error obtaining child information: Inappropriate ioctl for device
    error obtaining child information: Inappropriate ioctl for device
    Looking for target devices ...
      searching devices, found USB ID 05ac:020c
      searching devices, found USB ID 19d2:1013
       found matching vendor ID
      searching devices, found USB ID 05ac:1003
      searching devices, found USB ID 0424:ec00
      searching devices, found USB ID 0424:9512
      searching devices, found USB ID 1d6b:0002
     No devices in target mode or class found
    Looking for default devices ...
      searching devices, found USB ID 05ac:020c
      searching devices, found USB ID 19d2:1013
       found matching vendor ID
       found matching product ID
       adding device
      searching devices, found USB ID 05ac:1003
      searching devices, found USB ID 0424:ec00
      searching devices, found USB ID 0424:9512
      searching devices, found USB ID 1d6b:0002
     Found device in default mode, class or configuration (1)
    Accessing device 005 on bus 001 ...
    Getting the current device configuration ...
     OK, got current device configuration (1)
    Using first interface: 0x00
    Using endpoints 0x01 (out) and 0x81 (in)
    Inquiring device details; driver will be detached ...
    Looking for active driver ...
    USB error: could not get bound driver: No data available
     No driver found. Either detached before or never attached

    SCSI inquiry data (for identification)
    -------------------------
      Vendor String: Vodafone
       Model String: USB SCSI CD-ROM
    Revision String: 0001
    -------------------------

    USB description data (for identification)
    -------------------------
    Manufacturer: Vodafone (ZTE)
         Product: K3806-Z
      Serial No.: 81C1E060980851E27847AAF80DD57B43FBCFFA7B
    -------------------------
    Setting up communication with interface 0
    Using endpoint 0x01 for message sending ...
    Trying to send message 1 to endpoint 0x01 ...
     OK, message successfully sent
    Reading the response to message 1 (CSW) ...
     Response reading got error -110
     Device is gone, skipping any further commands
    -> Run lsusb to note any changes. Bye.

but the key didn't switch at all.
What it means this error:
USB error: could not get bound driver: No data available
No driver found. Either detached before or never attached

What can I do to fix the problem that the key works only if I attach it after boot?

Paolo

[benxico]

Hello,

it seems there is a bug on the raspberry pi for the USB modeswitch.
With a Huawei E173s I have similar problem :
http://www.draisberghof.de/usb_modeswit ... =raspberry

As LOM told me :

Raspberry Pi has USB port problems (google it ) and that is likely the reason for the misbehaviour that you see.

I have decided to use an other USB modem, because the only way to use the E173s would be to put a little relay on the power cable (red cable) on the usb cable, an to manage directly this relay from the GPIO to allow power off and power on the USB port of the E173s. This way it's possible to switch the E173s from "modem off to modem on".
But it was easier for me to use E220 that is working fine with the raspberry pi.

Hope this could be usefull for you.

Bests Regards,

Benxico