Sound In 10.3

I downloaded and installed the newer driver alsa-driver-1.0.14rc4.tar.bz2. Could not find same format file for tools and firmware. [/b]

Why 1.0.14.rc4? That is release candidate (RC) 4 prior to the released version of alsa-1.0.14, which was released a long time ago. Currently alsa is up to version 1.0.15. I think my post may have confused you .... there is no need to load 1.0.14.rc4 ... rather one should load a stable version of alsa AFTER 1.0.14rc4, which means either alsa-1.0.14 or alsa-1.0.15.

Packman have a v.1.0.14 rpm version of alsa for openSUSE-10.2. Hence my recommendation:

But the script file you provide suggest your alsa driver version is alsa-1.0.14 rc1. Please, if you have not done so already, can you go here and download and install the latest alsa drivers from Packman:
http://packman.links2linux.de/package/alsa
http://packman.links2linux.de/package/alsa-firmware
http://packman.links2linux.de/package/alsa-tools
[/b]

Please, can you consider that recommendation of mine?

Also, further to your post:

I downloaded and installed the newer driver alsa-driver-1.0.14rc4.tar.bz2. Could not find same format file for tools and firmware. [/b]

you are downloading a tar.bz2 file. That is commonly referred to as a "tarball" file, and it is not the same as an rpm file. Typically an rpm contains compiled executables. While a tarball typically contains source code and requires that you compile, and typically that is best done ONLY after one has checked to see if there are any rpm files available. In this case, there are rpms for alsa-1.0.14 (on Packman), and rpms for alsa-1.0.15 on the unofficial SUSE update site:
http://download.opensuse.org/repositories/..._Update/x86_64/

... now it may be necessary to take a tarball, and compile alsa, but if we have to cross that bridge, we should first get more information on your hardware, and also go for the latest alsa, and not some older alsa.

Now if those alsa versions (1.0.14 or 1.0.15) don't work for you, then there are a couple of scripts that I can have you run that will provide more diagnostic information on your setup. And perhaps only then (but not now) it might be useful to consider a custom compile.

a. go to YaST > HARDWARE > SOUND > Other and test your sound, if no sound then,
b. go to YaST > HARDWARE > SOUND > Other > Volume and setup your PCM and Master Volume levels up and test your sound (these actually appear to be ok by the script output you provided), and if no sound then,
c. go to YaST > HARDWARE > SOUND > EDIT and remove and then re-install/edit your sound configuration. Note when you remove the card, it is simply not configured, but neither is it removed, ..... and if still no sound then,
d. exit YaST and open a konsole (<ALT><F2> and type: konsole) and in the knosole type: su (enter root password when prompted), followed by: alsaconf and then setup your sound.[/b]

This suggestion works, alsacof test(heard the beep sound). And after reading the previous thread with suggestions to put rcalsasoft to boot.local, now my G4 sings . Just need to figure out how to get to the root permission to edit that file but works now I have a G4 400 mhz openSuSE 10.3. Thanks a bunch oldcpu


thanks,
-jack-ULL

This suggestion works, alsacof test(heard the beep sound). And after reading the previous thread with suggestions to put rcalsasoft to boot.local, now my G4 sings . Just need to figure out how to get to the root permission to edit that file but works now I have a G4 400 mhz openSuSE 10.3. [/b]

Glad to read the audio now works.

To edit such a file, if using KDE, and your favourite editor is kwrite, you can type: <span style="font-family:Courier New">gksu leafpad</span>
then enter root password, navigate to the file and change it. (needless to say, you need the leafpad editor for my specific example to work).

I'm a KDE user and not a gnome user, so I am guessing at the gnome lines. If gksu doesn't work, then maybe gnomesu?