I get terminal output from a sound test that suggests all is fine:
speaker-test -Dplug:front -c2 -l5 -twav
speaker-test 1.0.23
Playback device is plug:front
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 8 to 16384
Period size range from 8 to 16384
Using max buffer size 16384
Periods = 4
was set period_size = 4096
was set buffer_size = 16384
0 - Front Left
1 - Front Right
Time per period = 2.752631
0 - Front Left
1 - Front Right
Time per period = 3.071421
0 - Front Left
1 - Front Right
Time per period = 2.901829
0 - Front Left
1 - Front Right
Time per period = 3.071955
0 - Front Left
1 - Front Right
Time per period = 3.071213
Here’s some more text copied from a terminal window:
rpm -qa |grep alsa
alsa-utils-1.0.23-1.8.i586
alsa-oss-1.0.17-29.2.i586
alsa-1.0.23-2.12.i586
alsa-plugins-1.0.23-1.9.i586
rpm -qa | grep pulse
libpulse0-0.9.21-9.2.i586
libpulse-mainloop-glib0-0.9.21-9.2.i586
libxine1-pulse-1.1.18.1-1.37.i586
uname -a
Linux linux-ievq.site 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686 i686 i386 GNU/Linux
cat /etc/modprobe.d/sound
cat: /etc/modprobe.d/sound: No such file or directory
Even I can see that the last bit is probably a problem. However, don’t have a clue as to how to proceed.
The sound configuration is in a file called 50-sound.conf.
Thanks for your interest oldcpu. The page you referred to listed the applicable driver module in the kernal. Do I have to recompile my kernal with a different driver?
No, sound should work with the current driver. But its possible there are some quirks wrt the driver. Did you read this:
Note
On some models (T40, T43p, … R51e …) audio is muted if either Headphone or Line Jack are unmuted. See also ALSA Wiki FAQ [1]. Also, if Headphone Sense or Line Jack Sense are unmuted audio is dead (R52, X40). By default the Sense settings are not shown in GNOME.
and this:
Note
By default microphone capture is disabled when using the ALSA drivers (this may or may not be true with the OSS drivers). To enable microphone capture, use amixer or gnome-alsamixer to enable capture on the microphone and Capture devices, i.e., ‘amixer set ‘Mic’ cap; amixer sset ‘Capture’ cap’.
and this:
Note
A bug was introduced in the 2.6.20 kernel (between the rc1 and rc2 releases) which causes the sound to stop working after hibernation. Rebooting does not seem to fix the problem. A quick work-around is to do a suspend-to-ram, and then wake the machine up. This issue is chronicled in this bug report on Launchpad.net: The fix changing HIBERNATE_MODE=shutdown to HIBERNATE_MODE=platform in /etc/default/acpi-support worked very well. I don’t know if it possibly could introduce other bugs or if it’s a true fix.
Changing HIBERNATE_MODE=shutdown to HIBERNATE_MODE=platform in /etc/default/acpi-support seems to be solving this issue for many users. Confirmed to work with: X31, T43p
I see now that I have the right driver from the output
cat etc/modprobe.d/50-sound.conf
I’m using the default mixer. It only allows me to adjust four items. Master, PCM, CD, and headphone. Toggling mute on and off has no effect.
I haven’t even tried to use a microphone yet. That’s good to know for future reference. Is there another mixer that allows adjustment of microphone settings and line out settings?
On my system there is no /etc/default/acpi-support. It looks like I need to edit a configuration file. No problem, if I could find it.
Which mixer is this? It varies from desktop to desktop. Note there is also the command line ‘amixer’ that one can use to control the mixer (but its not user friendly).
Sometimes I recommend an edit to the /etc/modprobe.d/50-sound.conf file, changing a model option, but I am not aware of any such option for an AD1981B.
Worst comes to worst, and you could write a bug report on openSUSE component “sound” on openSUSE-11.3.
Attach (don’t copy and paste, but attach) to the bug report the text file from running:
/usr/sbin/alsa-info.sh --no-upload
and that will create the file /tmp/alsa-info.txt which can be added as an attachment. That has bunch of technical info that may show the alsa dev what is wrong with the alsa driver, IF you also describe the audio symptoms.
Note the SuSE-GmbH packager for sound is also an alsa developer, and if he fixes this, the fix gets sent upstream and ALL Linux distributions will benefit from your efforts with him.
There is guidance here for raising bug reports: Submitting Bug Reports - openSUSE … The alsa developer/openSUSE packager, may ask that you try a few different alsa versions, and hence if your schedule is too busy for such support (and I definitely know what that can be like) then its probably best NOT to write such a bug report.
Don’t reference this thread, as the SuSE-GmbH packager refuses to read forum threads. Its important the bug report has all the salient information.
You could if you wish run the diagnostic script again, and keep a local copy of it. It will have your PC settings that work ! And/or do a screen dump of your mixer settings and save that, so you have a guide to consult with in the future, if this does not work again.
Still have it not working. Only strange thing I notice is that speaker-test give write error -32. Not found a solution for it yet. Other hints like adding user to audio group, removing the file in /etc/modeprobe.d don’t work. Any idea?
I note this is your first post here. Welcome to openSUSE and welcome to openSUSE forums.
Generally speaking it is better to start your own thread rather than latch on to someone else’s which is SOLVED.
That error means nothing to me. I would not attempt to recommend an approach wrt your sound problem without more information. I do not know which openSUSE verison. I don’t know which desktop. I don’t know which architecture. I don’t know which hardware. Please, may I recommend you read our multimedia stickie: Welcome to multimedia sub-area and in particular the last half of that, providing the information recommended there.