*** This bug is a duplicate of bug 692029 ***
https://bugs.launchpad.net/bugs/692029
Same scenario: ASUS P8H67-M Pro w/i3-2105: "ALC892: BIOS auto-probing.
Too many connections", if HD disabled in BIOS no error but no sound
either.
--
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 692029 ***
https://bugs.launchpad.net/bugs/692029
** This bug has been marked a duplicate of bug 692029
[Realtek ALC892] ALSA test tone not correctly played back
* You can subscribe to bug 692029 by following this link:
https://bugs.launchpad.net/ubuntu/
This bug seems to be the same as #692029.
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/692029
I'm not sure which of the two reports should be marked as a duplicate of
the other though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
More discussion of this problem ("Too many connections" error, and no sound
output on Realtek ALC892) is here:
http://ubuntuforums.org/showthread.php?t=1635278
Here
http://www.linuxforums.org/forum/gaming-multimedia-entertainment/168732-solved-no-sound-alsa-except-microphone.html
someone seems to
I have an Asus P8P67 Pro motherboard with this sounds chip.
I was getting the error "Too Many Connections" on boot, I read that if
you made the audio AC97 and not HD then it would solve the problem. It
did - though I got some crackling on audio.
I then (for some unknown reason) disabled audio com
Using today's mainline kernel (2.6.38-999-generic #201103011141) I don'
t see this message anymore, however this doesn' t help with my original
sound issue (Bug #722294).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
There is mention of this problem here:
http://marc.info/?l=linux-kernel&m=129072236030208&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720799
Title:
"Too many connections" error on boot caused