Re: [PATCH 2/3] base-manager: handle NULL physical device more gracefully

On Fri, Feb 24, 2017 at 8:14 PM, Ben Chan wrote: >> > find_device_by_physdev_uid() expects a non-NULL UID of the physical >> > device. However, mm_kernel_device_get_physdev_uid() could potentially >> > return NULL on MMKernelDeviceUdev if find_physical_gudevdevice() in >> >

Re: ABOUT-NLS missing?

On Tue, Feb 14, 2017 at 4:59 PM, Colin Helliwell wrote: >> Just updated my env setup to the latest master >> (git://anongit.freedesktop.org/ModemManager/ModemManager), but configure is >> giving an error: >> >> configure.ac:86: error: required file './ABOUT-NLS'

Re: glib-mkenums error for ublox plugin

cceeded – but perhaps > because earlier build steps have created the relevant directory e.g. > build/src. Could you apply the attached patch and retry? It could just be the order of the files generated, because the .c file depends on the .h file and they were requested in the other way in B

Re: How to issue an "ifup broadband" when this is logged

On Sat, Feb 11, 2017 at 11:48 PM, Russ Westrem wrote: > Ok this looks a little different than the last debug. I had a ping going > and logged "LTE Down" when pings stopped. > > > > Sat Feb 11 16:40:43 2017 daemon.debug [1049]: [/dev/cdc-wdm0] Received > message...

Re: Modem creation/startup order

On Tue, Feb 14, 2017 at 11:39 AM, Colin Helliwell wrote: >> > Thanks. The question arises from needing to have monitoring & URCs etc on >> > one port of my mux driver, and ppp on the other - I need to make sure that >> > ppp doesn't get run on the 'monitoring'

Re: Cinterion bug? (Re: Handling received SMS)

On Tue, Feb 14, 2017 at 10:38 AM, Colin Helliwell wrote: > I'm currently pulling a source tarball (for Yocto environment) from > http://www.freedesktop.org/software/ModemManager/ > I wonder if I should, whilst in development at least, keep in step with your > git

Re: Cinterion plugin (in)compatibilities

On Tue, Feb 14, 2017 at 10:10 AM, Colin Helliwell wrote: >> > ... >> I'm not confident of correctly interpreting the regex in smong_query_ready() >> (let alone fixing it properly!), but I wonder if the SMONG problem is that >> it's getting an additional CRLF. The

Re: How to issue an "ifup broadband" when this is logged

On Fri, Feb 10, 2017 at 7:46 PM, Russ Westrem wrote: > Ok. So it seems I may have spoken a little too soon on the powered usb hub > working. Here is something I have noticed. > > It works for hours and hours at a time on bearer 0. Once an ifup is issued > to fix a

Re: Handling received SMS

On Fri, Feb 10, 2017 at 3:40 PM, wrote: > I’m digging into SMS reception, and trying understand how MM deals with it. > > I can see that it/mmcli reads the messages when the modem is enabled. When a > new SMS is then received, I can see the modem sending a “+CIEV:

Re: Modem creation/startup order

On Fri, Feb 10, 2017 at 3:39 PM, wrote: > I’ve got two ports whitelisted for use by MM. What determines which one of > them will be ‘Modem/0’ ? > Just the first modem that finishes first probing all ports. > Is there a way to get MM to create/initialise 0 first,

Re: How to issue an "ifup broadband" when this is logged

On Fri, Feb 10, 2017 at 11:08 PM, Russ Westrem wrote: > OK. I think we're getting to the bottom of this. For some reason if I drop > the connection for any reason the mc7455 tries to re-authenticate my > connection. I am not authorized to use this device from Sprint

Re: How to issue an "ifup broadband" when this is logged

On Fri, Feb 10, 2017 at 9:37 PM, Russ Westrem wrote: > Fri Feb 10 14:33:23 2017 daemon.debug [1042]: [/dev/cdc-wdm0] Received > message... >>> RAW: >>> length = 80 >>> data = >>>

Re: How to issue an "ifup broadband" when this is logged

You're getting error 0x24 (dec 36), and according to 3GPP 24008 that is: Cause value = 36 Regular deactivation This cause code is used to indicate a regular MS or network initiated PDP context deactivation or a regular network initiated MBMS context deactivation. so the network is de-registering

Re: How to issue an "ifup broadband" when this is logged

On Fri, Feb 10, 2017 at 11:37 PM, Russ Westrem wrote: > And generic firmware on the mc7455 is what I'm referring to. > Oh, so with the Generic firmware you do get a good persistent connection but not with the Sprint firnmware? -- Aleksander https://aleksander.es

Re: How to issue an "ifup broadband" when this is logged

On Tue, Feb 14, 2017 at 10:33 PM, Russ Westrem wrote: >> Ok, I'm using qmi in kernel 4.9 on LEDE now. So far 1 hour and no >> disconects. > > > > Seems to have the same issue using LEDE kernel 4.9 in QMI it will stay up > for an hour and then do this. > > > Tue Feb

Re: glib-mkenums error for ublox plugin

On Tue, Feb 14, 2017 at 7:51 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > Could you apply the attached patch and retry? It could just be the > order of the files generated, because the .c file depends on the .h > file and they were requested in the other way in BUILT_S

Re: Cinterion plugin (in)compatibilities

Technology act; >> > > Still reporting as invalid reply, I'm afraid. Please retry with the attached patch and let me know if you have any issue in the ^SMONG response parsing. -- Aleksander https://aleksander.es From d118f14a67402bb17de5acdd8748856a5496c050 Mon Sep 17 00:00:00 20

Re: glib-mkenums error for ublox plugin

On Wed, Feb 15, 2017 at 9:49 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > Worst case, we just add a custom mkdir step in those enums generation rules. Could you test the attached patch? -- Aleksander https://aleksander.es From 56d0c49dc80a66bb606b5ecea94c1ecdbb046ed6 Mon

Re: glib-mkenums error for ublox plugin

Hey, >> The issue is really related to the ublox subdir not existing before >> calling glib-mkenums. In my setup, the directory is created before >> glib-mkenums runs, though. What build tools are you using? i.e. which >> automake version? >> > > automake is version 1.15 > Possibly to do with

Re: Modem creation/startup order

On Wed, Feb 15, 2017 at 10:00 AM, Colin Helliwell <colin.helliw...@ln-systems.com> wrote: >> On 14 February 2017 at 17:28 Dan Williams <d...@redhat.com> wrote: >> >> On Tue, 2017-02-14 at 15:16 +, Colin Helliwell wrote: >> >> > > On 14 Febru

Re: Cinterion plugin (in)compatibilities

On Mon, Feb 13, 2017 at 2:56 PM, Colin Helliwell wrote: >> > For simplicity, I’d begun my exploration of MM using the Generic plugin. My >> > design has a choice of two Cinterion modems (BGS2 and EHS5), though they >> > don’t have much of the functionality

Re: crash in mm-device.c:modem_valid

On Sat, Feb 11, 2017 at 1:07 AM, Ben Chan wrote: > I encountered a crash in mm-device.c:modem_valid:345 where 'self->priv' > seemed invalid, but 'modem' looked fine. As there is no code to clear the > "notify::base-modem-valid" signal in MMDevice, I think MMDevice currently

Re: Handling received SMS

On Mon, Feb 13, 2017 at 3:37 PM, Colin Helliwell wrote: >> > >> > > All I'm seeing in the logs is "+CIEV: message,1". >> > > Checking back through the logs for unsolicited event setups, I also see >> > > [src/mm-broadband-modem.c:5888] >> > >

Re: Handling received SMS

On Mon, Feb 13, 2017 at 9:13 AM, wrote: > All I'm seeing in the logs is "+CIEV: message,1". > Checking back through the logs for unsolicited event setups, I also see > [src/mm-broadband-modem.c:5888] set_messaging_unsolicited_events_handlers(): > (ttyMux0)

Re: [PATCH] device: disconnect signal handlers when modem object removed

On Mon, Feb 13, 2017 at 7:05 PM, Ben Chan wrote: > thanks. lgtm. The g_signal_handler_is_connected check in clear_modem seems > unnecessary though? Yeah, we don't really remove the signal handler in any other place, so should be unnecessary. Will fix that before pushing.

Re: How to issue an "ifup broadband" when this is logged

On Thu, Feb 9, 2017 at 10:55 PM, lspwaterproofing wrote: > Also I'm using the same exact modem in the same location on Ubuntu 16.04 > using ModemManager with all the same settings and it stays up for hours with > no interruptions. So its not a network issue. Ok, the

Re: [PATCH] libmm-glib: set clear func by default in the MMModemPortInfo array

On Thu, Feb 9, 2017 at 3:54 PM, Piotr Figiel wrote: > I tested your patch and the reported issue doesn't appear any longer. > It all looks good and certainly better (more glib-style) than my initial > implementation. Although I wonder if this doesn't ever collide with >

Re: Modem creation/startup order

On Thu, Feb 16, 2017 at 1:31 PM, Colin Helliwell wrote: > > I'm back on this, trying to do it properly. I've removed by mod to > mm-plugin.c, and added a udev tag > > G_MODULE_EXPORT MMPlugin * > mm_plugin_create (void) > { > static const gchar *subsystems[] =

Re: glib-mkenums error for ublox plugin

On Thu, Feb 16, 2017 at 2:24 PM, Colin Helliwell wrote: >>> (By the way - the configure summary is reporting "ModemManager 1.7.0"?) >> >>That is normal. The version in git master is 1.7.x; the next stablemajor >>release will be 1.8.0. > > Is there a schedule for

Re: Updated plugin not being found

On Thu, Feb 16, 2017 at 12:23 PM, wrote: > I’m doing quite a bit of debug of a plugin, and simply copying the new .so > into the plugins directory. Oh, and also rebuilding the ModemManager now and > again. > > This did work a few times, but I’ve got a situation

Re: Cinterion plugin (in)compatibilities

On Thu, Feb 16, 2017 at 11:22 AM, Colin Helliwell wrote: >> > > > > I'm not confident of correctly interpreting the regex in >> > > > > smong_query_ready() (let alone fixing it properly!), but I wonder if >> > > > > the SMONG problem is that it's getting an

Re: Locking MM to 4g only

On Thu, Feb 16, 2017 at 4:29 PM, Russ Westrem wrote: > Im am trying to lock to 4g only. > > Modes| supported: 'allowed: 2g, 3g, 4g; preferred: none' >|current: 'allowed: 2g, 3g, 4g; preferred: none' > > > > root@LEDE:~# mmcli -m 0

Re: How to issue an "ifup broadband" when this is logged

On Wed, Feb 15, 2017 at 9:00 PM, Russ Westrem wrote: > Is there anything in the modemmanager scripts that I could change to have it > ignore the deregistered modem and stop it from removing it from the bearer. > I have a feeling these deregistrations happen often but

Re: Modem creation/startup order

On Wed, Feb 15, 2017 at 4:16 PM, Colin Helliwell <colin.helliw...@ln-systems.com> wrote: >> On 15 February 2017 at 15:07 Colin Helliwell >> <colin.helliw...@ln-systems.com> wrote: >> >> > On 15 February 2017 at 14:11 Aleksander Morgado

Re: Modem creation/startup order

On Wed, Feb 15, 2017 at 10:46 AM, Colin Helliwell wrote: >> > I get the feeling its written with nearly-but-not-quite up to date >> > methods, or just different ones. Certainly it's not easy to compare >> > against USB-based drivers. From what I can make out, the

Re: OpenWRT - MC7455 (MBIM) not working as expected.

On Tue, Jan 24, 2017 at 2:30 PM, Bjørn Mork wrote: >> Aleksander - have you had the mc7455 working in OpenWrt in MBIM? > Yes; I had it working, although I should check which kernel version I was running. Will do that later today. > Just a side note: It might work without the

Re: Modem creation/startup order

On Mon, Feb 13, 2017 at 2:05 PM, Colin Helliwell wrote: >> > I’ve got two ports whitelisted for use by MM. What determines which one of >> > them will be ‘Modem/0’ ? >> >> Just the first modem that finishes first probing all ports. >> >> > Is there a way to get MM

Re: [PATCH v2 2/2] kernel-device: use device sysfs if physdev sysfs isn't available

On Wed, Mar 1, 2017 at 3:59 AM, Ben Chan wrote: > find_device_by_physdev_uid() expects a non-NULL UID of the physical > device. However, mm_kernel_device_get_physdev_uid() could potentially > return NULL on MMKernelDeviceUdev if find_physical_gudevdevice() in >

Re: Modem not connecting on Ubuntu 16.04 (whereas it did on Ubuntu 14.04)

On Tue, Aug 30, 2016 at 8:56 AM, Ajay Garg wrote: > The reason turned out that I had disable USB-3.0 support in BIOS. > When I turned it on, the modem started connecting in both 14.04 and 16.04. > > However, in 14.04 the "wwan" interface appears fine (and after running >

Re: [PATCH v2] broadband-modem-huawei: implement Modem.Signal extended signal info interface

On Tue, Aug 30, 2016 at 10:32 PM, Dan Williams wrote: > Implement the detailed signal info interface for some Huawei 3GPP modems. > Some very minor thing, commented below. Other than that looks good to me, go merge it :) > --- > plugins/huawei/mm-broadband-modem-huawei.c

Re: Latest ModemManagaer and libqmi packages for raspberry-pi?

On Wed, Sep 7, 2016 at 6:42 AM, Ajay Garg wrote: > Are there PPAs for Raspberry-Pi. on similar lines as > > https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty > https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-xenial > > > If not, is

ANN: ModemManager 1.6.2 released

Hey hey, This is a new release in the ModemManager 1.6.x series. Overview of changes in ModemManager 1.6.2 --- * Huawei: fix setting up unsolicited voice messages * Blacklist: ignored u-blox GPS/GLOSNASS USB dongle and some new Arduinos. * ZTE: avoid

ANN: ModemManager 1.4.16 released

Hey hey, This is a new release in the ModemManager 1.4.x series. Overview of changes in ModemManager 1.4.16 --- * Build fixes for GCC 6. * MTK: add support for the D-Link DWM-156 A3. * Icera: deactivate context before authentication. * ZTE: avoid

Re: [PATCH 5/5] core: allow building and running without udev

On Fri, Sep 30, 2016 at 6:10 AM, Dan Williams wrote: >> The udev rule files are kept in place, and a simple custom parser is >> provided >> which preloads all rules in memory once and then applies them to the >> different >> kernel objects reported via ReportKernelEvent(), e.g.

Re: [PATCH v2] huawei: add basic support for ME909u-521

Hey Stefan, Patch looks much better, but see some additional comments below. On Fri, Sep 30, 2016 at 6:46 PM, Stefan Eichenberger wrote: > The ME909u-512 does theoretically support the DHCP feature over AT but if > this is done right after the NDISDUP command, it seems that

Re: [PATCH 2/2] telit: add GE910 #PORTCFG layouts

On 05/10/16 16:43, Daniele Palmas wrote: > GE910 family supports #PORTCFG layouts different than HE910 > family ones. > > This patch properly tags GE910 ports according to Telit document > "GE910 Family Ports Arrangements, 1vv0301049" Pushed to git master and mm-1-6, thanks. > --- >

Re: [PATCH 1/2] telit: add udev rules for supporting GE910

On 05/10/16 16:43, Daniele Palmas wrote: > This patch adds the udev rules for supporting GE910 (PID 0x22) Pushed to git master and mm-1-6, thanks. > --- > plugins/telit/77-mm-telit-port-types.rules | 4 > 1 file changed, 4 insertions(+) > > diff --git

New 'u-blox' plugin (v2)

Hey Dan & everyone, After Dan's review, I've updated the branch implementing support for the ublox devices with the following changes: * +CGCONTRDP parser is generic, and now supports both formats (pre and post TS 27.007 v9.4.0) * Added some additional comments to explain how the static IP

Re: Running ModemManager without udev (v2)

On Thu, Sep 29, 2016 at 3:38 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > [PATCH 1/5] core: allow identifying devices by a user-provided 'uid' > [PATCH 2/5] core: new kernel device object instead of an explicit... > [PATCH 3/5] core: allow disabling auto-scan and noti

Re: [PATCH] huawei: handle some weird SYSCFG acquisition orders

On Tue, Oct 4, 2016 at 10:48 PM, Dan Williams wrote: > (ttyUSB2): --> 'AT^SYSCFG?' > (ttyUSB2): <-- > '^SYSCFG:14,2,400380,1,2OK' > couldn't load current allowed/preferred modes: 'No SYSCFG combination > found matching the current one (14,2)' > > 14,2 means "WCDMA-only;

Re: [PATCH 04/10] api: new ReportKernelEvent() api method to report kernel device addition/removals

On Mon, Aug 29, 2016 at 11:25 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: >> In the API docs it talks about USB vid/pid, but MM does support at >> least one PCI-native device; the Option Nozomi. SDIO also uses 16-bit >> vid/pid, though I'm not sure why anyon

Re: Preventing MM from probing specific serial ports on supported modems

On Wed, Sep 21, 2016 at 1:16 PM, Bjørn Mork wrote: >mm_plugin_create_modem(): (tty/ttyUSB1): port is blacklisted > > message in there, but that's way after the probing is finished. So it > looks like the blacklisting is applied, but doesn't affect the probing. > Which makes it

Re: [PATCH] huawei,udev: fix udev rule

On Thu, Aug 25, 2016 at 4:57 PM, Stefan Eichenberger wrote: > Patch a66871a2876be2236f634ff6b5e59d20de1ce5df introduced a single usb > system check but this does not work on my system. It seems that the > check where GOTO is executed is applied per device. Subsystem is then >

Re: [PATCH] Add blacklist udev rule for U-blox7 GPS/GLOSNASS USB dongle.

Hey, On Fri, Aug 26, 2016 at 8:38 PM, Tabor Kelly wrote: > Hello, > > Please find attached my patch to keep ModemManager from doing anything with > the U-blox7 GPS/GLOSNASS USB dongle. > Thanks, pushed to git master, mm-1-6 and mm-1-4. -- Aleksander

Re: [PATCH 5/5] core: allow building and running without udev

On Fri, Sep 30, 2016 at 9:29 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: >>> The udev rule files are kept in place, and a simple custom parser is >>> provided >>> which preloads all rules in memory once and then applies them to the >>>

Re: Cant connect to network on thinkpad x240

On Fri, Sep 30, 2016 at 3:24 PM, Alfredo Palhares wrote: > ModemManager[31417]: Simple connect started... > ModemManager[31417]: PIN: > ModemManager[31417]: Operator ID: unspecified > ModemManager[31417]: Allowed roaming: yes > ModemManager[31417]: APN:

Re: Problems connecting with thinkpad x260 Sierra module

On 26/10/16 15:47, Alfredo Palhares wrote: > - > Status | lock: 'unknown' >| unlock retries: 'unknown' >| state: 'failed' >| failed reason: 'sim-missing' The SIM card isn't detected properly it seems? When in

Re: Preventing MM from probing specific serial ports on supported modems

On Tue, Nov 8, 2016 at 2:23 PM, Bjørn Mork wrote: > Totally unrelated: I had to disable the 'test-service-generic' test > while bulding this. Couldn't figure out why it failed or how to debug > the failure... Yeah, I need to debug that. I don't have the issue in my desktop pc but

Re:

Hey, On Wed, Nov 9, 2016 at 10:27 AM, Thinh Nguyen wrote: > I’m looking for an example to get signal strength of 3G use Dbus API to > communication with Modem manager. My problem is how to list all modem device > (/org/freedesktop/ModemManager1/Modems/#) You can

Re: Preventing MM from probing specific serial ports on supported modems

On Wed, Sep 21, 2016 at 2:29 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > On Wed, Sep 21, 2016 at 1:16 PM, Bjørn Mork <bj...@mork.no> wrote: >>mm_plugin_create_modem(): (tty/ttyUSB1): port is blacklisted >> >> message in there, but that's way a

Re: PolicyKit authorization error

On Thu, Nov 10, 2016 at 7:49 PM, matthew stanger wrote: > > I can provide a little patch, though I don't know if it's of value to the > community as I don't think it's best practice to not have your boot order > wrong. That being said would it make sense in

Re: Modem not getting detected

On Wed, Nov 2, 2016 at 10:39 PM, Rakesh wrote: > I have a "Sierra Wireless AirCard 313U LTE Mobile Broadband Modem " , when > I do lsusb it enumerates as Air Prime Sierra card. > > When I use modem manager "mmcli -L" the output is 'no modems are found" Could you get

Re: incorrect 'locked' status

On Wed, Oct 19, 2016 at 1:51 AM, David McCullough wrote: > I can confirm it works fine with your patch applied, Ok, thanks, will push it to git master and mm-1-6 then. Cheers! -- Aleksander https://aleksander.es ___

Re: incorrect 'locked' status

not initialized", which we translate to UNKNOWN. In this case, we should have provided the state of PIN1 and ignore the state of PIN2. Can you test the attached patch? -- Aleksander https://aleksander.es From 86f2ac1e660af39bc51d5521666ad5a2b7df2345 Mon Sep 17 00:00:00 2001 From: Aleksa

Re: [PATCH] Telit: Optimized supported and current band code

On 20/10/16 11:33, Carlo Lobrano wrote: > In place of two slightly different regexes for 2g/3g and 2g/3g/4g modems > we now use only one regex with conditional patterns for both supported > and current Bands detection. > > Adding also minor fix in test code Pushed to git master and mm-1-6,

Re: Differences in behaviour of old and new units of MC8090

On Thu, Oct 20, 2016 at 6:20 AM, Ajay Garg wrote: > ===ESTABLISHING CONNECTION=== > > > mmcli -m 0 --create-bearer="apn=airtelgprs.com,user=,password=" > Successfully created new bearer in modem: > /org/freedesktop/ModemManager1/Bearer/0 > [OK]

New 'aleksander/disable-ifaces' branch ready for review

Hey everyone, I've pushed to git a new 'aleksander/disable-ifaces' branch, which allows disabling the different modem feature interfaces one by one: https://cgit.freedesktop.org/ModemManager/ModemManager/log/?h=aleksander/disable-ifaces E.g. a custom build of ModemManager may be done with the

Re: [PATCH 1/1] broadband-modem-qmi: add QMI_PROTOCOL_ERROR_NOT_SUPPORTED case for pin status checking

On 25/10/16 14:50, Daniele Palmas wrote: > Telit LE922A does not like the legacy way for checking pin status, but > instead of returning QMI_PROTOCOL_ERROR_INVALID_QMI_COMMAND, it returns > QMI_PROTOCOL_ERROR_NOT_SUPPORTED, making the modem not to be fully > initialized. > > This patch adds

Re: Huawei ME906s: mbim transaction timeout

On Mon, Nov 14, 2016 at 3:06 PM, Andreas Fett wrote: > just to give you an update on this: > On 02/11/16 15:15, Andreas Fett wrote: >> for certain SIM cards (Vodafone Germany) and in certain Systems (ie. >> Lenovo t460s) ModemManager seems to have trouble detecting the

Re: Fallback MBIM on custom plugin

On Fri, Nov 11, 2016 at 3:26 PM, Carlo Lobrano wrote: > I'm working on a MBIM modem with GPS capabilities and my understanding is > that, since there is no service to access GPS through MBIM protocol, for the > gps APIs the ModemManager falls back to the generic broadband

Re: Fwd: Cinterion plugin patch

Hey Matthew, On Wed, Nov 23, 2016 at 10:28 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > Great work! it looks really good now, although there are some small > things that could still be fixed. Let me prepare a branch with your > patch and I'll include some additional

Re: Fwd: Cinterion plugin patch

On Sun, Nov 27, 2016 at 4:27 AM, matthew stanger wrote: > Sorry I sent that last email a little prematurely, was still targeting my > email client and ctrl-entered for another window. You can disregard that > second comment, I see what you did for IP config. Last little

Re: Fwd: Cinterion plugin patch

On Sun, Nov 20, 2016 at 7:26 PM, matthew stanger wrote: > Ok, so clearly I'm not as fast as I wish, but another patch never the less. > This should be pretty close but I'll keep at it if there are any changes > still needed so let me know :). Here are the changes since the

Re: Fwd: Cinterion plugin patch

On Thu, Nov 24, 2016 at 6:04 PM, matthew stanger wrote: > Uggg I am very sorry but that patch is not the right patch. It has none of > the fixes I worked on :(. Very sorry and terribly embarrassed. As soon as I > get back to my home computer I will mail out the correct one.

Re: Sierra EM7305 - No Network connection

On Wed, Nov 16, 2016 at 2:53 PM, Harald Jung - ECOS Technology wrote: > > So I switched it to bConfigurationValue=1 and mbim. Looks like it gets de-registered during the connection attempt? Nov 16 15:43:45 ThinClient ModemManager[2240]: Session ID '0': deactivated (IP

Re: Preventing MM from probing specific serial ports on supported modems

On Tue, Nov 8, 2016 at 5:42 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: >> Totally unrelated: I had to disable the 'test-service-generic' test >> while bulding this. Couldn't figure out why it failed or how to debug >> the failure... > > Yeah, I ne

ANN: ModemManager 1.6.4 released

Hey hey, This is a new release in the ModemManager 1.6.x series. Overview of changes in ModemManager 1.6.4 --- * Blacklist: ** Ignored new Infineon flashloader devices. ** Ignored Sigma Sport docking stations. * Core: ** USSD: don't rely on

ANN: ModemManager 1.4.18 released

Hey hey, This is a new release in the ModemManager 1.4.x series. Overview of changes in ModemManager 1.4.18 --- * Blacklist: ** Ignored new Infineon flashloader devices. ** Ignored Sigma Sport docking stations. * Core: ** USSD: don't rely on

Re: Fwd: Cinterion plugin patch

Hey! This looks much much better :) See comments next, in no particular order. On Mon, Oct 24, 2016 at 7:13 AM, matthew stanger wrote: > Here is finally the update... to the above code reviewed patch. A big thank > you Dan and Aleksander for the detail in the review it was

New 'u-blox' plugin (v3)

Hey Dan & everyone, This is the 3rd update on the 'aleksander/ublox' branch, with this additional changes done after Dan's last review: * Recovered the original DENIED registration state logic. * Implemented a generic +CFUN parser and then included plugin-specific parsers for the ublox,

Re: New 'u-blox' plugin (v2)

On Tue, Oct 11, 2016 at 10:13 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: >>> modem-helpers: new helper to parse +CESQ response into MMSignal >> objects >> >> There's some small differences from the way I implemented it in the >> Huawei sig

Re: New 'u-blox' plugin (v2)

On Tue, Oct 11, 2016 at 10:13 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: >>> ublox: new +UBANDSEL? response parser >> >> +dupstr = g_strdup (mm_strip_tag (response, "+UBANDSEL:")); >> +i = strlen (dupstr); >> +while (i >

Re: New 'u-blox' plugin (v3)

On Wed, Oct 12, 2016 at 5:29 PM, Dan Williams wrote: >> This is the 3rd update on the 'aleksander/ublox' branch, with this >> additional changes done after Dan's last review: >> >> * Recovered the original DENIED registration state logic. >> * Implemented a generic +CFUN parser

Re: [URGENT] Regressions in latest QMI-related packages

On Thu, Oct 13, 2016 at 7:53 AM, Ajay Garg wrote: > Looking at > https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty, it > seems that the packages were uploaded in June/July, well before my testing > in August. > That is what I was going to say; that

Re: [URGENT] Regressions in latest QMI-related packages

On Thu, Oct 13, 2016 at 12:24 PM, Ajay Garg wrote: > Where can I get the latest "official" versions of modem-manager, libqmi etc. > for Ubuntu-14.04.3? There isn't any official binary build of the latest stable versions for Ubuntu 14.04; you should get the source tarballs

Re: [PATCH 1/1] telit: fix supported and current bands query with GE910

On 10/10/16 14:42, Daniele Palmas wrote: > GE910 is a 2g only modem and when queried for bands it returns > only a 2g set of bands: > > --> 'AT#BND=?' > <-- '#BND: (0-3)OK' > > Current regex fails, since it considers the 3g bands block mandatory. > > A similar problem happens for current bands.

Re: New 'u-blox' plugin (v2)

Hey hey, Thanks again for the review :) >> >> * Added support for the new CSFB related registration state values. > > The DENIED handling looks like it changed: > > +/* Denied? */ > +if (ctx->cs == MM_MODEM_3GPP_REGISTRATION_STATE_DENIED || > +ctx->ps ==

Re: [URGENT] Regressions in latest QMI-related packages

On Mon, Oct 17, 2016 at 5:13 AM, Ajay Garg wrote: > > Please find the debug-logs-file for ModemManager attached, plus the > attempt-logs for starting NetworkManager as per the link. > > > Kindly let know what is the issue, and what steps I need to follow next to > nail the

Re: Are the commands to fetch IMEI/IMSI integrated in mmcli?

On Mon, Oct 17, 2016 at 8:34 PM, Ajay Garg wrote: > https://mail.gnome.org/archives/networkmanager-list/2011-September/msg00137.html > seems to be quite an old thread, but the following two are NOT listed in > SIM-options in the Modem-manager that I currently use (neither

Re: huawei signal info patch by Dan

On Tue, Dec 6, 2016 at 6:53 PM, Dan Williams wrote: > I've cherry-picked that and other signal-related stuff (+CESQ support) > to the dcbw/mm-1-6-signal branch. We'll see what Aleksander says about > merging that to MM 1.6. I'm ok with that. -- Aleksander

Re: huawei signal info patch by Dan

On Thu, Dec 8, 2016 at 11:58 PM, Mats Berndtsson wrote: > pi@plutten:~ $ sudo mmcli -m 0 --signal-get > > /org/freedesktop/ModemManager1/Modem/0 > - > Refresh rate: '5' seconds > mmcli: symbol lookup error: mmcli: undefined symbol:

Re: GPS blocked by enable

On Fri, Dec 9, 2016 at 11:04 PM, matthew stanger wrote: > I was just wondering if I could get the background on why the GPS flow > requires enable. It's causing us pain with unit's that don't have a SIM > inserted but which would still want to collect GPS data. Since we can't

[RFC] stanger/cinterion branch

Hey Dan, Matthew and others, I've pushed a couple of additional commits to the stanger/cinterion branch; main changes w.r.t to the last branch suggestion are: * Avoid the predefined CIDs (and therefore use the generic CID selection mechanism). * Fix connection setup when auth settings

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

On Fri, Jan 13, 2017 at 10:12 PM, Martin MOKREJŠ wrote: > thank you Alexander for clarification, I infer there is something wrong > with my cdc-wdm then. Isn't there anything interesting in the NM debug logs I > sent to the list already? This is the only interesting thing

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

On Sat, Jan 14, 2017 at 1:16 AM, Martin MOKREJŠ wrote: > Anyway, there are a few lines about the cdc-wdm0 but does not seem to be > much verbose. A few AT commands failed but on the ttyUSB1. Yeah, no AT command was correctly replied in the cdc-wdm interface so we couldn't

Re: [systemd-devel] WebUSB

On Wed, Jan 11, 2017 at 2:21 PM, Christer Weinigel wrote: >> Actually, that sounds like a very good compromise. I remember my own >> struggles 3-4 years ago when I had to get a device working properly on >> ChromeOS and Ubuntu, where the firmware had to handle that the

Re: [PATCH] telit: use g_assert instead of g_assert_true / g_assert_false

On 12/01/17 07:29, Ben Chan wrote: > `g_assert_true' and `g_assert_false' are defined in glib 2.38 or later. > The minimum glib version currently required by ModemMamanger is 2.36. > While `g_assert_true' and `g_assert_false' may be preferred over the > more generic `g_assert', it seems like

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

g, at least we would start the ball rolling to improve the docs. > > Aleksander Morgado wrote: >> On Thu, Jan 12, 2017 at 3:49 PM, Martin MOKREJŠ <mmokr...@gmail.com> wrote: >>> # mmcli --connect -m /org/freedesktop/ModemManager1/Modem/0 >>> error: no bear

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

Hey, >> >> I am a little bit surprised that the modem uses the ppp-interface in your >> case. When I read your logfiles right, then you have a device which is sold >> under the name "Speedsick LTE V" in Germany. > > How do you achieve non-PPP option in nm-applet? Whenever I select "Mobile >

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

On Thu, Jan 12, 2017 at 3:49 PM, Martin MOKREJŠ wrote: > # mmcli --connect -m /org/freedesktop/ModemManager1/Modem/0 > error: no bearer was specified --connect is a bearer action, you need to pass a bearer object path, not a modem object path. > # mmcli --list-bearers -m

<    1   2   3   4   5   6   7   8   9   10   >