ANN: ModemManager 0.6.2 released

2013-05-31 Thread Dan Williams
Hi, I'm happy to announce the latest stable release of ModemManager, version 0.6.2. This release brings a number of bug fixes and new hardware support, and is likely the last regular release in the 0.6.x line. We'll now be concentrating on releasing the much more capable and robust ModemManager 0

Re: MM 0.6.0 conflicts with USB GPS device?

2013-05-31 Thread Dan Williams
On Sat, 2013-06-01 at 00:05 +0200, W. Martin Borgert wrote: > On 2013-05-31 16:44, Dan Williams wrote: > > Perhaps MM is crashing and then respawning, then restarting the probing > > process? > > I don't think so, because I started MM manually with --debug and > --log-level=DEBUG. In this case the

Re: MM 0.6.0 conflicts with USB GPS device?

2013-05-31 Thread W. Martin Borgert
On 2013-05-31 16:44, Dan Williams wrote: > Perhaps MM is crashing and then respawning, then restarting the probing > process? I don't think so, because I started MM manually with --debug and --log-level=DEBUG. In this case there would be no automatic restart after a crash, right? > There was a bu

Re: MM 0.6.0 conflicts with USB GPS device?

2013-05-31 Thread Dan Williams
On Fri, 2013-05-31 at 21:56 +0200, W. Martin Borgert wrote: > On 2013-05-31 13:53, Dan Williams wrote: > > When you say "again and again", what do you mean? ModemManager sends a > > sequence of AT commands like AT+GCAP, ATI, etc, then moves on to binary > > QCDM commands, and if all of these fail,

Re: How can I make WWAN auto enable at startup?

2013-05-31 Thread Dan Williams
On Wed, 2013-05-29 at 18:46 +0200, Marius Kotsbak wrote: > See https://bugzilla.gnome.org/show_bug.cgi?id=667488 Updated that bug; I pushed a dcbw/wwan-fixes branch that gets us 50% of the way there, what we need now is smarter detection of when we can and cannot autoconnect based on the modem's s

Re: MM 0.6.0 conflicts with USB GPS device?

2013-05-31 Thread W. Martin Borgert
On 2013-05-31 13:53, Dan Williams wrote: > When you say "again and again", what do you mean? ModemManager sends a > sequence of AT commands like AT+GCAP, ATI, etc, then moves on to binary > QCDM commands, and if all of these fail, it will stop and leave the > device alone. That can take 10 or so

Re: Possible bug in network-manager-0.9.8

2013-05-31 Thread Dan Williams
On Fri, 2013-05-31 at 12:23 +0200, John Greene wrote: > Im running Debian jessie(testing), and after some recent updates with > network-manager to 0.9.8, i can no longer maintain a connection to my > wireless network. I have no problems on 0.9.4, (so i reverted back for > now), also, the access poi

Re: Allowed and preferred modes setting in NM modem connections

2013-05-31 Thread Dan Williams
On Fri, 2013-05-31 at 13:56 +0200, Aleksander Morgado wrote: > Hey, > > NetworkManager currently allows to pass allowed/preferred modes (e.g. 2G > & 3G but 3G preferred) when requesting a connection to ModemManager. I'd > like to suggest to have these settings removed from the connection > profile

Re: MM 0.6.0 conflicts with USB GPS device?

2013-05-31 Thread Dan Williams
On Fri, 2013-05-31 at 17:57 +0200, W. Martin Borgert wrote: > Hi, > > ModemManager 0.6.0 (02ddf9a6732fba19c248d83cadfb56452c815091) seems to > be confused, when a USB GPS device is connected. > The GPS device always sends permanently data in form of ASCII strings at > 4800 bps. > It does not ans

MM 0.6.0 conflicts with USB GPS device?

2013-05-31 Thread W. Martin Borgert
Hi, ModemManager 0.6.0 (02ddf9a6732fba19c248d83cadfb56452c815091) seems to be confused, when a USB GPS device is connected. The GPS device always sends permanently data in form of ASCII strings at 4800 bps. It does not answer to any commands, such as ATI. Unfortunately it idenfies itself as a

Allowed and preferred modes setting in NM modem connections

2013-05-31 Thread Aleksander Morgado
Hey, NetworkManager currently allows to pass allowed/preferred modes (e.g. 2G & 3G but 3G preferred) when requesting a connection to ModemManager. I'd like to suggest to have these settings removed from the connection profile (and therefore not passed to Simple.Connect()), and let system preferenc

Possible bug in network-manager-0.9.8

2013-05-31 Thread John Greene
Im running Debian jessie(testing), and after some recent updates with network-manager to 0.9.8, i can no longer maintain a connection to my wireless network. I have no problems on 0.9.4, (so i reverted back for now), also, the access point is PEAP/MSCHAPv2, which might be important. Im wondering w

Re: [MM] API changes for 0.8

2013-05-31 Thread Aleksander Morgado
On 31/05/13 00:18, Dan Williams wrote: >>> * Renamed 'Bands' property to 'CurrentBands'. >>> > > >>> > > * Renamed 'SetBands()' method to 'SetCurrentBands()'. >>> > > >>> > > * Updated the 'SupportedModes' property to give a list of >>> > > allowed+preferred combinations, instead of just a mas

Re: QMI and LTE: IP connection problems

2013-05-31 Thread Martin Anderseck
Bjørn Mork wrote: > So it > - works with DirectIP > - works with QMI and UMTS > - fails with QMI and LTE, except for DHCP > ? Nice short summary :-) > This pattern matches the firmware bug worked around by this commit: > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/dri