On 04/08/2013 11:51 PM, Arman Uguray wrote:
Added qmi_wwan as one of the supported drivers for the Gobi plugin.
Is there any modem which doesn't work without this fix?
I know it seems a clear fix to do, but it may have some side effects.
The drivers filter was thought for the qcserial case,
On 04/09/2013 06:19 PM, Dan Williams wrote:
On Tue, 2013-04-09 at 13:11 +0200, Aleksander Morgado wrote:
On 04/08/2013 11:51 PM, Arman Uguray wrote:
Added qmi_wwan as one of the supported drivers for the Gobi plugin.
Is there any modem which doesn't work without this fix?
I know it seems
We will very likely get the result of the connection attempt before the 2 mins,
either successful or error, but still we need to explicitly ask to keep the
DBus call open enough time.
This time should be enough to handle both the connection time (usually around
60s max), plus the time needed to
On 04/04/2013 10:05 PM, Dan Williams wrote:
On Thu, 2013-04-04 at 12:40 -0700, Ben Chan wrote:
---
src/mm-broadband-bearer.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
I'll assume then that somebody has a \ or in their APN then, right?
In any case, patch looks good.
On 04/05/2013 04:29 PM, Enrico Murador - Research Development - CET wrote:
Great news!
Now I'm able to successfully enable my modem with mmcli -m 0 -e
without MM crashing.
I also sent a SMS using mmcli -m 0 --messaging-create-sms ... and
mmcli -s (sms number) --send.
But...
I'm not able
On 04/03/2013 08:18 PM, Dan Williams wrote:
On Wed, 2013-04-03 at 18:59 +0200, Aleksander Morgado wrote:
On 03/04/2013 03:33 PM, Dan Williams wrote:
On Fri, 2013-03-01 at 15:08 +0100, Gerald Richter - ECOS wrote:
The following patch solves the problem for us. It works with all revisions
we
On 04/04/2013 11:08 AM, Aleksander Morgado wrote:
On 04/03/2013 08:18 PM, Dan Williams wrote:
On Wed, 2013-04-03 at 18:59 +0200, Aleksander Morgado wrote:
On 03/04/2013 03:33 PM, Dan Williams wrote:
On Fri, 2013-03-01 at 15:08 +0100, Gerald Richter - ECOS wrote:
The following patch solves
Some additional information about this device, forgetting about the APP1
port issue...
The MC8790 is really a Direct-IP capable device, but without DHCP.
Interesting. Let's try to figure out how to support that. Maybe
export the raw fwattr and let userspace figure it out instead?
The
On 04/03/2013 08:56 AM, Enrico Murador - Research Development - CET wrote:
Ok! Same issue also on qcdm_cmd_wcdma_subsys_state_info_result(), right?
It seems there are no other places where imxi_bcd_to_string() is used.
Dan already fixed that one as well in his commit, see:
On 04/02/2013 01:57 AM, Ori Inbar wrote:
Hello all
This is a log for the plugin run :
2013-04-01T16:19:30.614176-07:00 localhost ModemManager[1366]: debug
(Plugin Manager) [/sys/devices/s5p-ehci/usb1/1-1] Checking device support...
2013-04-01T16:19:30.614408-07:00 localhost
On 03/04/2013 03:33 PM, Dan Williams wrote:
On Fri, 2013-03-01 at 15:08 +0100, Gerald Richter - ECOS wrote:
The following patch solves the problem for us. It works with all revisions
we have available for testing
Pushed to git master and 0.6, thanks!
Dan
Gerald
---
Hey Dana,
THANK YOU so much for your help! It's made a huge difference.
I am now able --- through command line scripting --- to connect and
disconnect to the Internet via the broadband modem with consistent, 100%
reliable results. This is WONDERFUL! Another big THANK YOU to all the
On 04/02/2013 12:09 PM, Enrico Murador - Research Development - CET wrote:
Also, if you have
some time and the ability to run valgrind on the system, could you run
ModemManager under valgrind like so?
mv /usr/sbin/ModemManager /
killall -TERM ModemManager
G_SLICE=always-malloc valgrind
leack-check=full is really not needed here as we didn't want the leak
reports, just the invalid memory accesses reported by valgrind/memcheck.
Anyway, valgrind didn't say anything useful. Still the stack smashing
detected error is telling us we're writing out of bounds of an array or
Hey Dana,
Please forgive me if this list is not an appropriate venue for my question.
I'm trying to get an integrated Sierra Wireless MC7750 Modem (Verizon 4G LTE)
up and running using the latest ModemManager (0.7/0.8), libqmi, and
NetworkManager 0.9.8.
The modem works reliably on
On 04/01/2013 01:20 PM, David Castellanos wrote:
NM attempts to set allowed and preferred mode during the connection
process. The plugin x220x does not handle properly when NM request
allowed mode to '2g, 3g' and the preferred mode to 'none'.
This commit attempts to solve the problem
Hey,
+/*/
+/* Facility locks status loading (3GPP interface) */
+
+typedef struct {
+MMBroadbandModem *self;
+GSimpleAsyncResult *result;
+guint current;
+MMModem3gppFacility facilities;
+
Done, but when I try to enable the modem with [sudo] mmcli -m 0 -e
(or also with mmcli -L) I get couldn't find the ModemManager process
in the bus... I've checked with ps -def and gdb+MM seems running.
That's likely a crash. You didn't see anything reported within gdb?
Only for
On 27/03/13 21:25, ori inbar wrote:
This patch fixes a problem of disregarding CEREG/CGREG/CREG reported
access technology since we are in registering state - meaning we are
loading operator name+code. now even in this transition state the ACT
is updated.
Pushed, thanks.
---
On 27/03/13 21:14, ori inbar wrote:
---
src/mm-at-serial-port.c | 40 ++--
src/mm-at-serial-port.h | 2 ++
src/mm-plugin.c | 19 +++
src/mm-plugin.h | 1 +
src/mm-port-probe.c | 5 +
src/mm-port-probe.h | 1
On 27/03/13 10:41, Enrico Murador - Research Development - CET wrote:
When I try to send an SMS when connected (with MM 5.2), I get an error
like cannot send an SMS while connected (maybe connection is made
using only one USB port?). If data connection is not active, I still
cannot send SMS,
On 27/03/13 14:39, Enrico Murador - Research Development - CET wrote:
In MM 0.7.x, make sure you *unlock* the PIN (if needed) and *enable* the
modem before trying to send SMS, e.g. (assuming index 0 for SMS and
modem):
$ sudo mmcli -i 0 --pin=1234
$ sudo mmcli -m 0 -e
On rows 391/392 of
On 27/03/13 14:46, Dan Williams wrote:
Also, not sure what you mean with 'failed' startup. In the logs I just
see that the modem was plugged in, nothing else.
On MM 5.2 log, I see that modem goes from DISABLED state to ENABLING,
then ENABLED, then REGISTERED. After that I can start a
On 27/03/13 17:13, Enrico Murador - Research Development - CET wrote:
On 27/03/2013 16:52, Dan Williams wrote:
I don't think he meant you to literally write /| and |/; that'll cause
the shell to give you the prompt. It should basically be: mmcli -m 0
On 27/03/13 17:49, Enrico Murador - Research Development - CET wrote:
On 27/03/2013 17:36, Aleksander Morgado wrote:
That sequence is extremely strange... Was there any MM crash in between?
Yes... I've taken a quick look, the ModemManager PID changes just after
the completion of mmcli -m 0
+{
+MMBearerIpConfig *config;
+
+if (g_simple_async_result_propagate_error
(G_SIMPLE_ASYNC_RESULT (res), error))
+return FALSE;
+
+config = g_simple_async_result_get_op_res_gpointer
(G_SIMPLE_ASYNC_RESULT (res));
+
On 25/03/13 15:12, Enrico Murador - Research Development - CET wrote:
Hello,
I'm not able to send SMS with ModemManager and Telit UC864-E UMTS
Module. I've tried version 5.2 Ubuntu 12.04LTS and 6.0 on both 12.04 and
12.10.
Are you able to test this with MM git master?
Marius: There is
On 25/03/13 14:28, Thomas Bechtold wrote:
Hi,
this patch is for MM06. But I guess master is also affected.
Pushed to MM_06, and also made the fix in git master.
Thanks!
Cheers,
Tom
---
src/mm-sms-utils.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff
On 03/20/2013 06:01 PM, Gonzalez Calabozo, Jose Maria wrote:
So several patches can be applied to fix this issue.
The most simple is just to check the value of msg_errors[i].error:
--- a/src/mm-error-helpers.c
+++ b/src/mm-error-helpers.c
@@ -243,7 +243,7 @@ mm_message_error_for_string
On 05/03/13 22:21, Ben Chan wrote:
---
src/mm-broadband-modem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Pushed, thanks.
diff --git a/src/mm-broadband-modem.c b/src/mm-broadband-modem.c
index 9d127c9..b3ec35a 100644
--- a/src/mm-broadband-modem.c
+++
On 03/05/2013 02:00 AM, Ben Chan wrote:
---
src/mm-broadband-modem.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Nice catch :) Pushed.
diff --git a/src/mm-broadband-modem.c b/src/mm-broadband-modem.c
index 9f45904..9d127c9 100644
--- a/src/mm-broadband-modem.c
+++
On 03/05/2013 03:37 AM, Ben Chan wrote:
This patch changes MMIfaceModem3gpp to differentiate between deferrable
and non-deferrable 3GPP registration state updates. Periodic or
unsolicited registration state updates are deferrable, while internal
updates, e.g. due to modem being disabled, are
On 03/01/2013 06:09 PM, Ben Chan wrote:
Yep, that should work.
Pushed that fix as well; thanks for reviewing it.
Cheers!
On Fri, Mar 1, 2013 at 12:18 AM, Aleksander Morgado
aleksan...@lanedo.com mailto:aleksan...@lanedo.com wrote:
On 03/01/2013 09:06 AM, Ben Chan wrote
On 02/27/2013 11:04 PM, Ben Chan wrote:
---
src/mm-iface-modem-3gpp.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
When I reviewed your original patch I actually checked for when we were
removing the timeout when disabling, and assumed it was done when we set
the
On 02/28/2013 09:24 AM, ori.in...@altair-semi.com wrote:
From: ori inbar ori.in...@altair-semi.com
Looks good; some minor comments below.
Also, are you going to suggest a new plugin for MM using this property
set to TRUE? If so, it may be a good idea to send all relevant commits,
including
When I reviewed your original patch I actually checked for when we were
removing the timeout when disabling, and assumed it was done when we set
the GObject's data to NULL, but I mixed the two data objects we handle
here, as one of them (the one where this new timeout id is stored) isn't
On 02/28/2013 03:20 PM, Dan Williams wrote:
Also, are you going to suggest a new plugin for MM using this property
set to TRUE? If so, it may be a good idea to send all relevant commits,
including this one, in the same patch series, along with the plugin.
Now that I think about it, is there
On 02/28/2013 08:11 PM, Ben Chan wrote:
---
src/mm-iface-modem-3gpp.c | 15 +++
1 file changed, 15 insertions(+)
I pushed it after modifying it to include the
clear_deferred_registration_state_update() call in the first
DISABLING_STEP_PERIODIC_REGISTRATION_CHECKS step. As said
On 02/26/2013 12:54 PM, Bjørn Mork wrote:
is it so that ModemManager/NetworkManager require wwanX names for all 3G
etc modem network interfaces?
At least MM is happy with mobile broadband modems exporting either ethX,
usbX or wwanX names.
--
Aleksander
On 02/16/2013 12:17 AM, Ben Chan wrote:
This patch defers the update of 3GPP registration state by 15 seconds
when the registration state changes from 'registered' (home / roaming)
to 'searching'. This allows a temporary loss of 3GPP registration to
recover itself when relying on ModemManager
(Resent with gzipped log)
we have now tested with two MC8790 cards. One has work ever since with
modem-manger, the other didn't (as Harald reported last week).
From an usb point of view there is no difference (same product/vendor id
etc.).
The only difference is, that the card that
On 02/25/2013 01:53 PM, Gerald Richter - ECOS wrote:
Before we started to use network-manager we used a self made script (which
only supports the ppp interface) and if I remember correctly, we always used
the lowest ttyUSB Port as primary in case there was no other setup known for
a card.
On a side note, a user just reported an issue with a MC8790V (see the
trailing 'V' there), log attached. In this case, the issue is not about
using the APP1 port for PPP; the issue is that there is no non-APP port
shown, so we don't specify any port being 'primary', and we end up
choosing an
On 02/24/2013 11:16 AM, Colin Walters wrote:
See attached.
Pushed, thanks.
--
Aleksander
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Now the Modem Manager always detects the Huawei e303. :)
But with this version I have a compilation warning.
I get the next error:
make[3]: Entering directory `/home/jose/modemmanager/ModemManager/src'
CC ModemManager-mm-plugin.o
mm-plugin.c: In function
On 02/20/2013 07:22 AM, Ben Chan wrote:
Patch iface-modem: fix invalid modem state consolidation (commit
69aff6183a9e6532b4074c89831d6dcfa81ddcce) incorrectly consolidates the
modem state upon the disconnection of a bearer. The modem state remains
'connected' after the last bearer is
Thanks for your fast response! and thanks for the new NewtorkManager
packages. I have installed them and they seem to work fine.
I was using a Git version from the 18th. This morning I have updated my local
version with the latest version from the repository.
I have tried with the
On 02/20/2013 04:13 PM, Gonzalez Calabozo, Jose Maria wrote:
I'm not sure if this list allows attachments.
I send two log files attached:
ndis.txt -- System logs (ModemManager in debug mode) of an unsuccessful NDIS
Huawei connection attempt.
attachmodem-txt -- ModemManager logs where the usb
I have found another issue that I am not sure if it is a bug or not. It
seems that the ModemManager cannot detect the first time that I insert the
modem.
After try with many ports it prints the next lines:
ModemManager[7749]: debug [1361368039.448167] [mm-serial-port.c:994]
On 20/02/13 20:50, Ben Chan wrote:
Thanks! One more question that comes to my mind. Could it be possible
that there is no subsystem? If that's the case, the modem state will be
in the unknown state. Is that what we want?
There really needs to be a subsystem; either 3GPP or CDMA/EVDO; so
On 02/15/2013 06:26 PM, Ben Chan wrote:
I was also wondering if that's needed. I guess soft-resetting the modem
helps clear any unknown settings on the modem before ModemManager starts
managing it. For a hotplugged modem, I'd assume it is managed by
ModemManager from the beginning and have the
Hoola Jose María :)
I have downloaded and installed the last ModemManager version from the
Git repository. I also have installed the NetworkManager packages by
Aleksander to integrate MM with gnome3 in fedora18:
http://sigquit.wordpress.com/2012/11/13/integrating-the-new-modemmanager-in-gnome3/
On 02/19/2013 03:57 PM, Aleksander Morgado wrote:
I fixed quite some things since I created those packages, so let me
re-create whole new ones with the latest stuff. As said, the port to be
used as data port by pppd is the one given in the Bearer interface.
Try with these ones here:
/home
On 02/19/2013 04:49 PM, Aleksander Morgado wrote:
On 02/19/2013 03:57 PM, Aleksander Morgado wrote:
I fixed quite some things since I created those packages, so let me
re-create whole new ones with the latest stuff. As said, the port to be
used as data port by pppd is the one given
I have an ARM device that I'm trying to make use a Sierra Wireless 330U
to connect to Bell Canada. I'm working on getting ModemManager on the
device, but I'm fighting cross-compilation issues.
Until then, I'm trying to connect it manually and I'm having trouble.
First, when putting the
I have an ARM device that I'm trying to make use a Sierra Wireless 330U
to connect to Bell Canada. I'm working on getting ModemManager on the
device, but I'm fighting cross-compilation issues.
Until then, I'm trying to connect it manually and I'm having trouble.
First, when putting the
On 02/12/2013 02:18 AM, Ben Chan wrote:
This patch defers the update of 3GPP registration state by 15 seconds
when the registration state changes from 'registered' (home / roaming)
to 'searching'. This allows a temporary loss of 3GPP registration to
recover itself when relying on ModemManager
We avoid requesting to auto-start the service when the 'MMManager' is created,
so that we can use it to follow name-owner changes (when auto-starting
requested the 'MMManager' creation may fail).
We still handle the periodic poking to the service, but instead of re-creating
the 'MMManager', we
Make sure we cleanup all the signals when we remove our internal reference to
the 'MMManager' object.
---
src/modem-manager/nm-modem-manager.c | 64
1 file changed, 51 insertions(+), 13 deletions(-)
diff --git a/src/modem-manager/nm-modem-manager.c
The 'GDBusObjectManagerClient' won't signal added or removed objects when it
was created but no name owner was available in the bus. We can still use it for
name-owner changes, but in order to have added/removed object signals, we'll
need to re-create the whole 'MMManager' when we know the service
Make sure we cleanup all the signals when we remove our internal reference to
the 'MMManager' object.
---
src/modem-manager/nm-modem-manager.c | 64
1 file changed, 51 insertions(+), 13 deletions(-)
diff --git a/src/modem-manager/nm-modem-manager.c
The 'GDBusObjectManagerClient' won't signal added or removed objects when it
was created but no name owner was available in the bus. We can still use it for
name-owner changes, but in order to have added/removed object signals, we'll
need to re-create the whole 'MMManager' when we know the service
On 08/02/13 08:32, Aleksander Morgado wrote:
Make sure we cleanup all the signals when we remove our internal reference to
the 'MMManager' object.
---
src/modem-manager/nm-modem-manager.c | 64
1 file changed, 51 insertions(+), 13 deletions(-)
Please
---
src/modem-manager/nm-modem-manager.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/modem-manager/nm-modem-manager.c
b/src/modem-manager/nm-modem-manager.c
index d896b46..553c114 100644
--- a/src/modem-manager/nm-modem-manager.c
+++
On 30/01/13 21:21, Ben Chan wrote:
---
plugins/novatel/mm-broadband-modem-novatel-lte.c | 26
1 file changed, 26 insertions(+)
Pushed, thanks.
--
Aleksander
___
networkmanager-list mailing list
On 30/01/13 10:07, Ben Chan wrote:
$NWQMISTATUS sometimes returns 'ERROR'. This patch modifies the Novatel
LTE plugin to retry $NWQMISTATUS (up to 5 times) to determine if the
disconnect operation succeeds. It also changes the plugin to assume that
the disconnect operation succeeds if
On 30/01/13 21:32, Ben Chan wrote:
---
src/mm-iface-modem.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/mm-iface-modem.c b/src/mm-iface-modem.c
index 10144aa..722664c 100644
--- a/src/mm-iface-modem.c
+++ b/src/mm-iface-modem.c
@@ -3979,6 +3979,8 @@
On 24/01/13 02:16, Ben Chan wrote:
This patch fixes get_current_consolidated_state() in MMIfaceModem to
avoid invalid state transitions, e.g. from 'enabling' to 'disabled'.
https://code.google.com/p/chromium-os/issues/detail?id=38173
I modified the commit log to include the information from
On 22/01/13 05:39, Ben Chan wrote:
There may be better ways to collect this kind of performance data than
outputting them to ModemManager log. Is there a commonly used method
for ModemManager to report performance metrics in a way that other tools
can collect and analyze them?
I don't know of
On 19/01/13 17:50, Marius B. Kotsbak wrote:
power_state is an enum, not a string:
error: format '%s' expects argument of type 'char *', but argument 5 has type
'unsigned int' [-Werror=format]
We can print all enums as strings, so better do that instead:
On 18/01/13 08:11, Ben Chan wrote:
This patch adds a 'hotplugged' flag to MMBaseModem to indicate if a
modem is newly plugged in. A plugin can use this information to
determine if, for example, the modem needs to be soft reset using the
ATZ command.
Dan Williams d...@redhat.com contributed
On 18/01/13 08:11, Ben Chan wrote:
Soft resetting a Novatel LTE modem can a significant amount of time
(3-4 seconds). If the modem is newly plugged in, skip the unnecessary
soft reset when enabling the modem.
---
Merged, thanks!
--
Aleksander
___
On 18/01/13 08:06, Ben Chan wrote:
This patch modifies MMIfaceModem to schedule the periodic signal quality
check with a period of 3s instead of 30s (up to 5 periods) initially
until a non-zero signal quality value is obtained and then switch back
to the 30s period.
---
Merged, thanks!
--
I would very much like to know that goes. It should work in theory,
creating wwanX and /dev/cdc-wdmY devices. But do note that this
/dev/cdc-wdmY device is *not* speaking QMI. It expects MBIM control
protocol messages. Unfortunately there isn't any user app available for
that yet, but I
I pushed a new 'set-power-state' branch to the upstream MM git repo,
with the changes required to have the power state handled independently,
i.e. low-power not associated to the disabled state.
The branch includes a new 'PowerState' property (exposing the current
power state) and a new
On 08/01/13 08:52, Ben Chan wrote:
The patch addresses the firmware selection issue I mentioned. I think it
can be pushed as it is. Thanks!
Pushed then.
Cheers.
--
Aleksander
___
networkmanager-list mailing list
networkmanager-list@gnome.org
I pushed a new 'unlock-check' branch to MM git with some changes/fixes
regarding the lock check logic (PIN, PUK, unlock retries). I've tested
them quite a lot, but I wouldn't mind a second look before merging them
to git master.
Merged this branch into git master. Let me know if you find
:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Mon, 7 Jan 2013 22:19:02 +0100
Subject: [PATCH] broadband-modem: launch the Firmware interface even on fatal
errors
Even when there is a fatal error during initialization (e.g. missing PIN in a
3GPP modem), we should allow operations
On 07/01/13 23:34, Ben Chan wrote:
Thanks for the patch and it works.
Oh; cool. Nothing else needed then?
--
Aleksander
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Hey hey Ben,
I encounter an issue with firmware selection on my Novatel Gobi 3000
(E396) modem. When the UMTS firmware is initially selected and there is
no SIM card inserted, ModemManager can't fully initialize the modem and
firmware interface, which prevents me from selecting the CDMA
You cannot mix in the same async method a code execution path using
mm_base_modem_at_command() with another one using GSimpleAsyncResult and
completion in idle. When you use mm_base_modem_at_command(), in
finish() you're expected to use mm_base_modem_at_command_finish(), like
you did. But
On 04/01/13 03:50, Ben Chan wrote:
---
plugins/novatel/mm-broadband-modem-novatel-lte.c | 102
+-
src/mm-iface-modem.c | 20
src/mm-iface-modem.h |3 +
3 files changed, 124 insertions(+), 1 deletions(-)
On 03/01/13 07:44, Ben Chan wrote:
+/* The Novatel LTE modem does not properly support AT+COPS=? in LTE mode.
+ * Thus, do not try to scan networks when the current access technologies
+ * include LTE or cannot be determined.
Really? What happens?
--
Aleksander
On 03/01/13 20:13, Ben Chan wrote:
Also, based on my experiments, the modem sometimes seems to hang when
running AT+COPS=?. This patch avoids AT+COPS=? from being issued when
the modem is in LTE mdoe.
From what I can see, it also avoids the Scan when the access tech is
unknown:
+if
On 03/01/13 11:55, Ben Chan wrote:
This patch fixes a crash in periodic_registration_checks_ready() due to
access of an already deallocated RegistrationCheckContext.
Thread 0 *CRASHED* ( SIGSEGV @ 0x )
0x7fc344d355cd [ModemManager] - mm-iface-modem-cdma.c:1112
Also, based on my experiments, the modem sometimes seems to hang when
running AT+COPS=?. This patch avoids AT+COPS=? from being issued when
the modem is in LTE mdoe.
From what I can see, it also avoids the Scan when the access tech is
unknown:
+if
+static GList *
+scan_networks_finish (MMIfaceModem3gpp *self,
+ GAsyncResult *res,
+ GError **error)
+{
+const gchar *result;
+
+result = mm_base_modem_at_command_finish (MM_BASE_MODEM (self), res,
error);
+if (!result)
+
Hey,
I pushed a new 'set-power-state' branch to the upstream MM git repo,
with the changes required to have the power state handled independently,
i.e. low-power not associated to the disabled state.
The branch includes a new 'PowerState' property (exposing the current
power state) and a new
1) SIM lock after power up
So, we power-down the modem with CFUN=4 and we recover full
functionality mode with CFUN=1,0 (0 to avoid the reset). But, if the SIM
has PIN enabled, the modem will require SIM unlock before going on. If
you don't provide the SIM, it will end
Hey Dan, Marius everybody,
I recently got a ironywonderful/irony Sierra Wireless C885 modem
from eBay...
I fixed several obvious issues in MM git master to have it connected,
but I'm stuck with several things that I don't really know how to
properly handle.
1) SIM lock after power up
So, we
Not sure if I should try to update the firmware of the modem, or
directly re-sell it :-). My current firmware revision is:
'J1_0_1_6AP C:/WS/FW/J1_0_1_6AP/MSM7200A/SRC/AMSS 2008/07/09 07:52:58'
I would have upgraded it unless you have specific reasons for using this
old firmware.
Not sure if I should try to update the firmware of the modem, or
directly re-sell it :-). My current firmware revision is:
'J1_0_1_6AP C:/WS/FW/J1_0_1_6AP/MSM7200A/SRC/AMSS 2008/07/09 07:52:58'
I would have upgraded it unless you have specific reasons for using this
old firmware.
The Bus Pirate v4 presents itself as a CDC ACM device which
ModemManager attempts to configure. This results in a range
of confusing issues because it injects a bunch of AT commands
over whatever is going on at the time.
Firmware updates were failing at random points and avrdude
failed to
Hey Dan Ben,
I pushed a new 'unlock-check' branch to MM git with some changes/fixes
regarding the lock check logic (PIN, PUK, unlock retries). I've tested
them quite a lot, but I wouldn't mind a second look before merging them
to git master.
Cheers!
--
Aleksander
If, for any reason, MM exposes a modem object without 3GPP or 3GPP2
capabilities, just return an error instead of assert()-ing.
---
src/modem-manager/nm-modem-broadband.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git
I hope I'm not chumming up your list with a general question. I've spent many
hours trying to figure why the vendor/product isn't showing up in nm-applet.
NetworkManager and nm-aaplet work without issue. No error messages in the
console. This is the last minor issue I need to work out
Aleksander, thanks for the patch. I've been running suspend/resume test
with the patch. Seems like those glib warnings (and the crash) are gone
except for the following:
So, I pushed now the patch for both the Icera and HSO plugins; see
commit dc9bbef.
(ModemManager:2858):
On 06/12/12 12:49, Bastien Nocera wrote:
Otherwise, I'm in the market for a 3G modem that supports those. Cheaper
is better. Anything on eBay or Amazon that people would recommend?
That should be the Option 225, which has GPS functionality, but you may
need to enable it with
On 03/12/12 20:24, Ben Chan wrote:
Aleksander, thanks for the patch. I've been running suspend/resume test
with the patch. Seems like those glib warnings (and the crash) are gone
except for the following:
(ModemManager:2858): GLib-GObject-WARNING **: gsignal.c:2576: instance
`0x78624028'
On 30/11/12 02:18, Ben Chan wrote:
It looks like the modem is getting disposed but then something is
causing it to get enabled again after wakeup:
ModemManager[2858]: debug [1354146967.597474] [mm-base-modem.c:1252]
finalize(): Modem (Samsung) '/sys/devices/s5p-ehci/usb1/1-2/1-2.1'
201 - 300 of 664 matches
Mail list logo
