Hey Peter,
> >> # AWC EM12-AW
> >> # ttyUSB0 (if #0): QCDM/DIAG port
> >> # ttyUSB1 (if #1): GPS data port
> >> # ttyUSB2 (if #2): AT primary port
> >> # ttyUSB3 (if #3): AT secondary port
> >> ATTRS{idVendor}=="2c7c", ATTRS{idProduct}=="0512", ENV{.MM_USBIFNUM}=="00",
> >> SUBSYSTEM=="tty",
> >> We have created the issue in Gitlab and uploaded all the logs that related.
> >> https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/issues/81
> >>
> >> Please contact us if there is still anything missing.
> >> Waiting for your kind reply. Thanks!
> >>
> >
> > You missed to reply to my
Hey,
> ACTION!="add|change|move|bind", GOTO="mm_awc_port_types_end"
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="2c7c", GOTO="mm_awc_port_types"
> GOTO="mm_awc_port_types_end"
>
> LABEL="mm_awc_port_types"
>
> SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*",
>
Hey,
>
> We have created the issue in Gitlab and uploaded all the logs that related.
> https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/issues/81
>
> Please contact us if there is still anything missing.
> Waiting for your kind reply. Thanks!
>
You missed to reply to my question before:
Hey Elias,
>
> I have a Librem 5 phone with a BroadMobi BM818-E1 modem. The operating
> system is PureOS 10 with ModemManager 1.14.12. Making phonecalls works
> most of the time, but sometimes it does not work and I have been trying
> to figure out why.
>
> Having added the ModemManager --debug
>
> I can ge wds service connected, but still can't bind port to rmnet_data0,
> some more debugging needed.
>
QMI DPM open missing maybe?
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/235
--
Aleksander
https://aleksander.es
Hey,
>
> Thanks for your kind reply.
> As you have mentioned, the issue we met has been fixed in commit
> 16383670dcb471d6a5b802a9cca1e2a24eb86de5, but we failed to find this commit
> in your gitlab.
> Can you please give us a link about this?
>
Not sure where you looked for it :)
Hey
>
> I have met some issues about QMI CID leaks when using Quectel's modem with
> modem manager, and luckily I found some comments about the exactly some issue
> on the Mail Archive.(Re: QMI CID leaks (mail-archive.com)
>
> In this post, it is said that "it looks like this could be fixed
Hey
On Tue, Dec 14, 2021 at 10:42 PM Bruce A. Johnson
wrote:
>
> I wanted to clone the repository, and I'm getting a 504 error for
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager, the
> address shown for the development repository in the ModemManager product
> page,
Hey
>
> Attached are my log files from MM and qmi-proxy.
>
> This time when I set the preferred mode to 2G via MM, the sequence from
> AT-cmd did not change (first 4G then 2G). And after setting to 4G, the
> sequence from modem changed to: first 2G then 4G. See my test sequence below.
>
>
> #
Hey
On Wed, Dec 1, 2021 at 7:34 PM Bushman, Jeff wrote:
>
> I have attached the modem manager debug logs. Search for "simple connect".
> One odd thing I noticed was a log message about "reseting expected kernel
> data format to 802.3 in data interface 'wwan0'" which is not correct. The
>
Hey Ralf,
>
> we intend to use the JSON output of mmcli in one of our projects, e.g. we'd
> like to poll the current state of the modem. Our current problem is that we
> don't know which values could possibly be returned ("registered",
> "searching", etc.). Is there any further description of
Hey,
> >> However, and by all means convince me otherwise, I could still see
> >> the fall though case to PPP happening when things are not quite ready
> >> with the USB stack, QMI driver, etc. And that's a real problem for me.
> >
> > Here we're relying on two things: the kernel exposes all
Hey,
>
> Aleksander Morgado wrote on Fri, Dec 03, 2021 at 11:02:12AM +0100:
> > I'll give it some time before a new release I think; this issue should
> > affect openwrt only, and there was no bump to 1.18.4 there yet.
>
> I've missed why these udev rules should only
Hey Dominique
> > > > Could you please test the following single patch on top of 1.18.4?
> > > > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/700
> > >
> > > I ran through a couple of test cases and this appear to be doing the right
> > > thing. Thanks.
> > >
> >
Hey,
> > The udev rules themselves are robust. The problem may be the time
> > required by the module to expose the ports in the system, and the time
> > required by the module to actually reply anything in those ports.
> > Those two last things are handled by timeouts in ModemManager, and if
> >
> >>> Could you please test the following single patch on top of 1.18.4?
> >>> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/700
> >>>
> >>
> >> I ran through a couple of test cases and this appear to be doing the right
> >> thing. Thanks.
> >>
> >
> > Thanks for
Hey
> > Could you please test the following single patch on top of 1.18.4?
> > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/700
> >
>
> I ran through a couple of test cases and this appear to be doing the right
> thing. Thanks.
>
Thanks for testing, will merge
Hey Peter,
> > > Wondering, would you be able to also test 1.18.4 but with these 2
> > > changes reverted? The regex related fix was a big one, maybe it broke
> > > something else.
> > >
> > > 2beae71a6 kerneldevice,generic: simplify DEVPATH matching logic
> > > 1bd70df8a kerneldevice,generic:
Hey Peter,
> > Wondering, would you be able to also test 1.18.4 but with these 2
> > changes reverted? The regex related fix was a big one, maybe it broke
> > something else.
> >
> > 2beae71a6 kerneldevice,generic: simplify DEVPATH matching logic
> > 1bd70df8a kerneldevice,generic: input pattern
Hey,
> 2. Then I set the priority to 2G. Both MM and AT-cmd shows the 2G has now
> priority.
>
> # mmcli -m 1 --set-allowed-modes='2g|4g' --set-preferred-mode='2g'
> successfully set current modes in the modem
> #
> # mmcli -m 1 --command="AT+QCFG=\"nwscanseq\""
> response: '+QCFG:
Hey Jeff,
> I'm running a Sierra Wireless MC7455 modem with SWI9X30C_02.32.11.00 r8042
> CARMD-EV-FRMWR2 firmware. Using ModemManager 1.18.2 on Ubuntu 20.04.
>
> I can get the modem to connect using mmcli -m 0 --simple-connect=. when the
> modem is in MBIM mode.
> I can get the modem to connect
Hey,
> I have another question regarding my SIM-EAP interface. Testing has been
> going well however I noticed one of the methods of my interface has an
> invalid address (i.e. either (nil) or 0x2) despite having implementation. I
> noticed I'm getting this warning which may be responsible for
Hey
>
> I'm observing that in few cases (MM 1.18.2) that --simple-connect returns
> immediately in QMI mode without waiting for the timeout. No such premature
> exit is observed in MBIM i.e. MBIM mode works fine.
>
> It's easily reproducible in my setup.
>
> 1] Successfully connect bearer first
Hey
>
> On Sun, Nov 28, 2021 at 6:50 PM Aleksander Morgado
> wrote:
>>
>> Since MM 1.18.4 the FCC unlock operation needs to be explicitly
>> configured by the user, did you do that already, or is this issue
>> happening even after doing that?
>> https:/
Hey,
> I just got a new Lenovo X1 Extreme Gen 4 that comes with a Snapdragon X55
> WWAN modem by Foxconn. I'm running Arch Linux w/ kernel 5.15.5, ModemManager
> 1.18.4, libmbim 1.26.2 and libqmi 1.30.2.
>
> The X55 seems to be supported for older firmware versions (<= v48?) after
> setting up
Hey hey,
This is the second bugfix release in the 1.18.x series, built from the mm-1-18
branch.
ModemManager 1.18.4
---
* A new FCC unlock operation management via external scripts is introduced,
which will avoid to automatically unlock FCC locked
Hey Carlos,
>
> I have been testing a Quectel RG50xQ module with ModemManager 1.16.6 and
> everything works great, but I have noticed that my device gets an IP
> configuration with a subnet that can be /28, /29, /30 depending on the IP,
> and sets a default gateway. This tests are within a
Hey Sven,
>
> Where would I have to change the Quectel plug-in in order to use a DHCP
> bearer if there is a net interface (ECM) associated with a modem. Currently,
> a PPP bearer is created even if a net interface is available. This is for a
> BG95 modem which comes with a ECM mode.
>
I'm
Hey,
>
> I am trying to debug the reset sequence of my modem (I've posted today
> a separate message about this).
>
> I was wondering if there is a way to trace the communication between
> MM and the device, or perhaps between libqmi or the device to output
> the content and translation of the
Hey,
>
> I'm resetting the modem (SIMCOM_SIM7600G-H) with mmcli (mmcli 1.16.10)
>
> The modem status was fully connected before running:
>
> $ mmcli -m 0 --reset
> successfully reseted the modem
>
> After the reset, the device does not connect anymore, and only power
> cycling put things back to
Hey,
> I'm trying to check if my APN supports IPv6. I'm using MM 1.16.10 with
> the SIMCOM SIM7600G-H.
>
> mmcli -m 0 shows this:
> IP | supported: ipv4, ipv6, ipv4v6
>
> and mmcli -m 0 -b 0 shows this:
> Properties |apn: myapn
> |
Hey,
> Hi Aleksander,
>
> (gmail WebUI, but I'll try to do the quoting in a sane way!)
>
It's possible, I do it every day :D
> > > Can I force the Simtech plugin to be used, or would it make no sense
> > > because of the single serial port? Should it be claimed and usable by the
> > > AT
Hey,
>
> New enough QMI and MBIM modems have messages to gather all the data for each
> connected SIM. It's possible that the message is simply not supported by your
> modem, since 1.18.2 should be new enough such that the MBIM implementation of
> load_sim_slots, etc. is available.
>
Let's
Hey,
>
> I've just bought one of these
>
> https://www.waveshare.com/SIM7600E-H-4G-hat.htm
>
> and I'm trying to get it to work with ModemManager using (at the moment) the
> default version available in Raspberry Pi OS (mm 1.14.12). I'm also having
> some trouble convincing meson to build the
Hey all,
A lot of the source files in the libmm-glib library incorrectly had
the GPL text in the beginning of the file instead of the LGPL one.
libmm-glib has always been LGPLv2+ as a whole, and therefore the wrong
text is considered just a bug to fix, not a relicense of any kind.
Fixed here in
Hey,
> thanks for previous response. I've built DBUS and added to my device and
> warning disappeared. Unfortunately, I have another issue, I cannot run
> ModemManager, because there are undefined symbols during plugin load e.g.:
>
> ModemManager[6746]: [1637075895.604641] [filter]
Hey,
On Tue, Nov 16, 2021 at 12:08 AM Bushman, Jeff wrote:
> I’m just getting started with interfacing with the ModemManager via
> mm-glib. I am experimenting with the synchronous SIM slot APIs, and they
> don’t seem to work.
>
> I am running ModemManager 1.18.2 on Ubuntu 20.04 with a Sierra
Hey!
>
> after further investigation i finally found the problem. First of all you are
> perfectly right text/pdu mode is not the issue here. The actual issue was
> that mmcli sends SMS from a file in 8-bit encoding while message text given
> on the command line is send in 7-bit encoding.
Hey!
>
> I was able to find the problem! It turns out I was silly and forgot to set
> GError* error = NULL initially.
>
> Thanks for all the help and explanation :)
Ah! that was an easy fix then :)
--
Aleksander
https://aleksander.es
Hey Florence,
>
> Ah, I see, thanks for the explanation! However the command below still
> returns FALSE for me unfortunately...
> g_dbus_interface_skeleton_export (G_DBUS_INTERFACE_SKELETON (skeleton),
>connection,
>path,
Hey,
>
> I am writing an application that handles (multiple) LTE modems (currently
> using Sierra EM7455, but it is intended to be generic). The application makes
> calls to libmm-glib (version 1.12) to handle various modem actions.
>
> To reset the modem it calls mm_modem_reset_sync. The call
Hey,
> I am working on embedded device with linux. I’ve successfully built Modem
> Manager with my cross compile libraries/image. Device does not contain DBUS.
> I’ve installed built Modem Manager to device but there is warn message:
>
>
>
> ModemManager --debug
>
> ModemManager[19905]:
Hey,
>
>> Is that "self" in the g_object_get() the same as in the
>> g_dbus_interface_skeleton_export()?
>
>
> Yes, self refers to a a MMIfaceSimEap *. I have a MMsameGdbusSimEap* created
> by the command mm_gdbus_sim_eap_skeleton_new (). However is that not
> different from the
Hey Florence,
> Previously you mentioned the g_dbus_interface_skeleton_export() method to
> export my SIM interface, which I've been attempting to use. However I've been
> running with some issues with it. Currently I call this in my
> mm_iface_sim_eap_initialize method, like so:
>
Hey all,
See https://modemmanager.org/docs/modemmanager/fcc-unlock/
I've been complaining about the FCC unlock procedure since we first
knew about it some years ago. The sad truth is that more and more
laptops are being released these days with FCC locked modules, and
ModemManager should not
Hey,
> No, that's not the problem, if our gateway is also used for receiving SMS we
> can easily do the conversion in software, the problem is that there are
> historical devices (e.g. GSM modems) in use that cannot be replaced.
>
But what I mean here is that just changing the way an SMS is
Hey Ralf,
>
> the issue is not the SMS representation during transport but the
> representation for the recipient. Our business is M2M communication and we
> see older systems that require text mode SMS. As our gateway is not meant to
> support a variety of use-cases disabling PDU mode SMS in
Hey Ralf,
>
> as far as i understand adding a udev tag would basically remove the PDU SMS
> capability from a specific modem.
> Wouldn't it make more sense to add an option to mmcli like
> --smsmode= which would default to ?
>
I don't see it as a property of the SMS message, because if I
Hey,
>
> is there an option to make ModemManager send SMS in text mode? I'm aware that
> PDU mode ist by far preferred but we have to send SMS to an older system that
> is unable to process SMS in PDU mode.
>
For AT based devices, the support for PDU mode is checked with
AT+CMGF=?, and if PDU
> -MM_IFACE_MODEM (self->priv->modem),
> -known_lock,
> -(GAsyncReadyCallback)after_change_update_lock_info_ready,
> -ctx);
> +handle_change_pin_context_free (ctx);
> }
>
> Thanks
> Amol
>
> -Original Message-
> From: Aleksander Morgado
&g
Hey,
On Mon, Nov 8, 2021 at 11:36 AM Amol Lad wrote:
>
> # mmcli -i 1 --change-pin= --pin=1234
> error: couldn't change PIN code in the SIM: 'Timeout was reached'
>
> # mmcli -m 0 --command=AT+CPIN?
> response: '+CPIN: SIM PIN'
>
> So looks like modem is 'really' locked. Btw, which part of
Hey,
> Same problem is observed with Telit LN920 also so I don't this it's a
> firmware error.
They're both Qualcomm modules, it may be an issue in the generic
Qualcomm firmware implementation. I wouldn't think manufacturers touch
the MBIM protocol handling much.
> Also, please note that modem
Hey,
>
>
> If we attempt to change SIM Card PIN when the SIM is in locked state then
> "Timeout is reached" error is reported BUT the PIN is actually changed. Below
> are some details.
>
>
>
> # mmcli -m 0
>
> -
>
> General | path:
Hey all,
As part of
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/456,
I've created a new "main" branch as a copy of "master", and I'll
remove the "master" branch sometime in the next few weeks.
The new "main" branch is already the default one in the repo, so all
MRs
Hey!
> I have a successful internet connection with mmcli, but there is no AT port.
> So I cannot send AT commands.
>
> Hardware | manufacturer: Sierra Wireless, Incorporated
>|model: Sierra Wireless EM9191
>
> System | device:
Hey,
> In general, I think that the way that ublox intended to use the Toby-L2
> does not really match the way that MM works: In its application notes,
> ublox suggest to set the default bearer setting and then just to use the
> already connected context.
> If I map that to MM / NM, that would
Hey!
> I am using ModemManager with u-blox TOBY-L210 for a while now with older
> versions of ModemManager (1.7.x). I did some patches and home-brew code to
> make that combination work.
> I now want to switch to newer versions of MM (1.18), benefit from the good
> work on MM, and do it "the
Hey,
> I have encountered an issue using ModemManager 1.16.8 via dbus.
> In my case there is a need to send periodic AT commands to a Cinterion modem
> to get infos about connection.
> For example AT^SMONI is ok and the response is not empty. However I would
> like to get also the response from
Hey Bruno,
> Has anyone tried the PCIE mode on the newer 5G modems?
Yes yes, I use one almost everyday in my laptop.
> I have tested with both the Quectel RM500Q and the SIMCom 8202G with no
> success.
> The Quectel model is detected by the modemmanager but can't establish
> a connection:
>
>
Hey!
When we're attached to the packet service domain the device will
report which are the agreed uplink/downlink speeds. These values are
known at connection attempt time, and may also be updated during a
connection (e.g. if changing access techs).
With the following merge request, the Bearer
Hey all,
Here's an API update proposal for the 3GPP interface, adding a new
'PacketServiceState' property and a new 'SetPacketServiceState()'
method.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/661
Comments welcome
--
Aleksander
https://aleksander.es
Hey all,
The extended signal information interface only allowed to configure a
fixed polling rate as the method to update the values reported by the
interface properties. E.g. the user could say, please update the
interface properties every 30s. But polling is far from optimal, it
drains battery,
Hey Florence!
>
> I've been creating a DBus interface for the MM SIM object and I have been
> having issues specifically when it comes to exporting the interface. From the
> examples in other files it looks like there is a
> "mm_gdbus_object_skeleton_set_modem_*" generated export function that
Hey!
> > LIBQMI_WITH_MBIM_QMUX is enabled in libqmi and qmicli reports ok. It seems
> > for some reasons modemmanager is not able to read out the bands. Any input
> > regarding this will be helpful.
> >
>
> Currently Telit mbim plugin uses just AT commands for retrieving
> bands: maybe a
Hey,
>
> I just noticed that the wwan ports are listed as virtual too.
>
> ModemManager[15163]: [1633636532.558601] [base-manager] adding port
> wwan0 at sysfs path: /sys/devices/virtual/wwan_hwsim/hwsim0/wwan0/net/wwan0
> ModemManager[15163]: [1633636532.558641] [filter] (net/wwan0) port
>
Hey,
On Mon, Oct 4, 2021 at 3:01 PM Enrico Mioso wrote:
>
> Ok. My idea was to connect to the ::connected signals of each bearer to
> monitor their state.
> To do so, I'm going to keep a list of bearers I am managing, and in my case i
> would like them to be ideally all of the bearers of a
Hey!
>
> Thanks a lot for your (as always) kind answer. I am using libmm-glib! :)
> I am putting some code togeter but I haven't found the "proper" way to do so,
> at least not so far.
>
static void
bearers_updated (MMModem *modem,
GParamSpec *pspec,
Hey!
> I see there is no documented GSignals for bearers addition/removal.
> I understand I probably should get the bearers list and connect
> object-{added,removed} GSignals to it. But I would like to see some code
> snippets, to know the proper prototypes for the handlers.
>
We have the
Hey
> I'm finding that ModemManager crashes when ip-type is ipv4v6 in
> -simple-connect in MBIM mode. After investigation, I found that below seems
> to fix the crash
>
> diff --git a/src/mm-bearer-mbim.c b/src/mm-bearer-mbim.c
> index d509929..bf66c5d 100644
> --- a/src/mm-bearer-mbim.c
> +++
Hey,
>
> I'm testing MM 1.18.2 release and finding that the supported bands and
> current bands are shown empty. I'm using EM7511 modem in MBIM mode in OpenWRT
> framework (with QMI over MBIM enabled). The bands are displayed correctly in
> an older MM release (1.12.6). Please let me know what
Hey,
On Fri, Oct 1, 2021 at 5:52 PM Frederic Martinsons
wrote:
>
> Last try of the day, I built a ModemManager with WITH_NEWEST_QMI_COMMANDS
> enable and things goes pretty well since I got lot of more update than before
> (see log joined)
>
> Looking at the code implied, this is expected
On Fri, Oct 1, 2021 at 5:15 PM Frederic Martinsons
wrote:
>
> I just tested to grow the threasholds_data to have better granularity (I used
> { -90, -80, -70, -60, -58, -56, -54, -52, -50 } ) and like the comment in the
> code said, my modem didn't like is
>
> I got a "couldn't enable signal
Hey
On Fri, Oct 1, 2021 at 3:50 PM Frederic Martinsons
wrote:
>
> Ok thanks for the tips, should I issue a merge request with the modified
> threshold ?
>
Yes please, that would be good.
>
> I my application needs to have a rapid refresh rate of signal quality, do you
> think it will be
Hey,
> So I tried on my own computer and it was the same, as you suggested I
> activated extended signal interface every 10s and by moving around I managed
> to make the RSSI moved from -59 dBm to -75 dBm and the signal quality stays
> not updated.
>
> If I understand correctly, this is an
>
> I did your suggested modifications (patches mm-broadband-modem-qmi.c) and it
> seems to change nothing (I keep getting my signal quality "cached" and I
> don't see "Signal Strength" indications beside in the beginning of modem
> initialization)
>
If you cannot physically remove the antenna
Hey,
>
> > But what do you want? Do you want the extended signal interface
> > information, or do you want the percentage value (which is probably
> > what you were using when AT protocol was being used).
>
> I want the percentage value for the moment (to keep backward compatibility
> with what
Hey!
>
> I recently updated by system to drop ppp/AT usage for CDC. Now my EG25 dongle
> work through qmi-wwan driver and libqmi.
>
> But I began to experience a major difference with the old protocol method. My
> signal quality is not updated anymore (the information output in Status
>
Hey,
> Hey guys. I’m trying to connect 3+ modems on my PI, all of these modems are
> working if I connect them individually, but once I connect all of them
> together I get at least one that can’t get a connection.
>
> Something always happens on the third modem that makes it stay in a unknown
Hey,
>
> for now, MM is said to be licensed under GPLv2+ and LGPLv2+. But the files in
> libqcdm and libmm-glib seem to have a GPL boiler plate. Should we make
> this as in libmbim?
>
> LGPL-2.1-or-later.txt for both libs
> GPL-2.0-or-later.txt for the rest
>
Yes, please; that was always the
Hey Shawn,
> I'm running ModemManager 1.18 on Lenovo Yoga C630 laptop which is
> powered by Qualcomm SDM850 SoC. It works quite out of box for me
Nice!!
> with the only stumble on that qcom-soc plugin is not enabled by default.
> It seems that you made it so on purpose with commit[1]. As
Hey hey,
This is the first bugfix release in the 1.18.x series, built from the mm-1-18
branch.
This release is critical for anyone building the project with the new meson
build system, as it fixes several fundamental issues. But please note, the
meson build port is not fully operational yet
Hey all,
I'm reading through the GSMA TS.34 spec, IoT Device Connection
Efficiency Guidelines,
https://www.gsma.com/iot/gsma-iot-device-connection-efficiency-guidelines/
One of the sections, 5.10, outlines a set of requirements for modems
that support Device Host Identity Reporting (DHIR); which
Hey hey,
This is a new major release of ModemManager, which will be the base for the 1.18.x stable series
(the new "mm-1-18" branch in git). The release has been tagged as "1.18.0".
This is probably the biggest major release we have done since 1.0, and that is
thanks to a lot of people!
*
Hey Thomas
>
> I know the fibocom L830-EB-00 is quite old and the modemmanager version 1.12.6
> too.
>
> Nevertheless I can confirm it works with IPv4/IPv6 in Germany with Deutsche
> Telekom, Vodafone and Telefonica.
> As well with Deutsche Telekom IPv6-only.
>
Thanks for letting us know! Do
Hey Duane,
On Tue, Aug 31, 2021 at 6:46 PM Duane Murphy
wrote:
>
> We are seeing an installation where we the connection is disconnected every
> 60 seconds due to
>
> state change: activated -> failed (reason 'modem-no-carrier',
> sys-iface-state: 'managed')
>
> I have included an excerpt of
Hey Norbert,
> >> I'm creating a plugin for Sierra Wireless HL78xx LTE-M modem.
> >> Actually, it is already partly done.
> >>
> >> The HL78xx has its own TCP/TLS stack/interface. To use it as
> >> "generic linux network interface" though, PPP is used for the AT/PPP
> >> capable
> >> ttyACM1
Hey Norbert,
> I'm creating a plugin for Sierra Wireless HL78xx LTE-M modem.
> Actually, it is already partly done.
>
> The HL78xx has its own TCP/TLS stack/interface. To use it as
> "generic linux network interface" though, PPP is used for the AT/PPP capable
> ttyACM1 port. ttyACM0 is the AT
Hey Ramon,
> > Also, which ports are exposed in the system? Just the wwan control
> > port, or do you also have a NET port as well for the same fake device?
> > MM requires both things.
>
> As far as I understood I have the NET port.
>
> $ sudo modprobe wwan_hwsim
> $ ls /sys/class/wwan/
> $
> > Is that wwan_hwsim integration to be able to create fake modems in
> > userspace that are exposed via the new WWAN subsystem? If so, wouldn't
> > they already be supported by the current ModemManager, which supports
> > the new WWAN subsystem?
>
> I suppose the answer should be "yes they are
Hey Bruce,
> What is the state of things with respect to interoperability between
> ModemManager and systemd-networkd? My project involves an unmanaged
> device with a web interface to manage a few simple settings, and I'm
> trying to add mobile Internet access to it. We've been successfully
>
Hey Ramon,
> I was wondering if there is any plan to add some level of integration
> between ModemManager and wwan_hwsim (e.g. expose interfaces created by
> wwan_hwsim
> (https://github.com/torvalds/linux/blob/master/drivers/net/wwan/wwan_hwsim.c)
> to ModemManager - not sure if this is the
Hey Juan
> I have a system with MM 1.16.4 (NM 1.20.4) and I'm facing some
> problems with my SIMCOM SIM7600G-H
>
> In some systems, I get a successful activation of the cdc-wdm0 device
> and the wwan0 interface comes up and in some other systems, cdc-wdm0
> fails to be grabbed/activated and the
Hey all,
ModemManager 1.18-rc1 was just released this week, and the final 1.18
will happen sometime in the next few weeks, once the RC has been
tested and integrated properly.
Once 1.18 is released, we'll open git master again to new stuff. There
are some pending merge requests in gitlab that
Hey hey!
This is the first release candidate for the next 1.18 stable version. Please
refer to the NEWS file for the full list of updates in this version:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/blob/master/NEWS
The following notes are directed to package maintainers:
Hey Thomas!
> I'm trying to use ModemManager with a Sierra Wireless AirPrime EM919X,
> based on a Snapdragon X55 5G Modem, without success.
>
> The EM919X is connected to an i.MX6QDL through a MHI bus on top of a
> PCIe gen2 bus.
>
> I'm using the kernel 5.13.6, modemmanager 1.32.4, libqmi 1.30.0
Hey hey,
This is the fifth bugfix release in the 1.16.x series, built from the mm-1-16
branch.
ModemManager 1.16.10
---
* QMI:
** Fixed use of uninitialized memory in the 3GPP registration logic when
running NAS Set System Selection Preference.
*
Hey Tomasz,
>
> Thank you. The patch works. The correct vendor and device id are presented.
> The plugin manager still prints that it found 3 plugins to try, but now the
> first to try and best plugin is cinterion.
>
Please post your changes to add support for the WWAN subsystem in the
Hey Reinhard,
> > > I've been testing with all my modems for the next 1.18 release, and
> > > for the QMI and MBIM ones I've done tests with and without
> > > multiplexing support (i.e. connecting normally as we did until now,
> > > and also connecting with multiplexing enabled).
> > >
> > > All
Hey all,
I've been testing with all my modems for the next 1.18 release, and
for the QMI and MBIM ones I've done tests with and without
multiplexing support (i.e. connecting normally as we did until now,
and also connecting with multiplexing enabled).
All the QMI modems I have tested with have
301 - 400 of 2422 matches
Mail list logo
