On Wed, 2013-01-09 at 16:54 +0800, hockseng leow wrote: > I got the dmesg after having the parameters, usbserial.vendor=0x2357 > usbserial.product=0x0200" in the linux start-up. > > I already got the modem working under usb_modeswitch. > > No further work need to be done in the kernel. Are you able to provide the Windows .INF files from the device so we can determine what kernel drivers each interface of the device requires? Basically, instead of modeswitching the device, let the fake CD disk appear, tar+gzip the contents of the fake CD, and mail it to me so I can inspect it. What specific model number is this device? Is it the MA180? Or is it the MA260? What model number is printed on the device? Does it have an FCC ID printed anywhere on it? >From what I can see, after being switched, the device exposes 5 USB interfaces: 0: bulk in/out; FF FF FF 1: bulk in/out; FF FF FF 2: USB Storage (SD card) 3: bulk in/out + interrupt; FF FF FF 4: bulk in/out + interrupt; FF FF FF One of 3 or 4 is going to be the AT/PPP interface, while other one could be a pseudo-ethernet network interface port, perhaps with QMI. The device appears to use a MSM6290 chip, which means that interface 0 and 1 are likely either DIAG, NMEA, or secondary AT. Without the drivers we don't know for sure. Dan > Thanks. > > On Wed, Jan 9, 2013 at 12:46 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Jan 08, 2013 at 11:07:22PM +0800, hockseng leow wrote: > >> Hello, > >> > >> Please add the modem to a proper driver. > >> > >> Attached is the dmesg. > > > > What type of device is this? And where did you get the instructions > > that told you to add it to the generic USB Serial driver? > > > >> [51536.010224] usb 2-1.4: new full-speed USB device number 10 using uhci_hcd > >> [51536.224219] usb 2-1.4: New USB device found, idVendor=2357, idProduct=f006 > >> [51536.224233] usb 2-1.4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 > >> [51536.224243] usb 2-1.4: Product: TP-LINK HSUPA Modem > >> [51536.224252] usb 2-1.4: Manufacturer: TP-LINK, Incorporated > >> [51536.282204] hid-generic 0003:2357:F006.0006: hiddev0,hidraw2: USB HID v1.10 Device [TP-LINK, Incorporated TP-LINK HSUPA Modem] on usb-0000:00:1d.0-1.4/input0 > > > > Is this the same device? > > > >> [51537.811244] usb 2-1.4: USB disconnect, device number 10 > >> [51541.185312] usb 2-1.4: new full-speed USB device number 11 using uhci_hcd > >> [51541.274295] usb 2-1.4: not running at top speed; connect to a high speed hub > >> [51541.301304] usb 2-1.4: New USB device found, idVendor=2357, idProduct=0200 > >> [51541.301319] usb 2-1.4: New USB device strings: Mfr=3, Product=2, SerialNumber=4 > >> [51541.301329] usb 2-1.4: Product: TP-LINK HSUPA Modem > >> [51541.301338] usb 2-1.4: Manufacturer: TP-LINK, Incorporated > >> [51541.301346] usb 2-1.4: SerialNumber: 863077010232324 > >> [51541.309529] usbserial_generic 2-1.4:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes. > >> [51541.309548] usbserial_generic 2-1.4:1.0: Tell linux-usb@xxxxxxxxxxxxxxx to add your device to a proper driver. > >> [51541.309560] usbserial_generic 2-1.4:1.0: generic converter detected > >> [51541.310190] usb 2-1.4: generic converter now attached to ttyUSB0 > > > > It looks like you unplugged the device and then assigned it to the > > generic USB serial device instead? What happened to cause it to do > > this? > > > > thanks, > > > > greg k-h > > > > -- > Leow Hock Seng > Tel:64463211 > Mobile:96740759 > http://www.oses.sg > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
