linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219111] Xone:23C mixer not recognized as a 2in/2out device
Date: Sun, 04 Aug 2024 15:38:39 +0000	[thread overview]
Message-ID: <bug-219111-208809-ENWZCJrisU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219111-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219111

--- Comment #18 from CH (com+bugzilla-kernel@c-henry.fr) ---
Ok, so I finally managed to correclty install and run the patched kernel and it
appears your patch doesn't work. Here's the journalctl trace from when I plug
the mixer:

août 04 17:32:42 localhost kernel: usb 1-2: new high-speed USB device number 7
using xhci_hcd
août 04 17:32:42 localhost kernel: usb 1-2: Patch applied
août 04 17:32:42 localhost kernel: usb 1-2: Skipped second reset
août 04 17:32:42 localhost kernel: usb 1-2: New USB device found,
idVendor=22f0, idProduct=0008, bcdDevice= 2.00
août 04 17:32:42 localhost kernel: usb 1-2: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
août 04 17:32:42 localhost kernel: usb 1-2: Product: Xone:23C
août 04 17:32:42 localhost kernel: usb 1-2: Manufacturer: Allen&Heath
août 04 17:32:42 localhost kernel: usb 1-2: SerialNumber: no serial number
août 04 17:32:42 localhost kernel: usb 1-2: 1:2 : UAC_AS_GENERAL descriptor not
found
août 04 17:32:42 localhost kernel: usb 1-2: 2:2 : UAC_AS_GENERAL descriptor not
found
août 04 17:32:42 localhost kernel: usb 1-2: Quirk or no altset; falling back to
MIDI 1.0
août 04 17:32:42 localhost mtp-probe[5421]: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-2"
août 04 17:32:42 localhost mtp-probe[5421]: bus: 1, device: 7 was not an MTP
device
août 04 17:32:42 localhost (udev-worker)[5420]: 1-2:
/usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:19 Failed to write
ATTR{/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-2/bConfigurationValue},
ignoring: Invalid argument
août 04 17:32:42 localhost mtp-probe[5443]: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-2"
août 04 17:32:42 localhost mtp-probe[5443]: bus: 1, device: 7 was not an MTP
device
août 04 17:32:42 localhost kded6[3384]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost plasmashell[3409]: org.kde.pulseaudio: No object for
name "alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost kded6[3384]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost plasmashell[3409]: org.kde.pulseaudio: No object for
name "alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost kded6[3384]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost kded6[3384]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost plasmashell[3409]: org.kde.pulseaudio: No object for
name "alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost plasmashell[3409]: org.kde.pulseaudio: No object for
name "alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost kded6[3384]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost plasmashell[3409]: org.kde.pulseaudio: No object for
name "alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost kded6[3384]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_08_00.4.analog-stereo.monitor"
août 04 17:32:42 localhost plasmashell[3409]: org.kde.pulseaudio: No object for
name "alsa_output.pci-0000_08_00.4.analog-stereo.monitor"


You can see the *Patch applied* log which is a line I added to ensure I was
indeed running the patched kernel and the *Skipped second reset* line that
indicates the `if (maxp0 <= 18)` was skipped but udev still fails to apply the
`bConfigurationValue` rule.

If you want to test another patch, I now know how to do.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-08-04 15:38 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 18:11 [Bug 219111] New: Xone:23C mixer not recognized as a 2in/2out device bugzilla-daemon
2024-07-30 18:13 ` [Bug 219111] " 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 [this message]
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-ENWZCJrisU@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;
as well as URLs for NNTP newsgroup(s).