Use of the Multitech Multimodem MTCBA-G-U-F1 on Debian Linux

Multitech gprs modems are, I believe the best GPRS (Internet over GMS cellular telephone) modem available in the world today, at any price

In this article I refer to model  MTCBA-G-U-F1.  This is an industrial-quality modem with USB connection.

<SNIP>

Oct. 21, 2009 update:
This article used to provide patches to be able to use the Multitech USB modems with kernels 2.6.20.3.  However, this is no longer necessary, since as-of kernel 2.6.30.1, the module ti_usb_3410_5052 has been updated to work with the Multitech multimodems!  All you need to do is get this kernel version, or later, and forget about patching.  As far as I'm concerned, this news obsoletes this original article, which I have removed.  Go get a modern kernel!

I'm not sure whether or not the updated ti_usb_3410_5052 driver code is in the Debian kernels (due to licensing issues, but it is in the vanilla kernel from http://www.kernel.org, as well as in the precompiled Ubuntu kernels.

The 2.6.30.1 Ubuntu kernel can be downloaded here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30.1/  Remember that all LATER kernels should work too.

Heads Up:
These new kernels looks for the firmware in /lib/firmware/<kernel version>/  (replace <kernel version> with the output of "uname -r").

 

Comments

How to install 2.6.20 kernel

Hi!
I have downloaded the 2.6.20 kernel version with USB support. I dont know how to use this kernel . I installed using dpkg -i 2.6.20....deb but now I dont know how to use mu modem .
Can u post any help or guide to use the modem after install your kernel ??

TIA

Did you do anything more

Did you do anything more than install the kernel? You are supposed to do the following as well, most of which is indicated in my article and in the readme.txt file in the multimodem.zip file:

1. Boot into Linux using the new kernel. If the deb package did not create an entry in your grub menu, or you are not using grub but rather lilo to boot linux, you will have to read up on how to boot multiple kernels using your chosen boot loader. (Probably all you need to do is reboot your computer and choose the kernel whose name ends "mm5".)
2. Install the firmware and grps connection script. For this you need to download the file multimodem.zip (see my article above) and extract the 3 directories it contains into the root of your filesystem. You will need admin privileges to do this.
3. As my article also explains:
"You will need to set your GSM telephone PIN in the file /etc/ppp/peers/gprs-connect-chatmm, set your username in /etc/ppp/peers/gprsmm, and add a line with your username and password to /etc/peers/ppp/pap-secrets"

If you are unable to get this working, you can download the Puppy Linux 4.11 iso, "retro", and burn to CD. Puppy does not require its own Linux partition to use. In fact, it does not require a Linux partition at all.

This version of Puppy has the Multitech Multimodem USB connection driver built in, as well as the firmware. Boot it from the CD and click the "Connect" icon on the desktop, choose GPRS. It has a nice GUI to set up the GPRS connection - no editing ppp configuration files.

Installing new kernel for etch

Hi!
I am using your precompiled kernel into VM and I get an error and kernel panic
the error is this:
VFS:Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel Panic - not synccing: VFS Unable to mount root to fs on unknown-block(0,0)

How can I solve this ?
TIA

It looks to me like you need

It looks to me like you need to check your "root=" boot option (probably in file /boot/grub/menul.lst), like the error message suggests. This is a basic filesystem access issue. The correct "root=" boot option probably is something like "root=/dev/hda1". I think you want "hdxx" device names, since I don't think my precompiled kernel uses libata, which uses the newer "sda" (sata) drive access.

Note that since kernel version 2.6.30.1, the module ti_usb_3410_5052 has been updated to work with the Multitech multimodems! All you need to do is get this kernel version, or later, and forget about patching. As far as I'm concerned, this news obsoletes this article. Go get a modern kernel.

I'm not sure whether or not the updated code is in the Debian kernels, but it is in the vanilla kernel from http://www.kernel.org, as well as in the precompiled Ubuntu kernels. The 2.6.30.1 kernel can be downloaded here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30.1/

Heads Up:
These new kernels looks for the firmware in /lib/firmware// (replace

Thks! for information.i

Thks! for information.
i downloaded the new kernel 2.6.31.1 to test my modem. But I have one question yet.... I wanna use my modem to send SMS but I dont know how configure to do this,
Can you put me in rogth direction to do this?/

