Hello,
I am testing my 4G XS P14 dongle with UrukDroid on my archos A43, this android was modified and has usb_serial in kernel and all stuff need for run the USB-modeswitch script. My dongle works immediately in my linux PC, I have only installed the USB-modeswitch package, after connect the dongle the USB was switch to the right one, configuration over WVdial and I was connected.
But in my tablet with urukdroid is not working, I have the debug output, maybe someone can read out more from it and give me some possible step to do to solve the issue.
The output is:
--------------------------------------------------------------------------------------
export PATH=/usr/bin:$PATH
$ $su
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1c9e:f000
# /usr/local/sbin/usb_modeswitch -I -W -c /system/etc/usb_modeswitch.d/1c9e_f000
Reading config file: /system/etc/usb_modeswitch.d/1c9e_f000
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.1.8 (C) Josua Dietze 2011
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1c9e
DefaultProduct= 0xf000
TargetVendor= 0x1c9e
TargetProduct= not set
TargetClass= not set
TargetProductList="9000,9603,9605,9607"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
MessageEndpoint= not set
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
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: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
Looking for target devices ...
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 1c9e:f000
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0002
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 (0)
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem
Serial No.: 1234567890ABCDEF
-------------------------
Looking for active driver ...
USB error: could not get bound driver: No data available
No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
USB error: could not claim interface 0: No such file or directory
Could not claim interface (error -2). Skipping message sending
Checking for mode switch (max. 20 times, once per second) ...
Waiting for original device to vanish ...
USB error: could not claim interface 0: No such file or directory
USB error: could not release intf 0: No such file or directory
Original device can't be accessed anymore. Good.
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: No route to host
searching devices, found USB ID 1c9e:f000
found matching vendor ID
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 001 on 001
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 001 on 001
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 001 on 001
searching devices, found USB ID 1d6b:0002
No new devices in target mode or class found
Mode switch has failed. Bye.
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 1c9e:f000
#
--------------------------------------------------------------------------------
The only that I found interesting was the line:
---------------------------------------------------------------
USB error: could not claim interface 0: No such file or directory
Could not claim interface (error -2). Skipping message sending
----------------------------------------------------------------------------------
Best regards.
Ferenc.
-
todobarato
- Posts: 3
- Joined: 01 Aug 2011, 10:14
4G XS P14 Dongle and Android - Archos. (Solved)
Last edited by todobarato on 04 Aug 2011, 13:48, edited 1 time in total.
-
todobarato
- Posts: 3
- Joined: 01 Aug 2011, 10:14
Hello,Josh wrote:Hmm, can you check that there is a device tree under /sys/bus/usb ?
Also it is advised to re-plug the modem for each new switching attempt. There should be a driver bound to it after plugging, ususally usb_modeswitch reports "usb-storage" or "dummy".
in /sys/bus/usb/devices ,before I plug-in is empty the directory, after plug-in the dongle it show 3 devices with names: 1-0:1.0 , 1-1 and usb1
I dont see the usb-storage after plug-in the dongle, maybe this is the issue? in my linux PC will be recognized as usb-storage the first time before the modeswitch do his job.
or this text in the dmesg output it is in blue:
-------------------------------------------------------------------------------------------------------------------------
usb 1-1: new high speed USB device using musb_hdrc and address 29
usb 1-1: default language 0x0409
usb 1-1: New USB device found, idVendor=1c9e, idProduct=f000
usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-1: Product: USB Modem
usb 1-1: Manufacturer: USB Modem
usb 1-1: SerialNumber: 1234567890ABCDEF
usb 1-1: uevent
usb 1-1: usb_probe_device
usb 1-1: uevent
usb 1-1: rejected 1 configuration due to insufficient available bus power
usb 1-1: no configuration chosen from 1 choice
drivers/usb/core/inode.c: creating file '029'
hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 1-0:1.0: port 1 enable change, status 00000503
hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 1-1: USB disconnect, address 29
usb 1-1: unregistering device
usb 1-1: usb_disable_device nuking all URBs
usb 1-1: uevent
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
hub 1-0:1.0: hub_suspend
usb usb1: bus auto-suspend
usb usb1: usb resume
hub 1-0:1.0: hub_resume
hub 1-0:1.0: port 1: status 0101 change 0001
hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 1-1: new high speed USB device using musb_hdrc and address 30
usb 1-1: default language 0x0409
usb 1-1: New USB device found, idVendor=1c9e, idProduct=f000
usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-1: Product: USB Modem
usb 1-1: Manufacturer: USB Modem
usb 1-1: SerialNumber: 1234567890ABCDEF
usb 1-1: uevent
usb 1-1: usb_probe_device
usb 1-1: uevent
usb 1-1: rejected 1 configuration due to insufficient available bus power
usb 1-1: no configuration chosen from 1 choice
drivers/usb/core/inode.c: creating file '030'
hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 1-0:1.0: port 1 enable change, status 00000503
hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 1-1: USB disconnect, address 30
usb 1-1: unregistering device
usb 1-1: usb_disable_device nuking all URBs
usb 1-1: uevent
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
----------------------------------------------------------------------------------------------------------
I use one Y wiring that gives power to the dongle, it power up and works, but the android still says that it have one error do the power. It works only with on Hub?
Thanks for your time.
Best regard.
Ferenc.
Oh, I assumed you are using a powered hub ...
AFAIK, that's the only way to operate a 3G stick on an embedded device. These things are pulling the full legal 500 mA from the host. I believe the Archos' sockets are limited to 100 mA. I have an Archos 70, but even most of my memory sticks and card readers are not working when connected directly.
AFAIK, that's the only way to operate a 3G stick on an embedded device. These things are pulling the full legal 500 mA from the host. I believe the Archos' sockets are limited to 100 mA. I have an Archos 70, but even most of my memory sticks and card readers are not working when connected directly.
-
todobarato
- Posts: 3
- Joined: 01 Aug 2011, 10:14