Author Message

<  Device Information  ~  Haier CE682 (smartfren connect)

PostPosted: Sat Dec 10, 2011 6:15 am
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
Hi Josh,

I have a new haier ce682, it's still not supported by usb_modeswitch. I have tried to configure it but failed, and now i have to eject and modprobe manually before can connect to my isp. Here's my device data

Code:
# lsusb -v
Bus 002 Device 004: ID 201e:1023 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x201e
  idProduct          0x1023
  bcdDevice            0.00
  iManufacturer           1 China TeleCom
  iProduct                2 CBP7.1
  iSerial                11 ÿÿÿÿÿÿÿÿÿÿ
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 CONF1
    bmAttributes         0x40
      (Missing must-be-set bit!)
      Self Powered
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              9 Data Interface3
      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
Device Status:     0x0001
  Self Powered


It shows that the id is 201e:1023 but actually to work with the modem or after we eject the cd it changes to 201e:1022. Here's my usb_modeswitch config,

Code:
########################################################
# /etc/usb_modeswitch.conf
#
# Smart Haier CE682 (EVDO)
#

DefaultVendor=0x201e
DefaultProduct=0x1023

TargetVendor=0x201e
TargetProduct=0x1022

MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
#MessageContent="55534243f08cf1842400000080000612000000240000000000000000000000"

#MessageContent="55534243a82449852400000080000612000000240000000000000000000000"


#0x04: 55534243f08cf1842400000080000612000000240000000000000000000000
#0x84: 008000011f0000005344564449534b004556444f205265562041202020202000372e3030
#04: 55534243a82449852400000080000612000000240000000000000000000000

#04: 55534243080b5c8f0800000080000a25000000000000000000000000000000


I tried so many string but none is working. Here's my usb_modeswitch log from the above config,

Code:
Reading config file: /etc/usb_modeswitch.d/201e:1023

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

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x201e
DefaultProduct= 0x1023
TargetVendor=   0x201e
TargetProduct=  0x1022
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="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=1
ResponseEndpoint= not set

InquireDevice enabled (default)
Success check enabled, max. wait time 20 seconds
System integration mode disabled


Looking for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Found devices in default mode, class or configuration (1)
Accessing device 004 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x04 (out) and 0x84 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 No driver found. Either detached before or never attached

SCSI inquiry data (for identification)
-------------------------
  Vendor String: CDROM
   Model String: EVDO ReV A
Revision String: 7.00
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: China TeleCom
     Product: CBP7.1
  Serial No.: ÿÿÿÿÿÿÿÿÿÿ
-------------------------
Setting up communication with interface 0
Using endpoint 0x04 for message sending ...
Trying to send message 1 to endpoint 0x04 ...
 OK, message successfully sent
Reading the response to message 1 (CSW) ...
 OK, response successfully read (13 bytes).
Resetting response endpoint 0x84
Resetting message endpoint 0x04
 Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 No new devices in target mode or class found

Mode switch has failed. Bye.


And for the usb sniif log, can be downloaded from this link. I tried several time to include in this message but failed.

Could you help?

Best regard.


Offline Profile YIM
PostPosted: Sat Dec 10, 2011 10:35 am
Site AdminPosts: 4830Joined: Sat Nov 03, 2007 12:30 am
Your sniffing log seems to be from the modem mode of your device. There is no switching sequence in there because the mode switching was already completed before.

But never mind, I suppose you have overlooked the existing configuration for the Haier CE 100. It's likely that you can just copy the mode switching command from there.

See the file "201e:2009" in the current data package release (source folder). Copy it to "201e:1023" and adjust the "DefaultProduct" parameter inside to match your device (DefaultProduct=0x1023).

Then copy the existing Haier line in "40-usb_modeswitch.rules" and paste it somewhere,
again adjusting the product ID (ATTRS{idProduct}=="1023").

If you reinstall the modified data package, your device should be supported automatically.

Don't put any device configuration into /etc/usb_modeswitchconf !!