Thks in Advance

Edwin Quijada

Sorry, I know nothing about

Sorry, I know nothing about using this modem for SMS (Smart Message Service). You should contact Multitech support through their website at http://www.multitech.com.

Multitech MTCBA G-U-F4

Hello,
I installed the driver for MTCBA G-U-F4 in a kernel 2.4.20-8. Then this is What I do:

1) I load the module by doing "modprobe ti_usb"
2) I connect the Modem to the usb port
3) I can see the modem by doing "lsusb"

My problem is that the modem is not turned or when the power led button be ON?
I peformed all the steps the documentation mention, compiled the kernel, etc...
Any suggestion or what else I can do make this device working?

This is what I see in the log and I'm not sure if something is wrong or how do I know that is working properley?:

------------------------------------------
Jan 15 19:39:00 BlueAgent2 /etc/hotplug/usb.agent: Setup ti_usb for USB product 6e0/f111/101
Jan 15 19:39:00 BlueAgent2 kernel: usb.c: registered new driver ti_usb
Jan 15 19:39:00 BlueAgent2 kernel: ti_usb_serial.c: TI USB Serial support registered for TI USB 3410 1 port adapter
Jan 15 19:39:00 BlueAgent2 kernel: ti_usb_serial.c: detected TI USB 3410 1 port adapter, vendor 0x06E0, product 0xF111, ser
ial number 'NA'
Jan 15 19:39:00 BlueAgent2 kernel: invalid operand: 0000
Jan 15 19:39:00 BlueAgent2 kernel: ti_usb bnep rfcomm l2cap hci_usb hci_uart bluez cisco_ipsec autofs via-rhine mii keybdev
mousedev hid input usb-uhci usbcore ext3 jbd
Jan 15 19:39:00 BlueAgent2 kernel: CPU: 0
Jan 15 19:39:00 BlueAgent2 kernel: EIP: 0060:[] Tainted: P
Jan 15 19:39:00 BlueAgent2 kernel: EFLAGS: 00010202
Jan 15 19:39:00 BlueAgent2 kernel:
Jan 15 19:39:00 BlueAgent2 kernel: EIP is at ti_usb_serial_alloc_urbs [ti_usb] 0x282 (2.4.20-8)
Jan 15 19:39:00 BlueAgent2 kernel: eax: cb79c400 ebx: cdc00520 ecx: ce9f80e0 edx: 00008200
Jan 15 19:39:00 BlueAgent2 kernel: esi: cb79c41c edi: c1a19760 ebp: 00000040 esp: cb709d0c
Jan 15 19:39:00 BlueAgent2 kernel: ds: 0068 es: 0068 ss: 0068
Jan 15 19:39:00 BlueAgent2 /etc/hotplug/usb.agent: ... can't load module ti_usb
Jan 15 19:39:00 BlueAgent2 kernel: Process modprobe (pid: 2493, stackpage=cb709000)
Jan 15 19:39:01 BlueAgent2 kernel: Stack: c1a68198 000001f0 ffffffff 00000286 00000246 00000001 00000000 00000001
Jan 15 19:39:01 BlueAgent2 /etc/hotplug/usb.agent: missing kernel or user mode driver ti_usb
Jan 15 19:39:01 BlueAgent2 kernel: 00000001 04008200 00000000 ce9f8c60 cf467800 00000000 cb709d88 d00f114c
Jan 15 19:39:01 BlueAgent2 kernel: cb79c400 cf467800 d00ef9f8 cb79c400 cb709d74 cf467800 0000f111 cb709d88
Jan 15 19:39:01 BlueAgent2 kernel: Call Trace: [] .rodata.str1.1 [ti_usb] 0x538 (0xcb709d48))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_usb_serial_probe [ti_usb] 0x178 (0xcb709d54))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_1port_device [ti_usb] 0x0 (0xcb709d6c))
Jan 15 19:39:01 BlueAgent2 kernel: [] kmem_cache_free [kernel] 0x13 (0xcb709e0c))
Jan 15 19:39:01 BlueAgent2 kernel: [] __pte_chain_free [kernel] 0x17 (0xcb709e1c))
Jan 15 19:39:01 BlueAgent2 kernel: [] do_anonymous_page [kernel] 0x124 (0xcb709e28))
Jan 15 19:39:01 BlueAgent2 kernel: [] handle_mm_fault [kernel] 0x70 (0xcb709e40))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_usb_serial_driver [ti_usb] 0x20 (0xcb709e68))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_find_interface_driver [usbcore] 0x1d3 (0xcb709e78))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_usb_serial_driver [ti_usb] 0x20 (0xcb709e88))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_find_interface_driver [usbcore] 0x1d3 (0xcb709e98))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_usb_serial_driver [ti_usb] 0x0 (0xcb709eb0))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_driver_list [usbcore] 0x0 (0xcb709eb8))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_check_support [usbcore] 0x48 (0xcb709ecc))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_check_support [usbcore] 0x66 (0xcb709ee0))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_bus_list [usbcore] 0x0 (0xcb709ee8))
Jan 15 19:39:01 BlueAgent2 kernel: [] vendor_5052 [ti_usb] 0x0 (0xcb709eec))
Jan 15 19:39:01 BlueAgent2 kernel: [] usb_scan_devices_Rca4f6301 [usbcore] 0x2e (0xcb709ef0))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_usb_serial_register [ti_usb] 0x3a (0xcb709efc))
Jan 15 19:39:01 BlueAgent2 kernel: [] .rodata.str1.32 [ti_usb] 0x1080 (0xcb709f00))
Jan 15 19:39:01 BlueAgent2 kernel: [] .rodata.str1.1 [ti_usb] 0x0 (0xcb709f04))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_init [ti_usb] 0x93 (0xcb709f08))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_1port_device [ti_usb] 0x0 (0xcb709f0c))
Jan 15 19:39:01 BlueAgent2 kernel: [] sys_init_module [kernel] 0x4a2 (0xcb709f28))
Jan 15 19:39:01 BlueAgent2 kernel: [] .kmodtab [ti_usb] 0x0 (0xcb709f2c))
Jan 15 19:39:01 BlueAgent2 kernel: [] ti_init [ti_usb] 0x0 (0xcb709f58))
Jan 15 19:39:01 BlueAgent2 kernel: [] system_call [kernel] 0x33 (0xcb709fc0))
Jan 15 19:39:01 BlueAgent2 kernel:
Jan 15 19:39:01 BlueAgent2 kernel:
Jan 15 19:39:01 BlueAgent2 devlabel: devlabel service started/restarted
Jan 15 19:39:01 BlueAgent2 kernel: Code: 0f 44 54 24 24 8b 40 08 8b 40 50 81 ca 00 00 00 c0 89 41 54

