Quote:
|
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
Quote:
|
a few more questions please:[/b]
|
All good questions, and I will try to answer them.
Quote:
|
-- 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.
Quote:
|
-- 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.
Quote:
|
-- 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:
Quote:
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.
Quote:
|
-- 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.