[SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS

[Atlas Yu]

[ Impact ]

The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information,
and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops.
(lp: #2045276)

[ Test Plan ]

Under Jammy environment, with latest linux-oem kernel installed,
check output of `mmcli -L` to see if the modems are properly recognized.

Modems to check:
- EM061K-GL
- EM160
- EM160

[ Where problems could occur ]

EM160R-GL(1.22.0):
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs

EM061K-GL(1.22.0):
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs

RM520N-GL(1.22.0):
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs

All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones.

Noble contains these changes, so, only SRU jammy and mantic.

[ Other Info ]

These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate

[Atlas Yu (pseudoc)]

DELETED: ~~Patch for Jammy (22.04). ~~

[Simon Chopin (schopin)]

Hi Atlas,

Thanks for looking into this.

Please merge all your changelog entries into a single one. Also, could you please add some DEP-3 for the new patches added to the package? It makes it easier to track down the context for a given patch.

I'm a bit foggy on the upgrade paths that are still possible for Jammy, but in general when posting a SRU for 22.04, you should either fix it on all subsequent releases that are still supported or justify why we shouldn't, including interim releases. The rationale for this is that we don't want regressions for users upgrading.

[Simon Chopin (schopin)]

I'm unsubscribing ubuntu-sponsors, please re-subscribe once you feel my remarks have been addressed.

[Atlas Yu (pseudoc)]

Patch for Jammy (22.04).

[Atlas Yu (pseudoc)]

Hi Simon,

I squashed those entries into one, and add DEP3 headers for the patch files.

You might missed the line I mentioned in the [ Where problems could occur ] section:
> Noble contains these changes, so, only SRU jammy.

All these commits are in 1.22.0, and noble is based on upstream 1.23.4.

[Simon Chopin (schopin)]

Hi,

I didn't miss the line, it's just incomplete: Mantic is still supported, and Jammy users can still upgrade to Mantic :)

Cheers!

[Atlas Yu (pseudoc)]

Patch for Mantic (23.10).

[Atlas Yu (pseudoc)]

Hi Simon,

Thanks, I thought that the Mantic was out of support.

[Atlas Yu (pseudoc)]

Hi Ubuntu Sponsors,

I would be much appreciated if anyone could help reviewing this.

[Atlas Yu (pseudoc)]

Nudge.

[Benjamin Drung (bdrung)]

Sponsored modemmanager 1.20.0-1~ubuntu22.04.4. It is waiting in https://launchpad.net/ubuntu/jammy/+queue?queue_state=1 now. mantic went EOL in between.

[Andreas Hasenack (ahasenack)]

Hello Atlas, or anyone else affected,

Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted modemmanager (1.20.0-1~ubuntu22.04.4) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

cinnamon-control-center/5.2.1-2 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#modemmanager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Atlas Yu (pseudoc)]

Tested on 3 different Thinkpad with Quectel EM061K-GL/EM160/RM520N, outputs of `mmcli -L` are expected.

[Andreas Hasenack (ahasenack)]

Hi Atlas,

thanks for your verification.

Following the request in comment #12, though:

> If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the
> package you tested,

Could you please clarify the version of the package you tested?

[Atlas Yu (pseudoc)]

Hi Andreas,

The package on jammy-proposed(1.20.0-1~ubuntu22.04.4) fixes the bug for me.

u@Thames-1:~$ dpkg -l | grep modemmanager
ii gir1.2-modemmanager-1.0:amd64 1.20.0-1~ubuntu22.04.4 amd64 GObject introspection data for modemmanager
ii modemmanager 1.20.0-1~ubuntu22.04.4 amd64 D-Bus service for managing modems
ii modemmanager-dev:amd64 1.20.0-1~ubuntu22.04.4 amd64 D-Bus service for managing modems - development files
ii modemmanager-doc 1.20.0-1~ubuntu22.04.4 all D-Bus service for managing modems - documentation files
u@Thames-1:~$ mmcli -L
    /org/freedesktop/ModemManager1/Modem/0 [quectel] RM520N-GL