------------------------------------

Thanks in advance.

Oscar G.

Oscar, I used to use the 2.4

Oscar, I used to use the 2.4 series kernels with Linux (back in the says of Debian Sarge). The Multitech-supplied driver works fine as-is. I think you have made some sort of mistake compiling the kernel. Unfortunately, I do not use 2.4.x, and cannot take the time to investigate this. My suggestion is that you use my precompiled kernel if possible, which will probably do what you need and is compatible with most flavors of Linux. Also, please read my post here: http://www.voluntary-simplicity.org/linux/multimodem-on-linux#comment-21

Good luck and sorry I can not be of more help. -- Lloyd

Pre-Compiled kernel

Can you point me where is you pre-compiled kernel please.

Actually I compiled the kernel by changing some parameters that was causing a version problem.
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 20
#EXTRAVERSION = -8custom
EXTRAVERSION = -8

Thank you for you response which is giving me a clue.

Oscar G.

The precompiled kernel is

The precompiled kernel is offered right in this article (above), to which these comments pertain.
--
Lloyd

Kernel 2.6.27 - ti_usb_3410_5052

Hello Lloyd,
I have a new FC9 with Kerel 2.6.27 which includes already the driver for Multitech modem (ti_usb_3410_5052).

If I load the driver manually by doing /sbin/modprobe ti_usb_3410_5052 it loads without any problem, but when I plug the usb multitech modem device it seems that is not using the driver.

1) /sbin/modprobe ti_usb_3410_5052

usbcore: registered new interface driver usbserial
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
usbserial: USB Serial support registered for TI USB 3410 1 port adapter
usbserial: USB Serial support registered for TI USB 5052 2 port adapter
usbcore: registered new interface driver ti_usb_3410_5052
ti_usb_3410_5052: TI USB 3410/5052 Serial Driver v0.9

