Fixed in Feisty.
** Changed in: alsa-driver (Ubuntu)
Assignee: (unassigned) => Daniel T Chen
Status: Unconfirmed => Fix Released
--
Audio system in Dapper
https://launchpad.net/bugs/46787
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
** Changed in: Ubuntu
Sourcepackagename: None => alsa-driver
--
Audio system in Dapper
https://launchpad.net/bugs/46787
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
There's a better way to solve this, though I don't recall precisely how.
Basically there's a way to tell alsa that this device can't ever be the
default device.
--
Audio system in Dapper
https://launchpad.net/bugs/46787
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
I think i have the solution for me;
I added "saa7134_alsa" to the blacklist in /etc/modprobe.d/blacklist
because then the tv card is no longer known as primary soundcard.
--
Audio system in Dapper
https://launchpad.net/bugs/46787
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
I think i know now where the problem is!
I saw that when I was configuring my own kernel.
Device Drivers → Multimedia Devices → Video Capture Adapters
the point "Philips SAA7134 DMA audio support" should be turn off,
because if this point is activated; dapper thinks this is an sound card
and set
