no sound after installing Mandriva 2008, problem with ALSA
MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
no sound after installing Mandriva 2008, problem with ALSA
Hi everyone!
I've just installed Mandriva 2008 on my new Acer TravelMate 6291 laptop, along with Windows XP. Everything works like a charm except for the sound, and it seems pretty obvious that ALSA is the culprit.
First of all, I have no sound issue when I boot Windows.
Second of all, Mandriva has no problem detecting all the hardware, including the sound card, which is an Intel 82801G (ICH7 Family) High Definition Audio Controller; and the driver is present too: snd_hda_intel.
Third, during boot, I press Esc to see the details and I get this:
Code:
Alsa driver (version 1.0.14) is already running. Doing alsactl to mixer Settings :
Alsactl : get control : 209 : Cannot read control '2,0,0,Mic Boost,0' Invalid argument
Can't open /root/tmp/asound.state_tmp : No such file or directory.
Setting mixer settings alsactl : load-state : 1313 : Cannot open
/root/tmp/asound.state_tmp : No such file or directory
[FAILED]
Indeed, the asound.state file doesn't exist anywhere.
Apparently, the 82801G (ICH7 Family) High Definition Audio Controller sound card has been a pain to many, regardless of the Linux flavor.
Startup the Mandriva Control Centre (MCC), go to Hardware, click Browse and configure hardware, select your soundcard. Now look in the righthand pane. At the bottom where is says Alternative Drivers see what's listed there (if any) and try one of those.
Also, when I type the command alsactl in the Konsole, I get this:
Code:
alsamixer: function snd_mixer_load failed: Invalid argument
So looking around, I found this place "If alsamixer does not work:" and I suppose that the solution to my problem must be similar to this one. So my guess would be that if I wrote a file like the one being proposed there (but adapted for my hardware, which I don't know how to do that) and that I saved it as /root/tmp/sound.state_tmp then maybe it would work.
Just for fun, I tried it with their file and rebooted. During boot, the message I got now was:
Code:
Alsa driver (version 1.0.14) is already running. Doing alsactl to mixer Settings :
Alsactl : get control : 209 : Cannot read control '2,0,0,Mic Boost,0' Invalid argument
Setting mixer settings alsactl : no state present for card intel [FAILED]
Or maybe an easier solution would be to get version 1.0.15 of alsa driver and install it. I'll do that.
OK so apparently there's nothing to upgrade as practically everything is already at version 1.0.15-0.rc1. Also I forgot to mention it but it's Mandriva X86_64 that I have.
I think a step in the right direction has been taken here.
In /etc/modprobe.conf I added the following line :
Code:
options snd-hda-intel model=3stack
The result now is that I get a normal message at boot time :
Code:
Alsa driver (version 1.0.14) is already running. Doing alsactl to mixer Settings : [ OK ]
And ALSA commands have become usable. The only problem now is that I still don't have any sound yet. I'm wondering if there is something that is keeping the system mute.
Ok, apparently, the cause would be that there is a Realtek ALC268 sound chip that ALSA is having trouble with. The solution would be to patch alsa-driver and re-compile it.
I finally lost patience with my Mandriva install after finding other bugs, such a my USB sticks that were not mounted automatically, and decided to go with Fedora 7 instead. The sound problem was still there but I finally managed to solve it thanks to the solution mentioned above, which is posted here: http://paparadit.blogspot.com/2007/0...mate-6291.html
I post the link just in case that solution would work with Mandriva too. Could be useful for somebody.
I was going to say, and I am sure you already tried. but did you try typing alsaconf in Konsole? And when you open "alsamixer", did you check your sliders to see if they were up?
d-1
Quote:
Originally Posted by Iltbreg
Ok, apparently, the cause would be that there is a Realtek ALC268 sound chip that ALSA is having trouble with. The solution would be to patch alsa-driver and re-compile it.
I finally lost patience with my Mandriva install after finding other bugs, such a my USB sticks that were not mounted automatically, and decided to go with Fedora 7 instead. The sound problem was still there but I finally managed to solve it thanks to the solution mentioned above, which is posted here: http://paparadit.blogspot.com/2007/0...mate-6291.html
I post the link just in case that solution would work with Mandriva too. Could be useful for somebody.
Indeed dolphans1, I did try those two commands. I didn't know too much what to do with alsaconf but alsamixer was not showing anything wrong; the sliders were up. That's why I was wondering whether there was another way to check if the system was mute.
I believe that the way to solve that bug is to patch alsa-driver and recompile it. That's what made the sound work with Fedora 7, and I believe it shouldn't be much different for Mandriva 2008. The volume control is not perfect though, but I can live with it. I suppose that it's just a matter of waiting for the next update of alsa-driver, or the one after, for that bug to be dealt with once and for all.
Indeed dolphans1, I did try those two commands. I didn't know too much what to do with alsaconf but alsamixer was not showing anything wrong; the sliders were up. That's why I was wondering whether there was another way to check if the system was mute.
I believe that the way to solve that bug is to patch alsa-driver and recompile it. That's what made the sound work with Fedora 7, and I believe it shouldn't be much different for Mandriva 2008. The volume control is not perfect though, but I can live with it. I suppose that it's just a matter of waiting for the next update of alsa-driver, or the one after, for that bug to be dealt with once and for all.
Well thanks for the reply, I just know it works great here on my end, but then again I have an older box. AMD Athlon 1400 XP.....
I have this problem with every new version - here's my fix
Well, not mine, but I can't remember who to give proper credit to from two or three versions ago.
From your menu, under sound or multi-media, run volume control. (If your distro, like my new Mandriva 2008, doesn't have it it the menu, run gnome-volume-control from the "Run Command" in the start menu.
From here select the switches tab. Unclick the box "Audigy Analog/Digital Output Jack". Sit back and enjoy your tunes. Works every time for me.
"aumix -q" will tell you if the sound volume is muted or not
[root@localhost anabella]# aumix -q
vol 35, 35, P
pcm 74, 74
line 77, 77, P
mic 0, 0, R
cd 77, 77, P
pcm2 74, 74
igain 80, 80
line1 77, 77, P
dig1 0, 0
phin 77, 77, P
phout 74, 74, P
video 100, 100, P
[root@localhost anabella]#
"/sbin/fuser -v /dev/dsp" will tell which program uses the sound card.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.