public inbox for linux-hotplug@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans Jörg Paliege" <hans_paliege@web.de>
To: linux-hotplug@vger.kernel.org
Subject: Re Re: potential bug or quirk in the linux kernel usb subsystem, usb microphone sampling rate resolution rate
Date: Mon, 9 Mar 2026 10:04:46 +0100	[thread overview]
Message-ID: <ad98f262-0d9a-4d46-8f8b-b8d9ae7b7184@web.de> (raw)



Hello Mr. Hartman,



i am just a daily linux user and not familiar with the internal 
proceedings of bugreports, mailing lists and development teams.

Please dont take any of this personal. I just sent the report to the 
main developer according to the linux kernel documentation,

which is you. As with yesterdays and this email, i only clicked reply 
and i hope that the email finds its way to the right developer

and with some good luck maybe this quirk will be fixed.



Small addendum to the usb microphone quirk:


As a workaround i use a professional ZOOM H2 usb audio recording device 
from 2009. Specs can be found on a wikipedia page.



The main difference why this works fine is because during boot it is 
only powered up and on the device itself i have to

choose either to be a smd card storage device or a usb stereo 
microphone. At this point i have to manually set the

audio sample rate to either 44100 or 48000 and then initialize the usb 
connection with the pc. Once this is done,

it works and the usb subsystem does not override the sampling rate 
because it is set on the device itself.


As with todays dmesg messages, they are the same as yesterday. All other 
dmesg messages are fine with no errors, and all other usb devices work 
fine.


Thank you very much.


Best regards


Hans Paliege




                 reply	other threads:[~2026-03-09  9:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ad98f262-0d9a-4d46-8f8b-b8d9ae7b7184@web.de \
    --to=hans_paliege@web.de \
    --cc=linux-hotplug@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