Bug #384344 “[3G] NetworkManager does not detect ZTE AC8710 CDMA...” : Bugs : modemmanager package : Ubuntu

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-06-06:

#1

lsusb-vvv Edit (5.7 KiB, text/plain)

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-06-06:

#2

lshal Edit (149.8 KiB, text/plain)

Naveen N Rao (naveen-n-rao) on 2009-06-06

description:	updated
summary:	- [3G] NetworkManager does not detect ZTE 8710 CDMA/EVDO 3G Modem + [3G] NetworkManager does not detect ZTE AC8710 CDMA/EVDO 3G USB Modem

Revision history for this message

Tim Cole (timothy-j-cole) wrote on 2009-06-17:

#3

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/11

Replace /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules with that one. The one shipped with Jaunty does some check based on the driver that causes the probing to be skipped if you are using usbserial.

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-06-19:

#4

Tim,
I tried it and it didn't work - it seems to be specific to jaunty. I am still on intrepid, but using the latest network manager from the launchpad ppa.

FWIW, I've added information about the ZTE 3G card here: https://wiki.ubuntu.com/NetworkManager/Hardware/3G

I've been trying to figure out what's required to get a new 3G card working with NM and so far, I've come up with nothing. Isn't there a generic way we can get all usbserial-supported 3G cards to be recognized by NM?

- Naveen

Revision history for this message

Tim Cole (timothy-j-cole) wrote on 2009-06-21:

#5

Ive noticed that your device shows 4 ttys and i will assume that ttyUSB0 is the cdma modem since you say you can connect with wvdial on that tty.

These are the steps I followed to get my modem recognized by NetworkManager.

The clue here is the line that says:
"Jun 6 23:06:13 xxx NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:CDMA)"

In a working configuration I would expect it to say:
"Jun 6 23:06:13 xxx NetworkManager: <info> (ttyUSB0): found serial port (udev:CDMA hal:CDMA)" I'm guessing.

When you plug in your device, there are some udev rules that get run.
One of the rules that gets run, probes the modem to determine its capabilities. If this probe does not execute correctly, NM will not know that it can use your device.

The program that probes is /lib/udev/nm-modem-probe.

You can run this standalone to check that you modem is probed correctly.
try /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB0

You show get a bunch of output and ultimatleey two lines that read something like,
ID_NM_PROBED=1
ID_NM_CDMA=1 (just guessing here, mine is GSM).

Once you know the modem is being probed correctly, check that the rules are configured correctly.
In jaunty the live in
/lib/udev/rules.d/77-nm-probe-modem-capabilities.rules

for testing you could use something like

ACTION!="add|change", GOTO="nm_modem_probe_end"
SUBSYSTEM!="tty", GOTO="nm_modem_probe_end"
KERNEL!="tty*", GOTO="nm_modem_probe_end"

SUBSYSTEM=="tty", SUBSYSTEMS=="usb", DRIVERS=="?*", ENV{NM_MODEM_DRIVER}="$attr{driver}"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*", ENV{NM_MODEM_USB_INTERFACE_NUMBER}="$attr{bInterfaceNumber}"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="?*", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 3000 --export $tempnode", GOTO="nm_modem_probe_end"

LABEL="nm_modem_probe_end"

If this does not work, please attach the verbose output of nm-modem-probe.
Also attach the ouput of udevadm query all on the /sys/class/tty/ttyUSB0 path.

Ive noticed that your device shows 4 ttys and i will assume that ttyUSB0 is the cdma modem since you say you can connect with wvdial on that tty.

These are the steps I followed to get my modem recognized by NetworkManager.

The clue here is the line that says:
"Jun 6 23:06:13 xxx NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:CDMA)"

In a working configuration I would expect it to say:
"Jun 6 23:06:13 xxx NetworkManager: <info> (ttyUSB0): found serial port (udev:CDMA hal:CDMA)" I'm guessing.

When you plug in your device, there are some udev rules that get run.
One of the rules that gets run, probes the modem to determine its capabilities. If this probe does not execute correctly, NM will not know that it can use your device.

The program that probes is /lib/udev/nm-modem-probe.

You can run this standalone to check that you modem is probed correctly.
try /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB0

You show get a bunch of output and ultimatleey two lines that read something like,
ID_NM_PROBED=1
ID_NM_CDMA=1 (just guessing here, mine is GSM).

Once you know the modem is being probed correctly, check that the rules are configured correctly.
In jaunty the live in
/lib/udev/rules.d/77-nm-probe-modem-capabilities.rules

for testing you could use something like

ACTION!="add|change", GOTO="nm_modem_probe_end"
SUBSYSTEM!="tty", GOTO="nm_modem_probe_end"
KERNEL!="tty*", GOTO="nm_modem_probe_end"

SUBSYSTEM=="tty", SUBSYSTEMS=="usb", DRIVERS=="?*", ENV{NM_MODEM_DRIVER}="$attr{driver}"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*", ENV{NM_MODEM_USB_INTERFACE_NUMBER}="$attr{bInterfaceNumber}"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="?*", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 3000 --export $tempnode", GOTO="nm_modem_probe_end"

LABEL="nm_modem_probe_end"

If this does not work, please attach the verbose output of nm-modem-probe.
Also attach the ouput of udevadm query all on the /sys/class/tty/ttyUSB0 path.

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-06-22:

#6

Got it working!

Tim, the problem so far has been that nm-modem-probe is not under /lib/udev and I have been attributing that to the fact that I am on intrepid. I had ended up thinking that nm-modem-probe was something introduced in jaunty and I hadn't been able to find out how nm probed the modem in intrepid.

Before just responding to you, I thought I'll dig some more. And interestingly, I found nm-modem-probe under /etc/udev. I've now created a symlink to this from under /lib/udev. dpkg lists this file as being installed by network-manager:
$ dpkg -S nm-modem-probe
network-manager: /etc/udev/nm-modem-probe

So, the question is: who is responsible for creating the /lib/udev/nm-modem-probe symlink?

Of course, the simplified udev rules you pointed to earlier should work too.

As a reference, I am using Network Manager version 0.7.1-0ubuntu1~nm1~intrepid2 from the Network Manager ppa.

Thanks for all your help! We now need to see who should be responsible for /lib/udev/nm-modem-probe. Once that's done, and the udev rules updated, the only other part required to get a ZTE modem working would be the work needed to load usbserial module with the proper parameters.

- Naveen

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-07-09:

#7

After briefly failing to work with 0.7.1.git.3.7406e3a0e-0ubuntu1~nm1~intrepid1, Network Manager has started to work again with my card with 0.7.1.git.4.364ab2f86-0ubuntu1~nm1~intrepid1. I am enlisting the changes required on an intrepid machine to get a ZTE modem working so that the relevant changes can be made (how do I file this bug against hal-info?).

As a summary, these are the changes required for usbserial-supported ZTE 3G cards to function properly with network manager on intrepid:
1. [hal-info] Update /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi to add 19d2:ffff:

@@ -317,8 +317,9 @@

<match <email address hidden>:usb.vendor_id" int="0x19d2">
         
- <match <email address hidden>:usb.product_id" int_outof="0x0001;0xfffe">
+ <match <email address hidden>:usb.product_id" int_outof="0x0001;0xfffe;0xffff">
           <match <email address hidden>:usb.interface.number" int="0">
+ <append key="info.capabilities" type="strlist">modem</append>
             <append key="modem.command_sets" type="strlist">IS-707-A</append>
           </match>
         </match>

2. [udev] Update /etc/udev/rules.d/90-modprobe.rules to load usbserial on detecting ZTE modem:

@@ -66,4 +66,7 @@
# Load drivers that match kernel-supplied alias
ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe -Q $env{MODALIAS}"

+# Load usbserial for the 3G modem
+SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="ffff", RUN+="/sbin/modprobe usbserial vendor=0x19d2 product=0xffff"
+
LABEL="modprobe_end"

3. [network-manager] /lib/udev/nm-modem-probe (move or symlink to /etc/udev/nm-modem-probe)
4. [network-manager] Updated /etc/udev/rules.d/77-nm-probe-modem-capabilities.rules to support usbserial:

5. Finally, I see a new file being installed by Network Manager: /etc/udev/rules.d/77-nm-zte-port-types.rules. It didn't seem to have any effect on the working of my modem (even after adding rules for product ID ffff). So, what exactly does this do? And, should I be making any updates here?

- Naveen

After briefly failing to work with 0.7.1.git.3.7406e3a0e-0ubuntu1~nm1~intrepid1, Network Manager has started to work again with my card with 0.7.1.git.4.364ab2f86-0ubuntu1~nm1~intrepid1. I am enlisting the changes required on an intrepid machine to get a ZTE modem working so that the relevant changes can be made (how do I file this bug against hal-info?).

As a summary, these are the changes required for usbserial-supported ZTE 3G cards to function properly with network manager on intrepid:
1. [hal-info] Update /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi to add 19d2:ffff:

@@ -317,8 +317,9 @@
 
       <match key="@info.parent:usb.vendor_id" int="0x19d2">
         
-        <match key="@info.parent:usb.product_id" int_outof="0x0001;0xfffe">
+        <match key="@info.parent:usb.product_id" int_outof="0x0001;0xfffe;0xffff">
           <match key="@info.parent:usb.interface.number" int="0">
+            <append key="info.capabilities" type="strlist">modem</append>
             <append key="modem.command_sets" type="strlist">IS-707-A</append>
           </match>
         </match>

2. [udev] Update /etc/udev/rules.d/90-modprobe.rules to load usbserial on detecting ZTE modem:

@@ -66,4 +66,7 @@
 # Load drivers that match kernel-supplied alias
 ENV{MODALIAS}=="?*",			RUN+="/sbin/modprobe -Q $env{MODALIAS}"
 
+# Load usbserial for the 3G modem
+SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="ffff", RUN+="/sbin/modprobe usbserial vendor=0x19d2 product=0xffff"
+
 LABEL="modprobe_end"

3. [network-manager] /lib/udev/nm-modem-probe (move or symlink to /etc/udev/nm-modem-probe)
4. [network-manager] Updated /etc/udev/rules.d/77-nm-probe-modem-capabilities.rules to support usbserial:

5. Finally, I see a new file being installed by Network Manager: /etc/udev/rules.d/77-nm-zte-port-types.rules. It didn't seem to have any effect on the working of my modem (even after adding rules for product ID ffff). So, what exactly does this do? And, should I be making any updates here?

- Naveen

Changed in network-manager (Ubuntu):
status:	New → Confirmed

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-07-27:

#8

Nominated for Intrepid and Karmic so that ZTE devices can be used in a true plug-n-play fashion.

- Naveen

Naveen N Rao (naveen-n-rao) on 2009-08-28

affects:

network-manager (Ubuntu) → modemmanager (Ubuntu)

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-08-28:

#9

Tested out Karmic alpha 4. The issues remain the same:
- The modem (19d2:ffff) is not detected and the usbserial module is not loader.
- After loading the module, NetworkManager/ModemManager is unable to detect this as a 3G modem.
- With Intrepid, I could get my modem to work by tweaking how nm-modem-probe worked. With ModemManager, it looks like there is a plugin that needs to be updated.

So, again, how do I get Karmic to recognize my 3G modem out of the box?

- Naveen

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-09-30:

#10

Download full text (5.2 KiB)

With latest karmic, this is what I see with modem-manager and networkmanager in debug mode, and with usbserial modprobed with proper vendor and product IDs:

naveen@naveen-desktop:~$ sudo /usr/sbin/modem-manager --debug
** Message: Loaded plugin Option
** Message: Loaded plugin Huawei
** Message: Loaded plugin Generic
** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin MotoC
** Message: Loaded plugin Sierra
** Message: Loaded plugin Novatel
** Message: Loaded plugin Gobi
** Message: Loaded plugin ZTE
** Message: Loaded plugin Nokia
** Message: Loaded plugin Ericsson MBM
** Message: (ttyUSB2) opening serial device...
** (modem-manager:4969): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE'
** Message: (ttyUSB1) opening serial device...
** (modem-manager:4969): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE'
** Message: (ttyUSB0) opening serial device...
** (modem-manager:4969): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE'
** Message: (ttyUSB3) opening serial device...
** (modem-manager:4969): DEBUG: (ttyUSB3): probe requested by plugin 'ZTE'
** (modem-manager:4969): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CIS707-A, CIS-856, +MS, +ES, +DS, +FCLASS<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:4969): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** Message: (ttyUSB0) closing serial device...
** (modem-manager:4969): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** Message: (ZTE): CDMA modem /sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1 claimed port ttyUSB0
** (modem-manager:4969): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1
** (modem-manager:4969): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1 as /org/freedesktop/ModemManager/Modems/0
** (modem-manager:4969): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB2): --> 'ATI<CR>'
** Message: (ttyUSB2) closing serial device...
** (modem-manager:4969): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:4969): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** Message: (ttyUSB1) closing serial device...
** Message: (ttyUSB3) closing serial device...

The probing seems to last forever since modem-manager tries to probe ttyUSB[1-3] which don't respond. ttyUSB0 responds immediately as can be seen. It takes nearly 5 min for ttyUSB0 to be recognised as a CDMA modem and exported. NetworkManager still refuses to enlist this modem:

naveen@naveen-desktop:~$ sudo NetworkManager --no-daemon
NetworkManager: <info> starting...
NetworkManager: <info> modem-manager is now available
NetworkManager: SCPlugin-Ifupdown: init!
NetworkManager: SCPlugin-Ifupdown: update_system_hostname
NetworkManager: SCPluginIfupdown: management mode: unmanaged
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:05.0/net/eth0, iface: eth0)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/de...

Alexander,
Thanks for looking into this. I was on the latest level available in karmic - I upgraded to the latest level from the network-manager edge ppa you suggested:

naveen@naveen-desktop:~$ dpkg -l | grep network-manager
ii  network-manager                       0.8~a~git.20091009t060001.bc653d2-0ubuntu1~nmt2 network management framework daemon
ii  network-manager-gnome                 0.8~a~git.20091009t022925.b257961-0ubuntu2~nmt1 network management framework (GNOME frontend
naveen@naveen-desktop:~$ dpkg -l | grep modemmanager
ii  modemmanager                          0.2.git.20091012t184520.6f65ad7-0ubuntu2~nmt1   D-Bus service for managing modems

I still see the same issues - network manager trace is the same as seen previously. Here is the modem manager trace:

naveen@naveen-desktop:~$ sudo /usr/sbin/modem-manager --debug
** Message: Loaded plugin Option
** Message: Loaded plugin Huawei
** Message: Loaded plugin Generic
** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin MotoC
** Message: Loaded plugin Sierra
** Message: Loaded plugin Novatel
** Message: Loaded plugin Gobi
** Message: Loaded plugin ZTE
** Message: Loaded plugin Nokia
** Message: Loaded plugin Ericsson MBM
** Message: (ttyUSB2) opening serial device...
** (modem-manager:10204): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE'
** Message: (ttyUSB3) opening serial device...
** (modem-manager:10204): DEBUG: (ttyUSB3): probe requested by plugin 'ZTE'
** Message: (ttyUSB1) opening serial device...
** (modem-manager:10204): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE'
** Message: (ttyUSB0) opening serial device...
** (modem-manager:10204): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE'
** (modem-manager:10204): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
<LONG-PAUSE-1>
** (modem-manager:10204): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** (modem-manager:10204): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:10204): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
** (modem-manager:10204): DEBUG: (ttyUSB0): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CIS707-A, CIS-856, +MS, +ES, +DS, +FCLASS<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:10204): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
<LONG-PAUSE-2>
** Message: (ttyUSB0) closing serial device...
** (modem-manager:10204): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
<LONG-PAUSE-3>
** Message: (ZTE): CDMA modem /sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1 claimed port ttyUSB0
** (modem-manager:10204): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1
** (modem-manager:10204): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1 as /org/freedesktop/ModemManager/Modems/0
** (modem-manager:10204): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** (modem-manager:10204): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:10204): DEBUG: (ttyUSB2): --> 'ATI<CR>'
<LONG-PAUSE-4>
** Message: (ttyUSB2) closing serial device...
** (modem-manager:10204): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** (modem-manager:10204): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** Message: (ttyUSB3) closing serial device...
** Message: (ttyUSB1) closing serial device...

<LONG_PAUSE-X> identifies times when there was a long pause from modem-manager. Once modem manager exports the modem, network manager shows this message:

NetworkManager: Could not get device: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

This is with a stock install of network-manager - specifically, I didn't add anything in /lib/udev/rules.d/77-mm-zte-port-types.rules.

Let me know if you need anything else.

- Naveen

Revision history for this message

Alexander Sack (asac) wrote on 2009-10-15:

#13

i uploaded a new package batch now ... in a few hours you should get new bits on your mirros. please test those and let us know if they help your particular modem. thanks!

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-10-15:

#14

Thanks for the upload!
I tested it but no luck - I see the exact same behavior as before. The versions I now have:

naveen@naveen-desktop:~$ dpkg -l | grep -e network-manager -e modemmanager | tr -s ' ' | cut -d' ' -f2-3
modemmanager 0.2.git.20091014t233208.16f3e00-0ubuntu1
network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu2~nmt2
network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1

- Naveen

Revision history for this message

Piankhi (piankhi) wrote on 2009-10-26:

#15

I've managed to get NM to recognize my ZTE AC8710 (0xFFFF), by doing the following:

http://ubuntuforums.org/showthread.php?p=8170042#post8170042

Im using the NM package that is available in the repos as of 10/26/2009, 21:00 UTC, which is network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1 (i386)

But now i ran into this bug:

https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/334122

Perhaps someone else can pick it up from here?

Revision history for this message

Alexander Sack (asac) wrote on 2009-10-31:

#16

> I've managed to get NM to recognize my ZTE AC8710 (0xFFFF), by doing the following:
> http://ubuntuforums.org/showthread.php?p=8170042#post8170042

according to the forum post you forced the vid/pid to associated with the usbserial driver ...

"modprobe usbserial vendor=0x19d2 product=0xFFFF"

seems like usbserial just needs those IDs ... will add linux package.

> But now i ran into this bug:
> https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/334122

the bug you refer to is a generic bug without much direction. Could you please get good logs from modemmanager like described in https://wiki.ubuntu.com/DebuggingModemmanager ?

Thanks!

Revision history for this message

Alexander Sack (asac) wrote on 2009-10-31:

#17

Here for kernel folks what the forum post mentioned above suggests:

"Checked dmesg after that. "Option.ko" was loaded but it didn't recognize my modem. So i looked into the "option.c" source file and turns out it has AC8710 hard-coded with 0xFFF1 instead of 0xFFFF as the product id. I simply recompiled the "option.c" source file after editing 0xFFF1 to 0xFFFF, copied the compiled option.ko file to /lib/modules/2.6.31-14-generic/kernel/drivers/usb/serial, did a "depmod -a" and finally "modprobe option". Now my modem is recognized and working as soon as i plug it in."

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-11-02:

#18

Could only get to this today...

This method did not work for me. Interestingly, it looks like yours' is a GSM modem, while the one I have is a CDMA modem (which is strange considering the vendor id:product id match). As such, I suspect option module didn't work.

I suspect the problem is really with the way modem-manager is probing the modem ports - we just need a way to influence modem-manager's probing so that it only probes a certain serial device (ttyUSB0).

- Naveen

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2009-11-02:

#19

Oops.. spoke too soon. I am able to get this working, but there is a catch.

- In option.c, if I *replace*
#define ZTE_PRODUCT_AC8710 0xfff1
with
#define ZTE_PRODUCT_AC8710 0xffff
then, the modem is detected by NM/MM.

- if, however, I *add*
#define ZTE_PRODUCT_AC8710_1 0xffff
then, the modem won't be detected by NM/MM.

So, it seems there is some magic associated with the #define name

As an aside, in NM, if I select my service provider [India->Tata Indicom Photon+], the username and password fields are not filled in by default nor am I prompted to fill those. This results in CHAP failing. Would be nice to get those filled in by default (internet/internet).

So far, so good - thanks, Piankhi. Though this technique is much harder to follow for newer kernels unless accepted by ubuntu/upstream...

- Naveen

Revision history for this message

zeus (zeus-tunalkan) wrote on 2010-01-08:

#20

Hi there. I'm newby here, so sorry if I'm writing in the wrong place. However, this is the most similar thread to what I need that I've been able to find in the net.

I have a Novatel Merlin UX870 pc card (idxvendor=1410x1430) that I use as a modem. My OS is Xubuntu 9.04. My network-manager version is 0.7.1. My present linux kernel is version 2.6.28-17.

So far, everything worked ok. When I plugged in my card, it got detected by the system, properly loaded the modules (usbserial and option) and created the device nodes /dev/ttyUSB0 and /dev/ttyUSB1 (first one is the good one, the other I don't know its use), properly detected by NM, properly been able to create new mobile broadband connections with the applett netrowk-manager-gnome and, in general, all was happiness and joy.

But suddenly, since some days ago, after I-don't-know-what-I-may-have-possibly-done, NM doesn't like my modem any more. The system still sees it, and I can, for example, manually configure and "pon myconnection", and get online without problems. But NM refuses to accept the card.
The only relevant thing I remember having done recently is replacing the 2.6.28-15 kernel with the 2.6.28-17, but I'm not sure if that's the problem, as I think that dates of replacement/issue don't match. Besides, I've tried with another one kernel (2.6.24-23) and problem remains. So, probably that has nothing to do. I've a badly broken memory (in my head, I mean, not in the computer), but I don't remember having installed or uninstalled anything relevant. So, I'm at a loss.

Any clue? I'd very much appreciate some guideline or hint.

Useful information for somebody out there who will like to help me:

When plugged the card, or when restarted, NetworkManager logs that
(ttyUSB0): found serial port (udev: hal:GSM)
(ttyUSB0): ignoring due to lack of probed mobile broadband capabilities
(ttyUSB1): ignoring due to lack of mobile broadband capabilities

End of "nm-modem-probe /dev/ttyUSB0" command says that
modem_probe_caps(): GCAP response: +GCAP: +CGSM, +DS
ID_NM_MODEM_GSM=1
ID_NM_MODDM_PROBED=1
main(): /dev/ttyUSB0: caps (0x9) GSM

I've been modifying the /lib/udev/rules.d/77-nm-probemodem-capabilities.rules as suggested above in this post, tried all possible combinations, but NM insists in denying broadband capabilities to my card. Seems like if it wasn't running nm-modem-probe, or something...

Hi there. I'm newby here, so sorry if I'm writing in the wrong place. However, this is the most similar thread to what I need that I've been able to find in the net.

I have a Novatel Merlin UX870 pc card (idxvendor=1410x1430) that I use as a modem. My OS is Xubuntu 9.04. My network-manager version is 0.7.1. My present linux kernel is version 2.6.28-17.

So far, everything worked ok. When I plugged in my card, it got detected by the system, properly loaded the modules (usbserial and option) and created the device nodes /dev/ttyUSB0 and /dev/ttyUSB1 (first one is the good one, the other I don't know its use), properly detected by NM, properly been able to create new mobile broadband connections with the applett netrowk-manager-gnome and, in general, all was happiness and joy.

But suddenly, since some days ago, after I-don't-know-what-I-may-have-possibly-done, NM doesn't like my modem any more. The system still sees it, and I can, for example, manually configure and "pon myconnection", and get online without problems. But NM refuses to accept the card.
The only relevant thing I remember having done recently is replacing the 2.6.28-15 kernel with the 2.6.28-17, but I'm not sure if that's the problem, as I think that dates of replacement/issue don't match. Besides, I've tried with another one kernel (2.6.24-23) and problem remains. So, probably that has nothing to do. I've a badly broken memory (in my head, I mean, not in the computer), but I don't remember having installed or uninstalled anything relevant. So, I'm at a loss.

Any clue? I'd very much appreciate some guideline or hint.

Useful information for somebody out there who will like to help me:

When plugged the card, or when restarted, NetworkManager logs that
(ttyUSB0): found serial port (udev: hal:GSM)
(ttyUSB0): ignoring due to lack of probed mobile broadband capabilities
(ttyUSB1): ignoring due to lack of mobile broadband capabilities

End of "nm-modem-probe /dev/ttyUSB0" command says that
modem_probe_caps(): GCAP response: +GCAP: +CGSM, +DS
ID_NM_MODEM_GSM=1
ID_NM_MODDM_PROBED=1
main(): /dev/ttyUSB0: caps (0x9) GSM

I've been modifying the /lib/udev/rules.d/77-nm-probemodem-capabilities.rules as suggested above in this post, tried all possible combinations, but NM insists in denying broadband capabilities to my card. Seems like if it wasn't running nm-modem-probe, or something...

Revision history for this message

zeus (zeus-tunalkan) wrote on 2010-01-09:

#21

Another couple of things.

One is about what your comment, Naveen, on two cards having same id and vendor but being reported as having different capabilities, GSM and CDMA. Well, my card is a CDMA one, I'm positive about that, however NM reports it as GSM. I can only make a guess, fruit of my ignorance: maybe the NM report is related to the couple device+SIM? Thus, if we have a CDMA capable device but our ISP is only providing us GSM, might it be possible that NM reported GSM? Sorry if I'm talking nonsense, but the fact is that NM reports my card as GSM (while it's CDMA), and that presently I'm only getting GPRS connection from my ISP (I believe I might have exceeded the download limit above which they cut down the 3G speed to 2G). That might explain your case, Naveen, and I hope it explains mine! Because the other explanation I can think of is that, somehow, I've managed to damage my card (in one of those hotplugging-computer freezing-hotunplugging cycles). But would it still work?

The other thing is more related with the bug itself: after upgrading network-manager to version 0.7.2, now I don't get the
ID_NM_MODEM_GSM=1
but only the
ID_NM_MODEM_PROBED=1
when "nm-modem-probing" it

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-01-12:

#22

Well, I doubt if the GSM/CDMA aspect is relevant. What's more important is that your device seems to be supported out of the box, assuming it is being detected without any configuration changes. If so, the issue is just with how NM is probing the modem. You could try reverting to older NM levels to see if your modem starts working - newer NM could have broken compatibility with your modem.

You might also want to refer to:
https://wiki.ubuntu.com/NetworkManager/Hardware/3G/Probing
https://wiki.kubuntu.org/DebuggingNetworkManager

If nothing helps, you should file a new bug.

- Naveen

Revision history for this message

zeus (zeus-tunalkan) wrote on 2010-01-13:

#23

Thanks Naveen.

I've tried to revert to former NM versions, but it didn't work. Bug is still there. I took a look in the links you post, which are useful to find information about the modem in order to file a bug. That's actually what I'm going to do.

pablo

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-03-14:

#24

Hi Naveen,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, 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 384344

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the 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.

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

tags:	added: needs-kernel-logs
tags:	added: needs-upstream-testing
tags:	added: kj-triage
Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20:

#25

Hi Jeremy,
Tested with the brand new Lucid beta 1:
- The modem is still not recognized out of the box. I need to modprobe usbserial manually.
- NetworkManager/ModemManager looks to have been fixed as it is able to probe and detect the modem quickly (yay!)
- NM Modem configuration wizard still does not populate the username/password fields automatically (these are fixed entries, so should be included with the connection information (Tata Indicom Photon+): internet/internet).

I'll attach the required logs and test with the mainline kernel.

- Naveen

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: AlsaDevices.txt

#26

AlsaDevices.txt Edit (521 bytes, text/plain)

apport information

tags:	added: apport-collected
description:	updated

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: AplayDevices.txt

#27

AplayDevices.txt Edit (281 bytes, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: BootDmesg.txt

#28

BootDmesg.txt Edit (56.2 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: Card0.Amixer.values.txt

#29

Card0.Amixer.values.txt Edit (1.5 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: Card0.Codecs.codec.0.txt

#30

Card0.Codecs.codec.0.txt Edit (6.2 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: CurrentDmesg.txt

#31

CurrentDmesg.txt Edit (1.4 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: IwConfig.txt

#32

IwConfig.txt Edit (350 bytes, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: Lspci.txt

#33

Lspci.txt Edit (15.7 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: Lsusb.txt

#34

Lsusb.txt Edit (758 bytes, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: PciMultimedia.txt

#35

PciMultimedia.txt Edit (588 bytes, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: ProcCpuinfo.txt

#36

ProcCpuinfo.txt Edit (1.6 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: ProcInterrupts.txt

#37

ProcInterrupts.txt Edit (1.9 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: ProcModules.txt

#38

ProcModules.txt Edit (3.1 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: RfKill.txt

#39

RfKill.txt Edit (182 bytes, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: UdevDb.txt

#40

UdevDb.txt Edit (139.0 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: UdevLog.txt

#41

UdevLog.txt Edit (292.6 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20: WifiSyslog.txt

#42

WifiSyslog.txt Edit (400.8 KiB, text/plain)

apport information

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-03-20:

#43

Issue confirmed with upstream 2.6.33-020633-generic kernel - the behavior is similar to lucid with stock kernel.
Lucid didn't boot with the latest 2.6.34 kernel.

- Naveen

tags:

removed: needs-kernel-logs needs-upstream-testing

Naveen N Rao (naveen-n-rao) on 2010-03-22

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

madbiologist (me-again) wrote on 2010-05-10:

#44

A patch to add out-of-the-box support for this modem has been included upstream in kernel 2.6.34-rc7. From the changelog:

commit fe30bc1b16dcfbbadf3f77bbad1c9014b23704cd
Author: Mahesh Kuruganti
Date: Mon Apr 12 22:37:02 2010 +0530

USB: serial: option: ZTEAC8710 Support with Device ID 0xffff

PATCH TO EXTEND SUPPORT TO AC8710 WITH 0xFFFF Product ID.

Signed-off-by: Mahesh Kuruganti
Signed-off-by: Greg Kroah-Hartman

A PPA of this kernel is available at http://kernel.ubuntu.com/~kernel-ppa/mainline/

Changed in linux (Ubuntu):
status:	Confirmed → Fix Committed

Revision history for this message

Naveen N Rao (naveen-n-rao) wrote on 2010-05-11:

#45

That's a thumbs up - any chance this can be back-ported to Lucid?

- Naveen

Jeremy Foshee (jeremyfoshee) on 2011-01-10

Changed in linux (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

m0rtal (alexander-nagorny) wrote on 2011-10-20:

#46

I don't know what's going on, but same modem doesn't work on Ubuntu 11.10:

uname -a
Linux 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686 i686 i386 GNU/Linux

but it was working on 10.10!

Revision history for this message

asux (ckasux) wrote on 2012-03-09:

#47

chec packages .hwinfo

Affects		Status	Importance	Assigned to
	linux (Ubuntu)	Fix Released	Undecided	Unassigned
Nominated for Intrepid by Naveen N Rao
Nominated for Karmic by Naveen N Rao
	modemmanager (Ubuntu)	Confirmed	Undecided	Unassigned
Nominated for Intrepid by Naveen N Rao
Nominated for Karmic by Naveen N Rao

Ubuntu
modemmanager package

[3G] NetworkManager does not detect ZTE AC8710 CDMA/EVDO 3G USB Modem

Bug Description

Other bug subscribers

Related questions

Bug attachments

Remote bug watches

Ubuntumodemmanager package

[3G] NetworkManager does not detect ZTE AC8710 CDMA/EVDO 3G USB Modem

Bug Description

Other bug subscribers

Related questions

Bug attachments

Remote bug watches

Ubuntu
modemmanager package