Some recent commit broke compilation of the samsung plugin in
ModemManager, patch attached.
Cheers,
--
Aleksander
From dc814cd3204f04a85d9f6de93acadb71debbd83d Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Fri, 25 Mar 2011 17:24:48 +0100
Subject: [PATCH] samsung
.
Cheers,
--
Aleksander
From 34958190e198065beaaabcc3ac9cf9b9cdc50d35 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Mon, 28 Mar 2011 11:24:39 +0200
Subject: [PATCH 1/4] build: fix automake portability warnings
Makefile.am uses several GNU gcc extensions. -Wno
7.45 of Sierra Wireless, the AT+CPIN? query reply will never
have an OK (quoting here):
Read command
AT+CPIN?
+CPIN: code
Note: No OK
--
Aleksander
From 220c331a23c29e262d807435b1120e96f17c7eea Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
(
MM_AT_SERIAL_PORT (port),
mm_serial_parser_v1_parse,
parser,
mm_serial_parser_v1_destroy);
}
Comments?
Cheers!
--
Aleksander
From e0a4d4c2db931882b094d0af2ceefb65d60590fd Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Wed, 30 Mar
flow control */
g_value_set_string (value, +IFC=2,2);
break;
...
}
Cheers,
--
Aleksander
From 0091d624bbe0edc5056e7b523df148acf233a6e6 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Thu, 31 Mar 2011 10:39:43 +0200
Subject: [PATCH] generic-gsm
Hi Dan,
i have a detected Modem and tried to send the SIM-PIN with the dbus
method (with d-feet)
org.freedesktop.ModemManager.Modem.Gsm.Card.SendPin() and get a dbus
error back:
'org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include:
: Aleksander Morgado aleksan...@lanedo.com
Date: Wed, 6 Apr 2011 17:08:06 +0200
Subject: [PATCH] modem-base: allow NULL ports in get_card_info() if port_error given
So that cached values can be returned if querying while the port is connected.
---
src/mm-modem-base.c |6 +++---
1 files changed, 3
Hi all,
Finished implementing the basic ModemManager support for the Sierra
Wireless Airlink Fastrack Xtend GSM/UMTS modems [1]. The plugin was
developed using a Fastrack Xtend FXT009 (GPRS/EDGE) modem, but
implemented to support also 3G-based models (although completely
untested that part).
), and the ModemManager process
nicely exit()s (or abort()s, depending on who packages d-bus).
--
Aleksander
From af98190831564949d584b07051d5b6c53e6de7a2 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Tue, 12 Apr 2011 16:32:11 +0200
Subject: [PATCH] serial: ensure
Where on earth happens the modem initialization in NetWorkmanager?
My interest is for GSM/3G modems as well as for POTS/ISDN modems.
I've tried to browse the source code but it's quite difficult.
What I've found so far is that the initialization is done in the modemmanager.
It looks
Where on earth happens the modem initialization in NetWorkmanager?
My interest is for GSM/3G modems as well as for POTS/ISDN modems.
I've tried to browse the source code but it's quite difficult.
What I've found so far is that the initialization is done in the
modemmanager.
Hi Ran,
I would like to ask how NetworkManager/ModemManager deals with modems
which use the same port for ppp connection and for AT command.
As far as I understand we cannot retrieve any information using AT
command while there is a ppp connection on that port.
Therefore information such
Hi all,
The SetBand() operation in the Modem.GSM.Network interface restricts to
1 the bands that can be passed. This means that I cannot SetBand()
passing both EGSM and DCS flags, even if the modem supports it.
Why is this limitation imposed in ModemManager?
Cheers,
--
Aleksander
Hi all,
The SetBand() operation in the Modem.GSM.Network interface restricts to
1 the bands that can be passed. This means that I cannot SetBand()
passing both EGSM and DCS flags, even if the modem supports it.
Why is this limitation imposed in ModemManager?
As discussed on IRC,
Hi all,
(sorry for the long email)
ModemManager plugins need several steps to know whether they can handle
a given connected modem. The flow is usually something like this:
(1) Check vendor ID (and sometimes also product ID), with one of
the following methods:
Hi all,
Each MMCallbackInfo holds a weak reference to the MMModem to which the
AT command was sent. When the MMModem is destroyed,
mm-callback-info.c::modem_destroyed_cb() gets called and the modem
pointer in the callback info is reset to NULL, to avoid having a pointer
to an already disposed
Each MMCallbackInfo holds a weak reference to the MMModem to which the
AT command was sent. When the MMModem is destroyed,
mm-callback-info.c::modem_destroyed_cb() gets called and the modem
pointer in the callback info is reset to NULL, to avoid having a pointer
to an already
From a cursory reading of the bug reports you cited it seems like some
sierra modems crash when ModemManager sends CFUN=1 to them.
Can you help verify if this is indeed the case with yours as well?
So it really seems that not only Wavecom modems get a whole software
restart
patch and fix the problem correctly, it would be
great :)
Attached a patch which should do AT+CFUN=1 only if product ID is not
0x6832. Can you guys test it?
Cheers!
--
Aleksander
From a91835798a7d7a5fffddb905e71b45178ef05ebf Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan
is not
0x6832. Can you guys test it?
Minor fix in the previous patch, please use the one here instead.
Cheers,
--
Aleksander
From d76e86d336f090a45a66159944e4993c1269 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Fri, 20 May 2011 11:46:32 +0200
Subject: [PATCH
On Fri, 2011-05-20 at 14:59 +0200, Harald Jung wrote:
May 20 14:41:21 ThinClient modem-manager[3764]: debug
[mm-at-serial-port.c:298] debug_log(): (ttyHS0): -- 'AT
+CPMS=ME,ME,MECR'
It seems the first command not replied properly is the above CPMS
setting, which is the SMS-storage related
Attached a patch which should do AT+CFUN=1 only if product ID is not
0x6832. Can you guys test it?
Minor fix in the previous patch, please use the one here instead.
I updated the package in my ppa with your patch.
Gerd, can you test the new one?
I did so.
Hi Harald,
May 20 14:41:21 ThinClient modem-manager[3764]: debug
[mm-at-serial-port.c:298] debug_log(): (ttyHS0): -- 'AT
+CPMS=ME,ME,MECR'
I have removed the CPMS setting from the source code, I don't need any
sms support and the AT command caused the modem device to hang.
1) Does the device boot up in CFUN=1 mode already? This could be
determined via minicom/screen without MM running. If it does (my 8775
modules do) then we could avoid this issue by having the startup code
check AT+CFUN? before doing AT+CFUN=1 explicitly.
I will try to implement this,
1) Regarding frequency/band management:
* There is now AllowedBands and SupportedBands properties in the API,
but no GetBand() or SetBand(). So really seems the only way to set
specific bands is through writing the AllowedBands property. I don't
think its a good idea, as we really want
Hi all,
My understanding is that the whole support for caching capabilities
after port probing is done so that if a plugin requests a probe, the
remaining plugins to check for support don't need to relaunch a new port
probe. If this is not the case, please stop reading now :-)
Port probing and
Most (all?) implementations of grab_port() in the plugins rely on the
fact that the port probing task they get as input argument is exactly
the one which did the port probing: there are calls to
mm_plugin_base_supports_task_get_probed_capabilities() usually in
grab_port() in order to know
Finished developing a new 'cinterion' plugin for Cinterion/Siemens-based
modems (see [1]).
This development is ready for review in the 'plugin-cinterion' branch in
the following Gitorious repository [2]:
git://gitorious.org/lanedo/modemmanager.git
The branch is based on
All the stuff in the protect-callbacks branch looks good, please push.
I couldn't trigger crashes on a number of devices just pulling them out
in the middle of a tight loop hammering the modem for info. Good work.
This has been pushed to both git master and MM_05.
Cheers,
--
Aleksander
Finished developing a new 'cinterion' plugin for Cinterion/Siemens-based
modems (see [1]).
This development is ready for review in the 'plugin-cinterion' branch in
the following Gitorious repository [2]:
git://gitorious.org/lanedo/modemmanager.git
The branch is based on the
Most (all?) implementations of grab_port() in the plugins rely on the
fact that the port probing task they get as input argument is exactly
the one which did the port probing: there are calls to
mm_plugin_base_supports_task_get_probed_capabilities() usually in
grab_port() in order to
Hi Eric,
The additional error detail allows us to know that a connection failed
because of an invalid APN. Also, when handling access technology
changes, report the technology in use if we're connected. Finally,
avoid using CFUN=0 when disabling the modem.
A small thing to fix in the patch.
: Aleksander Morgado aleksan...@lanedo.com
Date: Thu, 9 Jun 2011 09:35:25 +0200
Subject: [PATCH 2/2] libnm-util: added missing U2600 GSM band enumeration
---
libnm-util/nm-setting-gsm.c |3 ++-
libnm-util/nm-setting-gsm.h |1 +
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git
I'm using a multimode GPRS/EDGE/UMTS/HSDPA USB key for internet
access, product ONDA WCDMA Technologies MSM. OS is Ubuntu Natty 11.04
64-bit, NetworkManager 0.8.4.
The device always connects and once connected it works pretty fine,
the only problem is that it takes some minutes before the
Debug logs would be helpful.
I attached them to this mail, hope this helps.
:-( Sorry, I forgot one step... You need to:
$ killall modem-manager
between the network-manager stop and the manual run of modem-manager.
The attached MM logs are not useful, as MM just exited because there
On Tue, 2011-06-14 at 23:33 +0200, dave guandalino wrote:
2011/6/14 Aleksander Morgado aleksan...@lanedo.com:
:-( Sorry, I forgot one step... You need to:
Np :-) Btw, thanks for watching.
So, this modem is reported as being a ZTE modem, and therefore uses the
ZTE plugin in ModemManager.
3
Hi Dan list,
Would it be a good idea to alternate QCDM port probing along with the AT
port probing?, something like:
* Try AT command(s)
* If timeouts, try QCDM
* If timeouts, try again AT command(s)
* If timeouts, trya gain QCDM
* If timeouts, try again AT command(s)
* If timeouts, failed
: nil; c-basic-offset: 4 -*-
#
# Copyright (C) 2009 Red Hat, Inc.
# Copyright (C) 2011 Aleksander Morgado aleksan...@lanedo.com
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software
Hi all,
Some fixes related to power-up/power-down some modems are available in
the 'power-up-check-needed' branch in the following Gitorious repo
[1]:
git://gitorious.org/lanedo/modemmanager.git
The changes being:
* Modified the generic GSM implementation so that we allow plugins to
check
On Wed, 2011-06-22 at 08:21 -0700, Manish S Runwal wrote:
Sorry to bother you. But I am deadly looking for solution for it.
Your modem-manager debug logs show that you get NO CARRIER errors when
trying to connect:
(ttyUSB3): -- 'ATD*99***1#CR'
(ttyUSB3): -- 'CRLFNO CARRIERCRLF'
(ttyUSB3):
Hi Dan,
Some fixes related to power-up/power-down some modems are available in
the 'power-up-check-needed' branch in the following Gitorious repo
[1]:
git://gitorious.org/lanedo/modemmanager.git
These all look good. I think in the future though we should just define
some stuff
after hibernation the system asks for the sim pin, which is accepted, but
still is unable to connect, see the attached log. I deactivate 3g broadband,
then reactivate. After giving it some time, i have it connect to my provider.
It then recognizes that it has no SIM PIN available, which
Hi,
By the virtue of
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/459052
I've ended up running modem-manager from git (today's master).
And yet, not all is well (there's no connection). Here's the syslog
bits that looked interesting to me:
modem-manager[6071]: info
If you're still interested, I can send the MM/NM logs from a typical
session (there are several error-like anomalous messages on the way).
It would be great if you could do that, indeed.
--
Aleksander
___
networkmanager-list mailing list
On Mon, 2011-07-11 at 00:04 +0400, Samium Gromoff wrote:
On Sun, 10 Jul 2011 21:54:42 +0200, Aleksander Morgado
aleksan...@lanedo.com wrote:
Could you please provide modem-manager debug logs?
https://wiki.ubuntu.com/DebuggingModemmanager
In the very beginning of that page
Hey Samium,
...
modem-manager[3878]: info [1311508930.212757] [mm-serial-port.c:938]
mm_serial_port_close(): (ttyUSB0) serial port closed
modem-manager[3878]: debug [1311508930.213324] [mm-manager.c:687]
supports_callback(): (tty/ttyUSB0): plugin 0x9542d20 (Cinterion) existing
0x9542f20
...
modem-manager[3878]: info [1311508930.212757] [mm-serial-port.c:938]
mm_serial_port_close(): (ttyUSB0) serial port closed
modem-manager[3878]: debug [1311508930.213324] [mm-manager.c:687]
supports_callback(): (tty/ttyUSB0): plugin 0x9542d20 (Cinterion) existing
0x9542f20
Hi everyone,
One of the things that came up during the NM/MM BoF during the Desktop
Summit was about the possibility of having a C library (libmm-glib? [1])
which will enable easy access to ModemManager info in GLib-based
applications.
I'm looking into preparing a ModemManager.h with common
So, what about having a common ModemManager.h, and making the daemon
use it as well? I have mixed feelings on whether it makes sense to have
it auto-generated from the DBus API XMLs, anyway, as we want it to be
used also internally; so I would propose to have it manually maintained,
just
Hi,
I'm not sure why it is better to manually maintain the file rather
than auto generating it (other than XSLT being a difficult language),
but I certainly agree with using enum types instead of #defines.
It actually depends on what we want to have in that common header. If we
just want to
I'm not sure why it is better to manually maintain the file rather
than auto generating it (other than XSLT being a difficult language),
but I certainly agree with using enum types instead of #defines.
It actually depends on what we want to have in that common header. If we
Hi hi,
I'm not sure why it is better to manually maintain the file rather
than auto generating it (other than XSLT being a difficult language),
but I certainly agree with using enum types instead of #defines.
It actually depends on what we want to have in that common
On Thu, 2011-08-18 at 14:50 -0500, Dan Williams wrote:
On Wed, 2011-08-17 at 10:55 -0400, Jason Glasgow wrote:
I think that looks great. -Jason
Yeah, looks good to me too.
Should I just merge it to git master, or wait until I get the libmm-glib
ready for review?
--
Aleksander
On Fri, 2011-08-19 at 15:38 -0500, Dan Williams wrote:
On Fri, 2011-08-19 at 12:27 +0200, Aleksander Morgado wrote:
On Thu, 2011-08-18 at 14:50 -0500, Dan Williams wrote:
On Wed, 2011-08-17 at 10:55 -0400, Jason Glasgow wrote:
I think that looks great. -Jason
Yeah, looks good
=46d757faa768db7d7bb23d51cc2af3196f7a7e30
--
Aleksander
From 425cc9294141b83e66a6ed62a3e68674144ca6d8 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Sat, 20 Aug 2011 17:22:28 +0200
Subject: [PATCH] nokia: use E1 E0 when initializing the modem
Passing E1 and E0 afterwards
(ttyHS0): -- 'AT_OPSYS?CR'
Sep 15 10:43:34 ThinClient modem-manager[2081]: debug
[mm-at-serial-port.c:298] debug_log(): (ttyHS0): --
'CRLFERRORCRLF'
Sep 15 10:43:34 ThinClient modem-manager[2081]: debug
[mm-serial-parsers.c:412] mm_serial_parser_v1_parse(): Got failure
code 100: Unknown
In an email from a few months ago I saw a reference to a modem-manager cli.
Is this a publicly availble program?
It is not finished yet, but quite usable if you speak English (not
translated yet) and if you know how to clone a git repo and compile
ModemManager youself:
1. Clone
In an email from a few months ago I saw a reference to a modem-manager cli.
Is this a publicly availble program?
AFAIK there's no mm-cli at all; there are a number of CLI tools (mainly
for testing) that talk to MM. A CLI MM tool wouldn't be hugely useful
for actual connections though,
Hi all,
I've been lately trying to improve the probing process in ModemManager,
so that it is faster and easier to maintain, keeping in mind the
different specific needs of the current plugins.
The current status of the work can be seen in the 'probing-refactor'
branch in the following git repo:
1. Plugin Manager
---
The MMManager object handled too many different tasks, that it made
sense to me to have an independent MMPluginManager object which takes
care of:
* Finding plugins and loading them
* Controlling the requests
Hey,
after doing a lot of testing with bad UMTS connections, I was able to solve
most of my problems with my patches from
http://mail.gnome.org/archives/networkmanager-list/2011-September/msg00040.html
.
There is one problem still left, which I am not able to solve on my own.
If
These methods were available in the old API, and are needed in the new one.
---
new/org.freedesktop.ModemManager1.xml | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/new/org.freedesktop.ModemManager1.xml
b/new/org.freedesktop.ModemManager1.xml
index
SIM objects will be listed as independent objects in the DBus API, and the 'Sim'
property in a given modem object will specify which SIM object is in use.
---
new/org.freedesktop.ModemManager1.Modem.xml |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git
Here is a set of changes to the proposed MM DBus API. Some of them were already
discussed some time ago in the following thread:
https://mail.gnome.org/archives/networkmanager-list/2011-May/msg00162.html
[PATCH 1/8] api: include ScanDevices() and SetLogging() in the new manager API
[PATCH 2/8]
New 'Manufacturer', 'Model' and 'Revision properties are added, all being
read-only strings.
---
new/org.freedesktop.ModemManager1.Modem.xml | 37 +--
1 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/new/org.freedesktop.ModemManager1.Modem.xml
Modems which only expose a single port will not be able to update the signal
quality value while in connected mode. The signal quality value reported in this
case, while the modem is connected, will be the last signal quality value read
before the connection.
The additional boolean value proposed
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are supported by the
Makes more sense to have the enum named just as 'mode', as it applies to both
Supported and Allowed.
---
new/org.freedesktop.ModemManager1.Modem.xml |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/new/org.freedesktop.ModemManager1.Modem.xml
Changing the allowed mode of a modem may fail, for example if trying to set a
mode which is not in the modes reported as Supported by the modem. Therefore, we
need an explicit SetAllowedModes() method with proper error reporting instead of
making the property writable.
---
Changing the allowed bands in a modem may fail, for example if trying to set a
frequency band which is not in the bands mask reported as Supported by the
modem.
Therefore, we need an explicit SetAllowedBands() method with proper error
reporting instead of making the property writable.
---
Hey Thomas,
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE
values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes
Here is a set of changes to the proposed MM DBus API. Some of them were
already
discussed some time ago in the following thread:
https://mail.gnome.org/archives/networkmanager-list/2011-May/msg00162.html
[PATCH 1/8] api: include ScanDevices() and SetLogging() in the new manager
Hey hey,
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE
values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are
Hey Thomas,
To reproduce, i do the following:
1 ) stop NM, MM and disconnect the modem from power supply
2 ) connect the modem to power supply
3 ) start MM: modem-manager --debug --log-level=DEBUG
4 ) start NM: /etc/init.d/network-manager start
5 ) nmcli con up uuid
. It modifies the common serial
parser, so not something Cinterion-specific, but the change is quite
small and shouldn't affect other plugins.
Cheers,
--
Aleksander
From 9d56d7b55c55859e259d22476eef515e90d84a0a Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Thu, 13 Oct 2011 14
Hi all,
The ObjectManager interface was recently added as a standard interface
in DBus:
http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager
For the 0.6 API, we could be using this interface instead of the
proposed GetDevices() method, the Modems property and
So the real problem here is that the Cinterion modem sends a NUL byte
before the CONNECT response:
[mm-at-serial-port.c:298] debug_log(): (ttyS1): -- 'ATD*99***1#CR'
modem-manager[2621]: debug [1317807408.548825]
[mm-at-serial-port.c:298] debug_log(): (ttyS1): -- '\0'
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE
values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are supported by the
Hi everyone,
I just pushed a new '06-api' [1] development branch in the upstream
ModemManager git repo. This branch will hold the port of ModemManager to
the new 0.6 API, using GDBus and also targeting the new multi-mode LTE
devices. At some point it will also include the new libmm-glib [2] and
Hey Eric,
Some comments inline below.
On Wed, 2011-10-19 at 15:42 -0400, Eric Shienbrood wrote:
From b129d263ec1674462c218b4ec91260cf082bf77e Mon Sep 17 00:00:00 2001
From: Eric Shienbrood e...@google.com
Date: Thu, 11 Aug 2011 13:58:59 -0400
Subject: [PATCH] Added new property to track
On Wed, 2011-10-19 at 15:42 -0400, Eric Shienbrood wrote:
From 7c718db20958c200bc9dcb086763bfe0ebb91399 Mon Sep 17 00:00:00 2001
From: Eric Shienbrood e...@google.com
Date: Thu, 14 Jul 2011 19:11:54 -0400
Subject: [PATCH] Correctly track the number of SIM PIN retries left.
There are other
i use latest git-snapshot from ModemManager with NM 0.8.4. I try to use
a Fastttrack XTend FXT009.
I'm unable to get a working connection (see MM-Log).
After the connection, the modem does not answer to any AT-commands (see
the end of MM-Log).
Hmm, maybe we're dialing too early?
i use a Fasttrack xTend FXT009 with an external power supply.
i use MM on an embedded device and the modem is connected over usb.
When i have an active connection with the modem, remove the power from
the embedded device (so MM has no chance to cleanup anything) and then i
restart the
On Tue, 2011-11-22 at 12:21 +0100, Marcel Holtmann wrote:
Actually the HTTP header makes a lot more sense since once you
received
the valid one, you can just terminate the HTTP request and do not have
to deal with downloading the whole file.
You can possibly do just a HTTP HEAD request,
Hey Eric Dan,
On Fri, 2011-11-11 at 15:10 -0500, Eric Shienbrood wrote:
Subject: [PATCH] Added new property to track which facility locks are
enabled.
The property EnabledFacilityLocks on the .Modem.Gsm.Card interface
is a bit mask that indicates which of the various personalization
codes
Hey hey,
I guess I don't have a problem with merging them, although strictly
speaking they refer to different things - locks vs. the PINs needed to
unlock those locks.
Yeah, you're totally right... but at the end the PIN/PUK codes are
directly related to facilities. E.g SIM facility, has PIN
Hey Dan ttuttle,
The 0.6 API in MM has 2 properties named ModemCapabilities and
CurrentCapabilities. The current ones will be the ones reported by
+GCAP, but how do we know the modem ones?
I am assuming here that the ModemCapabilities will be different to the
CurrentCapabilities only when the
Hey,
According to the DBus specs [1], no element within a DBus interface can
start with a digit... so org.freedesktop.ModemManager1.Modem.3gpp is a
bad name. :-/
I will temporarily fallback to use:
org.freedesktop.ModemManager1.Modem.Modem3gpp (along with
(For ChromeOS development, I have rigged up a black-box ModemManager
test system under autotest, which creates a fake gudev device and a
fake modem that responds to AT commands to test this kind of thing. It
might be interesting to adapt it into the MM build system somehow;
right now it's
This was the only code in ModemManager using g_error(), and not
appropriately, I think.
The codebase is still mixed on how to handle errors compiling regular
expressions; other places in this file use g_assert(), while the rest
of the code tends to report some kind of parse-failure error.
I guess I don't have a problem with merging them, although strictly
speaking they refer to different things - locks vs. the PINs needed to
unlock those locks.
Yeah, you're totally right... but at the end the PIN/PUK codes are
directly related to facilities. E.g SIM facility, has
According to the DBus specs [1], no element within a DBus interface can
start with a digit... so org.freedesktop.ModemManager1.Modem.3gpp is a
bad name. :-/
I will temporarily fallback to use:
org.freedesktop.ModemManager1.Modem.Modem3gpp (along with
I guess I don't have a problem with merging them, although strictly
speaking they refer to different things - locks vs. the PINs needed to
unlock those locks.
Yeah, you're totally right... but at the end the PIN/PUK codes are
directly related to facilities. E.g SIM
On Thu, 2011-06-30 at 11:51 -0500, Dan Williams wrote:
On Wed, 2011-06-22 at 16:35 +0200, Aleksander Morgado wrote:
Hi all,
Some fixes related to power-up/power-down some modems are available
in
the 'power-up-check-needed' branch in the following Gitorious repo
[1]:
git
On 12/21/2011 07:00 PM, John Hibbs wrote:
One thing I do see is 'ATD*99***1***2#CR'. This does not match the
settings I entered in.
Mobile Broadband Settings:
Connection name: ATT Mobile
IPv4 Method: Automatic(PPP)
Mobile Broadband Number: *99***1#
Mobile Broadband APN: isp.cingular
Type: Any
Hey!
One thing I do see is 'ATD*99***1***2#CR'. This does not match the
settings I entered in.
Mobile Broadband Settings:
Connection name: ATT Mobile
IPv4 Method: Automatic(PPP)
Mobile Broadband Number: *99***1#
Mobile Broadband APN: isp.cingular
Type: Any
Allow roaming
PPP Authentication
Hey,
One of the things that annoys me when using ModemManager is that
whenever I plug in a modem, I need to wait for the modem to get all
ports probed before I can see the NM applet updated with the new
broadband-related menu elements. In the worst case, where the modem just
returns errors
Hey Dan,
One of the things that annoys me when using ModemManager is that
whenever I plug in a modem, I need to wait for the modem to get all
ports probed before I can see the NM applet updated with the new
broadband-related menu elements. In the worst case, where the modem just
returns
Hey Jason,
One of the things that annoys me when using ModemManager is that
whenever I plug in a modem, I need to wait for the modem to get all
ports probed before I can see the NM applet updated with the new
broadband-related menu elements. In the worst case, where the modem
Hey Dan,
On Ubuntu 11.10 there is problem with connection via modem Huawei E220.
On Ubuntu 11.10 the NetworkManager is in version 0.9.1.90-0ubuntu5.1
On Ubunto 11.04 there is version 0.8.4~git.20110319t175609.d14809b-0ubuntu3
The issue for Ubuntu was submitted:
1 - 100 of 664 matches
Mail list logo
