LinuxQuestions.org - Cisco AM10

- Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)

- - Cisco AM10 (http://www.linuxquestions.org/questions/linux-hardware-18/cisco-am10-884027/)

clcbluemont

06-01-2011 06:39 PM

Cisco AM10

What do I need to do to get the following wireless usb dongle to work?
lsusb
Bus 001 Device 002: ID 1307:0169 Transcend Information, Inc.
Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB

The "Cisco Valet Connector" aka AM10 comes with an rt2870.inf file. I have tried using ndiswrapper and get:
ndiswrapper -l
rt2870 : driver installed

This I am guessing means it does not see the device.

I tried modprobe rt2800usb to see if the linux driver will work and get:
usb_modeswitch --default-vendor 0x1307 --default-product 0x1169

Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 005 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
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 ...
No driver found. Either detached before or never attached

and ifconfig -a does don't list a wireless device.

I tried modprobe rt2870sta and get the same result from usb_modeswitch and ifconfig.

I do not see the device ID numbers in the module alias files for either rt2800usb or rt2870sta, but I would have thought that using the driver that came with it would work. On http://linuxwireless.org/en/users/Dr...800usb/devices it says the Cisco AM10 should work, but the device numbers are different. Help? This is not the first time I come across a model number with different hardware under the hood, why do they that? augh.

camorri

06-03-2011 08:48 AM

The device is not being seen on the USB bus, that means hot pluging is not detecting the device. According to the site you listed above, you should see on the usb bus, 13b1-0031. It is not there. You need to get that to work, before loading a driver will do you any good. On my system, ( Slackware 13.37 ) the udev rules are in /etc/udev/rules.d/ . However, this varies with distors, as far as I know.

You can also open a konsole, and as root run the command 'dmesg' and look to see what happens when you plug the device in. This will show you if udev rules can not figure out what the device is.

This may have something to do with udev rules. Been a while since I poked into them, however, that has to work before loading any drive will get you closer to a working wireless device. Looks like the correct driver is called rt2800usb. You can do a 'locate rt2800usb' to see if you have the driver. If not, you will have to find it, it may be in the repos, if not, it becomes find the source, and compile it.

Hope this helps.

ohmysql

07-20-2011 01:17 PM

Quote:

Originally Posted by camorri (Post 4375116)

I am trying to get this AM10 to work on Ubuntu 11.04.

When I do locate rt2800usb I do get a number of drivers.

Code:

/lib/modules/2.6.38-10-generic/kernel/drivers/net/wireless/rt2x00/rt2800usb.ko

/lib/modules/2.6.38-8-generic/kernel/drivers/net/wireless/rt2x00/rt2800usb.ko

/usr/src/linux-headers-2.6.38-10-generic/include/config/rt2800usb

/usr/src/linux-headers-2.6.38-10-generic/include/config/rt2800usb.h

/usr/src/linux-headers-2.6.38-10-generic/include/config/rt2800usb/rt33xx.h

/usr/src/linux-headers-2.6.38-10-generic/include/config/rt2800usb/unknown.h

I do have udev rules here:

Code:

nautilus /etc/udev/rules.d/

Though I'm afraid I have no idea what to do from there. So you're saying I need to get my USB device to appear with that address that you mentioned.

camorri

07-20-2011 01:57 PM

Quote:

When I do locate rt2800usb I do get a number of drivers.

To load a driver 'sudo modprobe rt2800usb' ( without the quotes ) will load the driver. There is more than one driver ( its the file ending in .ko ) because you have had more than one kernel installed. Each new kernel will get new binary drivers. A driver for another kernel, ( not what is running now ) won't load.

Basically you do not need to worry about that, run the commnd, the correct one will be used.

However, if your device is not seen by the kernel, the driver won't help.

I'm not all that familiar with udev rules. Basically, when the device is plugged, or detected at boot time, there is info read from the device. It should create a device node ( a file ) in the /dev directory. Udev rules help that process. They are matching rules. You can view and change the rules.

At this point, dmesg will give us a clew. In a konsole, try 'sudo dmesg' That will dump the kernel messages to the screen.

Dump the messages once, then plug the usb device, and dump the messages again. What is happening will be at the end of the messages, about 8 to 10 lines.

Post that...

ohmysql

07-20-2011 02:53 PM

Quote:

Originally Posted by camorri (Post 4420419)

Ok, I ran it.

Quote:

However, if your device is not seen by the kernel, the driver won't help.

I'm not all that familiar with udev rules. Basically, when the device is plugged, or detected at boot time, there is info read from the device. It should create a device node ( a file ) in the /dev directory. Udev rules help that process. They are matching rules. You can view and change the rules.

Right, that's the problem. I've been trying to figure out usb_modeswitch to no luck so far. And modeswitch will automatically change the udev rules.

Quote:

At this point, dmesg will give us a clew. In a konsole, try 'sudo dmesg' That will dump the kernel messages to the screen.

Dump the messages once, then plug the usb device, and dump the messages again. What is happening will be at the end of the messages, about 8 to 10 lines.

Post that...

Hi I'd be happy to but the output is huge. Do you have any ideas how to run this? The terminal cuts off. It's huge. I can figure it out but it would take me a while.

camorri

07-20-2011 03:03 PM

I suggested you run dmesg once, just so you could see the output. Then plug the device. Run dmesg again. The messages when you plugged the device will be the last few lines. Cut and paste the last few lines, maybe 10 lines or so.

The other way...

run the command 'sudo dmesg >>/home/youruser/dmessages' That will dump the lines into a file called 'dmessages'. Root will own it, you should be able to edit it with any editor. The last few lines will show what happens when you plugged the device. Cut and past just those lines into the thread.

ohmysql

07-20-2011 03:13 PM

Quote:

Originally Posted by camorri (Post 4420481)

Thank you so much. The following is with the device unplugged.

Code:

[   17.896113] Intel AES-NI instructions are not detected.

[   18.331702] padlock_aes: VIA PadLock not detected.

[   18.841593] padlock_sha: VIA PadLock Hash Engine not detected.

[   19.351042] Adding 3928060k swap on /dev/mapper/cryptswap1.  Priority:-1 extents:1 across:3928060k 

[   20.901032] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0

[   22.680006] eth0: no IPv6 routers present

[   23.692914] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.

[ 5002.782905] forcedeth 0000:00:07.0: eth0: link down

[ 6118.568021] forcedeth 0000:00:07.0: eth0: link up

[ 6123.208893] forcedeth 0000:00:07.0: eth0: link down

[ 6127.827115] forcedeth 0000:00:07.0: eth0: link up

[ 6165.449972] forcedeth 0000:00:07.0: eth0: link down

[ 6177.071890] forcedeth 0000:00:07.0: eth0: link up

[ 6285.701038] forcedeth 0000:00:07.0: eth0: link down

[ 9059.072856] forcedeth 0000:00:07.0: eth0: link up

[ 9067.580982] forcedeth 0000:00:07.0: eth0: link down

[ 9072.726239] forcedeth 0000:00:07.0: eth0: link up

[ 9174.941734] forcedeth 0000:00:07.0: eth0: link down

[ 9186.725919] forcedeth 0000:00:07.0: eth0: link up

[ 9567.905893] cfg80211: Calling CRDA to update world regulatory domain

[ 9567.997709] cfg80211: World regulatory domain updated:

[ 9567.997716] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

[ 9567.997725] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 9567.997732] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)

[ 9567.997739] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)

[ 9567.997745] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 9567.997751] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 9568.093321] usbcore: registered new interface driver rt2800usb

[11250.601173] WARNING! power/level is deprecated; use power/control instead

[11250.710540] usb 1-4.1: USB disconnect, address 5

And this is when I plug in the Cisco Valet Connector AM10

Code:

[11250.601173] WARNING! power/level is deprecated; use power/control instead

[11250.710540] usb 1-4.1: USB disconnect, address 5

[11264.917598] usb 1-4: USB disconnect, address 3

[11270.600066] usb 1-4: new high speed USB device using ehci_hcd and address 6

[11270.751137] hub 1-4:1.0: USB hub found

[11270.751194] hub 1-4:1.0: 3 ports detected

[11271.030207] usb 1-4.1: new high speed USB device using ehci_hcd and address 7

[11271.141467] scsi5 : usb-storage 1-4.1:1.0

[11272.142389] scsi 5:0:0:0: Direct-Access              Cisco AM10       0.00 PQ: 0 ANSI: 2

[11272.143613] sd 5:0:0:0: Attached scsi generic sg2 type 0

[11272.144888] sd 5:0:0:0: [sdb] 253952 512-byte logical blocks: (130 MB/124 MiB)

[11272.145884] sd 5:0:0:0: [sdb] Write Protect is off

[11272.145899] sd 5:0:0:0: [sdb] Mode Sense: 00 00 00 00

[11272.145906] sd 5:0:0:0: [sdb] Assuming drive cache: write through

[11272.149985] sd 5:0:0:0: [sdb] Assuming drive cache: write through

[11272.280040]  sdb: sdb1

[11272.283145] sd 5:0:0:0: [sdb] Assuming drive cache: write through

[11272.283154] sd 5:0:0:0: [sdb] Attached SCSI removable disk

camorri

07-21-2011 06:22 AM

I was expecting to see some error messages, and I do not. The device seems to be seen as a scsi device. I would nave to think there may be something missing in the udev rules, but what?

This may take some research. I'll some googling and see what I can find. Sorry I don't have a suggestion any more specific.

ohmysql

07-21-2011 07:47 AM

Any googling you do would be much appreciated. I'm not sure what an SCSI device is but I can look that up without asking you. But I am curious: what were you expecting to see?

ohmysql

07-21-2011 06:16 PM

By the way, I wanted to share the results of lsusb. Note for some reason, there appears to be two devices?

Code:

 lsusb



Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB

Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc.



ubuntu:~$ sudo lsusb -v



Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB

Device Descriptor:

  bLength                18

  bDescriptorType         1

  bcdUSB               2.00

  bDeviceClass            0 (Defined at Interface level)

  bDeviceSubClass         0

  bDeviceProtocol         0

  bMaxPacketSize0        64

  idVendor           0x1307 Transcend Information, Inc.

  idProduct          0x1169 TS2GJF210 JetFlash 210 2GB

  bcdDevice            1.00

  iManufacturer           1 Cisco Systems, Inc.

  iProduct                5 Cisco AM10 AM10

  iSerial                 3 000000000000D9

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                 9

    bDescriptorType         2

    wTotalLength           39

    bNumInterfaces          1

    bConfigurationValue     1

    iConfiguration          0

    bmAttributes         0x80

      (Bus Powered)

    MaxPower               98mA

    Interface Descriptor:

      bLength                 9

      bDescriptorType         4

      bInterfaceNumber        0

      bAlternateSetting       0

      bNumEndpoints           3

      bInterfaceClass         8 Mass Storage

      bInterfaceSubClass      6 SCSI

      bInterfaceProtocol     80 Bulk (Zip)

      iInterface              0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x01  EP 1 OUT

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0200  1x 512 bytes

        bInterval               1

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x82  EP 2 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0200  1x 512 bytes

        bInterval               1

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x83  EP 3 IN

        bmAttributes            3

          Transfer Type            Interrupt

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0040  1x 64 bytes

        bInterval               8

Device Qualifier (for other device speed):

  bLength                10

  bDescriptorType         6

  bcdUSB               2.00

  bDeviceClass            0 (Defined at Interface level)

  bDeviceSubClass         0

  bDeviceProtocol         0

  bMaxPacketSize0        64

  bNumConfigurations      1

Device Status:     0x0000

  (Bus Powered)



Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc.

Device Descriptor:

  bLength                18

  bDescriptorType         1

  bcdUSB               2.00

  bDeviceClass            9 Hub

  bDeviceSubClass         0 Unused

  bDeviceProtocol         1 Single TT

  bMaxPacketSize0        64

  idVendor           0x1307 Transcend Information, Inc.

  idProduct          0x0169

  bcdDevice            1.00

  iManufacturer           1 Cisco Systems, Inc.

  iProduct                4 Cisco AM10 USB Hub

  iSerial                 0

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                 9

    bDescriptorType         2

    wTotalLength           25

    bNumInterfaces          1

    bConfigurationValue     1

    iConfiguration          0

    bmAttributes         0xc0

      Self Powered

    MaxPower               98mA

    Interface Descriptor:

      bLength                 9

      bDescriptorType         4

      bInterfaceNumber        0

      bAlternateSetting       0

      bNumEndpoints           1

      bInterfaceClass         9 Hub

      bInterfaceSubClass      0 Unused

      bInterfaceProtocol      0 Full speed (or root) hub

      iInterface              0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x81  EP 1 IN

        bmAttributes            3

          Transfer Type            Interrupt

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0001  1x 1 bytes

        bInterval               8

