Bug 1966283
| Summary: | Quectel em05-ce wwan module doesn't work after laptop resume / wake up | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | plumlis <plumerlis> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 34 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, cchen50, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, mpearson, ptalbert, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-06-07 22:37:14 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
plumlis
2021-05-31 20:04:33 UTC
As a note I've raised this internally at Lenovo (reference LO-1259). I'll let the WWAN experts comment We're still working on enabling WWAN so you may have to wait for that to complete. Support was added by Quectel and is upstream so you may want to try building a 5.13 kernel and try that - if you're comfortable building a kernel of course :) Mark Hi. I tried with latest Kernel 5.13. But no luck. It seems my moderm Quectel em05-ce can be recognized and works well even with Kernel 5.12 . But it stop working after wake up from suspend. And with S3 suspend it don't have this issue. I think the main problem is Moderm have some issues with sleep or suspend operation. Maybe it's Network manager related or maybe it's about Kernel drivers Or maybe Bios related? If you need me to do some tests. I'm very glad to. Thank you. Any news about this? I am using kernel 5.13 and found this issue still. Sorry for the slow reply - I completely missed your question. As a note - set needinfo and the system sends me daily nags :) We're still going through some testing - but I thought this was fixed in 5.14. I've nudged the WWAN team for confirmation. My apologies, I'd completely lost track of this issue. We've completed testing with the Quectel modem so it should work well now. I never got confirmation on the exact kernel versions but I think if you have 5.14, the latest modem manager and the latest modem firmware then it should be stable There are still some issues being worked on that may impact large data transfers for users on networks in Europe - Quectel are looking at that and it will likely be fixed by a FW update. This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed. |