no 5.1 sound on sound blaster live

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add the output requested in the Reporting Sound Bugs section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments? Thanks in advance.

 2.6.24-16-generic

Do you notice this with every application? Additionally, could you try testing this via 'aplay -Dplug:surround51 /usr/share/sounds/*up.wav'? Thanks again.

yes with every application.

andrei@andrei-desktop:~$ aplay -Dplug:surround51 /usr/share/sounds/*up.wav
aplay: main:546: audio open error: Device or resource busy
andrei@andrei-desktop:~$

http://ph.ubuntuforums.com/showthread.php?s=1624d7a5cf7d26ee1f34a9bf732a92cd&t=161817&page=3

Adding the change to ~/.asoundrc worked for me. I have Sound Blaster Live! 24-bit ( CA0106 ) working in 7.1 through alsa in Hardy.

The Intrepid Ibex 8.10 Alpha2 is scheduled for release today. It will appear at the following when available: http://www.ubuntu.com/testing/intrepid/alpha2 . It contains the actively developed 2.6.26 Ubuntu kernel. It would be great if you could test this upcoming release via a LiveCD and verify if the issue still exists without the ~/.asoundrc fix.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.