Bug 2040321
| Summary: | Logitech Brio doesn't initialise on USB 3.0 port of Asus M5A97 Evo R2.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Roy <nouveau> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 35 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-12-13 16:18:45 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
Roy
2022-01-13 13:29:32 UTC
Hi Roy, So the Asus M5A97 Evo R2.0 motherboard is somewhat old, its chipsets does not support USB-3 at all, so an extra chip with an early XHCI controller has been added on the board. In my experience the early USB-3 controllers sometimes where buggy. So this might just be an incompatibility between the used somewhat old XHCI controller and the quite new webcam. Another possible cause of issues like this is that some of the powerrails on your board might not be fully up2spec anymore (old capacitors) USB3 SuperSpeed tends to be somewhat sensitive to this. BTW with the Asus PN50 are you using a Type-C port there or a Type-A port, I guess the camera comes with a Type-C to -A convertor? That should be fine, but you may want to try a Type-A port on the PN50 to rule it out. Other then my above rambling, I think it would indeed be best to take this upstream, since it is an enumeration issue the right person to email about this would be Mathias Nyman <mathias.nyman> (XHCI maintainer) with linux-usb.org in the Cc. Feel free to Cc me too. Regards, Hans You're right, USB 3 Superspeed is added using: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller On the Asus PN50 I tried the same USB-A (to USB-C) cable that I used on the M5A97 motherboard. I'll make a report on the kernel bugzilla and link it here. Thanks! This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-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 EOL if it remains open with a 'version' of '35'. 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 35 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 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |