Re: ZTE modem problems and workrounds

[Rick Jones <rick activeservice co uk>]

Good and bad news ...

The fix was already picked up on launchpad, so I installed the new build. It always picks up the correct port - good - but something's broken when trying to make a connection.

This is the log:

Jul  3 16:07:42 mineee NetworkManager: <info>  Connected, Woo! 
Jul  3 16:07:42 mineee NetworkManager: <info>  Activation (ttyUSB2) Stage 2 of 5 (Device Configure) scheduled... 
Jul  3 16:07:42 mineee NetworkManager: <info>  Activation (ttyUSB2) Stage 2 of 5 (Device Configure) starting... 
Jul  3 16:07:42 mineee NetworkManager: <info>  (ttyUSB2): device state change: 4 -> 5 (reason 0) 
Jul  3 16:07:42 mineee NetworkManager: <info>  Starting pppd connection 
Jul  3 16:07:42 mineee NetworkManager: <debug> [1246633662.486882] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug ttyUSB2 noipdefault noauth nobsdcomp nodeflate usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so 
Jul  3 16:07:42 mineee NetworkManager: <debug> [1246633662.490995] nm_ppp_manager_start(): ppp started with pid 4508 
Jul  3 16:07:42 mineee NetworkManager: <info>  Activation (ttyUSB2) Stage 2 of 5 (Device Configure) complete. 
Jul  3 16:07:42 mineee NetworkManager: <info>  (ttyUSB2): device state change: 5 -> 6 (reason 0) 
Jul  3 16:07:42 mineee NetworkManager: <debug> [1246633662.601008] nm_serial_device_close(): Closing device 'ttyUSB2' 
Jul  3 16:07:45 mineee NetworkManager: <debug> [1246633665.000541] ensure_killed(): waiting for ppp pid 4508 to exit 
Jul  3 16:07:45 mineee NetworkManager: <debug> [1246633665.000791] ensure_killed(): ppp pid 4508 cleaned up 

Note that it closes ttyUSB2 after changing to state 6. This hasn't happened before, and it definitely is closed because I can open it with another app. The tray-icon continues to swirl with one green dot, and shows no sign of timing out. I have to click Disconnect on the menu. The log after discconnect is:

Jul  3 16:10:38 mineee NetworkManager: <info>  (ttyUSB2): device state change: 6 -> 3 (reason 39) 
Jul  3 16:10:38 mineee NetworkManager: <info>  (ttyUSB2): deactivating device (reason: 39). 
Jul  3 16:10:38 mineee NetworkManager: <info>  Policy set 'Auto Jones' (ra0) as default for routing and DNS. 
Jul  3 16:10:38 mineee NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Jul  3 16:10:38 mineee NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed

I don't know if this is a side-effect, or the result of some other change. I'm going to revert to the previous NM version for now.

Rick

--On Friday, July 03, 2009 12:21:58 +0100 Rick Jones <rick activeservice co uk> wrote:

> Thanks - I sympathise re. ZTE.
> 
> Is this likely to come through as an update to 0.7.1, or will we have to wait until NM .8 with MM?
> 

> > 
> > FWIW I've attempted to handle this issue in the following commits to
> > 
> > NM:
> > 7406e3a0e8147e23ad3c5b775b3ce940c93ada2a
> > 
> > and ModemManager:
> > 52da9990eef279bbc349685a7558d26cf4b7893b
> > 869c69e223208564302ba3be074dafbdf1b02cc2
> > 
> > and ZTE is now on my hate-list.  Option did this nicely by implementing
> > a firmware call that returns the port type, which is really the right
> > thing to do.  But it boggles my mind that *every ZTE device is
> > different* according to the .INF files.  What a maintenance nightmare.
> > 
> > Dan
> > 
> > 
> > 
> 
> 
>