2) When I plug the device I can see in the log this:

usb 2-1: new full speed USB device using uhci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: New USB device found, idVendor=06e0, idProduct=f111
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1: Product: TUSB3410 Serial Port
usb 2-1: Manufacturer: Texas Instruments

3) I have realized in the /dev appear two new devices:
crw-rw---- 1 root root 249, 6 2009-04-07 15:25 usbdev2.3_ep01
crw-rw---- 1 root root 249, 7 2009-04-07 15:25 usbdev2.3_ep00

After a few research I putted the file /etc/hotplug.d/usb/ti_usb_3410_5052.hotplug

But it seems that is not recognizing the device after it's plugged, also I created the files
/etc/udev/rules.d/026_ti_usb_3410.rules

Until now I'm totally lost and I don't know what should I do and make the device to work, I don't see errors but the device is not claming for the driver.

Any suggestion?

Thanks in advance.

Sorry for the delay in

Sorry for the delay in getting your comment published.

As I explained in my article, the ti_usb_3410_5052 driver that comes with Linux needs to be patched to work with the Multitech modems. If you are using the 2.6 kernel, you can use my patches, for kernel 2.6.20. Sometime after that (in a later 2.6 kernel) the ti_usb_3410_5052 source changed again, and my patches will not apply. I think that includes your 2.6.27 kernel.

So, you can either use my patched Debian kernel, or get non-Debian sources for 2.6.23 (the latest kernel that I know works with my patches), and apply my patches and recompile. My patched version does not require a hotplug script.

I do not have time to create new patches for recent kernel versions. Also, I cannot help you with any kernel compiling issues. If you cannot compile a kernel, you will have to use my patched supplied kernel.

(You will need non-Debian sources if you patch this yourself, since Debian removed the ti_usb_3410_5052 driver from the kernel source over licensing issues. I used a Ubuntu kernel.)

firmware not found

Thanks Lloyd,
I just created a new linux box with kernel version 2.6.20 and I applied your patch before kernel compilation. After kernel compilation and installation I loaded the module "modprobe ti_usb_3410_5052". After connecting the multitech usb device I got the following:

usb 1-2: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
ti_usb_3410_5052 1-2:1.0: TI USB 3410 1 port adapter converter detected
usb 1-2: ti_request_and_download_firmware - no firmware image found
ti_usb_3410_5052: probe of 1-2:1.0 failed with error -5
usb 1-2: device_add(1-2:1.0) --> -5

I just wondering if you have experienced this problem before ? or what could cause this issue?

Thanks.

Did you install the

Did you install the firmware?

Firmware

I just copied the firmware to /lib/firmaware and it starts working.

Thanks, you've been very helpful.

The MultiTech patch/firmware works great except on dis/reconnect

Hi Lloyd,

I did some minor porting to get the patches working with a 2.6.19 kernel, and they work quite nicely. Thanks!!! This is the first time we've used the TI USB-to-serial driver (I've used the Moschip and FTDI drivers before). While everything works great with the MultiTech USB EDGE, GPRS, and CMDA modems, once we start disconnecting and reconnecting them, syslog starts logging "interrupt response timeout" errors from the TI driver or sometimes errors with the tty close operation. In both cases, our USB ports on our system then become unuseable (for *any* device plugged in, be it keyboard, mouse, modem, etc.) until we reboot. Is this a known problem? If so, is it specific to the TI driver? In our other USB-to-serial uses, we currently don't allow users to disconnect those devices (i.e. they are built into the system), so this might be something with an issue on many (or all) USB-to-serial devices in general.

Thanks!

Pearce

I use a Multitech GPRS USB

I use a Multitech GPRS USB connection modem on a daily basis on Debian running a Ubuntu kernel (based on kernel 2.6.20.3), and there are definitely no issues with USB ports becoming unusable. If you had to do porting to get my patches to apply to the 2.6.19 kernel, I think your porting was not fully successful. My suggestion is that you upgrade to the 2.6.20.3 kernel, to which my modem driver patches will apply cleanly. In fact, my precompiled 2.6.20.3 kernel will probably work for you as-is (http://www.voluntary-simplicity.org/files/lloyd/linux-image-2.6.20.3-ubuntu1-mm5.deb)

If you would like to test your hardware with the Multitech EDGE/GPRS/CDMA USB drivers, note that Puppy 4.11 ("retro" kernel 2.7.21.7) has my patched drivers included. It is just a matter of "plug and play." There is also a GUI configuration utility I wrote. Puppy Linux is a very convenient way to get connected immedately.

I'm sorry I don't have time to look into why your patched 2.6.19 kernel is not working correctly with the USB modems. Good luck, and please post any solutions you might come up with here.

--
Lloyd

Are you disconnecting the

Are you disconnecting the modems at all while the system is running? To clarify further than my previous post, the failure case we're encountering is when we have a connection open to the modem (i.e. minicom) and we disconnect it from the system. If we do this a couple times, the modem (and any other USB devices we connect) will no longer enumerate until we reboot the system. I concede this could be an issue with the minor porting I did or with the 2.6.19 USB subsystem. We are not seeing any problems if we do not disconnect the modems or if we disconnect them but do not have a connection open to them prior to the disconnect.

Thanks for your efforts with these devices, Lloyd. You put together a nice package that is easy to use and is much appreciated!!! :)

USB disconnect issues

Hello Pearce,
Yes, of course we can disconnect the USB modems after they have been used, while the system is running, then reconnect, use other USB devices, etc.

I am quite sure that your connection issue is not a problem with the patched driver. My strong recommendation is that you use my supplied (compiled) kernel, if it has the capability you need. If not, I suggest you obtain the source code for the 2.6.20.3 kernel (or any other kernel source up to 2.6.21.7), and apply my patches. It will require no porting or other tweaking to make the USB Multitech modems work. You should not have to do any porting for the USB subsystem (are you using a non-standard USB subsystem?) These kernels are relatively recent, and will almost certainly have all the drivers you need available.

At some point after 2.6.21.7, the ti_usb_3410_5052 driver source changed, so that my patches will not longer apply. I may eventually create new patches. If anyone knows of any patches for these newer kernels, please let me know.

Note that Debian kernels cannot (easily) be used, since they do not contain the ti_usb_3410_5052 driver source. You should obtain an Ubuntu kernel, or else pristine kernel source from http://www.kernel.org.

To see how the USB modems ought to work, and to test your hardware, download Puppy 4.12 retro (ftp://ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.1.2retro-k2.6.21.7-seamonkey.iso). It is about a 100 meg download. Burn it to a CD, and you can run it live without any installation, partitioning, or bootloader. Installation of Puppy is a matter to saving a few files to any filesystem, even FAT or NTFS. This is the only Linux available that comes with built-in driver support for the Multitech USB connection GRPS/EDGE/CDMA modems, and even has a graphical setup program and easy connection program. Good luck!

Success using stock drivers

Lloyd,

I actually had no troubles using the supplied (unpatched) The 2.4 kernel driver on Slackware 10.2 (2.4.31 kernel and source stock Slackware 10.2 packages), and was up and running in a matter of minutes. No kernel recompile required, I just compiled the modem's driver and fired up minicom. I will have to see if this holds true for the latest 2.4 kernel. Hotplug scripts worked perfect as well under Slackware 10.2.

I believe the 2.6 driver would have worked the other night, as I figured out I needed to use 230K baud 8N1 instead of 115K baud after the 2.4 driver worked.

I still have to finalize the machine I'm going to use with this modem, so I'll give the Debian kernel a shot tonight, and may even have time to try out Puppy Linux.

It is really surprising to find so little information about these modems and their use with Linux on the internet! This modem really is a nice piece of hardware.

If you have anything you'd like me to try out, please let me know.

Hello Dan, I'm sorry, I did

Hello Dan,

I'm sorry, I did not realize you are using a 2.4 kernel. I assume then that you are using the Multitech-supplied driver source (ti_usb-1.1-1.src.rpm or
ti_usb-1.1.tgz.) It is provided as standalone driver code rather than as a patch.

All my information and code here are for later versions of the 2.6 kernel (I probably should make that more clear in th article.) The Multitech-supplied patch applied to the pristine driver source will work for some early 2.6 kernel versions, but not the the 2.6 kernels used with modern distros like Debian Etch and Ubuntu. The last Debian distro to work with the Multitech-supplied patch was Debian Sarge.

Glad you have had success! It would be very useful to me if you would try out your Edge modem with Puppy 4.00 and my driver package installed, to check that it works with Edge. Remember to get the version of Puppy that uses the 2.6.21.7 kernel. I compiled the driver for that kernel version.

Regards,
Lloyd

It worked!

Lloyd,

The precompiled kernel package worked very well on a fresh install of Debian 4.0r3 from a netinstall CD-ROM. I had to put the firmware files from the Multitech OEM CD-ROM in /lib/firmware, and reboot the machine after applying the patch.

Plugged the modem in after the reboot, and the devices was assigned to /dev/ttyUSB0. This worked through minicom using 230K baud and 8N1.

I've got more messing around to do, but this is looking very promising. Thanks for putting this package together!

moden gprs multitech

Hi! Dan
I wanna know if the precompiled kernel for GPRS multitech modem worked for you.
I have the same modem and I am trying to an app to send sms using it but I dont know how to put works this.
I wanna ask you how do you did?
If you want , I can contact to you privately my email is macaruchi@hotmail dot com

Tkhs in Advance

Thanks for checking this!

Thanks for checking this! This proves that the modified driver works with EDGE, as I expected.

The Puppy driver package is actually far easier to install and use. You just click the install icon, enter the phone PIN and so forth in a nice GUI setup program, then click on "MT-GPRS-Connect" from the Puppy menu and you go online. (If you have never tried Puppy Linux 4.00, you are in for a pleasant surprise.)

I was told by the Puppy developer, Barry Kauler, that he will include my modified version of the USB serial driver in the next release of Puppy Linux. In that case, my driver package would only need to supply the setup program, connection scripts, and possibly the firmware.

I'll have to give Puppy a

I'll have to give Puppy a try sometime. My main goal with this modem is to build an SMS gateway for an application that is undergoing development, so it's not really going to be used for internet access (at least, not at the moment).

Getting this modem to work with a modern version of Debian is a huge plus for this project.

Thanks again for the Debian kernel package!

EDGE version under Linux

Greetings!

I recently was charged with getting the EDGE version of this modem to work under Linux, and noticed how out of date the drivers on the CD were for Linux.

At the moment, I'm trying to get this working on a Slackware 10.2 system (2.6.13.3 vanilla kernel, working hotplug system). The modem is recognized, and I see the device binding to /dev/ttyUSB0, but I cannot seem to talk to the modem using minicom (115200 baud, 8N1).

I just found this site, and will look over the info you have posted to see if it will help me with my modem. Any other tips or tricks you might have to offer would be greatly appreciated.

It's a shame this modem doesn't have better Linux support. It appears to be a really nice piece of hardware!

Edge under Linux suggestions

Hello Dan,

Did you actually download my Debian kernel and try using that with Slackware, or are you using the unpatched driver? The Multitech-provided patches will not apply to the current driver source, and even if you hand-patch them, the driver will not work. The trouble has to do with resetting the configuration, apparently, but I really don't understand the problem, I just was lucky to find a fix that I adapted from a posting about a similar problem with a different driver. As far as I know, my patched version of the Multimodem driver is the only one available for modern versions of Linux.

I would really like to know if this works OK with EDGE. It is tested by me only for GPRS, but the driver is supposed to work for EDGE, and the firmware is included for EDGE.

To see if my driver will work for you , the easy way is to get Puppy Linux 4.00 and install my package for Puppy (called a "pet"), available on this site. This brand new "pet" uses a much smarter approach, providing a replacement driver rather than an entire kernel. Also, my Puppy pet driver package has an easy GUI setup program and includes PPP connection scripts. It "just works."

If that works with your EDGE modem and you cannot use my Multimodem-capable Debian kernel, then I suggest you use the patches I have provided in this article to compile a new driver for your Slackware kernel version. It should not be necessary to replace the whole kernel, just the ti_usb_3410_5052 driver.

By the way, Puppy Linux 4.00 is an extremely fast and full-featured Linux. It doesn't require a Linux partition to be installed. It essentially runs in memory, and saves the user's settings and files to a Linux filesystem that can be contained within a file stored on any filesystem type (including NTFS).

Lloyd