Author Message

<  Device Information  ~  Cisco AM10

PostPosted: Wed Aug 03, 2011 3:48 am
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
O-kay, here we go.

Get the program source with the same link as before and use it in the source folder, you know the drill. The target this time is the storage device again.

# usb_modeswitch -v 1307 -p 1169 -L -I -u -1



Ok, here's hoping I know the drill. I cd'd to the folder, I did make clean, sudo make uninstall, make, then sudo make install.

Then I had plugged in my device a while back so I unmounted. Then I ran the command you suggested. I've tried it twice and my computer crashed twice. Any ideas about why that might be?

That was really strange. I'll perhaps try again in the morning.

Hrm. I wasn't expecting that at all.

BUT THEN!!!

I totally had wireless internet for about 5 minutes. But for some reason when I try to access this page to tell you all about it, Ubuntu COMPLETELY FREEZES. And then I reset and try again and it freezes again. But the internet totally worked. I disabled the ethernet and accessed Google through the USB adapter. And I did lsusb and it totally worked. I'm going to try this in Chrome.


Offline Profile
PostPosted: Wed Aug 03, 2011 4:45 am
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
I still have no idea what causes the freezes, but I've unplugged my ethernet. So I'm browsing on Chrome in case it was firefox that was causing the freezes. But...

I AM WRITING YOU FROM THE AM10 DEVICE PLUGGED INTO MY UBUNTU!!!

YYYYYYES!!!

Here's the output:

Code:
sudo usb_modeswitchv 1307 -p 1169 -L -I -u -1

Output:

Looking for default devices ...
 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
Sending Cisco message sequence
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 write package 0 ...
 OK, response successfully read (1 bytes).
Trying to send message 2 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 1 ...
 OK, response successfully read (1 bytes).
Trying to send message 3 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 2 ...
 OK, response successfully read (13 bytes).
Trying to send message 4 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 3 ...
 OK, response successfully read (1 bytes).
Trying to send message 5 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 4 ...
 OK, response successfully read (13 bytes).
Trying to send message 6 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 5 ...
 OK, response successfully read (1 bytes).
Trying to send message 7 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 6 ...
 OK, response successfully read (13 bytes).
Trying to send message 8 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 7 ...
 OK, response successfully read (1 bytes).
Trying to send message 9 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 8 ...
 OK, response successfully read (1 bytes).
Trying to send message 10 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 9 ...
 OK, response successfully read (13 bytes).
Trying to send message 11 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to write package 10 ...
 OK, response successfully read (13 bytes).
-> Run lsusb to note any changes. Bye.

lsusb

Output:

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.

dmesg

Output:

[  423.046870] forcedeth 0000:00:07.0: eth0: link down
[  563.630131] usb 1-4.2: new high speed USB device using ehci_hcd and address 6
[  563.850144] usb 1-4.2: reset high speed USB device using ehci_hcd and address 6
[  564.029734] ndiswrapper (link_pe_images:565): fixing KI_USER_SHARED_DATA address in the driver
[  564.038441] ndiswrapper (link_pe_images:565): fixing KI_USER_SHARED_DATA address in the driver
[  564.047155] ndiswrapper: driver rt2870 (Cisco Consumer Products LLC,01/22/2010, 1.04.10.0000) loaded
[  565.451355] wlan0: ethernet device 68:7f:74:e3:f6:4b using NDIS driver: rt2870, version: 0x0, NDIS version: 0x501, vendor: 'IEEE 802.11n Wireless Card.', 13B1:0031.F.conf
[  565.451400] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[  565.591051] ndiswrapper: changing interface name from 'wlan0' to 'wlan1'
[  565.591143] <30>udev[1946]: renamed network interface wlan0 to wlan1
[  565.596657] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  576.213776] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[  587.140030] wlan1: no IPv6 routers present


Offline Profile
PostPosted: Wed Aug 03, 2011 4:49 am
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
I'm going to post a longer dmesg string because I find it strange. Maybe USB_modeswitch is hitting this device earlier? I'm not sure:

Code:
[  176.080124] usb 1-4: new high speed USB device using ehci_hcd and address 4
[  176.231373] hub 1-4:1.0: USB hub found
[  176.231495] hub 1-4:1.0: 3 ports detected
[  176.510290] usb 1-4.1: new high speed USB device using ehci_hcd and address 5
[  176.685933] usbcore: registered new interface driver uas
[  176.716463] Initializing USB Mass Storage driver...
[  176.716745] scsi4 : usb-storage 1-4.1:1.0
[  176.717019] usbcore: registered new interface driver usb-storage
[  176.717025] USB Mass Storage support registered.
[  177.712435] scsi 4:0:0:0: Direct-Access              Cisco AM10       0.00 PQ: 0 ANSI: 2
[  177.713627] sd 4:0:0:0: Attached scsi generic sg2 type 0
[  177.714800] sd 4:0:0:0: [sdb] 253952 512-byte logical blocks: (130 MB/124 MiB)
[  177.715661] sd 4:0:0:0: [sdb] Write Protect is off
[  177.715671] sd 4:0:0:0: [sdb] Mode Sense: 00 00 00 00
[  177.715678] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  177.719422] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  177.849437]  sdb: sdb1
[  177.852419] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  177.852429] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[  179.708734] FAT: Filesystem error (dev sdb1)
[  179.708742]     invalid access to FAT (entry 0x00c00000)
[  179.708750] FAT: Filesystem has been set read-only
[  179.708760] FAT: Filesystem error (dev sdb1)
[  179.708764]     invalid access to FAT (entry 0x00c00000)
[  179.708771] FAT: Filesystem error (dev sdb1)
[  179.708774]     invalid access to FAT (entry 0x00c00000)
[  179.708780] FAT: Filesystem error (dev sdb1)
[  179.708783]     invalid access to FAT (entry 0x00c00000)
[  179.708789] FAT: Filesystem error (dev sdb1)
[  179.708792]     invalid access to FAT (entry 0x00c00000)
[  179.708798] FAT: Filesystem error (dev sdb1)
[  179.708801]     invalid access to FAT (entry 0x00c00000)
[  179.708807] FAT: Filesystem error (dev sdb1)
[  179.708810]     invalid access to FAT (entry 0x00c00000)
[  179.708816] FAT: Filesystem error (dev sdb1)
[  179.708819]     invalid access to FAT (entry 0x00c00000)
[  179.708827] attempt to access beyond end of device
[  179.708835] sdb1: rw=0, want=12586911, limit=253920
[  179.708843] Buffer I/O error on device sdb1, logical block 12586910
[  179.708851] FAT: Filesystem error (dev sdb1)
[  179.708854]     invalid access to FAT (entry 0x00c00000)
[  179.708863] FAT: Filesystem error (dev sdb1)
[  179.708866]     invalid access to FAT (entry 0x00c00000)
[  179.708872] FAT: Filesystem error (dev sdb1)
[  179.708875]     invalid access to FAT (entry 0x00c00000)
[  179.708881] FAT: Filesystem error (dev sdb1)
[  179.708884]     invalid access to FAT (entry 0x00c00000)
[  179.708889] FAT: Filesystem error (dev sdb1)
[  179.708892]     invalid access to FAT (entry 0x00c00000)
[  179.708898] FAT: Filesystem error (dev sdb1)
[  179.708901]     invalid access to FAT (entry 0x00c00000)
[  179.708907] FAT: Filesystem error (dev sdb1)
[  179.708910]     invalid access to FAT (entry 0x00c00000)
[  179.708916] FAT: Filesystem error (dev sdb1)
[  179.708919]     invalid access to FAT (entry 0x00c00000)
[  179.708925] FAT: Filesystem error (dev sdb1)
[  179.708928]     invalid access to FAT (entry 0x00c00000)
[  179.708935] FAT: Filesystem error (dev sdb1)
[  179.708938]     invalid access to FAT (entry 0x00c00000)
[  179.708950] FAT: Filesystem error (dev sdb1)
[  179.708953]     invalid access to FAT (entry 0x00c00000)
[  179.708959] FAT: Filesystem error (dev sdb1)
[  179.708962]     invalid access to FAT (entry 0x00c00000)
[  179.708968] FAT: Filesystem error (dev sdb1)
[  179.708971]     invalid access to FAT (entry 0x00c00000)
[  179.708978] FAT: Filesystem error (dev sdb1)
[  179.708982]     invalid access to FAT (entry 0x00c00000)
[  179.708987] FAT: Filesystem error (dev sdb1)
[  179.708990]     invalid access to FAT (entry 0x00c00000)
[  179.708996] FAT: Filesystem error (dev sdb1)
[  179.708999]     invalid access to FAT (entry 0x00c00000)
[  179.709005] FAT: Filesystem error (dev sdb1)
[  179.709008]     invalid access to FAT (entry 0x00c00000)
[  179.709014] FAT: Filesystem error (dev sdb1)
[  179.709017]     invalid access to FAT (entry 0x00c00000)
[  179.709024] FAT: Filesystem error (dev sdb1)
[  179.709027]     invalid access to FAT (entry 0x00c00000)
[  179.709034] FAT: Filesystem error (dev sdb1)
[  179.709037]     invalid access to FAT (entry 0x00c00000)
[  179.709044] FAT: Filesystem error (dev sdb1)
[  179.709047]     invalid access to FAT (entry 0x00c00000)
[  179.709053] FAT: Filesystem error (dev sdb1)
[  179.709056]     invalid access to FAT (entry 0x00c00000)
[  179.709061] FAT: Filesystem error (dev sdb1)
[  179.709064]     invalid access to FAT (entry 0x00c00000)
[  179.709070] FAT: Filesystem error (dev sdb1)
[  179.709073]     invalid access to FAT (entry 0x00c00000)
[  179.709079] FAT: Filesystem error (dev sdb1)
[  179.709082]     invalid access to FAT (entry 0x00c00000)
[  179.709088] FAT: Filesystem error (dev sdb1)
[  179.709091]     invalid access to FAT (entry 0x00c00000)
[  179.709097] FAT: Filesystem error (dev sdb1)
[  179.709100]     invalid access to FAT (entry 0x00c00000)
[  179.709108] FAT: Filesystem error (dev sdb1)
[  179.709111]     invalid access to FAT (entry 0x00c00000)
[  179.709116] FAT: Filesystem error (dev sdb1)
[  179.709119]     invalid access to FAT (entry 0x00c00000)
[  179.709125] FAT: Filesystem error (dev sdb1)
[  179.709128]     invalid access to FAT (entry 0x00c00000)
[  179.709134] FAT: Filesystem error (dev sdb1)
[  179.709137]     invalid access to FAT (entry 0x00c00000)
[  179.709143] FAT: Filesystem error (dev sdb1)
[  179.709146]     invalid access to FAT (entry 0x00c00000)
[  179.709151] FAT: Filesystem error (dev sdb1)
[  179.709154]     invalid access to FAT (entry 0x00c00000)
[  179.709160] FAT: Filesystem error (dev sdb1)
[  179.709163]     invalid access to FAT (entry 0x00c00000)
[  179.709169] attempt to access beyond end of device
[  179.709175] sdb1: rw=0, want=12586911, limit=253920
[  179.709179] Buffer I/O error on device sdb1, logical block 12586910
[  179.710650] FAT: Filesystem error (dev sdb1)
[  179.710655]     invalid access to FAT (entry 0x37303531)
[  179.710665] FAT: Filesystem error (dev sdb1)
[  179.710669]     invalid access to FAT (entry 0x37303531)
[  179.710675] FAT: Filesystem error (dev sdb1)
[  179.710678]     invalid access to FAT (entry 0x37303531)
[  179.710686] FAT: Filesystem error (dev sdb1)
[  179.710689]     invalid access to FAT (entry 0x37303531)
[  179.710695] FAT: Filesystem error (dev sdb1)
[  179.710698]     invalid access to FAT (entry 0x37303531)
[  179.710703] FAT: Filesystem error (dev sdb1)
[  179.710706]     invalid access to FAT (entry 0x37303531)
[  179.710712] FAT: Filesystem error (dev sdb1)
[  179.710715]     invalid access to FAT (entry 0x37303531)
[  179.710721] FAT: Filesystem error (dev sdb1)
[  179.710724]     invalid access to FAT (entry 0x37303531)
[  179.710732] attempt to access beyond end of device
[  179.710738] sdb1: rw=0, want=925910224, limit=253920
[  179.710744] Buffer I/O error on device sdb1, logical block 925910223
[  179.710751] FAT: Filesystem error (dev sdb1)
[  179.710754]     invalid access to FAT (entry 0x37303531)
[  179.710761] FAT: Filesystem error (dev sdb1)
[  179.710764]     invalid access to FAT (entry 0x37303531)
[  179.710770] FAT: Filesystem error (dev sdb1)
[  179.710773]     invalid access to FAT (entry 0x37303531)
[  179.710779] FAT: Filesystem error (dev sdb1)
[  179.710782]     invalid access to FAT (entry 0x37303531)
[  179.710788] FAT: Filesystem error (dev sdb1)
[  179.710791]     invalid access to FAT (entry 0x37303531)
[  179.710797] FAT: Filesystem error (dev sdb1)
[  179.710800]     invalid access to FAT (entry 0x37303531)
[  179.710806] FAT: Filesystem error (dev sdb1)
[  179.710809]     invalid access to FAT (entry 0x37303531)
[  179.710814] FAT: Filesystem error (dev sdb1)
[  179.710818]     invalid access to FAT (entry 0x37303531)
[  179.710823] FAT: Filesystem error (dev sdb1)
[  179.710826]     invalid access to FAT (entry 0x37303531)
[  179.710846] FAT: Filesystem error (dev sdb1)
[  179.710851]     invalid access to FAT (entry 0x37303531)
[  179.710858] FAT: Filesystem error (dev sdb1)
[  179.710861]     invalid access to FAT (entry 0x37303531)
[  179.710867] FAT: Filesystem error (dev sdb1)
[  179.710871]     invalid access to FAT (entry 0x37303531)
[  179.710876] FAT: Filesystem error (dev sdb1)
[  179.710880]     invalid access to FAT (entry 0x37303531)
[  179.710888] FAT: Filesystem error (dev sdb1)
[  179.710891]     invalid access to FAT (entry 0x37303531)
[  179.710897] FAT: Filesystem error (dev sdb1)
[  179.710900]     invalid access to FAT (entry 0x37303531)
[  179.710906] FAT: Filesystem error (dev sdb1)
[  179.710909]     invalid access to FAT (entry 0x37303531)
[  179.710914] FAT: Filesystem error (dev sdb1)
[  179.710917]     invalid access to FAT (entry 0x37303531)
[  179.710923] FAT: Filesystem error (dev sdb1)
[  179.710926]     invalid access to FAT (entry 0x37303531)
[  179.710933] FAT: Filesystem error (dev sdb1)
[  179.710936]     invalid access to FAT (entry 0x37303531)
[  179.710947] FAT: Filesystem error (dev sdb1)
[  179.710950]     invalid access to FAT (entry 0x37303531)
[  179.710956] FAT: Filesystem error (dev sdb1)
[  179.710959]     invalid access to FAT (entry 0x37303531)
[  179.710965] FAT: Filesystem error (dev sdb1)
[  179.710968]     invalid access to FAT (entry 0x37303531)
[  179.710974] FAT: Filesystem error (dev sdb1)
[  179.710977]     invalid access to FAT (entry 0x37303531)
[  179.710983] FAT: Filesystem error (dev sdb1)
[  179.710986]     invalid access to FAT (entry 0x37303531)
[  179.710991] FAT: Filesystem error (dev sdb1)
[  179.710994]     invalid access to FAT (entry 0x37303531)
[  179.711000] FAT: Filesystem error (dev sdb1)
[  179.711004]     invalid access to FAT (entry 0x37303531)
[  179.711009] FAT: Filesystem error (dev sdb1)
[  179.711012]     invalid access to FAT (entry 0x37303531)
[  179.711020] FAT: Filesystem error (dev sdb1)
[  179.711023]     invalid access to FAT (entry 0x37303531)
[  179.711029] FAT: Filesystem error (dev sdb1)
[  179.711032]     invalid access to FAT (entry 0x37303531)
[  179.711038] FAT: Filesystem error (dev sdb1)
[  179.711041]     invalid access to FAT (entry 0x37303531)
[  179.711047] FAT: Filesystem error (dev sdb1)
[  179.711050]     invalid access to FAT (entry 0x37303531)
[  179.711056] FAT: Filesystem error (dev sdb1)
[  179.711059]     invalid access to FAT (entry 0x37303531)
[  179.711064] FAT: Filesystem error (dev sdb1)
[  179.711067]     invalid access to FAT (entry 0x37303531)
[  179.711073] FAT: Filesystem error (dev sdb1)
[  179.711076]     invalid access to FAT (entry 0x37303531)
[  179.711082] attempt to access beyond end of device
[  179.711088] sdb1: rw=0, want=925910224, limit=253920
[  179.711092] Buffer I/O error on device sdb1, logical block 925910223
[  222.545548] exe (2106): /proc/2106/oom_adj is deprecated, please use /proc/2106/oom_score_adj instead.
[  423.046870] forcedeth 0000:00:07.0: eth0: link down
[  563.630131] usb 1-4.2: new high speed USB device using ehci_hcd and address 6
[  563.850144] usb 1-4.2: reset high speed USB device using ehci_hcd and address 6
[  564.029734] ndiswrapper (link_pe_images:565): fixing KI_USER_SHARED_DATA address in the driver
[  564.038441] ndiswrapper (link_pe_images:565): fixing KI_USER_SHARED_DATA address in the driver
[  564.047155] ndiswrapper: driver rt2870 (Cisco Consumer Products LLC,01/22/2010, 1.04.10.0000) loaded
[  565.451355] wlan0: ethernet device 68:7f:74:e3:f6:4b using NDIS driver: rt2870, version: 0x0, NDIS version: 0x501, vendor: 'IEEE 802.11n Wireless Card.', 13B1:0031.F.conf
[  565.451400] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[  565.591051] ndiswrapper: changing interface name from 'wlan0' to 'wlan1'
[  565.591143] <30>udev[1946]: renamed network interface wlan0 to wlan1
[  565.596657] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  576.213776] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[  587.140030] wlan1: no IPv6 routers present


Offline Profile
PostPosted: Wed Aug 03, 2011 8:34 am
Site AdminPosts: 4855Joined: Sat Nov 03, 2007 12:30 am
I don't find anything strange in the "dmesg" output.

At second 176, you are plugging the stick.

At 177.8 it is being mounted as a storage device. There is a file system error when accessing it, a result of that failed attempt before.

At 423, you are removing (or disabling) the wired ethernet.

At second 563, you are running usb_modeswitch and the new device is popping up as desired. You obviously had everything ready for it, the driver starts going right away.

Rejoice!

As for the crashes and freezes, I'm certainly not the right specialist; using ndiswrapper is always a bit daring, I suppose ...
Or it was really just a routing conflict between wired and wireless connection. I don't know.
Maybe there are traces of what happened in /var/log/syslog ?

Anyway, we had a break-through with the command sequence. All that tedious logging, hard thinking and trying was rewarded in the end. Splendid !!

The next step will be to make everything work automatically. See you after work ...



Offline Profile
PostPosted: Wed Aug 03, 2011 5:42 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
I don't find anything strange in the "dmesg" output.

At second 176, you are plugging the stick.

At 177.8 it is being mounted as a storage device. There is a file system error when accessing it, a result of that failed attempt before.

At 423, you are removing (or disabling) the wired ethernet.

At second 563, you are running usb_modeswitch and the new device is popping up as desired. You obviously had everything ready for it, the driver starts going right away.

Rejoice!

As for the crashes and freezes, I'm certainly not the right specialist; using ndiswrapper is always a bit daring, I suppose ...
Or it was really just a routing conflict between wired and wireless connection. I don't know.
Maybe there are traces of what happened in /var/log/syslog ?

Anyway, we had a break-through with the command sequence. All that tedious logging, hard thinking and trying was rewarded in the end. Splendid !!

The next step will be to make everything work automatically. See you after work ...



I agree, rejoice!!! Ok, I'm here to help get this process automated - how lovely! Sometime soon, someone will be able to more or less just plug in their AM10 and have it work. That is awesome!

Ok, I bet you're right about it being the ndsiwrapper. I'll play around with the driver after we automate things and see if that helps. Talk to you soon. This is great news!

OMS


Offline Profile
PostPosted: Wed Aug 03, 2011 11:24 pm
Site AdminPosts: 4855Joined: Sat Nov 03, 2007 12:30 am
Sent you links to test packages.

Unpack and "make install" the program package.

Unpack and "make install-packed" the data package

Logging is enabled already, so you should get something from usb_modeswitch in /var/log shortly after plugging in.

I assume you have the "tcl" package installed, right?



Offline Profile
PostPosted: Wed Aug 03, 2011 11:32 pm
Site AdminPosts: 4855Joined: Sat Nov 03, 2007 12:30 am
Oh, and I'd like to add you as contributor for the AM10 if you don't object. You really followed through.

If you want, give me your real name (or a nickname of your choice) to go into the device reference file.


Offline Profile
PostPosted: Thu Aug 04, 2011 1:28 am
Posts: 2Location: South Carolina, USAJoined: Tue Jul 26, 2011 6:01 pm
I am following along with great interest. Do you mean tcl and tcl-dev?


Offline Profile
PostPosted: Thu Aug 04, 2011 4:15 am
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
chili555 wrote:
I am following along with great interest. Do you mean tcl and tcl-dev?


I do have tcl and I just installed tcl-dev (why not). I'm trying the new version of usb_modeswitch now!

What exact usb_modeswitch command do you want me to run? Just open terminal and do

Code:
usb_modeswitch
(I tried that and it didn't do anything)

I'll try your previous command until further notice.

I removed both ndiswrapper and the rt3572sta driver - I don't know what driver it's using, but it's now working like a charm!!! At least for the moment. Usually it froze after a few minutes, so I take this as an excellent sign that 1.1.9 is working so far. I like Cisco mode!

I would love to test running this from startup, but it will have to wait for tomorrow morning, I suppose, as I am sleepy.

So, please do let me know what commands and tests you think might help. I'll think about the name to attach to this driver. I feel really honored, thank you.

And I'll try to automate all this and look to see how automating usually works in the past.

Thanks - this is so cool!

OMS


Offline Profile
PostPosted: Thu Aug 04, 2011 8:26 am
Site AdminPosts: 4855Joined: Sat Nov 03, 2007 12:30 am
Uhm, there is a slight misconception ... If the new package works as it is supposed to, you would not have to do anything but plugging the stick !
(Run lsusb repeatedly to see the changes.)

If you haven't had the opportunity yet to have a look on the usb_modeswitch main doc page, feel free to do so. In the "Download" paragraph you can find a link to the "device_reference.txt" which is at the same time the "Hall of Fame" for contributors. In the "Troubleshooting" paragraph, there are hints about usb_modeswitch's logging facility.

The "tcl-dev" package is needed only when you want to develop new extensions for the Tcl language framework, but it won't hurt anybody while just sitting there.

Looking forward to your report. If you find the usb_modeswitch log that you should get in "/var/log", can you post its content here (between <code> tags) ?



Offline Profile
PostPosted: Thu Aug 04, 2011 4:55 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
Uhm, there is a slight misconception ... If the new package works as it is supposed to, you would not have to do anything but plugging the stick !
(Run lsusb repeatedly to see the changes.)


I'd actually read that before. Ok! I know that at the end of this process I should be able to just plug in. So we should be there now... ok! Good to know. It is definitely not happening just by plugging in right now.

Quote:
If you haven't had the opportunity yet to have a look on the usb_modeswitch main doc page, feel free to do so. In the "Download" paragraph you can find a link to the "device_reference.txt" which is at the same time the "Hall of Fame" for contributors. In the "Troubleshooting" paragraph, there are hints about usb_modeswitch's logging facility.

The "tcl-dev" package is needed only when you want to develop new extensions for the Tcl language framework, but it won't hurt anybody while just sitting there.

Looking forward to your report. If you find the usb_modeswitch log that you should get in "/var/log", can you post its content here (between <code> tags) ?



Code:

USB_ModeSwitch log from Fri Jul 29 16:14:54 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 dir exists: /sys/bus/usb/devices/1-4.1
----------------
USB values from sysfs:
  manufacturer   Cisco Systems, Inc.
  product   Cisco AM10 AM10
  serial   000000000000D9
----------------
Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz
Searching overriding entries named: /etc/usb_modeswitch.d/1307:1169*
Aargh! Config file missing for 1307:1169! Exiting


Offline Profile
PostPosted: Thu Aug 04, 2011 5:16 pm
Site AdminPosts: 4855Joined: Sat Nov 03, 2007 12:30 am
The date in the log says it's from July. I think it may be an old one.
Which means there is no new log created. Oh well.

I suppose you installed everything, program and data, as root or with sudo.
You might want to check if there is a file (one file!) named "<...>usb_modeswitch.rules" in the folder
"/lib/udev/rules.d". This is the starting point for the action that follows.



Offline Profile
PostPosted: Thu Aug 04, 2011 5:30 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
The date in the log says it's from July. I think it may be an old one.
Which means there is no new log created. Oh well.


Yes, I've found the log is not always there. If you have ideas on how to get a more consistent log, I'm all ears.

Quote:
I suppose you installed everything, program and data, as root or with sudo.


Yes, as far as I know. Just to be safe I just did it again.

Quote:
You might want to check if there is a file (one file!) named "<...>usb_modeswitch.rules" in the folder
"/lib/udev/rules.d". This is the starting point for the action that follows.



Yes, there is only 40-usb_modeswitch.rules. Ok, I'm ready for the next step.

OMS


Offline Profile
PostPosted: Thu Aug 04, 2011 6:06 pm
Site AdminPosts: 4855Joined: Sat Nov 03, 2007 12:30 am
Now check if logging is really enabled (and global switching not disabled) in
/etc/usb_modeswitch.conf.

Edit: just checked that file in my own package. Turns out I was already too tired when preparing it.

"DisableSwitching" is active and "EnableLogging" is not. It should be the other way round ...

Sorry for that hickup. Not enough sleep lately.



Offline Profile
PostPosted: Thu Aug 04, 2011 6:41 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
Now check if logging is really enabled (and global switching not disabled) in
/etc/usb_modeswitch.conf.

Edit: just checked that file in my own package. Turns out I was already too tired when preparing it.

"DisableSwitching" is active and "EnableLogging" is not. It should be the other way round ...

Sorry for that hickup. Not enough sleep lately.



Ah I thought it was me who had done that! Anyway, now I changed it - Disable is 0, logging is 1. I just reset and here is the log:

Code:
USB_ModeSwitch log from Thu Aug 04 12:37:23 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: /etc/usb_modeswitch.d/1307:1169
Using config file from override folder /etc/usb_modeswitch.d
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -c /etc/usb_modeswitch.d/1307:1169)


Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 4 of 9
131 posts
Go to page Previous  1, 2, 3, 4, 5, 6, 7 ... 9  Next
Users browsing this forum: No registered users and 1 guest
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum