| |
Activation Codes and Methods, Hardware Details, Sniffing
-
waferhead
- Posts: 7
- Joined: 29 May 2012, 15:36
Post
by waferhead » 04 Oct 2012, 08:57
I currently run Mageia2 primarily, on my ~6 year old Gobook3 "car" laptop I currently have Mageia2 (with working Semtech touchscreen!) and Mandriva 2010.2.
Recent kernels have what I consider a bug that cuts the 16550A serial ports speed in ~1/2 and causes lost data.
Alan Cox seems to be of the opinion he fixed something, and who am I to argue...
So I'm still loading up an obsoltete version distro if I want fast serial comms via a real serial port (or WinXP  )
I have a couple USB adapters that don't have the issue for obvious reasons, but I still lose ~20-30% speed vs the properly working real meatspace 16550A comm port.
-
maihoaomv
- Posts: 6
- Joined: 05 Jan 2013, 19:08
Post
by maihoaomv » 05 Jan 2013, 21:42
Hi
I was refereed to this forum from the ubuntu forums
http://ubuntuforums.org/showthread.php? ... 690&page=4
suggesting I may be able to get some help with my problem here. I bought a Cisco AM10 USB WiFi recently to attempt to convert my NAS to wireless. The device works with Win 7, Win XP, Linux Mint 13 and Linux Mint 14 pretty much plug-n-play so I know the device is working.
I'm trying to get it to work on a Seagate GoFlex Home NAS server that has been hacked to get rid of the Seagate (yuk!) stock O/S. The problem is it has an ARM processor (marvell armv5tel) rather than an i386/i686 processor which, I suspect, would not be able to load and run a widows driver using ndiswapper. It currently has Debian squeeze installed with a 3.3.2-kirkwood-dg #1 kernel. It runs well and Debian seems to have good support for my device. This is not a work related production machine and is only used on my dinky LAN mostly for learning.
Ok, so with all that said I tried working my way through the previous forum and this one but somewhere I got lost, I think possibly, where it's talking about udev and recompiling a modified version of usb_modeswitch. I'm not what you would say 'well versed' in Linux although I wouldn't consider myself a n00b either.
I compared what I was seeing on Linux Mint to what I was seeing on the NAS. They both appear to have the same (related) kernel drivers and software installed with the exception of ndiswrapper-utils (on the NAS), which probably wouldn't work anyway. Apparently it's not in the Debian armel repository. And Linux Mint doesn't appear to be using the usb_modeswitch.conf file as it's contents is pretty much unchanged from the default install. So I'd like to get this to work on the NAS without having to use ndiswrapper.
Here is the contents of /etc/usb_modeswitch.conf from the NAS. it appears to be working in so far as seeing the devices and indicates that the switch may have succeeded but when I look at it with lsusb the new device is not there.
Code: Select all root@GoFlexHome:/etc# cat usb_modeswitch.conf
# Configuration for the usb_modeswitch package, a mode switching tool for
# USB devices providing multiple states or modes
#
# This file is evaluated by the wrapper script "usb_modeswitch_dispatcher"
# in /usr/sbin
# To enable an option, set it to "1", "yes" or "true" (case doesn't matter)
# Everything else counts as "disable"
# Disable automatic mode switching globally (e.g. to access the original
# install storage)
DisableSwitching=0
# Enable logging (results in a extensive report file in /var/log, named
# "usb_modeswitch_<interface-name>" (and probably others)
EnableLogging=1
# oms edit 2011-07-20
# Cisco Valet Connector AM10
#
# Contributor: ohmysql (quite the n00b so please help if you see errors)
# No. 1
DefaultVendor= 0x1307
DefaultProduct= 0x1169
#TargetVendor= 0x13b1
#0x1307
#TargetProduct= 0x0031
#0x0169
#MessageEndpoint=0×05
MessageContent="5553424308f024820002000000000a2a0000000fc000000100000000000000"
MessageContent2="5553424330c5e2810002000000000a2a000001117000000100000000000000"
NeedResponse=1
CheckSuccess=20
#Found these numbers here: http://linuxwireless.org/en/users/Drivers/rt2800usb/devices?highlight=%28am10%29
#DefaultVendor= 0x13b1
#DefaultProduct= 0x0031
root@GoFlexHome:/etc#
This is what I get when I run usb_modeswitch
Code: Select all root@GoFlexHome:/etc# usb_modeswitch -c /etc/usb_modeswitch.conf
Note: target parameter missing; success check limited
Looking for default devices ...
Found devices in default mode or class [ 8469.218444] usb 1-1.4.1: usbfs: process 11467 (usb_modeswitch) did not claim interface 0 before use
(1)
Accessing device 009 on bus 001 ...
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String:
Model String: AM10
Revision String: 0.00
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
Product: AM10
Serial No.: 0000000000145B
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to the message (CSW) ...
Response reading got error -110, can probably be ignored
Device is gone, skipping any further commands
Checking for mode switch (max. 20 times, once per second) ...
Original device is gone already, not checking
(For a better success check provide target IDs or class)
Original device vanished after switching
Mode switch most likely succeeded. Bye.
root@GoFlexHome:/etc#
This is what I get when I run lsusb after running modeswitch
Code: Select all root@GoFlexHome:/etc# lsusb
Bus 001 Device 009: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 008: ID 1307:0169 Transcend Information, Inc.
Bus 001 Device 007: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@GoFlexHome:/etc#
The device is not there.
Now to confuse things even more this is what I get when I run lsusb on the Linux Mint machine.
Code: Select all maihoa@LinuxMint13 ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0c45:6480 Microdia Sonix 1.3 MP Laptop Integrated Webcam
Bus 002 Device 004: ID 046d:c508 Logitech, Inc. Cordless Trackball
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 002 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 002 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 010: ID 1307:0169 Transcend Information, Inc.
Bus 002 Device 011: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 002 Device 012: ID 13b1:0031 Linksys AM10 v1 802.11n [Ralink RT3072]
maihoa@LinuxMint13 ~ $
LM13 assigns it as
Bus 002 Device 012: ID 13b1:0031 Linksys AM10 v1 802.11n [Ralink RT3072]
which is what, I believe, ohmysql was seeing once he got his device to work.
This is what I get when I run modprobe on the NAS. So it looks like the correct kernel driver is installed. It's exactly the same thing I see on Linux Mint
Code: Select all root@GoFlexHome:/etc# modprobe -l |grep rt28
kernel/drivers/net/wireless/rt2x00/rt2800lib.ko
kernel/drivers/net/wireless/rt2x00/rt2800pci.ko
kernel/drivers/net/wireless/rt2x00/rt2800usb.ko
root@GoFlexHome:/etc# modprobe -l |grep ndis
kernel/drivers/net/wireless/rndis_wlan.ko
kernel/drivers/net/usb/rndis_host.ko
I also installed firmware-ralink and wireless-tools on the NAS.
Where do I go to from here? Any ideas or thoughts other than it can't be done would be appreciated.
Thanks
John
-
Josh
- Site Admin
- Posts: 6593
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 06 Jan 2013, 13:34
This may be a problem related to the specific USB host hardware or its driver.
If you have the "dmesg" program available, run it after the mode switch. It may provide more detailed information about the USB devices being discovered.
-
maihoaomv
- Posts: 6
- Joined: 05 Jan 2013, 19:08
Post
by maihoaomv » 06 Jan 2013, 18:43
Good morning
This time it hung up when I ran modeswitch rather than indicating that it had succeeded. I booted from a cold start with the AM10 plugged in. That may be why it reacted differently. I will try it again this time by unplugging/replugging the device. anyway here is what I got the first time around.
Code: Select all root@GoFlexHome:~# usb_modeswitch -c /etc/usb_modeswitch.conf
Note: target parameter missing; success check limited
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 005 on bus 001 ...
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
This is the output from dmesg. I don't see anything for the AM10 until line 176. It looks like it might be seening 3 devices. I see the 1307:0169 and the 1307:1169 but I don't see 13b1:0031. At the moment it doesn't make a lot of sense to me. I added line numbers to make it easier to find in the text.
Code: Select all 1 root@GoFlexHome:~# dmesg
... [edited for brevity]
176 [ 13.977239] usb 1-1.4: new high-speed USB device number 4 using orion-ehci
177 [ 14.095699] usb 1-1.4: New USB device found, idVendor=1307, idProduct=0169
178 [ 14.102608] usb 1-1.4: New USB device strings: Mfr=1, Product=4, SerialNumber=0
179 [ 14.109961] usb 1-1.4: Product: Cisco AM10 USB Hub
180 [ 14.114769] usb 1-1.4: Manufacturer: Cisco Systems, Inc.
181 [ 14.125166] hub 1-1.4:1.0: USB hub found
182 [ 14.135053] hub 1-1.4:1.0: 3 ports detected
183 [ 14.415073] usb 1-1.4.1: new high-speed USB device number 5 using orion-ehci
184 [ 14.525819] usb 1-1.4.1: New USB device found, idVendor=1307, idProduct=1169
185 [ 14.532905] usb 1-1.4.1: New USB device strings: Mfr=1, Product=5, SerialNumber=3
186 [ 14.540432] usb 1-1.4.1: Product: AM10
187 [ 14.544195] usb 1-1.4.1: Manufacturer: Cisco Systems, Inc.
188 [ 14.549737] usb 1-1.4.1: SerialNumber: 0000000000145B
189 [ 14.569833] usbcore: registered new interface driver uas
190 [ 14.580072] Initializing USB Mass Storage driver...
191 [ 14.585374] scsi1 : usb-storage 1-1.4.1:1.0
192 [ 14.590861] usbcore: registered new interface driver usb-storage
193 [ 14.596952] USB Mass Storage support registered.
194 [ 15.587412] scsi 1:0:0:0: Direct-Access AM10 0.00 PQ: 0 ANSI: 2
195 [ 15.604758] sd 1:0:0:0: [sdb] 253952 512-byte logical blocks: (130 MB/124 MiB)
196 [ 15.616359] sd 1:0:0:0: [sdb] Write Protect is off
197 [ 15.621179] sd 1:0:0:0: [sdb] Mode Sense: 00 00 00 00
198 [ 15.621964] sd 1:0:0:0: [sdb] Asking for cache data failed
199 [ 15.627492] sd 1:0:0:0: [sdb] Assuming drive cache: write through
200 [ 15.639339] sd 1:0:0:0: [sdb] Asking for cache data failed
201 [ 15.644852] sd 1:0:0:0: [sdb] Assuming drive cache: write through
202 [ 15.652471] sdb: sdb1
203 [ 15.665627] sd 1:0:0:0: [sdb] Asking for cache data failed
204 [ 15.671143] sd 1:0:0:0: [sdb] Assuming drive cache: write through
205 [ 15.677285] sd 1:0:0:0: [sdb] Attached SCSI removable disk
206 [ 22.135724] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2
207 [ 22.872865] udev[167]: starting version 164
...
238 root@GoFlexHome:~#
More to follow after I get a chance to retry it by un/re plugging the device
thanks
-
maihoaomv
- Posts: 6
- Joined: 05 Jan 2013, 19:08
Post
by maihoaomv » 06 Jan 2013, 20:12
Results after replugging device. Ok I guess there is a difference by booting it attached as opposed to replugging. This time the reaction is the same as I was seeing before.
Code: Select all root@GoFlexHome:~# usb_modeswitch -c /etc/usb_modeswitch.conf
Note: target parameter missing; success check limited
Looking for default devices ...
Found devices in default mode or class [ 6174.931180] usb 1-1.4.1: usbfs: process 8908 (usb_modeswitch) did not claim interface 0 before use
(1)
Accessing device 007 on bus 001 ...
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String:
Model String: AM10
Revision String: 0.00
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
Product: AM10
Serial No.: 0000000000145B
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to the message (CSW) ...
Response reading got error -110, can probably be ignored
Device is gone, skipping any further commands
Checking for mode switch (max. 20 times, once per second) ...
Original device is gone already, not checking
(For a better success check provide target IDs or class)
Original device vanished after switching
Mode switch most likely succeeded. Bye.
root@GoFlexHome:~#
The output from dmesg
Code: Select all root@GoFlexHome:~# dmesg |nl
... [edited]
237 [ 4268.137339] usb 1-1.4.1: usbfs: USBDEVFS_CONTROL failed cmd usb_modeswitch rqt 128 rq 6 len 255 ret -71
238 [ 4268.141571] usb 1-1.4.1: usbfs: USBDEVFS_CONTROL failed cmd usb_modeswitch rqt 128 rq 6 len 255 ret -71
239 [ 4268.145588] usb 1-1.4.1: usbfs: USBDEVFS_CONTROL failed cmd usb_modeswitch rqt 128 rq 6 len 255 ret -71
240 [ 4268.145735] usb 1-1.4.1: usbfs: process 1516 (usb_modeswitch) did not claim interface 0 before use
241 [ 4268.166821] usb 1-1.4: USB disconnect, device number 4
242 [ 4268.173773] usb 1-1.4.1: USB disconnect, device number 5
243 [ 6155.630101] usb 1-1.4: new high-speed USB device number 6 using orion-ehci
244 [ 6155.740445] usb 1-1.4: New USB device found, idVendor=1307, idProduct=0169
245 [ 6155.747366] usb 1-1.4: New USB device strings: Mfr=1, Product=4, SerialNumber=0
246 [ 6155.754722] usb 1-1.4: Product: Cisco AM10 USB Hub
247 [ 6155.759534] usb 1-1.4: Manufacturer: Cisco Systems, Inc.
248 [ 6155.768276] hub 1-1.4:1.0: USB hub found
249 [ 6155.773460] hub 1-1.4:1.0: 3 ports detected
250 [ 6156.049832] usb 1-1.4.1: new high-speed USB device number 7 using orion-ehci
251 [ 6156.160570] usb 1-1.4.1: New USB device found, idVendor=1307, idProduct=1169
252 [ 6156.167669] usb 1-1.4.1: New USB device strings: Mfr=1, Product=5, SerialNumber=3
253 [ 6156.175202] usb 1-1.4.1: Product: AM10
254 [ 6156.178967] usb 1-1.4.1: Manufacturer: Cisco Systems, Inc.
255 [ 6156.184513] usb 1-1.4.1: SerialNumber: 0000000000145B
256 [ 6156.209903] scsi2 : usb-storage 1-1.4.1:1.0
257 [ 6157.212165] scsi 2:0:0:0: Direct-Access AM10 0.00 PQ: 0 ANSI: 2
258 [ 6157.229875] sd 2:0:0:0: [sdb] 253952 512-byte logical blocks: (130 MB/124 MiB)
259 [ 6157.237983] sd 2:0:0:0: [sdb] Write Protect is off
260 [ 6157.242881] sd 2:0:0:0: [sdb] Mode Sense: 00 00 00 00
261 [ 6157.248985] sd 2:0:0:0: [sdb] Asking for cache data failed
262 [ 6157.254546] sd 2:0:0:0: [sdb] Assuming drive cache: write through
263 [ 6157.266716] sd 2:0:0:0: [sdb] Asking for cache data failed
264 [ 6157.272322] sd 2:0:0:0: [sdb] Assuming drive cache: write through
265 [ 6157.412866] sdb: sdb1
266 [ 6157.423854] sd 2:0:0:0: [sdb] Asking for cache data failed
267 [ 6157.429387] sd 2:0:0:0: [sdb] Assuming drive cache: write through
268 [ 6157.435536] sd 2:0:0:0: [sdb] Attached SCSI removable disk
269 [ 6174.931180] usb 1-1.4.1: usbfs: process 8908 (usb_modeswitch) did not claim interface 0 before use
root@GoFlexHome:~#
Note the last line (#269) of dmesg:
Code: Select all 269 [ 6174.931180] usb 1-1.4.1: usbfs: process 8908 (usb_modeswitch) did not claim interface 0 before use
What I don't understand is the MessageContent line in the modeswitch config file. How is this value derived? is it some how derived from usb sniffing? If so how??? if the device isn't working? I wasn't able to figure that one out.
Code: Select all MessageContent="5553424308f024820002000000000a2a0000000fc000000100000000000000"
MessageContent2="5553424330c5e2810002000000000a2a000001117000000100000000000000"
Also I don't understand about udev or udev rules, what if any part they may play in this process. Should I create a udev rule for it?
-
maihoaomv
- Posts: 6
- Joined: 05 Jan 2013, 19:08
Post
by maihoaomv » 07 Jan 2013, 08:28
made some progress. it now switches the device. this is great news. now i need to figure out how to get it do actually do something useful.
how to i set the parameters with iwconfig?
Code: Select all Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 015 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String:
Model String: AM10
Revision String: 0.00
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
Product: AM10
Serial No.: 0000000000145B
-------------------------
Looking for active driver ...
No driver found. Either detached before or never attached
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 ...
OK, message successfully sent
Reading the response (CSW) to bulk message 11 ...
OK, response successfully read (13 bytes).
Warning: ignoring MessageContent. Can't combine with special mode
-> Run lsusb to note any changes. Bye.
root@GoFlexHome:/etc# [ 2904.687862] usb 1-1.2: new high-speed USB device number 16 using orion-ehci
[ 2904.834721] usb 1-1.2: New USB device found, idVendor=13b1, idProduct=0031
[ 2904.841648] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2904.849002] usb 1-1.2: Product: Cisco AM10
[ 2904.853117] usb 1-1.2: Manufacturer: Cisco
[ 2904.957857] usb 1-1.2: reset high-speed USB device number 16 using orion-ehci
[ 2905.170108] udev[5355]: renamed network interface wlan0 to eth1
root@GoFlexHome:/etc# lsusb
Bus 001 Device 016: ID 13b1:0031 Linksys AM10 v1 802.11n [Ralink RT3072]
Bus 001 Device 015: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 014: ID 1307:0169 Transcend Information, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@GoFlexHome:/etc#
root@GoFlexHome:/etc# iwconfig
lo no wireless extensions.
eth1 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
eth0 no wireless extensions.
-
Josh
- Site Admin
- Posts: 6593
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 07 Jan 2013, 13:16
For details about the mode switching in Linux, you may want to read the main doc page of usb_modeswitch (See link in the top nav bar).
For further guidance about using your device, this is most certainly the wrong place, but I'm sure there are plenty of other communities where you can find that information.
-
ohmysql
- Posts: 55
- Joined: 22 Jul 2011, 16:47
Post
by ohmysql » 07 Jan 2013, 18:54
I agree, I would now bring that question back to ubuntuforums.
-
maihoaomv
- Posts: 6
- Joined: 05 Jan 2013, 19:08
Post
by maihoaomv » 08 Jan 2013, 08:49
ohmysql
ok then if you don't mind me asking. does it actually use the windows driver or the rt2800usb linux driver? if it uses the windows driver then it ain't ever going to work on this ARM device. it appears to be switching but it's not xmitting, the power level is zero.
-
ohmysql
- Posts: 55
- Joined: 22 Jul 2011, 16:47
Post
by ohmysql » 08 Jan 2013, 21:47
maihoaomv wrote:ohmysql
ok then if you don't mind me asking. does it actually use the windows driver or the rt2800usb linux driver? if it uses the windows driver then it ain't ever going to work on this ARM device. it appears to be switching but it's not xmitting, the power level is zero.
I use the rt2800usb driver 
-
maihoaomv
- Posts: 6
- Joined: 05 Jan 2013, 19:08
Post
by maihoaomv » 09 Jan 2013, 07:41
good, that's what I needed to know so I won't be wasting time on something that can't be done.
-
ohmysql
- Posts: 55
- Joined: 22 Jul 2011, 16:47
Post
by ohmysql » 10 Mar 2015, 04:13
Just a note to say that the Cisco AM10 is acting up out of the box on Ubuntu 14.04 and Linux Mint 17. That's really too bad since it was working out of the box on many systems... and in fact, it was working out of the box on the Linux Mint install CD!!! So I'm not sure what's going on when it's finally installed but I'm on the case... 
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 10 Mar 2015, 05:55
ohmysql wrote:Just a note to say that the Cisco AM10 is acting up out of the box on Ubuntu 14.04 and Linux Mint 17. That's really too bad since it was working out of the box on many systems... and in fact, it was working out of the box on the Linux Mint install CD!!! So I'm not sure what's going on when it's finally installed but I'm on the case... 
Update usb_modeswitch to version 2.2.1 and it will work.
-
ohmysql
- Posts: 55
- Joined: 22 Jul 2011, 16:47
Post
by ohmysql » 10 Mar 2015, 07:36
Version 2.1.1 or something like that ships out with Ubuntu 14.04, Linux Mint etc. But the Cisco AM10 has been working since version 1.9. In fact I see "cisco mode" with my precise lsusb output and it's not working.
Here are my two attempts to get it to work:
Code: Select all usb_modeswitch -v 1307 -p 1169 -W -L
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1307
DefaultProduct= 0x1169
CiscoMode=1
NeedResponse=0
Look for default devices ...
found USB ID 1307:1169
vendor ID matched
product ID matched
found USB ID 1307:0169
vendor ID matched
found USB ID 1d6b:0002
found USB ID 045e:00db
found USB ID 045e:077f
found USB ID 2188:0ae1
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 010 on bus 001
Current configuration number is 1
Use interface number 0
Use 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 ...
No active driver found. Detached before or never attached
Set up Cisco interface 0
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 1 ...
Response reading failed (error -7)
Device returned error -7, skip further commands
-> Run lsusb to note any changes. Bye!
And:
Code: Select all usb_modeswitch -v 1307 -p 1169 -V 13b1 -P 0031 -L -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1307
DefaultProduct= 0x1169
TargetVendor= 0x13b1
TargetProduct= 0x0031
CiscoMode=1
NeedResponse=0
Look for target devices ...
found USB ID 1307:1169
found USB ID 1307:0169
found USB ID 1d6b:0002
found USB ID 045e:00db
found USB ID 045e:077f
found USB ID 2188:0ae1
found USB ID 1d6b:0001
No devices in target mode or class found
Look for default devices ...
found USB ID 1307:1169
vendor ID matched
product ID matched
found USB ID 1307:0169
vendor ID matched
found USB ID 1d6b:0002
found USB ID 045e:00db
found USB ID 045e:077f
found USB ID 2188:0ae1
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 010 on bus 001
Current configuration number is 1
Use interface number 0
Use 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 ...
No active driver found. Detached before or never attached
Set up Cisco interface 0
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 1 ...
Response successfully read (1 bytes).
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 2 ...
Response successfully read (13 bytes).
Trying to send message 3 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 3 ...
Response successfully read (1 bytes).
Trying to send message 4 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 4 ...
Response successfully read (13 bytes).
Trying to send message 5 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 5 ...
Response successfully read (1 bytes).
Trying to send message 6 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 6 ...
Response successfully read (13 bytes).
Trying to send message 7 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 7 ...
Response successfully read (1 bytes).
Trying to send message 8 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 8 ...
Response successfully read (13 bytes).
Trying to send message 9 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 9 ...
Response successfully read (1 bytes).
Trying to send message 10 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 10 ...
Response successfully read (13 bytes).
Trying to send message 11 to endpoint 0x01 ...
OK, message successfully sent
Read the response (CSW) to bulk message 11 ...
Response successfully read (13 bytes).
-> Run lsusb to note any changes. Bye!
More generally, if I run:
It asks me to be more precise about how to switch the device basically.
-
ohmysql
- Posts: 55
- Joined: 22 Jul 2011, 16:47
Post
by ohmysql » 10 Mar 2015, 17:20
UPDATE: Sorry, I didn't realize there was a bug with 2.1.1. See the post below this one for an updated attempt to get it to work.
Sorry, let me give an update to the last post.
I just noticed this bug report in 2.1.1.
https://bugs.launchpad.net/ubuntu/+sour ... modeswitch
That said, I just tried to modeswitch in Arch Linux, which is using 2.2.0 and it didn't work either. I got the exact same error messages when I tried something along the lines of (in su) usb_modeswitch -v 1307 -p 1169 -L
Here's what happened when I tried the .deb file:
Code: Select all Error: dependency is not satisfiable: libjim0.75 (>= 0.72)
Here's my attempt to make usb_modeswitch:
I see the wrong version of libusb is installed? So QUESTION: does a usable version of libusb ship with 14.04--if so, how can I direct usb_modeswitch to it?
Code: Select all make
cc -o usb_modeswitch usb_modeswitch.c -Wall `pkg-config --libs --cflags libusb-1.0`
Package libusb-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libusb-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libusb-1.0' found
usb_modeswitch.c:50:19: fatal error: stdio.h: No such file or directory
#include <stdio.h>
^
compilation terminated.
make: *** [usb_modeswitch] Error 1
If not, my attempt to create libusb failed also:
Code: Select all configure:3287: error: in `/home/mint/Desktop/Geek/libusb-1.0.9':
configure:3289: error: C compiler cannot create executables
See `config.log' for more details
I can give you the log if you like. I know you're not responsible for maintaining libusb but I am quite confused.
|
|