Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 05 Aug 2011, 01:12

Hmm, can it be that there is an old config file from an earlier attempt (or a whole bunch of them from an old usb_modeswitch version) in /etc/usb_modeswitch.d ? The best thing would be to clean that folder completely (move the files somewhere else if you feel better keeping them).

Also, have a look in /usr/share/usb_modeswitch, there should be only the compressed configuration package file in there.

Top
ohmysql
Posts: 55
Joined: 22 Jul 2011, 16:47

Post by ohmysql » 05 Aug 2011, 02:21

Josh wrote:Hmm, can it be that there is an old config file from an earlier attempt(or a whole bunch of them from an old usb_modeswitch version) in /etc/usb_modeswitch.d ?
Indeed there was one. And it is now in /etc/usb_modeswitch.d/Backup where hopefully it will do no harm.
The best thing would be to clean that folder completely (move the files somewhere else if you feel better keeping them).

Also, have a look in /usr/share/usb_modeswitch, there should be only the compressed configuration package file in there.
There are a bunch of files in /usr/share/usb_modeswitch/ (196 to be exact), one of whom is called 1307:1169. This should all be in one file (an archive)? I don't think I unpacked these files... let me know what I should do about that. I can pack them all into something if that helps.

FYI:

In /etc/udev/rules.d/70-persistent-net.rules this is the entry I have for this device:

# USB device 0x13b1:0x0031 (usb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:7f:74:e3:f6:4b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"

Anyway, after making the first change you requested I restarted. I noticed it was taking forever to boot up and then when I tried to do something I realized the computer had frozen.

I had to shut off my computer. THAT'S FANTASIC NEWS!!!

My computer freezing means that the wireless device switched automatically (because it tends to freeze within a couple seconds of switching)! So before starting again, I unplugged the ethernet, and the wireless booted with startup!!!!

YES!!!!

Here's the log:

Code: Select all


USB_ModeSwitch log from Thu Aug 04 20:30:20 EDT 2011

Raw args from udev: /1-4.1: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 (1-4.1:1.0) ...
----------------
USB values from sysfs:
  manufacturer	Cisco Systems, Inc.
  product	Cisco AM10 AM10
  serial	000000000000D9
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /usr/share/usb_modeswitch/1307:1169
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -c /usr/share/usb_modeswitch/1307:1169)

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are expected in the process)
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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

Reading config file: /usr/share/usb_modeswitch/1307:1169

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

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x1307
DefaultProduct= 0x1169
TargetVendor=   0x13b1
TargetProduct=  0x0031
TargetClass=    not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=1
MessageEndpoint=  not set
MessageContent=""
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

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


Looking for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Found devices in target mode or class (1)
Looking for default devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
  searching devices, found USB ID 1307:1169
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:0169
   found matching vendor ID
  searching devices, found USB ID 1d6b:0002
 Found devices in default mode, class or configuration (1)
Accessing device 005 on bus 001 ...
Skipping the check for the current configuration
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 000000000000D9
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Preparing for sending Cisco message sequence
Setting up communication with interface 0
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 1 ...
 OK, response successfully read (1 bytes).
Trying to send message 2 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 2 ...
 OK, response successfully read (1 bytes).
Trying to send message 3 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 3 ...
 OK, response successfully read (13 bytes).
Trying to send message 4 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 4 ...
 OK, response successfully read (1 bytes).
Trying to send message 5 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 5 ...
 OK, response successfully read (13 bytes).
Trying to send message 6 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 6 ...
 OK, response successfully read (1 bytes).
Trying to send message 7 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 7 ...
 OK, response successfully read (13 bytes).
Trying to send message 8 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 8 ...
 OK, response successfully read (1 bytes).
Trying to send message 9 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 9 ...
 OK, response successfully read (1 bytes).
Trying to send message 10 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 10 ...
 OK, response successfully read (13 bytes).
Trying to send message 11 to endpoint 0x01 ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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
 OK, message successfully sent
Reading the response (CSW) to bulk message 11 ...
 OK, response successfully read (13 bytes).

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:000usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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
1
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 No new devices in target mode or class found

Mode switch has failed. Bye.

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


All done, exiting
Here's lsusb on startup:

Code: Select all

Bus 001 Device 006: ID 13b1:0031 Linksys AM10 v1 802.11n [Ralink RT2870]
Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 004: ID 1307:0169 Transcend Information, Inc.
OMS
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 05 Aug 2011, 08:55

About the many configuration files in "/usr/share/usb_modeswitch", that is fine. There is two ways of installing the data package: "make install" will just copy all config files while "make install-packed" will put them into a compressed package first. Unless you are extremely short of hard disk space, you can leave things as they are. The usb_modeswitch program can handle both.

About that program response "Mode switch has failed. Bye." - that's why I needed someone to test the new version ... There is a bug obviously.
As soon as you get "found matching vendor ID - found matching product ID" in the log, the searching should have stopped and the program should have started rejoicing and boasting about this gigantic success.
Which it didn't.

It's my part to fix that, obviously. Expect a corrected file tonight (early afternoon at your side of the ball).

Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 05 Aug 2011, 19:18

Back from work - and back to business ...

Get the program source with the same link as before and use it in the source folder, you really know the drill now.

Check that the "usb_modeswitch.cfg" file is corrected in the source folder as well, or else you will re-install the wrong settings ...

Do annother "make install" in the source folder. Replug your stick to see if you get a success message in the log this time.

Top
ohmysql
Posts: 55
Joined: 22 Jul 2011, 16:47

Post by ohmysql » 06 Aug 2011, 00:26

Josh wrote:Back from work - and back to business ...

Get the program source with the same link as before and use it in the source folder, you really know the drill now.

Check that the "usb_modeswitch.cfg" file is corrected in the source folder as well, or else you will re-install the wrong settings ...

Do annother "make install" in the source folder. Replug your stick to see if you get a success message in the log this time.
Thanks for the reminder about change modeswitch.cfg in my source folder. Done.

Here's the code from the log. Looking sexy:

Code: Select all



USB_ModeSwitch log from Fri Aug 05 18:23:38 EDT 2011

Raw args from udev: /1-4.1: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 (1-4.1:1.0) ...
----------------
USB values from sysfs:
  manufacturer	Cisco Systems, Inc.
  product	Cisco AM10 AM10
  serial	000000000000D9
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /usr/share/usb_modeswitch/1307:1169
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -c /usr/share/usb_modeswitch/1307:1169)

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are expected in the process)
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device

Reading config file: /usr/share/usb_modeswitch/1307:1169

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

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x1307
DefaultProduct= 0x1169
TargetVendor=   0x13b1
TargetProduct=  0x0031
TargetClass=    not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=1
MessageEndpoint=  not set
MessageContent=""
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

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


Looking for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1307:1169
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:0169
   found matching vendor ID
  searching devices, found USB ID 1d6b:0002
 Found devices in default mode, class or configuration (1)
Accessing device 005 on bus 001 ...
Skipping the check for the current configuration
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 000000000000D9
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Preparing for sending Cisco message sequence
Setting up communication with interface 0
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 1 ...
 OK, response successfully read (1 bytes).
Trying to send message 2 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 2 ...
 OK, response successfully read (1 bytes).
Trying to send message 3 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 3 ...
 OK, response successfully read (13 bytes).
Trying to send message 4 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 4 ...
 OK, response successfully read (1 bytes).
Trying to send message 5 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 5 ...
 OK, response successfully read (13 bytes).
Trying to send message 6 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 6 ...
 OK, response successfully read (1 bytes).
Trying to send message 7 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 7 ...
 OK, response successfully read (13 bytes).
Trying to send message 8 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 8 ...
 OK, response successfully read (1 bytes).
Trying to send message 9 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 9 ...
 OK, response successfully read (1 bytes).
Trying to send message 10 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response (CSW) to bulk message 10 ...
 OK, response successfully read (13 bytes).
Trying to send message 11 to endpoint 0x01 ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 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 error: error sending control message: Broken pipe
Error: could not get description string "serial number"
 OK, message successfully sent
Reading the response (CSW) to bulk message 11 ...
 OK, response successfully read (13 bytes).

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
  searching devices, found USB ID 045e:007d
  searching devices, found USB ID 045e:00db
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 13b1:0031
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1307:1169
  searching devices, found USB ID 1307:0169
  searching devices, found USB ID 1d6b:0002

Found target device, now opening

Found target device 006 on bus 001

Target device description data
-------------------------
Manufacturer: Cisco
     Product: Cisco AM10
  Serial No.: 
-------------------------
 Found correct target device

Mode switch succeeded. Bye.

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

Doing no driver checking or binding for this device
Checking for AVOID_RESET_QUIRK attribute
 AVOID_RESET_QUIRK activated

All done, exiting
I'm using it to send this message, but my computer will probably freeze soon. Btw is there a way I need to unmount the usb adapter after doing modeswitch, or is it safe to just unplug.

Anyway, this is looking VERY good! Lots of reason for celebrating - unless I'm wrong, it looks like we may be nearing done with this project. (Next project: why does my computer keep freezing).

OMS
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 06 Aug 2011, 08:52

Now, that's the way a log is supposed to look. I officially declare that this device is supported by usb_modeswitch !

About unplugging: there should be no problem with just pulling out. In the case of USB devices, there is only one reason to be careful about unplugging: if something or someone is writing data to the device. That may be the case for your average memory stick, or for any other device during a firmware update. In theory, the driver storage on your stick should not be writable; we know that it is but you are not using it for file storage, right?

BTW, did you try to repair that file system? To do that, disable mode switching in /etc/usb_modeswitch.conf, plug in and wait a moment. If the install storage appears on your desktop, unmount it ("remove safely"). If not, don't bother and run (as root or with sudo):
# fsck.vfat /dev/sdb1
You might be able to get rid of these FAT error messages.

About the freezing: did you look for anything suspicious in the log files (/var/log/syslog or /var/log/messages) ?
If your system is configured well, you should have a time stamp preceding every entry there which may help finding the exact places where the freeze occurred. There should be a time jump when you rebooted.

Top
ohmysql
Posts: 55
Joined: 22 Jul 2011, 16:47

Post by ohmysql » 07 Aug 2011, 03:39

Josh wrote:Now, that's the way a log is supposed to look. I officially declare that this device is supported by usb_modeswitch !
All the program's boasting is totally justified. I love modeswitch!
About unplugging: there should be no problem with just pulling out. In the case of USB devices, there is only one reason to be careful about unplugging: if something or someone is writing data to the device. That may be the case for your average memory stick, or for any other device during a firmware update. In theory, the driver storage on your stick should not be writable; we know that it is but you are not using it for file storage, right?
Right, I'm not using it for storage. I doubt anything would be writing to it. Once usb_modeswitch does it's thing, it disappears as a storage device.
BTW, did you try to repair that file system? To do that, disable mode switching in /etc/usb_modeswitch.conf, plug in and wait a moment. If the install storage appears on your desktop, unmount it ("remove safely"). If not, don't bother and run (as root or with sudo):
# fsck.vfat /dev/sdb1
You might be able to get rid of these FAT error messages.
Hmm, I tried, not too much luck. Oh well! Not a big deal, like you said, I won't be using it, but it is bizarre.
About the freezing: did you look for anything suspicious in the log files (/var/log/syslog or /var/log/messages) ?
If your system is configured well, you should have a time stamp preceding every entry there which may help finding the exact places where the freeze occurred. There should be a time jump when you rebooted.
I don't have a file called /var/log/messages (as far as I can tell), but I do have syslog.

Yeah, I've been reading that log a bit. The reason for the freezing is pretty variable. Well, listen, it's probably a driver issue. It wouldn't be really very appropriate for a usb_modeswitch forum - I doubt it anyway. I'm going to try deinstalling the driver and if my computer doesn't freeze, there's no way it's modeswitch. So I'll let you know.

I'm pretty exhausted with all the repairs we've been doing! After a little break, I'm going to post on ubuntuforums about the freezing issue. And I'll pass the link. No pressure to help but if you're able and it would be fun for you, that would be pretty awesome!

But I'm going to take a minute to celebrate this. Usb_modeswitch got the job done. And I am almost there and very happy about it.

OMS
Top
unvoiced
Posts: 1
Joined: 15 Aug 2011, 02:56

Instructions on AM10 from Start to Finish

Post by unvoiced » 15 Aug 2011, 03:06

now that you've all been able to get this to work, is anyone able to post instructions on how we can also get our AM10 adapters working? I'm still new to Ubuntu any help would be greatly appreciated.

Many thanks
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 15 Aug 2011, 08:06

Version 1.1.9 of usb_modeswitch (see "Announcements") together with data package 20110805 includes everything you need.

Install from source or from the Debian packages ("sid / unstable"). See the main doc page, paragraph "Download".

Top
doubleplus
Posts: 1
Joined: 15 Aug 2011, 17:35

Post by doubleplus » 15 Aug 2011, 22:53

Im brand new to using unbuntu, and the AM10 is my ONLY way of accessing the internet with Unbunut (Using windows currently). I THINK I have Usb modeswitch properly installed, but it says "No driver detected" and I have no idea were to find the driver or how to install it. (I apologize in advance if this isnt the right place to ask... Ive been watching this topic for a couple weeks, and just made an account so I have no idea where else to ask)
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 15 Aug 2011, 23:58

I don't know about the driver situation for this device, but you may get further hints at the Ubuntu forum that ohmysql pointed to in his second posting in this thread:

http://ubuntuforums.org/showthread.php? ... st11077654
Top
ohmysql
Posts: 55
Joined: 22 Jul 2011, 16:47

Post by ohmysql » 11 Sep 2011, 03:34

Josh, question for you. My Ubuntu freezes and refuses to get past grub whenever I have the USB device plugged in. Do you think modeswitch might be involved? Any idea how I can tell? I can get you a syslog or dmesg readout if you think that will help.

OMS!
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 11 Sep 2011, 08:05

No, that's probably rather a matter of the BIOS. I have one machine that refuses to boot if one of my 3G sticks is plugged. Some of these try to fake a CDROM which may confuse the boot code of the PC.

If you see grub, nothing from Ubuntu is loaded yet (except a fancy splash screen).

You can try to fiddle with the BIOS settings (boot order, legacy USB or others), but there is no guarantee for success.

Top
ohmysql
Posts: 55
Joined: 22 Jul 2011, 16:47

Post by ohmysql » 11 Sep 2011, 15:44

Are you sure? My understanding is you see GRUB after the BIOS loading is over. In fact, I see a screen that says "loading operating system", then GRUB beeps, then right you see the Ubuntu splash screen. I doubt it's BIOS loading if you see an Ubuntu screen, non?

Well anyway, I tried with a different USB key and it loaded fine!

No other suggestions? I turned off USB loading in my BIOS, I don't think it did much.

Maybe some content on my USB key is making it screw up. I'll have to try different stuff I guess.

But if it were USB_modeswitch, how would I know?

OMS!
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 13 Sep 2011, 17:10

The stick may alter the disk order, confusing grub. I don't know for sure if this can be fixed with BIOS settings.

As long as the "udev" service is not started yet, there is no way usb_modeswitch is responsible for anything.

Top
Post Reply

Return to “Device Information”