https://bugs.freedesktop.org/show_bug.cgi?id=39664
Colin Guthrie <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Colin Guthrie <[email protected]> 2011-07-30 08:13:51 PDT --- Hi Antonio, Thanks for the bug report. Would it be possible to get us a better log from PA. The details in the syslog are pretty sparse, so if you could disable autospawning via: "echo autospawn=no >>~/.pulse/client.conf" and then run PA manually on the command line via "pulseaudio -vvvvv" then it should give you a lot more info which could help. I suspect that the trick here will be to write a specific profile for this device (it's quite specialised after all) which will then be able to give the right names to the devices. Note however, that our channel names are relatively fixed (they have to be so that sounds can be mapped to channels properly) and thus you may not be able to get the perfect names here. http://pulseaudio.org/wiki/WritingProfiles In addition to the the debug output please also supply: 1. amixer -c1 (where 1 is the card number - cat /proc/adound/cards) 2. pacmd ls (when the device is working properly - perhaps after restarting PA) Note that even when PA is restarted, udev is used to detect things. I suspect the problem of it not showing up is related to some kind of race condition. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
