public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
Cc: Jaroslav Kysela <perex-/Fr2/VpizcU@public.gmane.org>,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-sound-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org
Subject: Re: Cannot load snd-usb-audio on 3.12-rc2
Date: Wed, 09 Oct 2013 20:01:08 +0000	[thread overview]
Message-ID: <20131009200108.GA6136@xanatos> (raw)
In-Reply-To: <s5hfvssdlo2.wl%tiwai-l3A5Bk7waGM@public.gmane.org>

On Thu, Sep 26, 2013 at 10:36:29AM +0200, Takashi Iwai wrote:
> At Mon, 23 Sep 2013 16:41:07 -0700,
> Sarah Sharp wrote:
> > 
> > The snd-usb-audio driver no longer loads properly on 3.12-rc2 when I
> > plug in my USB headset.  It worked fine on 3.11-rc4 (not sure about
> > vanilla 3.11).
> > 
> > Trying to manually load the driver fails:
> > 
> > sarah@xanatos:~$ sudo modprobe snd-usb-audio
> > FATAL: Error inserting snd_usb_audio
> > (/lib/modules/3.12.0-rc2/kernel/sound/usb/snd-usb-audio.ko): Invalid argument
> > 
> > dmesg shows:
> > 
> > [   44.231668] snd_usb_audio: `-2' invalid for parameter `index'
> 
> There is no corresponding code change in the USB audio driver side, so
> I guess it must be in the module parameter parser that got broken.
> 
> Does the patch below fix?

Hi Takashi,

I didn't get around to applying the patch, but USB audio seems to be
fixed in 3.12-rc4.

Thanks!
Sarah Sharp

  parent reply	other threads:[~2013-10-09 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130923234107.GA4876@xanatos>
2013-09-24 15:52 ` Cannot load snd-usb-audio on 3.12-rc2 Daniel Mack
2013-09-26  8:10   ` [alsa-devel] " David Henningsson
2013-09-26  8:36 ` Takashi Iwai
     [not found]   ` <s5hfvssdlo2.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2013-10-09 20:01     ` Sarah Sharp [this message]
2013-10-10  7:44       ` Takashi Iwai

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=20131009200108.GA6136@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=linux-sound-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=perex-/Fr2/VpizcU@public.gmane.org \
    --cc=tiwai-l3A5Bk7waGM@public.gmane.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