Bug 625751
Summary: | yealink driver broken | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pavel Alexeev <pahan> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, treitmayr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-28 14:21:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pavel Alexeev
2010-08-20 10:48:07 UTC
I think it is incorrect bug report - my phone does not work at all. I think you own a phone model which is not supported by the kernel's yealink driver. Vanilla kernels only support the original USB-P1K, which uses packets of 16 bytes (therefore the "expected 16"). Unfortunately many Yealink phone models use the same VID/PID and have to be distinguished in the driver by other measures. However the yealink driver does not even consider that there might be a different model connected and treats it like a P1K. So you just get the initial warning and then, because the subsequent packets have the wrong format, an "unexpected response fd" from your phone. My extended driver from http://devbase.homelinux.org:5071/viewvc/voip/yealink-module at least refuses to handle the device so the system is not clogged by useless USB traffic, but that does not help too much in your case. What is the name of your phone model? Is it a video phone? No, it is just voice, without video. Unfortunately now I have not such phone anymore :( . Sorry. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed. |