Bug 1352137
| Summary: | Sierra EM7455 unable to connect | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nathaniel Nutter <iam> | ||||||
| Component: | ModemManager | Assignee: | Lubomir Rintel <lkundrak> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 24 | CC: | dcbw, djao, fgiudici, gromovd, lkundrak, lrintel | ||||||
| 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: | 2016-11-15 17:24:17 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
Nathaniel Nutter
2016-07-01 18:23:00 UTC
The upstream bug is believed to be fixed. From https://bugs.freedesktop.org/show_bug.cgi?id=96623#c7, This issue is now fixed when using MM 1.5.993, libqmi 1.16.0 and libmbim 1.14.0, all including the QMI over MBIM support: https://lists.freedesktop.org/archives/modemmanager-devel/2016-July/003177.html https://lists.freedesktop.org/archives/libqmi-devel/2016-July/001638.html https://lists.freedesktop.org/archives/libmbim-devel/2016-July/000752.html Additionally, this NCM driver patch in the kernel is also needed, which should be available in the next stable Linux kernel release: http://www.spinics.net/lists/linux-usb/msg143399.html After installing libqmi, libmbim, and ModemManager from Rawhide my modem was able to connect. I'm still haven't got out over the modem but that's probably a config issue. $ sudo dnf install fedora-repos-rawhide $ sudo dnf install --enablerepo rawhide --best --allowerasing libqmi libmbim ModemManager Created attachment 1180824 [details]
Logs from NetworkManager when connecting
I've attached logs showing that the modem seems to be working even though I can't ping gateway or DNS servers.
The last piece to get the modem working reliably was to install a newer kernel, $ sudo dnf install --enablerepo rawhide --best --allowerasing kernel With kernel, libqmi, libmbim, and ModemManager from rawhide the cellular modem is working fine. I can confirm that those fixes work on Lenovo X1 Carbon 4th gen. Nathaniel (or any one else): The modem works fine on my T460s following your instructions, but afterwards if I try to suspend and resume, the modem stops working with no way to recover other than a reboot. Do you have this problem too? David Jao, I am not aware of any issues relating to suspend/resume. I rarely shutdown my laptop and am routinely using the cellular modem after waking from sleep. Thanks Nathaniel. After updating my system to the latest F24 (a few hundred packages), the modem works fine on suspend/resume; however it does take a minute or so to reappear in NetworkManager after resume. Also, the modem number increments by 1 in ModemManager each time it resumes (e.g. /org/freedesktop/ModemManager1/Modem/0 becomes /org/freedesktop/ModemManager1/Modem/1 becomes /org/freedesktop/ModemManager1/Modem/2 ...) (In reply to David Jao from comment #8) > Thanks Nathaniel. After updating my system to the latest F24 (a few hundred > packages), the modem works fine on suspend/resume; however it does take a > minute or so to reappear in NetworkManager after resume. Also, the modem > number increments by 1 in ModemManager each time it resumes (e.g. > /org/freedesktop/ModemManager1/Modem/0 becomes > /org/freedesktop/ModemManager1/Modem/1 becomes > /org/freedesktop/ModemManager1/Modem/2 ...) Yeah, that's expected. MM needs time to re-probe the modems after a resume and the modems also take time to boot up. Closing this as it's fixed with the current release. |