HUAWEI ETS1000 CDMA modem doesn't work anymore in 8.04

[Maris Nartiss]

I have HUAWEI ETS1000 CDMA modem [1] and it was working just fine on i386 7.10 after I followed instructions how to create custom udev rule [2]. After Ubuntu upgrade to 8.04 those instructions doesn't help anymore and no /dev/ttyUSB* device is created for modem.

Unfortunately this modem is far, far away and as it's only way to internet from there, thus I can't post various ls*/dmesg stuff, but I double checked, that idVendor and idProduct numbers reported by lsusb match those listed in [2] and - more important - they where working in previous Ubuntu release :(

1. http://www.huawei.com/mobileweb/en/products/view.do?id=320&pageId=null
2. http://blog.mohanjith.net/2007/06/installing-huawei-ets1000-on-linux.html

For record (if [2] goes down).
Udev rule:
#TI USB 3410
SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"

dmesg messages after plugging in USB device:
ti_usb_3410_5052 1-1:1.0: TI USB 3410 1 port adapter converter detected
ti_usb_3410_5052: probe of 1-1:1.0 failed with error -5

[Maris Nartiss (maris-nartiss)]

I made some tests with that usb to serial converter and modem.
First - I connected to my Gentoo laptop (udev-122, 2.6.25-gentoo-r1) and I got same error message in dmesg as in Ubuntu 8.04. I added new udev rule, replugged device and it started to work in Gentoo. Conclusion - issue is not only Ubuntu specific and it's fixable.
For reference - the new udev rule, that worked on my Gentoo box (2.6.15 kernel): SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="3410", RUN+="/bin/sh -c 'echo 2 > /sys%p/bConfigurationValue'"

As next step I used same udev rule on Ubuntu 8.04 but without any luck - for some reason it doesn't work in Ubuntu.
More info from Ubuntu 8.04 box (lsmod, udevinfo and udevtest in attachment):

dmesg:
[ 473.753611] usb 2-1: new full speed USB device using ohci_hcd and address 3
[ 473.987653] usb 2-1: configuration #1 chosen from 1 choice
[ 473.993599] ti_usb_3410_5052: probe of 2-1:1.0 failed with error -5

uname -a:
Linux zakis 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 GNU/Linux

# This part is strange, as on Gentoo I can freely change that /sys%p value with "echo 2 >"
root@zakis:~# echo 2 > /sys/bus/usb/devices/usb2/2-1/bConfigurationValue
-su: echo: write error: Invalid argument

# As You can see, previous command was not successfull and also udev rule has failed.
root@zakis:~# cat /sys/bus/usb/devices/usb2/2-1/bConfigurationValue
1

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[stomarti (stomarti)]

I got my device working with intrepid!

Output of lsusb:
Bus 003 Device 004: ID 0451:3410 Texas Instruments, Inc. TUSB3410 Microcontroller

My
/etc/udev/rules.d/026_ti_usb_3410.rules:

SUBSYSTEM=="usb_device" ACTION=="add"
SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"

Driver ti_usb_3410_5052 is requesting firmware ti_usb-3410.bin, which is not installed.

linux-image-2.6.27-7-generic installs the firmware here:
"/lib/firmware/2.6.27-7-generic/ti_3410.fw"

cp /lib/firmware/2.6.27-7-generic/ti_3410.fw /lib/firmware/ti_usb-3410.bin

did the trick.

Output of dmesg:

[ 889.808032] usb 3-1: new full speed USB device using uhci_hcd and address 2
[ 890.024191] usb 3-1: configuration #1 chosen from 1 choice
[ 890.258475] usbcore: registered new interface driver usbserial
[ 890.260476] usbserial: USB Serial support registered for generic
[ 890.262069] usbcore: registered new interface driver usbserial_generic
[ 890.262081] usbserial: USB Serial Driver core
[ 890.272343] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[ 890.274503] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
[ 890.276488] ti_usb_3410_5052 3-1:1.0: TI USB 3410 1 port adapter converter detected
[ 890.276504] firmware: requesting ti_usb-3410.bin
[ 890.896025] usb 3-1: reset full speed USB device using uhci_hcd and address 2
[ 891.039819] usb 3-1: device firmware changed
[ 891.041097] ti_usb_3410_5052: probe of 3-1:1.0 failed with error -5
[ 891.042680] usb 3-1: USB disconnect, address 2
[ 891.045277] usbcore: registered new interface driver ti_usb_3410_5052
[ 891.045291] ti_usb_3410_5052: TI USB 3410/5052 Serial Driver v0.9
[ 891.156035] usb 3-1: new full speed USB device using uhci_hcd and address 3
[ 891.377952] usb 3-1: configuration #1 chosen from 2 choices
[ 891.380841] ti_usb_3410_5052 3-1:1.0: TI USB 3410 1 port adapter converter detected
[ 891.381340] ti_usb_3410_5052: probe of 3-1:1.0 failed with error -5
[ 891.452966] ti_usb_3410_5052 3-1:2.0: TI USB 3410 1 port adapter converter detected
[ 891.460337] usb 3-1: TI USB 3410 1 port adapter converter now attached to ttyUSB0

[stomarti (stomarti)]

Here it was important to have a new line after "SUBSYSTEM=="usb_device" ACTION=="add"" in the udev rule.

/etc/udev/rules.d/026_ti_usb_3410.rules should look like:

SUBSYSTEM=="usb_device" ACTION=="add"
SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"

not like:

SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"

[Jordi Soucheiron Estruch (jordixou-gmail)]

This didn't work in my intrepid. If I try it manually as root I get:
$echo 2 > /sys/bus/usb/devices/usb1/1-2/bConfigurationValue
bash: /sys/bus/usb/devices/usb1/1-2/bConfigurationValue: Permission denied
$ ls -la /sys/bus/usb/devices/usb1/1-2/bConfigurationValue
-rw-r--r-- 1 root root 4096 2008-12-01 09:36 /sys/bus/usb/devices/usb1/1-2/bConfigurationValue

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[OGT (oguerra70)]

I have a Kernel 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.

[Jeremy Foshee (jeremyfoshee)]

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains in Jaunty, Please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-2.6.28-11-generic 236247

If you could also test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

-JFo

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]