From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219111] New: Xone:23C mixer not recognized as a 2in/2out device
Date: Tue, 30 Jul 2024 18:11:58 +0000 [thread overview]
Message-ID: <bug-219111-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219111
Bug ID: 219111
Summary: Xone:23C mixer not recognized as a 2in/2out device
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: com+bugzilla-kernel@c-henry.fr
Regression: No
Created attachment 306638
--> https://bugzilla.kernel.org/attachment.cgi?id=306638&action=edit
dmesg
The problem is very similar to
https://bugzilla.kernel.org/show_bug.cgi?id=217089: the Xone:23C is supposed to
be a 2 stereo input/2 stereo outputs but only 1 in and 1 out show under Linux
(Windows with related drivers installs show the correct amount of in/out).
Trying to set bConfigurationValue, either by editing
/sys/bus/usb/devices/1-9/bConfigurationValue by hand or using a udev rule won't
work:
# echo 2 >
/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-2/bConfigurationValue
bash: echo: write error: Invalid argument
Please find enclosed with this ticket, the relevant journalctl, dmsg, lsusb and
`cat /sys/kernel/debug/usb/usbmon/1u` of the moment I plug the device.
Reproduced on a Fedora 40 with kernel 6.9.11.
--
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 reply other threads:[~2024-07-30 18:11 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 18:11 bugzilla-daemon [this message]
2024-07-30 18:13 ` [Bug 219111] Xone:23C mixer not recognized as a 2in/2out device bugzilla-daemon
2024-07-30 18:14 ` bugzilla-daemon
2024-07-30 18:14 ` bugzilla-daemon
2024-07-30 18:16 ` bugzilla-daemon
2024-07-31 14:59 ` bugzilla-daemon
2024-07-31 15:38 ` bugzilla-daemon
2024-07-31 15:46 ` bugzilla-daemon
2024-07-31 15:47 ` bugzilla-daemon
2024-07-31 18:14 ` bugzilla-daemon
2024-07-31 18:53 ` bugzilla-daemon
2024-07-31 19:20 ` bugzilla-daemon
2024-07-31 19:21 ` bugzilla-daemon
2024-07-31 19:27 ` bugzilla-daemon
2024-07-31 19:28 ` bugzilla-daemon
2024-08-01 7:41 ` bugzilla-daemon
2024-08-01 15:01 ` bugzilla-daemon
2024-08-04 10:39 ` bugzilla-daemon
2024-08-04 15:38 ` bugzilla-daemon
2024-08-04 19:13 ` bugzilla-daemon
2024-08-05 13:41 ` bugzilla-daemon
2024-08-05 13:41 ` bugzilla-daemon
2024-08-05 14:55 ` bugzilla-daemon
2024-08-05 16:13 ` bugzilla-daemon
2024-08-05 16:15 ` bugzilla-daemon
2024-08-05 16:20 ` bugzilla-daemon
2024-08-06 14:09 ` bugzilla-daemon
2024-08-06 14:12 ` bugzilla-daemon
2024-08-06 14:41 ` bugzilla-daemon
2024-08-06 15:46 ` bugzilla-daemon
2024-08-06 15:50 ` bugzilla-daemon
2024-08-06 19:08 ` bugzilla-daemon
2024-08-07 12:28 ` bugzilla-daemon
2024-08-07 12:29 ` bugzilla-daemon
2024-08-08 7:30 ` bugzilla-daemon
2024-08-08 12:02 ` bugzilla-daemon
2024-08-08 16:19 ` bugzilla-daemon
2024-08-08 17:12 ` bugzilla-daemon
2024-08-08 18:22 ` bugzilla-daemon
2024-08-08 18:36 ` bugzilla-daemon
2024-08-08 19:49 ` bugzilla-daemon
2024-08-08 20:11 ` bugzilla-daemon
2024-08-09 1:38 ` bugzilla-daemon
2024-08-09 8:14 ` bugzilla-daemon
2024-08-09 9:33 ` bugzilla-daemon
2024-08-09 14:06 ` bugzilla-daemon
2024-08-09 14:56 ` bugzilla-daemon
2024-08-09 15:20 ` bugzilla-daemon
2024-08-09 15:29 ` bugzilla-daemon
2024-08-09 15:44 ` bugzilla-daemon
2024-08-10 10:48 ` bugzilla-daemon
2024-08-10 11:48 ` bugzilla-daemon
2024-08-10 15:49 ` bugzilla-daemon
2024-08-10 17:10 ` bugzilla-daemon
2024-08-10 17:19 ` bugzilla-daemon
2024-08-10 19:37 ` bugzilla-daemon
2024-08-11 1:52 ` 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-219111-208809@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.