TP-Link MA180The TP-Link MA180 is in their words a "3.75G HSUPA USB Adapter".
I'm not using udev on this system, but the usb_modeswitch config file that works for me is: Code: Select all
Re: TP-Link MA180Hi Complexgeek, I just purchase TP Link MA180, unfortunately not working on my linux machine (linuxmint). I just google and found this post on this forum. Could you detail as above code, how i could tweak on modeswitch config? or simple tutorial? Thanks! please share how u get TP-Link MA180 to work. I got v1 here but cant get it to work
all I see upon plugging in the device is [ 7772.715779] usb 4-2: new full-speed USB device number 3 using uhci_hcd [ 7773.044891] generic-usb 0003  F006.0006: hiddev0,hidraw3: USB HID v1.10 Device [TP-LINK, Incorporated TP-LINK HSUPA Modem] on usb-0000:00:1a.1-2/input0[ 7774.211050] usb 4-2: USB disconnect, device number 3 [ 7777.205605] usb 1-4: new high-speed USB device number 8 using ehci_hcd [ 7777.343862] scsi7 : usb-storage 1-4:1.0 [ 7778.343029] scsi 7:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 [ 7778.343786] scsi 7:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 [ 7778.347004] sr2: scsi-1 drive [ 7778.347362] sr 7:0:0:0: Attached scsi CD-ROM sr2 [ 7778.347623] sr 7:0:0:0: Attached scsi generic sg8 type 5 [ 7778.348480] sd 7:0:0:1: Attached scsi generic sg9 type 0 [ 7778.350570] sd 7:0:0:1: [sdg] Attached SCSI removable disk I cant unmount nor eject something. Trying to adopt your modeswitch_config resulted in sudo usb_modeswitch -c /etc/usb_modeswitch.d/2357\:0201 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 008 on bus 001 ... Getting the current device configuration ... OK, got current device configuration (1) Using first interface: 0x00 Using endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) ------------------------- Manufacturer: TP-LINK, Incorporated Product: TP-LINK HSUPA Modem Serial No.: 863077010030736 ------------------------- Looking for active driver ... No driver found. Either detached before or never attached Setting up communication with interface 0 Using endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... Sending the message returned error -110. Trying to continue Resetting response endpoint 0x81 Resetting message endpoint 0x01 Checking for mode switch (max. 10 times, once per second) ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... Searching for target devices ... No new devices in target mode or class found Mode switch has failed. Bye.
I am interested in more information about this, too. I have this TP-Link MA180 modem and I don't know how to make it work in an OpenWRT router (fonera2.0n). I put the sugested file in /etc/usb_modemswitch.d/2357:0200 but I have no idea about next steps. Thank you for any help. -- Alfredo "Freddy" Soro MA180 not switchingHi all,
I have downloaded and installed the latest data package (as of 2012/08/22), however the TP-Link MA180 fails to mode switch. I'm running Ubuntu 12.04LTS. Below is the USB device info and the output of running usb_modeswitch manually. Any idea where the problem lies? I'm happy to try any suggestions and report back here. Code: Select all Code: Select all
tp-link ma180 works on fedora 17Managed to get the modem working for Fedora 17 with the following steps:
________________________________________________________________________ Create a new file: /etc/usb_modeswitch.d/2357:0200 contains: # TP-Link MA180 TargetVendor= 0x2357 TargetProduct= 0x0201 MessageContent="5553424312345678000000000000061b000000020000000000000000000000" _________________________________________________________________________ Add a new entry: # TP-Link MA180 ATTRS{idVendor}=="2357", ATTRS{idProduct}=="0200", RUN+="usb_modeswitch '%b/%k'" to /usr/lib/udev/rules.d/40-usb_modeswitch.rules __________________________________________________________________________ unplugged and plugged in the usb modem. Many activities show in /var/log/messages. The NetworkManager sees the device. To setup the mobile broadband, right click on the Network icon at the top-right corner to edit. Left click to activate. Re: TP-Link MA180Hi,
I am using a TP-Link MA180 V1.1 and I have tried this config and it is not working for me under Ubuntu 12.04, with the latest mode switch and mode switch data. According to Windows the default and target VIDS/PIDS are the same. When running modeswitch manually with your config I get the following output Code: Select all I have tried sniffing under Windows and got a different string... Code: Select all Thanks Richard Re: TP-Link MA180There seems to be an unresolved issue with USB 3.0 ports, where the behaviour is very much the same as the one you are seeing:
https://bugs.launchpad.net/bugs/979697 The current hypothesis is that there is a certain driver/hardware combination causing this. So if you are in fact on a 3.0 port, try annother one if avaiable. Re: TP-Link MA180I have't tried with USB 3.0 ports, only 2.0 on three different machines now... however all are running Ubuntu 12.04.
I will try with OpenWRT and Fedora when I get a chance and post any developments. Re: TP-Link MA180Not working for me
The first stage, usb_modeswitch, appears to succeed, the new device 2357:0201 appears after about 5 seconds However, there are no /dev/ttyUSB* devices and /proc/bus/usb/devices doesn't appear to show any comm class devices I am using OpenWRT attitude adjustment on the TL-WR1043ND Code: Select all Re: TP-Link MA180Hmm, maybe usbserial was already loaded before?
To be on the safe side, I'd try to "rmmod usbserial" before loading it again with the new ID. BTW, are you sure there is no "option" module on your OpenWRT installation? This is the recommended driver for all things 3G. Re: TP-Link MA180Ok, further observations, my OpenWRT didn't actually have the usbserial module package installed at all
However, there was no error output from the insmod command, so I had no idea that usbserial was missing I've install kmod-usb-serial and kmod-usb-serial-wwan, I find that I can load usbserial with this command: Code: Select all Do you believe I should definitely use the `option' drive with the TP-Link? These are the modules available from OpenWRT: Code: Select all |