| Summary: | lt4120 SnapDragox X5 not recognized | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Roberto N <robnunin> | ||||||||
| Component: | ModemManager | Assignee: | Lubomir Rintel <lkundrak> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 25 | CC: | brian.peletz, dcbw, fgiudici, lkundrak | ||||||||
| Target Milestone: | --- | Flags: | robnunin:
needinfo?
(lkundrak) |
||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-12-12 10:56:49 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: | |||||||||
| Attachments: |
|
||||||||||
Created attachment 1227618 [details]
Output from modemmanager started with debug option
I'm obviously available for any test would be useful to fix this issue. no changes after 4.9.13-201.fc25.x86_64. no changes after Fedora 26 alpha no changes after Fedora 26 beta. Did someone will take care of this ? Created attachment 1313496 [details]
right udev rule to set lt4120 in config #3
Thanks to Tore Anderson, pointing me in the right direction. Applying the udev rule posted, I was able to have modemmanager to detect lt4120 and use it. Tested with both simple (internet) and complex(company apn) configurations, successfully. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1227617 [details] udev rules to let udevd identify device as usable modem. Description of problem: HP branded, internal, pci-x, lt4120 LTE modem not recognized by ModemManager as usable device. Version-Release number of selected component (if applicable): T77W595.F0.0.0.6.5.GC.028 1 [Jul 06 2016 23:00:00] How reproducible: Install OS on an operated laptop with named device. From scratch, device is listed only on lsusb output: Bus 001 Device 002: ID 03f0:9d1d Hewlett-Packard No device are created, until loading dedicated udev rule file (in attachment) Steps to Reproduce: 1. Install os 2. Load udev rule file 3. issue mmcli -L command Actual results: No modems were found Expected results: Device identified to be used as a WWAN capable device. Additional info: Without loading the udev rule, device is recognized (partially) like and additional Ethernet adapter. Reading notes in the mentioned Launchpad Bug, additional functions to libqmi-utils must be added, to allow loading firmware inside the device.