-
- Posts: 7
- Joined: 30 Aug 2010, 15:21
-
- Posts: 7
- Joined: 30 Aug 2010, 15:21
After updating libpcap I see my wireshark dump as follows from link: http://pastebin.com/4FPMbxXX
It looks almost similar to SniffUSB one.
I suspect that I connected the usb-device to the virtualbox machine near the frame#165.
I even used 55534243123456780800000080000a4a010000100000000800000000000000 and 55534243123456781200000080000603000000120000000000000000000000 messages for usb_modeswitch but had no success.
Do you have a chance of taking a look at the packets dump to check if there is anything to point out to correct message(s) I should use?
PS. The driver was completely installed before I connected device to windows. After connecting a device Linux displayed
in its log.
I can provide the whole dump starting from installing a driver in windows if it could help.
Thanks in advance.
It looks almost similar to SniffUSB one.
I suspect that I connected the usb-device to the virtualbox machine near the frame#165.
I even used 55534243123456780800000080000a4a010000100000000800000000000000 and 55534243123456781200000080000603000000120000000000000000000000 messages for usb_modeswitch but had no success.
Do you have a chance of taking a look at the packets dump to check if there is anything to point out to correct message(s) I should use?
PS. The driver was completely installed before I connected device to windows. After connecting a device Linux displayed
Code: Select all
Sep 13 21:34:07 t500 kernel: [17349.438132] usbcore: registered new interface driver cdc_acm
Sep 13 21:34:07 t500 kernel: [17349.439242] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
I can provide the whole dump starting from installing a driver in windows if it could help.
Thanks in advance.
Thanks for the wireshark log, it provided some interesting insights. I only could respond just now because I have been travelling.
Now, could one of you AirPlus owners try the following manual command? To check if it does anything good just run dmesg afterwards and see if "cdc_acm" was activated (like after switching in Windows).
Now, could one of you AirPlus owners try the following manual command? To check if it does anything good just run dmesg afterwards and see if "cdc_acm" was activated (like after switching in Windows).
Code: Select all
usb_modeswitch -I -v 1edf -p 6003 -u 2
after running this command got device /dev/ttyACM0 usable as modem, working fine.Josh wrote:Thanks for the wireshark log, it provided some interesting insights. I only could respond just now because I have been travelling.
Now, could one of you AirPlus owners try the following manual command? To check if it does anything good just run dmesg afterwards and see if "cdc_acm" was activated (like after switching in Windows).
Code: Select all
usb_modeswitch -I -v 1edf -p 6003 -u 2
dmesg|tail
sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00
sr: Sense Key : Hardware Error [current]
sr: Add. Sense: No additional sense information
usb 4-2: reset full speed USB device using uhci_hcd and address 4
usb 4-2: reset full speed USB device using uhci_hcd and address 4
usb 4-2: reset full speed USB device using uhci_hcd and address 4
usb 4-2: reset full speed USB device using uhci_hcd and address 4
usb 4-2: reset full speed USB device using uhci_hcd and address 4
usb 4-2: reset full speed USB device using uhci_hcd and address 4
cdc_acm 4-2:2.0: ttyACM0: USB ACM device
Thanks!
I think that "sense error" is what we see in the Windows log as well, where it takes around 10 seconds for the device to arrive at the modem mode. It might help to detach the storage driver first; try:
Code: Select all
usb_modeswitch -I -d -v 1edf -p 6003 -u 2
-
- Posts: 7
- Joined: 30 Aug 2010, 15:21
Works great!
Thanks a lot, Josh!
Code: Select all
Oct 26 17:17:34 t500 kernel: [531365.905190] scsi 4:0:0:0: rejecting I/O to dead device
Oct 26 17:17:34 t500 kernel: [531365.911728] cdc_acm 6-2:2.0: ttyACM0: USB ACM device
Oct 26 17:17:34 t500 kernel: [531365.914426] usbcore: registered new interface driver cdc_acm
Oct 26 17:17:34 t500 kernel: [531365.914429] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Oct 26 17:17:34 t500 modem-manager: (ttyACM0) opening serial device...
Oct 26 17:17:34 t500 modem-manager: (ttyACM0): probe requested by plugin 'Generic'
Oct 26 17:17:35 t500 modem-manager: (ttyACM0) closing serial device...
Oct 26 17:17:35 t500 modem-manager: (Generic): CDMA modem /sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2 claimed port ttyACM0
Oct 26 17:17:35 t500 modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2
Oct 26 17:17:35 t500 modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2 as /org/freedesktop/ModemManager/Modems/0
Oct 26 17:17:36 t500 NetworkManager: <info> (ttyACM0): new CDMA device (driver: 'cdc_acm')
Oct 26 17:17:36 t500 NetworkManager: <info> (ttyACM0): exported as /org/freedesktop/NetworkManager/Devices/2
Oct 26 17:17:36 t500 NetworkManager: <info> (ttyACM0): now managed
Oct 26 17:17:36 t500 NetworkManager: <info> (ttyACM0): device state change: 1 -> 2 (reason 2)
Oct 26 17:17:36 t500 NetworkManager: <info> (ttyACM0): deactivating device (reason: 2).
Oct 26 17:17:36 t500 NetworkManager: <info> (ttyACM0): device state change: 2 -> 3 (reason 0)
-
- Posts: 7
- Joined: 30 Aug 2010, 15:21
Code: Select all
:~# time usb_modeswitch -c /etc/usb_modeswitch.d/1edf\:6003
Looking for default devices ...
Found default devices (1)
Accessing device 004 on bus 003 ...
USB description data (for identification)
-------------------------
Manufacturer: Selectwireless Incorporated
Product: Selectwireless CDMA USB Modem
Serial No.: Data Interface
-------------------------
Only detaching storage driver for switching ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Changing configuration to 2 ...
OK, configuration set
-> Run lsusb to note any changes. Bye.
real 0m0.479s
user 0m0.010s
sys 0m0.000s