Reinstalled and I have sound. Thank you for leading a grasshopper down
the right path!
--
Soundcard not detected (Actually driver not loaded because of symbol confusion)
https://bugs.launchpad.net/bugs/669731
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
In 2.6.23-24 cat /proc/asound/version indicates 1.0.21... Under
2.6.23-25 I have 1.0.23 which I believe I compiled myself, but I thought
I did it before the kernel update i.e. under 2.6.23-24.
It would make some sense that the updated kernel would lead to the
symbol confusion... I will try re-ins
Boot to 2.6.32-24 and sound OK. Phonon still won't recognize
Pulseaudio, but I have sound again.
--
Soundcard not detected (Actually driver not loaded because of symbol confusion)
https://bugs.launchpad.net/bugs/669731
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "fwiw alsa.sh output"
https://bugs.launchpad.net/bugs/669731/+attachment/1720209/+files/alsa-info.txt.oQINOZW1Ug
--
Soundcard not detected (Actually driver not loaded because of symbol confusion)
https://bugs.launchpad.net/bugs/669731
You received this bug notification b
Public bug reported:
The sound card is there, confirmed by 'lspci |grep -i sound', but when I
manually try to load via modprobe snd_ca0106 I get this error:
sudo modprobe snd_ca0106
WARNING: Error inserting snd_seq_device
(/lib/modules/2.6.32-25-generic/kernel/sound/acore/seq/snd-seq-device.ko):
** Attachment removed: "output from alsa-info.sh"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/619544/+attachment/1683405/+files/alsa-info%20output
--
[CA0106 - CA0106] ALSA test tone not correctly played back
https://bugs.launchpad.net/bugs/619544
You received this bug notifica
output from alsa-info.sh
** Attachment added: "output from alsa-info.sh"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/619544/+attachment/1683405/+files/alsa-info%20output
--
[CA0106 - CA0106] ALSA test tone not correctly played back
https://bugs.launchpad.net/bugs/619544
You re
~/.pulse
--
just upgraded from 9.04 to 9.10 no sound pulseaudio alsa-source snd_ca0106
https://bugs.launchpad.net/bugs/484614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Muting 'IEC958' does work, but only after I deleted ~.pulse. Thank you
for your help!
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
just upgraded from 9.04 to 9.10 no sound pulseaudio alsa-source snd_ca0106
https://bugs.launchpad.net/bugs/484614
You received this bug not
Also please note the syslog attachment including this line:
Nov 17 23:25:03 user-desktop pulseaudio[2551]: alsa-source.c: Most
likely this is a bug in the ALSA driver 'snd_ca0106'. Please report this
issue to the ALSA developers.
--
just upgraded from 9.04 to 9.10 no sound pulseaudio alsa-source
Hello-
I removed the files and used alsamixer to mute the IEC958 mixer. This
did not fix the issue.
I tried to restart alsa (/etc/init.d/alsa-utils restart)and got this:
* Shutting down ALSA... [ OK ]
* Setting up ALSA...
** Attachment added: "syslog"
http://launchpadlibrarian.net/35814095/syslog.log
** Attachment added: ".etc.asound.conf.txt"
http://launchpadlibrarian.net/35814096/.etc.asound.conf.txt
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/35814097/AlsaDevices.txt
** Attac
Public bug reported:
Sound worked fine before upgrade. I have Sound Blaster Live! 24-bit.
ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: jared 2551 F...m pulseaudio
/dev/snd/controlC0: jared 2551 F pulseaudio
/dev/sn
skrimpy-
If you run 'xsensors' and you get a tiny minimized-looking window that
is blank when you expand the bug is fixed. This is NOT the bug. This
simply means that you either don't have the sensors setup or they don't
exist for your hardware- try sudo sensors-detect as was mentioned. The
bug
see comment #28. I'm on Jaunty now but the fix worked fine for me on
Hardy. I believe it was a one line change involving the location of the
configuration file that determines which sensors should be used/polled.
--
[hardy] Error opening config file: /etc/sensors.conf
https://bugs.launchpad.net
I tested the the patch ( xsensors_0.50-1ubuntu3.diff.gz ) on my Hardy
machine using pbuilder and it fixed the issue without any new problems.
I would like to see this get submitted for an SRU, so I subscribed
ubuntu-universe-sponsors since I cannot upload. Hopefully that was the
correct next step
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.
--
no 5.1 sound on sound blaster live
https://bugs.launchpad.net/bugs/2
17 matches
Mail list logo
