Comment 6 for bug 384344

Revision history for this message
Naveen N Rao (naveen-n-rao) wrote :

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?

I also needed to modify the default udev rules. The rules on my TP had a line that looked only for certain drivers - I added usbserial_generic to the list:
DRIVERS=="option|sierra|hso|cdc_acm|qcserial|usbserial_generic", GOTO="probe"

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