modemmanager: Fix Quectel modems initialization bug #3478
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexgg
approved these changes
Jul 24, 2024
floion
force-pushed
the
fix_quectel_modems
branch
from
0599e2a to
8b81baa
Compare
|
Website deployed to CF Pages, 👀 preview link https://ec76a2ba.balena-os.pages.dev |
With the update to ModemManager version 1.22.0 we now have some Quectel modems failing to use QMI properly: ModemManager[1178]: [modem0] power state updated: on ModemManager[1178]: [modem0] (quectel) modem reset detected, triggering reprobe ModemManager[1178]: [modem0] (quectel) modem reset detected, triggering reprobe . . . ModemManager[1178]: [modem0] failed waiting for final state: Too much time waiting to get to a final state ModemManager[1178]: [modem0] failed enabling modem: Operation was cancelled ModemManager[1178]: [modem1] couldn't start initialization: Transaction timed out ModemManager[1178]: [modem1] fatal error initializing: Fatal error: modem is unusable This has been fixed upstream with the 2 patches we backport here: ModemManager[1139]: [modem0] power state updated: on ModemManager[1139]: [modem0] (quectel) continuing without enabling profile manager events Change-type: patch Signed-off-by: Florin Sarbu <[email protected]>
floion
force-pushed
the
fix_quectel_modems
branch
from
8b81baa to
2d53d2c
Compare
|
@resin-jenkins test this please |
5 similar comments
|
@resin-jenkins test this please |
|
@resin-jenkins test this please |
|
@resin-jenkins test this please |
|
@resin-jenkins test this please |
|
@resin-jenkins test this please |
|
@resin-jenkins retest this please |
|
@resin-jenkins test this please |
3 similar comments
|
@resin-jenkins test this please |
|
@resin-jenkins test this please |
|
@resin-jenkins test this please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the update to ModemManager version 1.22.0 we now have some Quectel modems failing to use QMI properly:
ModemManager[1178]: [modem0] power state updated: on ModemManager[1178]: [modem0] (quectel) modem reset detected, triggering reprobe ModemManager[1178]: [modem0] (quectel) modem reset detected, triggering reprobe .
.
.
ModemManager[1178]: [modem0] failed waiting for final state: Too much time waiting to get to a final state ModemManager[1178]: [modem0] failed enabling modem: Operation was cancelled ModemManager[1178]: [modem1] couldn't start initialization: Transaction timed out ModemManager[1178]: [modem1] fatal error initializing: Fatal error: modem is unusable
This has been fixed upstream with the 2 patches we backport here:
ModemManager[1139]: [modem0] power state updated: on
ModemManager[1139]: [modem0] (quectel) continuing without enabling profile manager events
Contributor checklist
Change-typepresent on at least one commitSigned-off-byis presentReviewer Guidelines