Snap: pwl-linux-pkgs-dw5826e, revision 1 (uploaded, not released to any channel; held for
manual review for the dbus slot and gpio-control).
pwl-linux-pkgs-dw5826e provides the host-side services for the PWL cellular modem
(Dell DW5826e, USB, 413c:8217/8218/8219/81ea/81eb/81ec) shipped in Dell
notebooks: modem bring-up, AT/MBIM adaptation, firmware update, and carrier
preference. Four daemons, strict confinement, core22. Published by Palcom
International Corporation. The snap has been verified end to end on the
target hardware under strict confinement — including a full firmware flash
— with zero AppArmor denials.
Host-side integration (udev rules, a ModemManager drop-in, the FCC unlock
hook) is not done from this snap. It ships as a separate OEM deb through
the Dell/Canonical OEM channel, the same way lenovo-wwan-unlock and
foxconn-pc-services do. Nothing in this request touches host
configuration.
We are asking for the following. Each item is tied to a code path the product cannot function without.
1. dbus slot on the system bus, name com.pwl.core (allow-installation),
and auto-connect of this snap’s own pwl-core-dbus-client plug to it
pwl-core owns this name; the other three daemons reach it by name, and
the snap’s per-user dialog agent (daemon-scope: user) plugs the same name
to receive the progress-dialog signal. Without the slot the daemons cannot
find each other; without the plug connection the user never sees the
firmware-update dialog.
2. modem-manager — auto-connect
This is the snap’s primary function. The daemons talk MBIM to the modem
through the host’s mbim-proxy (MBIM_DEVICE_OPEN_FLAGS_PROXY), which this
interface’s @mbim-proxy unix rule grants, and inhibit ModemManager over
D-Bus around firmware flashing. Without it no daemon can reach the modem
at all. Same justification as lenovo-wwan-dpr (2021-08) and
quectel-firmware-switch (2021-12).
3. hardware-observe — auto-connect
Reads /sys/class/dmi/id/product_sku to select the firmware category for
the machine, and walks /sys/bus/usb/devices/*/idVendor to detect the
module. Without it every daemon exits at start with “unsupported device”.
4. raw-usb — auto-connect
Firmware is flashed with fastboot (staged in the snap) over usbfs while the
module is re-enumerated as 413c:8219. Without it the flash cannot start.
5. gpio-control — allow-installation and auto-connect
Hardware recovery after a failed flash: the daemon power-cycles the module
by writing /sys/class/gpio/export, gpioN/direction and gpioN/value
for the pin that the machine’s SKU maps to. This is the last recovery step
before the module is considered unrecoverable, so it has to be present on
every machine, not connected by hand after a failure. gpio-control is a
system slot on classic Ubuntu (implicitOnClassic); the pin numbers are
selected at runtime from a SKU table in the daemon. We considered moving
the GPIO write into the host deb as a helper; we would rather keep it in
the snap so the recovery logic stays in one place under confinement, but
can move it if reviewers prefer.
What is not requested
No system-files, no custom-device, no classic. The firmware images are
bundled in this snap; the content plug (pwl-firmware) is kept for a future same-publisher split and needs nothing from the store.
Verification
Dell Pro 14 Plus (Ubuntu 24.04.3, kernel 6.17 OEM, snapd 2.76.3) with a
DW5826e, SIM in, this revision plus the host OEM deb. Under strict
confinement with the interfaces above connected: install and FCC unlock
(the unlock’s verdict reaching pwl-core over the dbus slot), then two
full firmware flashes by snap refresh (07.62 → 07.64 → 07.62, image over
usbfs, module reboot). Each flash: ModemManager inhibited over D-Bus before
the switch to download mode, the module unlocked after its first boot,
the device released back to ModemManager, the preferred carrier set again,
version read back and the modem registered. Zero AppArmor denials during
both flows. gpio-control was verified separately: with the plug
connected a strict snap can export and drive a pin through
/sys/class/gpio.
Thanks & Regards, Tinny Tseng (Tinny.tseng@palcomwireless.com)