Offline Profile
PostPosted: Sat Dec 10, 2011 1:11 pm
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
Josh,

It's switched now.. but there's still error from usb_modeswitch (at the arrow sign) and no modprobe action. And i think it's because of the error, am i right here? Is it possible to autorun the modprobe after the switching's done?

Here's usb_modeswitch log.

Code:

USB_ModeSwitch log from Sat Dec 10 17:58:19 WIT 2011

Raw args from udev: /2-2:1.0

Using global config file: /etc/usb_modeswitch.conf
Bus ID for device not given by udev.
 Trying to determine it from kernel name (2-2:1.0) ...
----------------
USB values from sysfs:
  manufacturer   China TeleCom
  product   CBP7.1
  serial   ÿÿÿÿÿÿÿÿÿÿ
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /etc/usb_modeswitch.d/201e:1023
Using config file from override folder /etc/usb_modeswitch.d
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -D -u -1 -f $configBuffer)

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are expected in the process)
--------------------------------

Reading long config from command line

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

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x201e
DefaultProduct= 0x1023
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    0xff
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="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled


Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 201e:1023
   found matching vendor ID
   found matching product ID
   target class ff not matching
   adding device
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Found devices in default mode, class or configuration (1)
Accessing device 004 on bus 002 ...
Skipping the check for the current configuration
Using first interface: 0x00
Using endpoints 0x04 (out) and 0x84 (in)

USB description data (for identification)
-------------------------
Manufacturer: China TeleCom
     Product: CBP7.1
  Serial No.: ������------------------------
Looking for active driver ...
 OK, driver found; name unknown, limitation of libusb1
 OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x04 for message sending ...
Trying to send message 1 to endpoint 0x04 ...
 OK, message successfully sent
Reading the response to message 1 (CSW) ...
 OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x04 ...
libusb:warning [do_sync_bulk_transfer] unrecognised status code 1                     <-----------
libusb:error [op_clear_halt] clear_halt failed error -1 errno 71                                <-----------
libusb:error [op_clear_halt] clear_halt failed error -1 errno 71                                <-----------
 OK, message successfully sent
Reading the response to message 2 (CSW) ...
 OK, response successfully read (13 bytes).
Resetting response endpoint 0x84
 Could not reset endpoint (probably harmless): -34                                                  <---------
Resetting message endpoint 0x04
 Could not reset endpoint (probably harmless): -34                                                  <---------
 Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 201e:1022
   found matching vendor ID
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
 No new devices in target mode or class found

Mode switch has failed. Bye.

fail:
--------------------------------
(end of usb_modeswitch output)


All done, exiting




>Don't put any device configuration into /etc/usb_modeswitchconf !!

Ohh.. i've deleted my old /etc/usb_modeswitch.d directory when installing the new version and
now that directory is only a symlink to usb_modeswitch dir (/usr/share/.....). As i've taken a look
at the new dir, it is better.


Best regard.
Ebed


Offline Profile YIM
PostPosted: Sat Dec 10, 2011 3:49 pm
Site AdminPosts: 4830Joined: Sat Nov 03, 2007 12:30 am
The libusb error is expected when the device is switching. You can ignore it.

If you change your new config file to reflect the values of your device, you will get a success report:

- Delete the TargetProductClass line

- Add "TargetVendor=0x201e"

- Add "TargetProduct=0x1022"



Offline Profile
PostPosted: Sat Dec 10, 2011 5:12 pm
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
Wow... it works flawlessly.

Thanks alot josh.



Best regard.
Ebed


Offline Profile YIM
PostPosted: Sat Dec 10, 2011 7:27 pm
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
Josh wrote:
Your sniffing log seems to be from the modem mode of your device. There is no switching sequence in there because the mode switching was already completed before.


I just understood why you said this.. that my log i sended to you was happened after the device successfully switched. I resniff my usb by installing and deinstalling the driver so many time, finally i understand which part of the string have to be send to my usb. Here's the new config, however i still include the last string you told me.. just in case... but it's ok after i reboot my system without the modem then plug it in again.

