From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217089] New: xone23c mixer
Date: Sun, 26 Feb 2023 09:36:31 +0000 [thread overview]
Message-ID: <bug-217089-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217089
Bug ID: 217089
Summary: xone23c mixer
Product: Drivers
Version: 2.5
Kernel Version: <5.4.0.33
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: kaufmich@valino.info
Regression: No
Having a few problems with the Xone32c though not sure if this is an ALSA
issue or general USB stack problem.
It's a USB soundcard that is supposed to have 4 inputs and 4 outputs. It
seems to have 2 USB configurations (bNumConfigurations : 0x2). When plugged
in, bConfigurationValue is 0x1 and only 2 inputs and 2 outputs show up.
Change this value to 0x2 and it shows up (as it should) as 4 inputs and 4
outputs.
I can change the bConfigurationValue with this udev rule, or with a `echo 2
/sys/bus/usb/devices/1-1.4/bConfigurationValue`:
This has all been working OK on Ubuntu 20.04 running kernel
5.4.0-33-generic. However, I just updated to 5.4.0-37-generic and now there
is only a single USB configuration (bNumConfigurations : 0x1) and
bConfigurationValue can't be changed to 0x2:
--
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:[~2023-02-26 9:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 9:36 bugzilla-daemon [this message]
2023-02-26 19:15 ` [Bug 217089] xone23c mixer bugzilla-daemon
2023-02-26 21:33 ` bugzilla-daemon
2023-02-26 22:33 ` bugzilla-daemon
2023-02-27 10:02 ` bugzilla-daemon
2023-02-27 21:22 ` bugzilla-daemon
2023-02-27 21:23 ` bugzilla-daemon
2023-02-27 21:24 ` bugzilla-daemon
2023-02-27 21:25 ` bugzilla-daemon
2023-02-27 21:33 ` bugzilla-daemon
2023-02-28 2:13 ` bugzilla-daemon
2023-02-28 11:06 ` bugzilla-daemon
2023-02-28 11:07 ` bugzilla-daemon
2023-02-28 11:09 ` bugzilla-daemon
2023-02-28 11:13 ` bugzilla-daemon
2023-02-28 16:25 ` bugzilla-daemon
2023-02-28 16:52 ` bugzilla-daemon
2023-02-28 16:55 ` bugzilla-daemon
2023-02-28 19:35 ` bugzilla-daemon
2023-03-01 9:20 ` bugzilla-daemon
2023-03-01 15:26 ` bugzilla-daemon
2023-03-01 15:39 ` bugzilla-daemon
2023-03-01 15:55 ` bugzilla-daemon
2023-03-01 16:07 ` bugzilla-daemon
2023-03-01 20:27 ` 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-217089-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.