packages/net/modemmanager/files/usr/share, branch masterMirror of packages feedhttps://git-03.infra.openwrt.org/feed/packages/atom?h=master2026-08-03T11:03:31Zmodemmanager: skip live report when the service isn't up yet2026-08-03T11:03:31ZMichael Pfeifroth2026-07-31T12:05:38Zurn:sha1:187382d9d1444c0308355f2f34fc0c759ab73440
At boot procd replays every previously-seen uevent before
/etc/init.d/modemmanager starts. Each replay walks the hotplug.d/
tree, which calls mm_report_event() in modemmanager.common. That
helper does two independent things:
1) appends the event to ${MODEMMANAGER_EVENTS_CACHE}, and
2) runs 'mmcli --report-kernel-event=...' to notify a live MM.
Step 1 is what matters for boot; step 2 exists so events fired
after MM is running get reported without waiting for the next
cache replay. The cache path is intentional: ModemManager-wrapper
starts MM, then mm_report_events_from_cache() polls 'mmcli -L'
until the bus is available and replays every cached event.
At boot the modemmanager service instance hasn't been spawned by
procd yet, so step 2 always fails with:
daemon.err ModemManager[NNN]: hotplug: Couldn't report kernel
event: error: couldn't get bus: Could not connect: No such
file or directory
That's one daemon.err line per hotplug script per port, per boot.
On a dual-modem board that's a dozen spurious errors before the
service even starts. Nothing is lost -- the wrapper's cache
replay picks them all up seconds later -- but the log noise makes
real ModemManager errors harder to spot.
Guard the live call with a cheap pidfile-based liveness check.
The pidfile is procd's, so it proves the service instance has
been spawned, not that MM is already reachable on the bus; the
brief wrapper-startup window (procd spawns the wrapper -> wrapper
execs MM -> MM reaches the bus) is not covered. In practice no
fresh uevents fire in that window on the boards this was tested
on, and events that do arrive there are still cached. If the
service hasn't been spawned yet, the event is silently cached and
the wrapper handles it. If it has, behavior is unchanged.
Signed-off-by: Michael Pfeifroth <micpf@westermo.com>
modemmanager: add config optional netifd integration2025-02-26T09:03:30ZGilles Lenaerts2025-02-11T12:58:57Zurn:sha1:5cb12d479b43eaed89066827690a23f4e1e994a7
This change introduces an optional configuration
of the netifd integration in the ModemManager package.
When disabled, it removes the NETIFD dependency and
other unwanted components from the root filesystem
during the build phase.
Additionally, in the modemmanager.common the netifd-proto.sh
inclusion line can be savely removed as there is no usage
of it in its functions.
Signed-off-by: Gilles Lenaerts <gilles.lenaerts_ext@softathome.com>
modemmanager: report events for virtual netdevices2024-03-06T09:16:21ZDaniele Palmas2024-02-27T11:15:40Zurn:sha1:c51a804a63e17806db22fa88b3c816bad8bd95da
Virtual netdevices created for multiplexing should not be skipped
when reporting events, otherwise it is not possible to setup the
data connection.
Add these exceptions in mm_report_event function.
Signed-off-by: Daniele Palmas <dnlplm@gmail.com>
modemmanager: moving the openwrt related files to subdirectories2024-03-05T12:04:59ZFlorian Eckert2024-03-05T11:59:23Zurn:sha1:dab2cdc44c1db81d1384a495c5e0ca7774c497cf
Moving the openwrt related files to subdirectories as they are installed
on the system. This change makes it immediately apparent during development
where the file is to be installed in the running system.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>