From: Andrzej Giniewicz <gginiu@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Sound got mute in kernel 3.5.4 (Fast Track Pro USB Sound Card), found commit that causes it - how to proceed?
Date: Thu, 20 Sep 2012 18:33:33 +0200 [thread overview]
Message-ID: <505B455D.2040603@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hello,
today I updated kernel to 3.5.4 and noticed, that all my sound from Fast
Track Pro USB Sound Card got mute. I haven't noticed any error reports
or messages, all seems to work, the card is just silent. I downgraded to
3.5.3 and applied patched from usb sound module one by one and found
out, that 3.5.4 minus " ALSA: snd-usb: fix calls to next_packet_size "
works fine:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=ca150f7ade5973c3bce19261bca6174d5c3cc342
Does this change require some update of configuration I missed?
There are some informations about device from lsusb:
http://pastie.org/private/odiuw0ve3iszdat9mwpa
My system runs 64 bit Arch Linux, there is config used by it:
https://projects.archlinux.org/svntogit/packages.git/plain/trunk/config.x86_64?h=packages/linux&id=59ae346478ff01f0d2dc47b04a3a1297046b1900
How can I proceed with this issue? Any more information I can provide to
help in solving this?
Thank you,
Andrzej Giniewicz.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 551 bytes --]
next reply other threads:[~2012-09-20 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 16:33 Andrzej Giniewicz [this message]
2012-09-22 9:14 ` Sound got mute in kernel 3.5.4 (Fast Track Pro USB Sound Card), found commit that causes it - how to proceed? Andrzej Giniewicz
2012-09-24 13:05 ` Andrzej Giniewicz
2012-09-28 13:00 ` Dan Carpenter
2012-10-06 16:23 ` Andrzej Giniewicz
2012-10-08 7:50 ` 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=505B455D.2040603@gmail.com \
--to=gginiu@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.