From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220027] USB 3.2 capture cards using incorrect USB speed
Date: Fri, 18 Apr 2025 01:07:22 +0000 [thread overview]
Message-ID: <bug-220027-208809-kP096dZLj4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220027-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220027
--- Comment #1 from Niko (nrkowalski@gmail.com) ---
I decided to try the 6.14.0-15 Kernel and I'm still having the same issue, but
getting some more information from dmesg.
[ 847.836967] usb 8-1: new SuperSpeed Plus Gen 2x1 USB device number 3 using
xhci_hcd
[ 853.084344] usb 8-1: unable to get BOS descriptor or descriptor too short
[ 853.110389] usb 8-1: unable to read config index 0 descriptor/start: -71
[ 853.110406] usb 8-1: can't read configurations, error -71
[ 853.293248] usb 8-1: new SuperSpeed USB device number 4 using xhci_hcd
[ 853.372723] usb 8-1: LPM exit latency is zeroed, disabling LPM.
[ 853.624234] usb 8-1: New USB device found, idVendor=0fd9, idProduct=009c,
bcdDevice= 0.02
[ 853.624252] usb 8-1: New USB device strings: Mfr=6, Product=7,
SerialNumber=3
[ 853.624259] usb 8-1: Product: Elgato 4K X
[ 853.624265] usb 8-1: Manufacturer: Elgato
[ 853.624271] usb 8-1: SerialNumber: A7SNB504228NRE
[ 853.690719] uvcvideo 8-1:1.1: Unknown video format
30313050-0000-0010-8000-00aa00389b71
[ 853.690749] usb 8-1: Found UVC 1.00 device Elgato 4K X (0fd9:009c)
[ 853.856379] usb 8-1: 3:2: failed to get current value for ch 0 (-22)
[ 854.820221] retire_capture_urb: 15 callbacks suppressed
[ 854.836455] usb 8-1: cannot submit urb (err = -19)
[ 854.837512] usb 8-1: cannot submit urb 0, error -19: no device
[ 855.165030] usb 8-1: reset SuperSpeed USB device number 4 using xhci_hcd
[ 855.236908] usb 8-1: LPM exit latency is zeroed, disabling LPM.
[ 855.322103] uvcvideo 8-1:1.1: Unknown video format
30313050-0000-0010-8000-00aa00389b71
[ 855.322126] usb 8-1: Found UVC 1.00 device Elgato 4K X (0fd9:009c)
[ 855.407009] usb 8-1: 3:2: failed to get current value for ch 0 (-22)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-04-18 1:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 18:26 [Bug 220027] New: USB 3.2 capture cards using incorrect USB speed bugzilla-daemon
2025-04-18 1:07 ` bugzilla-daemon [this message]
2025-04-26 8:39 ` [Bug 220027] " bugzilla-daemon
2025-04-26 16:15 ` bugzilla-daemon
2025-04-27 23:27 ` bugzilla-daemon
2025-04-30 6:35 ` bugzilla-daemon
2025-04-30 19:54 ` bugzilla-daemon
2025-05-02 9:41 ` bugzilla-daemon
2025-05-02 15:19 ` bugzilla-daemon
2025-05-02 20:36 ` bugzilla-daemon
2025-05-03 15:31 ` bugzilla-daemon
2025-05-03 15:59 ` bugzilla-daemon
2025-05-04 0:27 ` bugzilla-daemon
2026-02-12 21:59 ` bugzilla-daemon
2026-02-14 21:27 ` bugzilla-daemon
2026-02-15 6:59 ` Greg KH
2026-02-15 6:59 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-220027-208809-kP096dZLj4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox