All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Nandakumar Edamana <nandakumar@nandakumar.co.in>
Cc: alsa-devel@alsa-project.org
Subject: Re: Behringer UMC202HD issues and a partial solution
Date: Fri, 14 Jan 2022 00:41:39 -0300	[thread overview]
Message-ID: <YeDw89KZOh4yG7c8@geday> (raw)
In-Reply-To: <e1a7d67d-9862-3085-4e01-091ca443d2df@nandakumar.co.in>

On Fri, Jan 14, 2022 at 08:04:08AM +0530, Nandakumar Edamana wrote:
> Thank you very much for the kind reply.
> 
> > You made the dmesg warning go away, but that didn't necessarily solve
> > the underlying issue. May I ask that you post the "lsusb -v -d
> > 1397:0507" ?
> 
> Here it is, connected to a USB 2.0 port (xHCI still enabled).
>

Thanks, Nandakumar!

Have you tried unloading the snd-usb-audio module and the reloading it
with implicit_fb=1 as in "modprobe -r snd-usb-audio" and "modprobe
snd-usb-audio implicit_fb=1" ?

If not, try it. If it works and your playback issues are gone then
your device may just need a quirk. If it doesn't work we still
have dyndbg to go through.

Last but not least, please use a vanilla kernel for these tests.

Thank you,
Geraldo Nascimento

  reply	other threads:[~2022-01-14  3:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 14:37 Behringer UMC202HD issues and a partial solution Nandakumar Edamana
2022-01-13 19:00 ` Geraldo Nascimento
2022-01-14  2:34   ` Nandakumar Edamana
2022-01-14  3:41     ` Geraldo Nascimento [this message]
2022-01-14  4:36       ` Nandakumar Edamana
2022-01-14  7:44         ` Geraldo Nascimento
2022-01-14 13:39           ` Nandakumar Edamana
2022-01-14 22:28             ` Geraldo Nascimento
     [not found]               ` <5fba3e63-6fd2-de1c-1564-ac6b8870e730@nandakumar.co.in>
2022-01-16  1:00                 ` Geraldo Nascimento
2022-01-18 11:20                   ` Nandakumar Edamana
2022-01-18 19:20                     ` Geraldo Nascimento

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=YeDw89KZOh4yG7c8@geday \
    --to=geraldogabriel@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nandakumar@nandakumar.co.in \
    /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.