Hub Descriptor:

  bLength               9

  bDescriptorType      41

  nNbrPorts             3

  wHubCharacteristic 0x0004

    Ganged power switching

    Compound device

    Ganged overcurrent protection

    TT think time 8 FS bits

  bPwrOn2PwrGood       50 * 2 milli seconds

  bHubContrCurrent     49 milli Ampere

  DeviceRemovable    0x0a

  PortPwrCtrlMask    0xff

 Hub Port Status:

   Port 1: 0000.0503 highspeed power enable connect

   Port 2: 0000.0100 power

   Port 3: 0000.0100 power

Device Qualifier (for other device speed):

  bLength                10

  bDescriptorType         6

  bcdUSB               2.00

  bDeviceClass            9 Hub

  bDeviceSubClass         0 Unused

  bDeviceProtocol         0 Full speed (or root) hub

  bMaxPacketSize0        64

  bNumConfigurations      1

Device Status:     0x0001

  Self Powered

camorri

07-24-2011 02:11 AM

I did some googling, did a search on 'ID 1307:1169' and found some interesting results. Here is a link to one of the more interesting threads-->http://ubuntuforums.org/showthread.php?t=1808690

From what I have read, this device is more than one USB devices, as the output of lsusb you posted shows. One part is a USB storage device, another is the wireless device. Apparently, there are drivers installed in the USB storage device. Depending on the OS, one of the drivers needs to get loaded in the operating system to enable the wireless part.

I have not seen a link yet that indicates someone has this working in linux, so that is not so good.

One thread I read indicated you may need a Cisco wireless router to use all the functions of the device. Not sure it that is true or not.

Here is another link I found. -->http://www.linuxquestions.org/questi...ss-fob-858048/

So, you are not alone. However, I don't have any magic answers.

As far as my comment on a SCSI device, that for me is a method of addressing devices. There is a lot of SCSI emulation used on other devices. I have seen it mostly on various kinds of drives CD, etc. When I made the comment, I was surprised to see more than one device showing up on a USB adapter, that we though was a wireless adapter.

Did you get any documentation with the device? Have you looked for doc on Cisco's web site? Have you seen any indication the wireless adapter is supported in linux?

camorri

07-24-2011 02:19 AM

More googling...

Found this link-->http://www.wikidevi.com/wiki/Cisco_AM10

I followed the RAdrivers link listed, and there are linux drivers -->http://www.ralinktech.com/support.php?s=2

and this link to the current progress to getting this working...

http://www.draisberghof.de/usb_modes...724e52201f233c

They are not there yet.

camorri

07-24-2011 02:34 AM

I found this in a 'review'

Quote:

Help & Support:

Cisco provides an unusually wide range of options to get product support. Their web site includes live chat, form driven email and a toll-free telephone number. We particularly like the site’s interactive Guide Me feature which allows the user to enter a question and then refine it to get to the very specific solution that is needed.

The device is compatible with Windows 7, Windows Vista and Windows XP. Mac users and those with older versions of Windows will have to look elsewhere. It’s covered by a 1-year warranty.

This answers a lot of the questions I asked above.

ohmysql

07-29-2011 08:38 PM

Hi Cliff,

Awesome! Yeah, I'd come across a lot of those. I decided to just join that German forum and tag myself along to the thread that had died a month before. That person sounded prepared to deliver a working AM10 for sure.

You may have some insight into the latest happenings there.

http://www.draisberghof.de/usb_modes...hp?p=4883#4883

I'm hoping we solve this soon. We're starting to get clues about what causes the device to change its vendor and product number (from 1307:1169 to 13b1:0031 - and yes I have those memorized at this point. Scary isn't it!)

You can see the full USBsniffing log here:

http://www.berrypi.com/UsbSnoop5.log

oh my SQL!!

ohmysql

08-02-2011 09:56 PM

We got it! We've got it working! I'm writing you from the AM10 right now!

http://www.draisberghof.de/usb_modes...hp?p=4912#4912

All times are GMT -5. The time now is 04:16 AM.