Lenovo Ideapad Y510 Sound

have installed 10.3 on a lenovo y510 ideapad. sound was detected as snd-hda-intel, and for the most part it works. this machine does have a sub-woofer and i don't get an lfe slider in the sound apps. also don't believe all of the sound features are working (i did not boot vista to see what it did.) when searching for a solution, the ubuntu folks have said to append model=lenovo-ms7195-dig to the sound options statement. when i tried this, the speakers began to squeal and the system locked up. probably different versions of alsa.

has anyone been able to get all the sound features to work on this laptop?


thanks.

Cut and paste from oldcpu

Did you install alsa-firmware? Did you try yast? alsaconf? edit your /etc/modprobe.d/sound with various options? ....

How about trying to work your way through the audio troubleshooting guide:
http://en.opensuse.org/AudioTroubleshooting

... and if nothing else, post the output URL from the two diagnostic scripts:
http://en.opensuse.org/AudioTroubles...ed_information
... such that we can check if you made a mistake in your configuration/setup.

Also, it would help if you posted here the contents of your /etc/modprobe.d/sound file.[/b]

i have not installed alsa-firmware. it is my understanding that this is not required for hda compliant sound systems. please correct me if i'm wrong.

i have not tried any additional options than the one mentioned earlier. there seem to be several and i can't determine which one is correct.

options snd-hda-intel enable=1 index=0
# u1Nb.xvbr5hti0dD:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel

http://pastebin.ca/945159

i have not installed alsa-firmware. it is my understanding that this is not required for hda compliant sound systems.[/b]

who knows? I don't for sure. I don't think so, but I don't know for certain. Do you? I won't bet money on it (I hate betting). It probably is not needed, but installing it probably does not hurt. I'm not a believer in wasting dozens of hours trying to find the optimal solution. Instead, if I think it might be useful, I simply install the application (making note of what I installed). We are not talking GBytes of wasted space here.

I hate being in the position of not installing an application, banging my head for dozens of hours 'cause the app that I thought was not needed, was indeed needed. But thats just me. I probably learn less as a result, but I also save time.

Hey its your call. Its your time that gets spent. Like you note, alsa-firmware "probably" is not needed.

i have not tried any additional options than the one mentioned earlier. there seem to be several and i can't determine which one is correct.[/b]

well, some are more obvious than most. Some common sense needs to be applied. I'll try to give you some hints, but ULTIMATELY you have to try some. I definitely would NOT blindly apply some solution, ... not at least checking with the ALSA-Configuration.txt file (that IS on your computer) to see if it even makes sense.

options snd-hda-intel enable=1 index=0
# u1Nb.xvbr5hti0dD:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel[/b]

Many thanks. That is helpful.

http://pastebin.ca/945159[/b]

Thanks! Posting that script saves dozens of questions.

I see from the script you have a 32-bit openSUSE-10.3, and you have never applied any of the recommended security fixes to your SUSE kernel. I see your laptop has an ALC883 codec.

I note you have alsa-1.0.14. For alsa-1.0.14, the following options are possible in your /etc/modprobe.d/sound file as a "model" option:

****ALC883/888
******3stack-dig****3-jack with SPDIF I/O
******6stack-dig****6-jack digital with SPDIF I/O
******3stack-6ch****3-jack 6-channel
******3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
******6stack-dig-demo**6-jack digital for Intel demo board
******acer********Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
******medion****Medion Laptops
******medion-md2****Medion MD2
******targa-dig****Targa/MSI
******targa-2ch-dig****Targs/MSI with 2-channel
******laptop-eapd** 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
******lenovo-101e****Lenovo 101E
******lenovo-nb0763****Lenovo NB0763
******lenovo-ms7195-dig Lenovo MS7195
******6stack-hp****HP machines with 6stack (Nettle boards)
******3stack-hp****HP machines with 3stack (Lucknow, Samba boards)
******auto********auto-config reading BIOS (default)

You could try in your /etc/modprobe.d/sound file:

options snd-hda-intel enable=1 index=0 model=lenovo-ms7195-dig
# u1Nb.xvbr5hti0dD:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel

Which was the Ubuntu recommendation. Then restart your alsa in an xterm/konsole with:
<span style="font-family:Courier New">rcalsasound restart</span>
... and then test your sound (don't forget to check your mixer).

If that doesn't work, instead of "lenovo-ms7195-dig" try "lenovo-101e". Restart your alsa, test your sound. If that doesn't work, then try (one at at time, restarting alsa between each attempt, and testing sound between each attempt) "lenovo-nb0763", "laptop-eapd", ... etc ....

Now I also did a search on your ALC883 (per the audio troubleshooting guide) to see if there were any updates to the ALC883 between alsa 1.0.14 and alsa 1.0.16, and there were:
http://www.alsa-project.org/main/index.php...LC883&go=Go
... with the following options being added to the ALSA-Configuration.txt file.

acer-aspire****Acer Aspire 9810
haier-w66****Haier W66
6stack-dell****Dell machines with 6stack (Inspiron 530)
mitac**********Mitac 8252D

None of them appear applicable to your lenovo, but its possible the underlying alsa code has been improved for your Lenovo. If it were me, and the model=something entry in the /etc/modprobe.d/sound file did not work, I would update alsa, and after updating try the various lenovo options again in the /etc/modprobe.d/sound file. But thats just me.

In case you do decide to update alsa, since you have the un-updated kernel (with out the security fixes) you will need to use a different zypper command than is in the audio troubleshooting guide. In your case with the less secure kernel you will need to run (in an xterm/konsole with root permissions):

zypper ar http://download.opensuse.org/reposit...openSUSE_10.3/ multimedia-audio-old-kernel******
zypper install alsa alsa-driver-kmp-default alsa-utils alsa-tools alsa-firmware
zypper rr http://download.opensuse.org/reposit...openSUSE_10.3/

You can skip the alsa-firmware update, if you are happy its not needed. I suspect you don't want to lose that 3.0 MBytes of space.

Note if you update alsa, get your sound working, and then update your kernel, you could find your sound functioning strange again (or even broken). The alsa versions on that site are specific to certain kernel versions.

Also note if you do a hand edit to the /etc/modprobe.d/sound file (like I am recommending) then do NOT run alsaconf nor yast>hardware>sound as that WILL wipe out your custom /etc/modprobe.d/sound file settings.

Good luck.

the ubuntu folks have said to append model=lenovo-ms7195-dig to the sound options statement. when i tried this, the speakers began to squeal and the system locked up. [/b]

Before I forget, some common sense (in case you did not check this).

I don't know about the lockup, but back off from 100% in your volume. You have it on 100%. Don't do that. That is WAY too high, and will lead to distortion.

Also, note if your microphone is active, you could get feedback causing the very squealing you are referring to. MAKE CERTAIN that is not what you are experiencing.

oldcpu,

you gave me a bunch to work with, took awhile.

the mic's and pcm kept coming up set to 100%. after manually editing asound.state to mute the mics and set pcm to 0, the system could start w/o all the squealing and timeouts. after these changes, the lenovo-ms7195-dig option appears to be working. this all seemed so unnecessary, but since i come from old SVR3 i'm not much for gui config thingys anyway.

i also had to enable 6ch mode in asound.state for the lfe and center channels to work.

off to test all this some more...

a few more questions please:
-- where did you find the options list for the alc883?
-- how did you determine from the report that no security patch kits had been applied? (patch kits, sorry vms terminology.)
-- where do i find what security patches need to be applied w/o all the auto-update stuff (that i've disabled. i'll maintain my system.)
-- one of the good things about moving from slackware to suse is that i've not had to reconfigure a suse kernel. do suse updates usually require kernel rebuilds?


thanks.

the mic's and pcm kept coming up set to 100%. after manually editing asound.state to mute the mics and set pcm to 0, the system could start w/o all the squealing and timeouts. after these changes, the lenovo-ms7195-dig option appears to be working. [/b]

Excellent! I confess I have never had to manually edit my asound.state file, so you could teach me a thing or two here, ... please stick around!

If it had been me, I would have updated the mixer levels, and then in a konsole with root permissions ran:
<span style="font-family:Courier New">alsactl store</span>
reference: http://www.linuxjournal.com/node/1000262

a few more questions please:[/b]

All good questions, and I will try to answer them.

-- where did you find the options list for the alc883?[/b]

For the alsa version that comes with your openSUSE-10.3, take a look on your computer under:
/usr/src/linux-<your kernel-number>/Documentation/sound/alsa/ALSA-Configuration.txt
For example, on my openSUSE-10.3 PC it is under:
/usr/src/linux-2.6.22.17-0.1/Documentation/sound/alsa/ALSA-Configuration.txt

Now to find out for alsa 1.0.16, I went to the alsa website, and downloaded the tarball for alsa-driver-1.0.16
http://www.alsa-project.org/main/index.php/Main_Page
and then looked in the tarball for alsa-driver-1.0.16 under ~/alsa-driver-1.0.16/sound/Documentation/ALSA-Configuration.txt (which has been updated). I then compared the two files to see the differnces for the ALC883.

Simply search the ALSA-Configuration.txt file for the ALC883 options.

-- how did you determine from the report that no security patch kits had been applied? (patch kits, sorry vms terminology.)[/b]

I read (from the diagnostic script) that you are using kernel-2.6.22.5-31-default on openSUSE-10.3. I remember this to be the default kernel version that comes with openSUSE-10.3. Now I suppose it is possible you added the security patch kits, and custom recompiled the kernel youself (in which case I would be wrong), but I suspect that to be unlikely.

-- where do i find what security patches need to be applied w/o all the auto-update stuff (that i've disabled. i'll maintain my system.)[/b]

Most of us use a software package manager to look after this stuff for us. Most users will use yast/zypper combination. Others (a small number) use Smart Package manager. In the case of yast/zypper if you go here:
http://opensuse-community.org/Repositories/10.3
you will note it states:

head over to YaST -> Software -> Community Repositories, and add:

* OSS
* Non-OSS
* Packman
* Main Update Repository [/b]

where I believe the "Main Update Repository" has your kernel updates. Alternatively, if you look here:
http://en.opensuse.org/Package_Repositories
which leads you here for a 32-bit openSUSE:
http://download.opensuse.org/update/10.3/rpm/i586/
you will see many kernel-default versions, the latest of which is:
kernel-default-2.6.22.17-0.1.i586.rpm

If you wish, you can search google for the many security differences between your 2.6.22.5-31 and the openSUSE 2.6.22.17.

-- one of the good things about moving from slackware to suse is that i've not had to reconfigure a suse kernel. do suse updates usually require kernel rebuilds?[/b]

In the openSUSE world we are lazy, and Novell/SuSE-GmbH do this for us, and then provide rpms. However if you are using any non openGL drivers (ie proprietary) there is a good chance a kernel update will break the functionality of the driver (because Novell do not directly provide nor package those proprietary drivers). Fortunately there are many volunteers who offer 3rd party packaging of proprietary drivers for the latest kernel releases of Novell/SuSE.

For example, our family laptop has an ipw-2100 wireless. Drivers are openSource, and that driver has never been broken by a kernel update by Novell/openSUSE. But my wife's PC has a DLink wireless (atheros chipset), which uses the madwifi wireless driver, and that is almost always broken by each and every rpm update of the kernel by Novell/openSUSE. Which means before installing the new kernel on her PC, I search and download the latest rpm (for her new kernel/madwifi) ie with updated madwifi. Then I update her kernel, and update her madwifi.

Some light openSUSE reading:
http://en.opensuse.org/Concepts

I hope the above helped. Please stick around. Your comfort in editing your asound.state file suggests to me you could be of help in our forum.