All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Diffey <gdiffey@gmail.com>
To: chris-alsa@rauros.net
Cc: alsa-devel@alsa-project.org
Subject: Re: M-Audio FastTrack C400
Date: Thu, 19 Apr 2012 21:09:06 +1000	[thread overview]
Message-ID: <CACckToWQr=XBNH+p+twGzKQscjZs5WyG3jazJ79x9jpU=DteGg@mail.gmail.com> (raw)
In-Reply-To: <4F8FE83E.2070600@rauros.net>

On Thu, Apr 19, 2012 at 8:26 PM, Chris Cavey <chris-alsa@rauros.net> wrote:

> Complete snippet from the log
>
> [  374.104138] usbcore: deregistering interface driver snd-usb-audio
> [  374.875660] snd-usb-audio: probe of 1-1:1.1 failed with error -5
> [  374.881649] snd-usb-audio: probe of 1-1:1.2 failed with error -5
> [  374.887654] snd-usb-audio: probe of 1-1:1.3 failed with error -5
> [  374.895366] usbcore: registered new interface driver snd-usb-audio
>
> Sidenote - While I don't have a midi device to test with, it would
> appear that the midi portion registers correctly and is accessible (at
> least through amidi and aplaymidi)
>
> On 04/19/2012 04:53 AM, Clemens Ladisch wrote:
> > Chris Cavey wrote:
> >>   snd-usb-audio: probe of 1-1:1.1 failed with error -5
> >>   snd-usb-audio: probe of 1-1:1.2 failed with error -5
> >>   snd-usb-audio: probe of 1-1:1.3 failed with error -5
> > Are there no other messages immediately before this?
> >
>
that looks like a snippet on unload can I have another 10 lines either side?

  reply	other threads:[~2012-04-19 11:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 12:37 M-Audio FastTrack C400 Chris Cavey
     [not found] ` <CACckToXF6yW+GzhzJ3zVBKi3e+thwrpDVnFmMCtjQOqePuixZg@mail.gmail.com>
     [not found]   ` <4F8DF29B.9090907@rauros.net>
2012-04-18  1:12     ` Grant Diffey
2012-04-18  7:26       ` Clemens Ladisch
2012-04-19  2:01         ` Chris Cavey
2012-04-19  7:58           ` Chris Cavey
2012-04-19  8:53           ` Clemens Ladisch
2012-04-19 10:26             ` Chris Cavey
2012-04-19 11:09               ` Grant Diffey [this message]
2012-04-19 11:19                 ` Chris Cavey
     [not found]                   ` <CACckToXHxm0y28ir+HGjE+Wug9PusHdrOeJpb3zQAFgQLjdP5w@mail.gmail.com>
2012-04-19 19:47                     ` Chris Cavey
2012-04-20  7:54             ` Daniel Mack
2012-04-21  1:29               ` Chris Cavey
2012-04-21  8:10                 ` Felix Homann
2012-04-21  8:48                   ` Felix Homann
2012-04-21  9:19                   ` Grant Diffey
2012-04-21 16:07                     ` Chris Cavey
2012-04-29  3:09                     ` Chris Cavey
2012-04-29  6:51                       ` Felix Homann
2012-04-29 13:30                         ` Chris Cavey
2012-05-02 10:05                           ` Felix Homann
2012-05-02 20:44                             ` Chris Cavey
2012-05-03 14:58                               ` Felix Homann
2012-05-04  4:54                                 ` Chris Cavey
2012-05-04  8:26                                   ` Felix Homann
2012-05-04 22:42                                     ` Chris Cavey
2012-05-05  7:05                                       ` Felix Homann
2012-05-09  1:11                                         ` Chris Cavey
2012-05-09  8:33                                           ` Felix Homann
2012-08-18 17:47       ` Mudwalker
2012-11-02 16:11 Raphael Souza

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='CACckToWQr=XBNH+p+twGzKQscjZs5WyG3jazJ79x9jpU=DteGg@mail.gmail.com' \
    --to=gdiffey@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=chris-alsa@rauros.net \
    /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.