Automatic Activation, Hotplug and UDEV, Configuration
Post Reply
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Mode switch succeeded. Bye, pppd unrecognized option ttyUSB0

Post by mserafin » 03 Jul 2011, 04:20

# usb_modeswitch -I -W -c usb_modeswitch.conf
error obtaining child information: Inappropriate ioctl for device
USB error: could not clear/halt ep 129: Protocol error
Error resetting endpoint: -71
Resetting message endpoint 0x01
USB error: could not clear/halt ep 1: No such device
Error resetting endpoint: -19
USB error: could not release intf 0: No such device
Device is gone, skipping any further commands
in the end
Found target device, now opening

Found target device 004 on bus 001

Target device description data
-------------------------
Manufacturer: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Found correct target device

Mode switch succeeded. Bye.
pppd call gprs >>>unrecognized option /dev/ttyUSB0

¿¿¿¿¿????????
Top
Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 03 Jul 2011, 08:56

Please post the content of your "usb_modeswitch.conf".
Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 03 Jul 2011, 14:19

# usb_modeswitch -I -W -c usb_modeswitch.conf

Reading config file: usb_modeswitch.conf

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

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x12d1
DefaultProduct= 0x1520
TargetVendor= 0x12d1
TargetProduct= 0x1465
TargetClass= not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

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

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
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
usb_os_find_devices: Found 001 on 002

Looking for target devices ...
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 12d1:1520
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 12d1:1520
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
Found devices in default mode, class or configuration (1)
Accessing device 002 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
USB error: could not clear/halt ep 129: Protocol error
Error resetting endpoint: -71
Resetting message endpoint 0x01
USB error: could not clear/halt ep 1: No such device
Error resetting endpoint: -19
USB error: could not release intf 0: No such device
Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found 004 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 3 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 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
usb_os_find_devices: Found 001 on 002
searching devices, found USB ID 12d1:1465
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001

Found target device, now opening

Found target device 004 on bus 001

Target device description data
-------------------------
Manufacturer: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Found correct target device

Mode switch succeeded. Bye.
Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 03 Jul 2011, 14:26

usb_modeswitch.config
########################################################
# Huawei K3765
DefaultVendor= 0x12d1
DefaultProduct=0x1520
TargetVendor= 0x12d1
TargetProduct= 0x1465
CheckSuccess=20
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
Top
Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 03 Jul 2011, 14:52

This device is included with the latest data package (20110619).

You will only get the proper driver binding if the automatic switching is working. I recommend to install the current program version too (1.1.8).

If your distribution does not have them yet, just install from source which is not hard and should work right away. See "How to install" on the main doc page in that case.

Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 03 Jul 2011, 15:23

Sorri
my job is
zt-180 android 2.2 a static binary for ARM: usb_modeswitch-1.1.7-arm-static.bz2
Top
Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 05 Jul 2011, 00:26

Oh boy - I'm not sure that you know what's laying ahead ...

In theory, you can bind the driver module manually - but you have to have it as a module on Android first. Most installations/kernels don't come with the "option" module.

So you have to make sure you find it or get it; you may have to compile the kernel which matches the one on your target device.

Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 05 Jul 2011, 02:04

Bueno a ver si aparece firmware con android 3
Gracias por tu tiempo
Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 07 Jul 2011, 21:08

Josh
Then I can do.
I do not understand this message.
What to do exactly
Top
Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 08 Jul 2011, 07:34

You can probably switch the modem on Android. But you need the right driver, too.

This driver is probably not included on your Android device.
Top
dune
Posts: 25
Joined: 07 Apr 2011, 08:37
Contact:
Contact dune

Post by dune » 08 Jul 2011, 08:39

Manuel, in case the path /sys/bus/usb-serial/drivers/option1 does not exist on your file system, you may need to insert the option kernel module with 'insmod' at the command prompt. After that, 'echo "your_vendor:device_target_ID" > /sys/bus/usb-serial/drivers/option1/new_id'.

I have a precompiled option module for 2.6.32.9, but I am not sure if it will work with your processor. The file is here
Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 08 Jul 2011, 11:38

if there is a path /sys/bus/usb-serial/drivers/option1 ok
get commands,,,,,
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system ,,,,,,OK
mount -t usbfs usbfs /proc/bus/usb,,,,, No such filr or directory ????
i have /proc/bus/input,,,,no /proc/bus/usb
Top
mserafin
Posts: 9
Joined: 03 Jul 2011, 02:50
Location: spain

Post by mserafin » 08 Jul 2011, 11:41

Josh
usb_modeswitch AT^U2DIAG=0
recognizes,,,switch does
Top
Post Reply

Return to “Setup Discussion”