Code:

########################################################
# /etc/usb_modeswitch.conf
#
# Smart Haier CE682 (EVDO)
#

DefaultVendor=0x201e
DefaultProduct=0x1023

TargetVendor=0x201e
TargetProduct=0x1022
 
#MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
#MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"

MessageContent="55534243b076e484c000000080000671030000000000000000000000000000"
NeedResponse=1

CheckSuccess=20





Best regard.
Ebed.


Offline Profile YIM
PostPosted: Sun Dec 11, 2011 4:13 am
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
Josh,

I think i find a bug. Last night i turned off the logging (in /etc/usb_modeswitch.conf) before i went to bed, this morning i turned on my computer and found my modem couldn't connect. After a little check i found there's no ttyUSB and module usbserial wasn't in the lsmod, i turned on the logging again, turned off my computer, unpluged the power, make it back to on again and reboot, the problem was gone. I guess its a bug in the usb_modeswitch as i had tried to test it using the 3 messageContent strings above, and found the same mistake.




Best regard.
Ebed.


Offline Profile YIM
PostPosted: Mon Dec 12, 2011 8:18 am
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
For all who have haier ce682 (smartfren), here's my last working config, don't forget to try to enable the logging first (/etc/usb_modeswitch.conf) if you use usb_modeswitch v1.2.0 and found that module usbserial won't load after plugging your device. In my openSuse 11.4 it will load the module after suceessfully switched.


########################################################
#
# Smart Haier CE682 (EVDO)
#

DefaultVendor=0x201e
DefaultProduct=0x1023

TargetVendor=0x201e
TargetProduct=0x1022

MessageContent="5553424378bc46850000000000000600000000000000000000000000000000"
MessageContent2="55534243b076e484c000000080000671030000000000000000000000000000"
NeedResponse=1

CheckSuccess=20



Best regard.
Ebed.


Offline Profile YIM
PostPosted: Fri Dec 16, 2011 11:00 pm
Site AdminPosts: 4830Joined: Sat Nov 03, 2007 12:30 am
Can you try the test version of 1.2.1 ?

It may fix the "log" problem. Get it here:
http://www.draisberghof.de/usb_modeswit ... ta.tar.bz2



Offline Profile
PostPosted: Sat Dec 17, 2011 7:01 am
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
ok.. i'll install and test it tonight.


Offline Profile YIM
PostPosted: Sat Dec 17, 2011 1:32 pm
Posts: 8Joined: Sat Dec 10, 2011 4:14 am
it's working good right now.

Thanks so much josh.


Offline Profile YIM
PostPosted: Fri Mar 16, 2012 5:16 pm
Posts: 1Joined: Fri Mar 16, 2012 1:01 pm
Hi Josh and Ebed

I'm installing the latest version of usb-modeswitch (1.2.3), along with usb-modeswitch-data (latest version also). Before I come here, I already tried the solutions from so many sources/articles. But none works as I want. I'm a newbie also, so please forgive me if I'm not clear enough.

Ubuntu version = 11.10

First try :
I install libusb (version 1.0.0), and usb-modeswitch 1.2.3, everything is running flawlessly

