This fix has now been committed upstream. Herton has announced in
stable-queue for 3.5, and I got an email from someone who wanted to
backport it to 3.2, so it will reach stable kernels in some time.
** Package changed: alsa-driver (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
It was on 3.2.0-35-generic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1095315
Title:
[USB-Audio - FastTrack Pro, recording] No sound at all
Status in “alsa-driver” package
Hi djfun,
Just a quick question - when you tested my patch, was that on top of a
3.2 kernel or a later kernel?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1095315
Title:
On 01/04/2013 05:02 PM, David Henningsson wrote:
A patch in the 3.2 kernel caused regression with hotplugging the
M-Audio Fast track pro, or sound after suspend. I don't have the
device so I haven't done a full analysis, but it seems userspace
(both udev and pulseaudio) got confused when a
** Patch added:
0001-ALSA-usb-fix-race-in-creation-of-MAudio-Fast-track-p.patch
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1095315/+attachment/3473909/+files/0001-ALSA-usb-fix-race-in-creation-of-MAudio-Fast-track-p.patch
--
You received this bug notification because you are
Looking a bit at the snd_usb_fasttrackpro_boot_quirk function, it calls
usb_driver_set_configuration, which has the following comment:
* Device interface drivers are not allowed to change device configurations.
* This is because changing configurations will destroy the interface the
*
The patch works. I get sound from the analog inputs when I have device-
strings = hw:%f,1,0 hw:%f,0,0 or only hw:%f,1,0 in my maudio-fasttrack-
pro.conf now.
I'll attach the output in syslog after the patch and the output of lsusb
-v
--
You received this bug notification because you are a
** Attachment added: syslog_output_after_patch.log
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1095315/+attachment/3473929/+files/syslog_output_after_patch.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: lsusbv.txt
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1095315/+attachment/3473930/+files/lsusbv.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1095315
Title:
[USB-Audio - FastTrack Pro, recording] No sound at all
Status in “alsa-driver” package in
I'm suspecting that ,0,0 records from SPDIF in your case and ,1,0 from
analog. If so we could just try ,1,0 first and then ,0,0, i e the string
becomes hw:%f,1,0 hw:%f,0,0
The question is if it is the other way around for other Fasttrack Pro
devices, so this would regress behaviour for them. It
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=0f5733b0c883158b13366ae34b5e4bd52a1ac346
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1095315
Title:
After I read a bit through the changes Raymond linked in #9, I downloaded a
snapshot of the alsa sources, changed the function
static int snd_usb_fasttrackpro_boot_quirk(struct usb_device *dev) in
sound/usb/quirks.c to always return 0, compiled and installed alsa. Then, after
reloading the
you have to send email to the author of the patch
i think the usage of the parameter device_setup should be put in
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=blob;f=Documentation/sound/alsa
/ALSA-
Configuration.txt;h=b9cfd339a6fa3d4e89cebb3316e5152f9ff0d252;hb=HEAD
and 0x80 is
http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/src/modules/alsa/mixer
/profile-sets/maudio-fasttrack-pro.conf
if it work with pulseaudio 0.9.x version
you have to send email to the author of these patches and the pulseaudio
mailing list why it fail at pulseaudio 2.0
--
You received this
22.631445] thinkpad_acpi: disagrees about version of symbol snd_ctl_add
[ 22.631449] thinkpad_acpi: Unknown symbol snd_ctl_add (err -22)
[ 22.631506] thinkpad_acpi: disagrees about version of symbol
snd_card_register
[ 22.631509] thinkpad_acpi: Unknown symbol snd_card_register (err -22)
[
Thanks! With device-strings = hw:%f,1,0 in my maudio-fasttrack-pro.conf
it works now. In earlier versions of Ubuntu I needed the hw:%f,0,0
hw:%f,1,0 from the patch of David Henningsson. I will send him an email
about it.
--
You received this bug notification because you are a member of Desktop
One other question: is the maudio-fasttrack-pro.conf being used by alsa
or why could I not record with deactivated pulseaudio?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1095315
With device-strings = hw:%f,1,0 in my maudio-fasttrack-pro.conf it
works now.
So, first it was hw:%f,0,0, then it became hw:%f,0,0 hw:%f,1,0 and
now you're proposing we change it to just hw:%f,1,0, is that correct?
What I'm afraid of is that there might be more than one model out there,
and
So, first it was hw:%f,0,0, then it became hw:%f,0,0 hw:%f,1,0 and
now you're proposing we change it to just hw:%f,1,0, is that correct?
The older 2 versions hw:%f,0,0 and hw:%f,0,0 hw:%f,1,0 at least do
not work here for me in Ubuntu 12.04 Precise. I can test these 2 with a
USB live system of
20 matches
Mail list logo
