All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Oliphant <oliphant@nostatic.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Support for NUX MG-300 USB interface
Date: Mon, 18 Jan 2021 08:33:35 -0800	[thread overview]
Message-ID: <CAHXb3bdt6mgUcZ0+MH1i7QeYF03MSwx=kad-YBBNeVjqoH=KhA@mail.gmail.com> (raw)
In-Reply-To: <s5hr1mik7vu.wl-tiwai@suse.de>

Thanks for the response. I'm running a very recent build of the master
kernel tree (~ 5.11-rc2).

I'll give dyndbg a try.

Mike

On Sun, Jan 17, 2021 at 11:43 PM Takashi Iwai <tiwai@suse.de> wrote:

> On Sun, 17 Jan 2021 19:56:01 +0100,
> Mike Oliphant wrote:
> >
> > I recently got a NUX MG-300 USB guitar fx interface with high hopes that
> it
> > would work in Linux. It is supposed to be class-compliant, and works in
> iOS
> > and macOS without a driver.
> >
> > Unfortunately, while it is recognized as a USB audio device by Linux, it
> is
> > not working.
> >
> > The core issue seems to be that "stream0" reports no playback rates.
> dmesg
> > also shows errors, including "__uac_clock_find_source(): selector
> reported
> > illegal value".
> >
> > Any help identifying the issue would be much appreciated. I have some
> > experience troubleshooting the USB audio kernel code and am happy to try
> > doing so if I can get a nudge in the right direction.
> >
> > Output from "stream0", dmesg, and lsusb follows.
>
> Did you try the latest 5.11-rc kernel?  There have been lots of
> changes in USB-audio and this might work better there.
>
> If it still doesn't work with 5.11-rc, please try to enable the debug
> option, e.g. boot with snd_usb_audio.dyndbg=+p boot option, plug the
> device, and get the kernel logs (at plugging and during the audio
> operations).
>
>
> thanks,
>
> Takashi
>

  reply	other threads:[~2021-01-18 16:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 18:56 Support for NUX MG-300 USB interface Mike Oliphant
2021-01-18  7:43 ` Takashi Iwai
2021-01-18 16:33   ` Mike Oliphant [this message]
2021-01-18 17:54     ` Mike Oliphant
2021-01-18 19:19       ` Takashi Iwai
2021-01-18 21:15         ` Mike Oliphant
2021-01-18 21:59           ` Takashi Iwai
2021-01-19  0:26             ` Mike Oliphant
2021-01-19  9:05               ` Takashi Iwai
2021-01-19 17:40                 ` Mike Oliphant
2021-01-20 14:33                   ` Takashi Iwai
2021-01-20 21:17                     ` Mike Oliphant
2021-01-20 21:38                       ` Takashi Iwai
2021-01-20 21:47                         ` Mike Oliphant
2021-01-21 19:04                           ` Mike Oliphant
2021-01-21 20:18                             ` Mike Oliphant

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='CAHXb3bdt6mgUcZ0+MH1i7QeYF03MSwx=kad-YBBNeVjqoH=KhA@mail.gmail.com' \
    --to=oliphant@nostatic.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.