Newcomer
Here we go:
rpm -qa | grep alsa
alsa-oss-1.0.15-48.1
alsa-utils-1.0.16-35.1
alsa-driver-kmp-pae-1.0.16.20080707_2.6.25.5_1.1-1.1
alsa-1.0.16-39.1
alsa-driver-unstable-kmp-pae-1.0.16.20080704_2.6.25.5_1.1-1.1
alsa-plugins-1.0.16-57.1
alsa-firmware-1.0.16-24.1
alsa-plugins-pulse-1.0.16-57.1
-------------------------------------------------------------
rpm -qa | grep pulse
libpulse-browse0-0.9.10-26.1
pulseaudio-module-lirc-0.9.10-26.1
libpulse0-0.9.10-26.1
pulseaudio-esound-compat-0.9.10-26.1
libpulsecore4-0.9.10-26.1
gstreamer-0_10-pulse-0.9.7-42.pm.1
pulseaudio-module-zeroconf-0.9.10-26.1
pulseaudio-module-bluetooth-0.9.10-26.1
libpulse-mainloop-glib0-0.9.10-26.1
pulseaudio-module-gconf-0.9.10-26.1
pulseaudio-utils-0.9.10-26.1
pulseaudio-0.9.10-26.1
alsa-plugins-pulse-1.0.16-57.1
pulseaudio-module-x11-0.9.10-26.1
-------------------------------------------------------------
rpm -q libasound2
libasound2-1.0.16-39.1
-------------------------------------------------------------
cat /etc/modprobe.d/sound
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
-------------------------------------------------------------
Please, IMHO trying to play a file with a proprietary codec (ie an mp3) is not the best test to see if your overall system has sound. It is too specific. Instead, please copy and paste the following into a konsole and use it as your test:
speaker-test -c2 -Ddefault -l5 -twav
From your posts above I see you tried that sort of konsole "speaker-test" before, and I urge you to keep doing that sort of test each time you want to test your system sound. We can solve any kaffeine mp3 playing issues later.
Thank you for the various command outputs. That looks good (except for /etc/modprobe.d/sound file). Note when your run alsaconf or YAST>HARDWARE>SOUND it will wipe out any custom settings you may have entered in your /etc/modprobe.d/sound file. So if you get a setting in that file that works, do NOT run alsaconf nor YAST>HARDWARE>SOUND.
Ok, did you try the edits from the post above, post#4 with ALC883/888 options possibly applicable to an ALC889 to your /etc/modprobe.d/sound file (where we noted that the ALC883/888 options may work for an ALC889 (which you have in your Acer Aspire 6920G) ??
Also, IMHO the /etc/modprobe.d/sound file above is what you get after running alsaconf. We can try edit that variant, although it may be that is not a good baseline, and it may be better to try this after YAST>HARDWARE>SOUND.
anyway, please add the line "options snd-hda-intel model=auto" to the end of that file, ie try:then restart your alsa with "rcalsasound restart" and test your sound. Be certain to check your mixer as it could have been reset.Code:alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel options snd-hda-intel model=auto
If that fails, instead of "auto" you could try "acer" and if that fails "acer-aspire".
And if that fails, go to yast and try YAST>HARDWARE>SOUND and try configure your sound card (which will create a different /etc/modprobe.d/sound file) and then using that newly created sound file as a baseline, add the line "options snd-hda-intel model=auto" at the end of the file as noted above, restart your alsa, and continue testing again, as above.
Newcomer
dear friends,
iam following this topic with great interest.
i have also a 6920g and like to install it for a testproject an a mac emulation. sound problem is the same and it looks even other have probs with that 889 in the acer, looks a bit different than the usual alc 889 drivers.
when u get it run, u may tell me whats the different to the regular 889 drivers and may with luck i can use that information to bring my system run in my emulation.
thanks and fine regards
chris
Newcomer
Dear All
I too have been following this with great interest. I have an acer aspire 5920.
I had a similar problem after installing SUSE 11 i.e. no audio from the laptop speakers.
You have probably already tried this but this fixed it for me:-
I installed the alsa-utils as suggest (thanks oldcpu ;-))
I then launched the volume control from the start menu (or gnome-volume-control from xterm).
After much messing around I found that for some reason the laptop speakers had been assigned the "surround" channel. This is hidden and muted by default.
To access it, in the volume application select edit -> preferences.
check the "surround" option and close the preferences window.
Unmute the option and raise the volume level. Try the following command again to test:-
speaker-test -c2 -Ddefault -l5 -twav
I then had sound. I've yet to figure out how to get the volume appelet to launch gnome-volume-control as default but that is another thread ;-)
BTW thanks to all on the Forums
Newcomer
I have been having the same issues with sound on my ASUS Laptop, i have managed to sort it by editing /etc/modprobe,d/sound
options snd slots=snd-hda-intel
options snd-hda-intel model=hp
# u1Nb.ULiNFUWt9WF:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
I now have sound from the speakers but not the headphones, its a start, I hope this helps someone
Newcomer
I had the same problem with Intel ICH8 family on my laptop Asus F9S.
I installed Alsa 1.0.17.git20080715-1.1 putting the option "lenovo" instead of "auto".
It seems that the word "lenovo" is the magic solution.
Note that there are many possible options that one can put in the /etc/modprobe.d/sound file. But one needs to put the option that is specific to their hardware, and often no two laptops are alike. For example, if one looks at the ALSA-Configuration.txt file for the lastest (as of today I think) 1.0.18RC1 of the alsa driver, various audio codecs are as follows (with each of them having a different model options that can be applied):
ALC880, ALC260, ALC262, ALC267/268, ALC269, ALC662/663, ALC882/885, ALC883/888, ALC861/660, ALC861VD/660VD, CMI9880, AD1882, AD1884A / AD1883 / AD1984A / AD1984B, AD1884, AD1981, AD1983, AD1984, AD1986A, AD1988/AD1988B/AD1989A/AD1989B, Conexant 5045, Conexant 5047, Conexant 5051, STAC9200, STAC9205/9254, STAC9220/9221, STAC9202/9250/9251, STAC9227/9228/9229/927x, STAC92HD71B*, STAC92HD73*, STAC9872
I copied the latest alsa 1.0.18 RC1 here:
general pastebin - ALSA-Configuration.txt - post number 1198249
(paste good for 1 year).
So as you can see, stating one has a specific model option applied, often only is directly useful if one also states what hardware audio codec is in use. Else one has to check the ALSA-Configuration.txt file.
As an example, searching the ALSA-Configuration.txt file, one can see that the model option "lenovo" (of that exact syntax) is only applicable to the ALC861VD/660VD for 1.0.18 RC1 of alsa. Different alsa versions may be slightly different.
Bookmarks