Can't get Multi-Tech MT9234ZBA-USB modem to work

gunhed · 12-23-2008, 04:49 PM

I'm running CentOS 5.2 with a 2.6.27.2 linux kernel. I've got a Multi-Tech MT9234ZBA-USB external modem that I can't get to work. I tested the modem on a Windows system, so I know the hardware is good. When I plug the modem into any USB port on the linux system, I get some basic responses in the logs, but no tty is being assigned to it (i.e. /dev/ttyUSB0). I'm using the mts_ti_usb-2.6-1.3.1-1.i386.rpm drivers downloaded from Multi-Tech's web site, which installed OK. I've also attempted to compile the source code drivers, but I can't for the life of me get it to compile - major headache.

After the RPM driver install, I did an 'lsmod', and it seems to be installed and active:

Code:

Module                  Size  Used by
ti_usb_3410_5052       25416  0
usbserial              30696  1 ti_usb_3410_5052

There are no errors showing in the logs, but I do see that the install was noticed in the kernel logs:

Code:

Dec 23 15:41:13 comm0 kernel: usbcore: registered new interface driver usbserial
Dec 23 15:41:13 comm0 kernel: usbserial: USB Serial support registered for generic
Dec 23 15:41:13 comm0 kernel: usbcore: registered new interface driver usbserial_generic
Dec 23 15:41:13 comm0 kernel: usbserial: USB Serial Driver core
Dec 23 15:41:13 comm0 kernel: usbserial: USB Serial support registered for TI USB 3410 1 port adapter
Dec 23 15:41:13 comm0 kernel: usbserial: USB Serial support registered for TI USB 5052 2 port adapter
Dec 23 15:41:13 comm0 kernel: usbcore: registered new interface driver ti_usb_3410_5052
Dec 23 15:41:13 comm0 kernel: ti_usb_3410_5052: TI USB 3410/5052 Serial Driver v0.9

When the modem is connected, I see activity in the kernel log:

Code:

Dec 23 15:46:46 comm0 kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2
Dec 23 15:46:46 comm0 kernel: usb 2-1: configuration #1 chosen from 1 choice

When the modem is disconnected, the logs simply says:

Code:

Dec 23 15:48:11 comm0 kernel: usb 2-1: USB disconnect, address 2

...And that's all. There are no errors to speak of, and I don't see any attempt to register a tty (there are no new tty devices listed in /dev), so there's nothing to talk to. Any and all attempts to access standard ttys (ttyS0), etc. get no response (using minicom), so I know it's not trying to use any of those. Other USB modems actually show a tty being assigned (i.e. ttyACM0), and they appear dynamically in /dev. What am I missing?