Code:
$ dmesg
[9838.679425] scsi 3:0:0:0: Direct-Access     SDVDISK  EVDO ReV A       7.00 PQ: 0 ANSI: 0 CCS
[ 9838.687145] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 9838.696389] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[ 9839.084972] usbcore: registered new interface driver usbserial
[ 9839.086786] USB Serial support registered for generic
[ 9839.089005] usbcore: registered new interface driver usbserial_generic
[ 9839.089015] usbserial: USB Serial Driver core
[ 9839.117683] USB Serial support registered for GSM modem (1-port)
[ 9839.119963] usbcore: registered new interface driver option
[ 9839.119972] option: v0.7.2:USB Driver for GSM modems
[ 9839.125085] option 2-1:1.1: GSM modem (1-port) converter detected
[ 9839.125421] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 9839.125563] option 2-1:1.2: GSM modem (1-port) converter detected
[ 9839.125770] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 9839.150647] usb 2-1: usbfs: process 2877 (usb_modeswitch) did not claim interface 0 before use
[ 9839.150664] usb 2-1: usbfs: process 2877 (usb_modeswitch) did not claim interface 0 before use
[ 9839.175570] usb 2-1: usbfs: process 2883 (usb_modeswitch) did not claim interface 0 before use
[ 9839.175602] usb 2-1: usbfs: process 2883 (usb_modeswitch) did not claim interface 0 before use
[ 9839.183428] usb 2-1: usbfs: process 2885 (usb_modeswitch) did not claim interface 0 before use
[ 9839.183483] usb 2-1: usbfs: process 2885 (usb_modeswitch) did not claim interface 0 before use
[ 9839.570435] usb 2-1: usbfs: process 2916 (usb_modeswitch) did not claim interface 0 before use
[ 9839.570492] usb 2-1: usbfs: process 2916 (usb_modeswitch) did not claim interface 0 before use


Code:
sangprabo@sherylhunter:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter
Bus 002 Device 005: ID 201e:1022 


The problem persist when I tried to connect using wvdial

Code:
sangprabo@sherylhunter:~$ sudo wvdial smart
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT#777
--> Waiting for carrier.
ATDT#777
OK
CONNECT 3100000
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Tue Mar 13 19:15:58 2012
--> Pid of pppd: 3470
--> Using interface ppp0
--> pppd: � ���
--> pppd: � ���
--> pppd: � ���
--> pppd: � ���
--> Disconnecting at Tue Mar 13 19:16:02 2012
--> The PPP daemon has died: Loopback detected (exit code = 17)
--> man pppd explains pppd error codes in more detail.
--> I guess that's it for now, exiting
--> The PPP daemon has died. (exit code = 17)


Someone said to use the previous version of usb-modeswitch (1.2.0), but none works like a charm. At 1.2.0, I have to manually modprobe the usbserial module to make the modem gives a response.

I thought that's was because of my wvdial.conf. But I have exactly the same configuration as others. Here is the content of my /etc/wvdial.conf

Code:
[Dialer smart]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Password = smart
;Auto DNS = 1
Phone = #777
Command Line = ATDT
Modem Type = Analog Modem
Stupid Mode = 1
Baud = 460800
;Baud = 230400
Modem = /dev/ttyUSB2
ISDN = 0
Username = smart
;Carrier Check = no
;New PPPD = yes

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
ISDN = 0
Phone = #777
Modem = /dev/ttyUSB2
Username = smart
Password = smart
Baud = 9600


Someone said that it's because the Stupid mode, Init3, Carrier check, new PPPD, Baud. I tried every single combination but none works. The other said you have to disable your wifi card or eth0, even if I don't believe that it makes any sense, I did that but it doesn't work.

Why can't I connect to the internet? If it's because the usbserial, or pppd, or wvdial, I think it's not the right place to ask and please forgive me. But if you can give me any clue, I really appreciate it.

Thank you very much.


Offline Profile
PostPosted: Tue Mar 20, 2012 8:24 pm
Site AdminPosts: 4830Joined: Sat Nov 03, 2007 12:30 am
Hmm, your documentation seems to have some holes ...

1. You are using ttyUSB2 in your wvdial configuration, but I don't see that in the output of "dmesg".

2. Does the modem really switch modes? There should be a line in the "dmesg" output saying "USB disconnect, address XX".

usb_modeswitch is only relevant until you get those ttyUSB ports. There is nothing it can do afterwards.
There are things that can go wrong with pppd though. Maybe you want to google for "wvdial <your_provider>", it happens that other people have sorted out all issues already.
Maybe you find a different dial command than "ATDT#777". This is known to have an effect on the ppp response.



Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 1
13 posts
Users browsing this forum: Bing [Bot] and 2 guests
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum