Bug 1101850
| Summary: | USB Device needs to be blacklisted Pololu A-Star 32U4 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Derichs <chris+rhbugzilla> | ||||
| Component: | ModemManager | Assignee: | Dan Williams <dcbw> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | davidegrayson, dcbw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-29 20:50:08 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: |
|
||||||
Hello, Chris. This is David from Pololu. You should be able to follow the instructions we wrote in the A-Star's README.txt in order to add a udev rule for the A-Star that tells the ModemManager not to use it: https://github.com/pololu/a-star/blob/master/README.txt Also, we submitted a patch to the ModemManager project to generally ignore all Pololu devices: http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=09d92ef3338effa85eff7f4efa416afe11f780a0 --David This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 899823 [details] dmesg during reprogramming when it is working Description of problem: ModemManager is breaking my ability to upload code to an Arduino compatibile usb device similar to the Leonardo. It should be blacklisted. Everytime the chip resets the usb interface (which the upload does as part of uploading) I find from lsof on /dev/ttyAMC0 that ModemManager has the port open. The usb has multiple ID's. Normal state: New USB device found, idVendor=1ffb, idProduct=2300 During reprogramming: New USB device found, idVendor=1ffb, idProduct=0101 I tried blacklisting it by manually editing 77-mm-...something just like the arduino entries and it didn't work. I'm just now noticing in dmesg as part of reprogramming it appears as a different PID. I eventually just did yum remove ModemManager to get it to work. Attached is an excerpt from dmesg. Version-Release number of selected component (if applicable): ModemManager-1.1.0-2.git20130913.fc20.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Product page www.pololu.com/product/3101 Normal state: 1ffb:2300 During reprogramming: 1ffb:0101