From: Cyrus Harmon <cyrus@bobobeach.com>
To: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] add Steinberg UR44 USB Audio Interface support to quirks-table
Date: Mon, 2 Feb 2015 23:14:56 -0800 [thread overview]
Message-ID: <54D07570.8040703@bobobeach.com> (raw)
In-Reply-To: <54674E72.4070607@ladisch.de>
On 11/15/2014 05:00 AM, Clemens Ladisch wrote:
> (Sorry for the delay.) Cyrus Harmon wrote:
>> [ 2.978159] snd-usb-audio 3-3.2:1.1: probe step 2 [ 2.978334]
>> snd-usb-audio 3-3.2:1.1: probe failed
> Still mysterious. Please try with this patch instead.
(Sorry for yet another delay)
I'm not sure the debugging patch here was properly applied/installed,
but I think so. In any event, perhaps with this patch, and definitely
for your previous 2 patches, updated for the 3.19-rc7 sources, I get the
following errors when I try to load snd-usb-aduio:
[ 294.270316] snd-usb-audio 1-3.2:1.0: checking PCM interface
[ 294.270319] snd-usb-audio 1-3.2:1.0: quirk return code: -19
[ 294.270321] snd-usb-audio 1-3.2:1.0: probe failed
[ 294.270773] snd-usb-audio 1-3.2:1.1: checking PCM interface
[ 294.270775] snd-usb-audio 1-3.2:1.1: altsets found
[ 294.270776] snd-usb-audio 1-3.2:1.1: endpoint found
[ 294.270778] snd-usb-audio 1-3.2:1.1: iso found
[ 294.270779] snd-usb-audio 1-3.2:1.1: descriptors found
[ 294.272941] snd-usb-audio 1-3.2:1.1: first interface successful
[ 294.272943] usb 1-3.2:1.0: checking PCM interface
[ 294.272945] usb 1-3.2:1.2: checking PCM interface
[ 294.272946] usb 1-3.2:1.2: altsets found
[ 294.272947] usb 1-3.2:1.2: endpoint found
[ 294.272948] usb 1-3.2:1.2: iso found
[ 294.272949] usb 1-3.2:1.2: descriptors found
[ 294.275044] snd-usb-audio 1-3.2:1.2: interface 2 successful
[ 294.275047] usb 1-3.2:1.3: checking PCM interface
[ 294.275056] snd-usb-audio 1-3.2:1.3: interface 3 successful
[ 294.275057] usb 1-3.2:1.4: checking PCM interface
[ 294.275065] snd-usb-audio 1-3.2:1.4: interface 4 successful
[ 294.275066] snd-usb-audio 1-3.2:1.4: create_autodetect_quirks successful
[ 294.275067] snd-usb-audio 1-3.2:1.1: quirk return code: 0
[ 294.275068] snd-usb-audio 1-3.2:1.1: probe step 2
[ 294.275297] snd-usb-audio 1-3.2:1.1: probe failed
[ 294.275465] snd-usb-audio: probe of 1-3.2:1.1 failed with error -16
[ 294.275490] usbcore: registered new interface driver snd-usb-audio
[ 294.276043] systemd-udevd[4350]: Failed to apply ACL on
/dev/snd/pcmC3D0p: No such file or directory
[ 294.276047] systemd-udevd[4350]: Failed to apply ACL on
/dev/snd/pcmC3D0p: No such file or directory
[ 294.276164] systemd-udevd[4348]: Failed to apply ACL on
/dev/snd/controlC3: No such file or directory
[ 294.276169] systemd-udevd[4348]: Failed to apply ACL on
/dev/snd/controlC3: No such file or directory
[ 294.276219] systemd-udevd[4353]: Failed to apply ACL on
/dev/snd/pcmC3D0c: No such file or directory
[ 294.276223] systemd-udevd[4353]: Failed to apply ACL on
/dev/snd/pcmC3D0c: No such file or directory
[ 294.276802] systemd-udevd[4354]: Failed to apply ACL on
/dev/snd/midiC3D0: No such file or directory
[ 294.276806] systemd-udevd[4354]: Failed to apply ACL on
/dev/snd/midiC3D0: No such file or directory
So the call that must be failing is:
err = snd_card_register(chip->card);
and of course this all works with the quirks table modified for the
ur44. I'm at a loss. Any further debugging suggestions would be greatly
appreciated.
thanks,
Cyrus
> Regards, Clemens --- a/sound/core/pcm.c +++ b/sound/core/pcm.c @@
> -1086,6 +1086,7 @@ static int snd_pcm_dev_register(struct snd_device
> *device) mutex_lock(®ister_mutex); err = snd_pcm_add(pcm); if (err)
> { + printk(KERN_ERR "snd_pcm_add(%d) failed\n", pcm->device);
> mutex_unlock(®ister_mutex); return err; } @@ -1115,6 +1116,7 @@
> static int snd_pcm_dev_register(struct snd_device *device)
> &snd_pcm_f_ops[cidx], pcm, str, dev); if (err < 0) { + dev_err(dev,
> "snd_register_device_for_dev failed: %d\n", err);
> list_del(&pcm->list); mutex_unlock(®ister_mutex); return err;
next prev parent reply other threads:[~2015-02-03 7:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 18:12 [PATCH] add Steinberg UR44 USB Audio Interface support to quirks-table Cyrus Harmon
2014-03-10 9:42 ` Takashi Iwai
2014-03-10 12:07 ` Clemens Ladisch
2014-03-10 15:26 ` Cyrus Harmon
2014-03-10 15:30 ` Takashi Iwai
2014-03-10 15:40 ` Clemens Ladisch
2014-03-11 6:33 ` Cyrus Harmon
2014-03-11 8:31 ` Clemens Ladisch
2014-03-11 9:30 ` Cyrus Harmon
2014-03-17 16:29 ` Cyrus Harmon
2014-11-04 0:36 ` Cyrus Harmon
2014-11-04 6:28 ` Takashi Iwai
2014-11-04 8:55 ` Cyrus Harmon
2014-11-05 23:14 ` Takashi Iwai
2014-11-06 4:39 ` Cyrus Harmon
2014-11-06 5:28 ` Vlad Catoi
2014-11-06 5:32 ` Cyrus Harmon
2014-11-06 13:46 ` Vlad Catoi
2014-11-04 8:59 ` Clemens Ladisch
2014-11-04 9:00 ` Clemens Ladisch
2014-11-05 18:16 ` Cyrus Harmon
2014-11-05 21:17 ` Clemens Ladisch
2014-11-06 5:47 ` Cyrus Harmon
2014-11-15 13:00 ` Clemens Ladisch
2015-02-03 7:14 ` Cyrus Harmon [this message]
2014-11-06 16:05 ` Cyrus Harmon
2014-11-06 16:49 ` Takashi Iwai
2014-11-06 16:54 ` Cyrus Harmon
2014-11-08 4:24 ` Vlad Catoi
2014-11-08 4:25 ` Vlad Catoi
2015-02-03 6:56 ` Cyrus Harmon
2015-02-03 9:02 ` Takashi Iwai
2014-11-06 17:32 ` Clemens Ladisch
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 15:37 Cyrus Harmon
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=54D07570.8040703@bobobeach.com \
--to=cyrus@bobobeach.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox