At Mon, 27 Jun 2011 13:29:30 -0300,
Diego Jacobi wrote:
>
> Thanks.
>
> I did sended you already as CC the same mail that i sended to alsa-devel.
> It has the alsa-infos.
>
>
> 2011/6/27 Takashi Iwai <ti...@suse.de>:
> > At Mon, 27 Jun 2011 12:30:05 -0300,
> > Diego Jacobi wrote:
> >>
> >> >> > Did it work before with another GNU/Linux distribution?
> >> >>
> >> >> I have never used this laptop with another distribution. I would
> >> >> require to install and learn to set the parameters for the right
> >> >> model. Can not do that from livecd.
> >> >
> >> > You are right. It is tedious to remove the sound modules during runtime
> >> > since some graphical programs use/depend on them and there are also many
> >> > sound modules.
> >> >
> >> > The command you would be looking for is `modprobe` and you would pass
> >> > the parameter `model` with a file in `/etc/modprobe.d/` or when loading
> >> > the module directly with `modprobe snd-hda-intel model=…`.
> >>
> >> I remember to have tested many models.
> >> Fortunately in openSUSE it is quite easy to change the value, but not
> >> to find the right one.
> >>
> >> When i did that, i right one was "m51va"
> >> It was also quite hard to find it out and to get the list of options.
> >> Thats no task for any non-programmer.
> >> And most answers finded in google just say "try this" and not "read
> >> this file and look for your chipset and the list of available models".
> >
> > The recent version of BIOS auto-parser works often better than the
> > model quirks. For openSUSE, the alsa-driver-kmp is available for
> > the updates to the latest alsa-driver snapshot.
> > See the Wiki page for details:
> > http://en.opensuse.org/SDB:Alsa-update
> >
> > After installing alsa-driver-kmp, remove model option, and reload
> > the driver (or reboot). Check the mixer status again, then retest.
> > If the problem still persists, give alsa-info.sh output. (Put me to
> > Cc.)
> >
> > The latest alsa-driver-kmp might still have a bug at volume
> > initialization I fixed today. I can check it when alsa-info output is
> > available. In anyways, you can try alsa-driver-kmp later again in
> > such a case, too.
> >
> > At best, take alsa-info.sh output during the mic is working and during
> > the mic doesn't work. In that way, we can compare the difference more
> > directly.
> >
> >
> > thanks,
> >
> > Takashi
> >
>
> alsa-driver-kmp wasnt on my software manager, i had to find it at
> software.opensuse.org.
Make sure that you installed from the right repository.
When the kernel version doesn't match, the modules might be not
updated properly. There are different repos for the original 11.4 and
updated 11.4 kernels, for example.
For checking whether it's updated, check like
/snd/modinfo snd-hda-intel | grep filename:
If the filename shown there is something like
/lib/modules/.../updates/... or /lib/modules/.../weak-updates/...,
it's fine. If it's still /lib/modules/.../kernel/sound/..., it means
that the update went wrong by some reason.
Takashi
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
