Once aggain I have had some limited success.
Firstly, loging off and on again had no effect. Even tried rebooting and that was no better.
I was baffled at the fact that both the network manager (that is what that icon which lists all the available networks attaches to... isn't it) and wvdial were telling me I have a connection, but FireFox, Evolution and even the ping in Network Tools were telling me otherwise.
By way of experiment, I tried going through all the old steps which I'd tried earlier with both the CS-15 and the MA260 after removing and re-inserting the dongle. Here's a transcript of that session:
Code:
achim@achim-W840SU-Series:~$ dmesg| tail -40
[15313.614715] usb-storage 2-2.1:1.0: USB Mass Storage device detected
[15313.614969] scsi7 : usb-storage 2-2.1:1.0
[15314.613014] scsi 7:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[15314.613709] scsi 7:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[15314.616531] sr0: scsi-1 drive
[15314.616864] sr 7:0:0:0: Attached scsi CD-ROM sr0
[15314.617122] sr 7:0:0:0: Attached scsi generic sg1 type 5
[15314.617693] sd 7:0:0:1: Attached scsi generic sg2 type 0
[15314.631034] sd 7:0:0:1: [sdb] Attached SCSI removable disk
[15314.636550] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 10 ep 2 with no TDs queued?
[15314.654642] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 10 ep 2 with no TDs queued?
[15515.014434] usb 2-2.1: usbfs: process 4278 (usb_modeswitch) did not claim interface 0 before use
[15633.177257] usb 2-2.1: usbfs: process 4284 (usb_modeswitch) did not claim interface 0 before use
[15794.019444] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[15794.033831] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[15794.085755] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
[15794.085901] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
[15794.094116] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[15794.094368] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[15794.110665] r8169 0000:03:00.1 eth0: link down
[15794.110709] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[15794.110996] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[15802.430715] wlan0: authenticate with 00:15:0c:82:df:5e
[15802.431700] wlan0: send auth to 00:15:0c:82:df:5e (try 1/3)
[15802.433722] wlan0: authenticated
[15802.434085] iwlwifi 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[15802.434097] iwlwifi 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[15802.436136] wlan0: associate with 00:15:0c:82:df:5e (try 1/3)
[15802.438568] wlan0: RX AssocResp from 00:15:0c:82:df:5e (capab=0x461 status=0 aid=47)
[15802.439591] wlan0: associated
[15802.439650] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[15817.668247] wlan0: deauthenticating from 00:15:0c:82:df:5e by local choice (reason=3)
[15817.669729] cfg80211: Calling CRDA to update world regulatory domain
[15817.679166] cfg80211: World regulatory domain updated:
[15817.679175] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[15817.679180] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[15817.679185] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[15817.679189] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[15817.679193] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[15817.679197] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
achim@achim-W840SU-Series:~$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 003: ID 8087:07dc Intel Corp.
Bus 002 Device 004: ID 5986:0536 Acer, Inc
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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 013: ID 2357:f000
Bus 002 Device 005: ID 03f0:2112 Hewlett-Packard OfficeJet Pro L7500
Bus 002 Device 012: ID 0557:2221 ATEN International Co., Ltd
achim@achim-W840SU-Series:~$ sudo usb_modeswitch -v 0x2357 -p 0xf000 -P 0x9000 -M "5553424312345678000000000000061b000000020000000000000000000000"
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 013 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Nothing further happened and I hit Ctrl-C. The session continues... note carefully the next use of usb_modeswitch, it gives an interesting result:
Code:
^Cachim@achim-W840SU-Series:~$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 003: ID 8087:07dc Intel Corp.
Bus 002 Device 004: ID 5986:0536 Acer, Inc
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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 013: ID 2357:f000
Bus 002 Device 005: ID 03f0:2112 Hewlett-Packard OfficeJet Pro L7500
Bus 002 Device 012: ID 0557:2221 ATEN International Co., Ltd
achim@achim-W840SU-Series:~$ sudo usb_modeswitch -v 0x2357 -p 0xf000 -P 0x9000 -M "5553424312345678000000000000061b000000020000000000000000000000"
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 013 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
SCSI inquiry data (for identification)
-------------------------
Vendor String: TP-LINK
Model String: MMC Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: TP-LINK, Incorporated
Product: TP-LINK HSPA+ Modem
Serial No.: 863745010134688
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
-> Run lsusb to note any changes. Bye.
achim@achim-W840SU-Series:~$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 003: ID 8087:07dc Intel Corp.
Bus 002 Device 004: ID 5986:0536 Acer, Inc
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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 013: ID 2357:f000
Bus 002 Device 005: ID 03f0:2112 Hewlett-Packard OfficeJet Pro L7500
Bus 002 Device 012: ID 0557:2221 ATEN International Co., Ltd
achim@achim-W840SU-Series:~$ dmesg| tail -40
[15802.439650] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[15817.668247] wlan0: deauthenticating from 00:15:0c:82:df:5e by local choice (reason=3)
[15817.669729] cfg80211: Calling CRDA to update world regulatory domain
[15817.679166] cfg80211: World regulatory domain updated:
[15817.679175] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[15817.679180] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[15817.679185] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[15817.679189] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[15817.679193] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[15817.679197] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[15870.987419] usb 2-2.1: USB disconnect, device number 11
[15885.059596] usb 2-2.4: USB disconnect, device number 10
[15885.430177] usb 2-2.4: new low-speed USB device number 12 using xhci_hcd
[15885.454519] usb 2-2.4: New USB device found, idVendor=0557, idProduct=2221
[15885.454530] usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[15885.454536] usb 2-2.4: Product: UC-10KM V1.3.124
[15885.454542] usb 2-2.4: Manufacturer: ATEN
[15885.454547] usb 2-2.4: SerialNumber: USB Composite device
[15885.454830] usb 2-2.4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[15885.454846] usb 2-2.4: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[15885.463083] input: ATEN UC-10KM V1.3.124 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.4/2-2.4:1.0/input/input19
[15885.463347] hid-generic 0003:0557:2221.0007: input,hidraw0: USB HID v1.10 Keyboard [ATEN UC-10KM V1.3.124] on usb-0000:00:14.0-2.4/input0
[15885.468886] input: ATEN UC-10KM V1.3.124 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.4/2-2.4:1.1/input/input20
[15885.469221] hid-generic 0003:0557:2221.0008: input,hidraw1: USB HID v1.10 Mouse [ATEN UC-10KM V1.3.124] on usb-0000:00:14.0-2.4/input1
[15888.584423] usb 2-2.1: new high-speed USB device number 13 using xhci_hcd
[15888.603084] usb 2-2.1: New USB device found, idVendor=2357, idProduct=f000
[15888.603095] usb 2-2.1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[15888.603102] usb 2-2.1: Product: TP-LINK HSPA+ Modem
[15888.603108] usb 2-2.1: Manufacturer: TP-LINK, Incorporated
[15888.603112] usb 2-2.1: SerialNumber: 863745010134688
[15888.782697] usb-storage 2-2.1:1.0: USB Mass Storage device detected
[15888.782928] scsi8 : usb-storage 2-2.1:1.0
[15889.780901] scsi 8:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[15889.781654] scsi 8:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[15889.783794] sr0: scsi-1 drive
[15889.784378] sr 8:0:0:0: Attached scsi CD-ROM sr0
[15889.787007] sr 8:0:0:0: Attached scsi generic sg1 type 5
[15889.787906] sd 8:0:0:1: Attached scsi generic sg2 type 0
[15889.793912] sd 8:0:0:1: [sdb] Attached SCSI removable disk
[15961.741991] usb 2-2.1: usbfs: process 4530 (usb_modeswitch) did not claim interface 0 before use
achim@achim-W840SU-Series:~$ sudo usb_modeswitch -v 0x2357 -p 0xf000 -P 0x9000 -M "5553424312345678000000000000061b000000020000000000000000000000"
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 013 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
^Cachim@achim-W840SU-Series:~$
At this point nothig was happening, so again I hit Ctrl-C. The interesing part is that second use of usb_modeswitch, which suggested that the system had correctly identified and initialised the device. The subsequent lsusb contradicts this. What happens after that is something of a mystery.
Subsequently running wvdial gave the following unhappy result:
Code:
achim@achim-W840SU-Series:~$ sudo wvdial
--> WvDial: Internet dialer version 1.61
--> Cannot open /dev/ttyUSB2: No such file or directory
--> Cannot open /dev/ttyUSB2: No such file or directory
--> Cannot open /dev/ttyUSB2: No such file or directory
Now it gets positively weird... I again removed and re-inserted the dongle. Then I used the disk utility to "eject" the phantom CD drive. Then I ran wvdial with the following result:
Code:
achim@achim-W840SU-Series:~$ sudo wvdial
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: AT+CGDCONT=1,"IP","internet.t-mobile","",0,0
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
CONNECT 7200000
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sun Feb 16 20:54:13 2014
--> Pid of pppd: 4696
--> Using interface ppp0
--> pppd: x�w�8��[08][10]��[08][01]
--> pppd: x�w�8��[08][10]��[08][01]
--> pppd: x�w�8��[08][10]��[08][01]
--> pppd: x�w�8��[08][10]��[08][01]
--> pppd: x�w�8��[08][10]��[08][01]
--> pppd: x�w�8��[08][10]��[08][01]
--> local IP address 10.29.207.244
--> pppd: x�w�8��[08][10]��[08][01]
--> remote IP address 10.64.64.64
--> pppd: x�w�8��[08][10]��[08][01]
--> primary DNS address 10.74.210.210
--> pppd: x�w�8��[08][10]��[08][01]
--> secondary DNS address 10.74.210.211
--> pppd: x�w�8��[08][10]��[08][01]
Clearly it was claiming once again that a connection had been established. I didn't hold out much hope, but for the sake of completeness I tried accessing a website from FireFox. Bingo! It worked. I am using that connection to submit this post. The Network manager also tells me that my default wireless broadband connection is available.
Does anybody have an idea of what is going on?
Addendum
In case anybody is following this, I have some encouraging news. This evening I tried the procedure again.
1. start Network Manager (I don't think this is required in this situation but if you use a NM connection mechanism you'll need to do this)
2. System > Control Center > Drive Utility.
3. Select the "CD drive" that corresponds to your dongle and click the "eject" button.
4. Start your wvdial script and you should get a connection (in this case you probably don't need step 1). Alternatively, check the NM icon and see if your Broadband config is listed as active and available. If so, you can select that and you should be online.
The good news is that it still works as it did the first time . The not so good news is that I haven't the vaguest idea why it didn't work before. Still, for any MA260 users out there it is worth try.
I am going to try other approaches in the coming days to see if there isn't a more convenient way to get the MA260 to respond (sorry, I can't do it faster than that). Incidentally, although I'm still using 12.04 LTS, I am now running kernel 3.11.0-15. My advice to anybody with htis device is to upgrade as soon as possible. If you need long term support, as I do, do the kernel enablement as described here and upgrade to 14.04 when it comes out.
I'll keep updating this over the next few days with the results of my experimentation. After that I think I'll mark this as solved.
@Sandro Kensan: I don't know if this will help with your distro. If you try the method, please let me know if it works or not. Good Luck whatever you try.
Adv Reply
Re: TP Link MA260, Ubuntu 12.04 LTS
Originally Posted by epek
Bookmarks