*** This bug is a duplicate of bug 584844 ***
https://bugs.launchpad.net/bugs/584844
** This bug has been marked a duplicate of bug 584844
Lucid upgrade: No sound after wakeup from standby
--
Lucid upgrade: No sound after wakeup from standby
https://bugs.launchpad.net/bugs/578660
You rece
Tobias, please file a separate bug against alsa-driver. Yours isn't
pulseaudio-related.
--
Lucid upgrade: No sound after wakeup from standby
https://bugs.launchpad.net/bugs/578660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
I solved my issue! Put in /etc/modprobe.d/alsa-base.conf the following line:
-%<-
options snd-hda-intel model=dell-bios
-%<-
--
Lucid upgrade: No sound after wakeup from standby
https://bugs.launchpad.net/bugs/578660
You received this bug notification because you are a member of U
Romano, also removing ~/.pulse does not solve my issue. Still no sound
at all after wakeup. Has anybody more hints?
--
Lucid upgrade: No sound after wakeup from standby
https://bugs.launchpad.net/bugs/578660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Romano, your tip using a alsactl does not work for me:
-%<-
tob...@tobias-xps:~$ alsactl init
Unknown hardware: "HDA-Intel" "SigmaTel STAC9228"
"HDA:83847616,1028022e,00100402" "0x1028" "0x022e"
Hardware is initialized using a guess method
-%<-
Still no sound afterwakeup.
--
Luci
Hmm, I suppose I do not know where to look and what to look for, but if
you need something, tell me and I'll execute. And no, no bios update to
this laptop.
Another point. I discovered how that to make my mics work again (see
bug#579557 with more data): removing $HOME/.pulse directory and
rebootin
Not impossible, rather what you're seeing is the complex interaction of
subsystems claiming (and interacting with) resources. Have you carefully
examined dmi and dmesg information? Was there a bios update involved?
--
Lucid upgrade: No sound after wakeup from standby
https://bugs.launchpad.net/bu
I really don't know what are you meaning here... I remember doing tests years
ago, and the submitted a line to Takashi with the automatic selection of the
toshiba model for my laptop. Since then, all was working without having to add
parameters to the module.
Then now in Lucid I need the parame
On Wed, May 12, 2010 at 6:44 PM, Romano Giannetti
wrote:
> but the mics are still not here. I really am puzzled. I myself submitted
> the DMI info to automatically select the model *ages* ago to the alsa
> dev list, and it workd alone, and now this...
Are you *certain* it was the correct model qu
The problem with no sound after resume was resolved by putting
options snd-hda-intel model=toshiba
in /etc/modprobe.d/alsa-base.conf
but the mics are still not here. I really am puzzled. I myself submitted
the DMI info to automatically select the model *ages* ago to the alsa
dev list, and it wor
Me too. Intel HDA chipset. I have sound, but no mics, after bootup. No
sound at all after resume from suspend-to-ram.
If I do a
(0)rukbat:~% alsactl init
Unknown hardware: "HDA-Intel" "Realtek ALC268" "HDA:10ec0268,1179ff50,0013
HDA:11c11040,11790001,00100200" "0x1179" "0xff50"
Hardware is i
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/48257055/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/48257056/ArecordDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48257057/BootDmesg.txt
**
12 matches
Mail list logo
