[solved] Toshiba Latop Without Sound

Thanks in advance for anytime spent on this topic.

As the name suggests I am rather new to Linux, I purchased a new laptop and am installing openSUSE 10.3. I have managed to figure out the video and wifi, but the sound still eludes me. I have gone through the troubleshooting guide at:

<blockquote>Audio Troubleshooting -http://en.opensuse.org/SDB:AudioTroubleshooting</blockquote>

which is a very well written guide. I have just had no luck getting it to work for me, I need some help interpreting the the outputs.

Check ALSA firmware:

# rpm -q alsa alsa-utils alsa-firmware
alsa-1.0.16.hg20080510-1.1
alsa-utils-1.0.16.hg20080429-1.2
alsa-firmware-1.0.16.hg20080314-1.2

Alsa Ver:

# cat /proc/asound/version 
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).

Loaded Modules:

# cat /proc/asound/modules
 0 snd_hda_intel

Devices:

# cat /proc/asound/cards
 0 [SB************ ]: HDA-Intel - HDA ATI SB
**********************HDA ATI SB at 0xf8700000 irq 17

First Script: Script 1 Output-http://pastebin.ca/1028059

Second Script: Script 2 Output-http://nopaste.com/p/aerPc8J5L

etc/modprobe.d/sound:

options snd-hda-intel model=3stack enable=1 index=0
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel

Line 1 added by me after an alsaconf, the file was just the last 2 lines.

Something I noticed in the boot log:

<6>ALSA sound/pci/hda/hda_codec.c:1804: hda_codec: model '3stack' is selected
<3>ALSA sound/pci/hda/patch_si3054.c:244: si3054: cannot initialize. EXT MID = 0000
<7>ALSA sound/pci/hda/patch_si3054.c:256: Link Frame Detect(FDT) is not ready (line status: 0000)

Not sure if this bears significance.

Anything else? Thanks for any help, and feel free to smack me if I did something wrong.

Thanks in advance for anytime spent on this topic.
First Script: Script 1 Output
Second Script:
[/b]

Typically new Users are not allowed to post URLs.

Just make the URL kind of funny, like: NHTTP:/??/pastebin.ca/somenumber
and I'll figure it out.

First Script: Script 1 Output http://pastebin.ca/1028059
Second Script: Script 2 Output http://nopaste.com/p/aerPc8J5L[/b]

OK, so 32-bit openSUSE-10.3 on Satellite A215-S5849 with 2.6.22.17-0.1 openSUSE kernel.
Sound hardware Codec is: Generic 11c1 Si3054

I note there are updates in 1.0.15 and 1.0.16 of alsa for the Si3054:
http://www.alsa-project.org/main/index.php...i3054&go=Go

I also noted you did not install the 1.0.14 driver. You only installed part of the needed alsa applications. In particular you are missing alsa-driver-kmp-default. If you are going to update to 1.0.14, I recommend you install them all as listed in the guide (including libasound2).

Reference the alsa command, a better rpm command (to see what alsa packages you have installed) is to querry all rpm packages, but put a grep "filter" on so only those with 'alsa' come thru. ... ie:
Note the above are exactly 3 commands.[/i]

Please reboot your PC after this update, and then check your sound.

Typically new Users are not allowed to post URLs.

Just make the URL kind of funny, like: NHTTP:/??/pastebin.ca/somenumber
and I'll figure it out.
[/b]

was wondering what was happening with the urls, thanks.

I have gone through the troubleshooting guide at:
<blockquote>Audio Troubleshooting -http://en.opensuse.org/SDB:AudioTroubleshooting</blockquote>
which is a very well written guide.[/b]

Thanks for the kind words, ... I keep tuning the guide to try and make it easier, but I still have much work to do on it. ... I'll also have to update it soon with openSUSE-11.0 coming out soon.

OK, so 32-bit openSUSE-10.3 on Satellite A215-S5849 with 2.6.22.17-0.1 openSUSE kernel.
Sound hardware Codec is: Generic 11c1 Si3054

I note there are updates in 1.0.15 and 1.0.16 of alsa for the Si3054:
http://www.alsa-project.org/main/ind......i3054&go=Go

I also noted you did not install the 1.0.14 driver. You only installed part of the needed alsa applications. In particular you are missing alsa-driver-kmp-default. If you are going to update to 1.0.14, I recommend you install them all as listed in the guide (including libasound2).

Reference the alsa command, a better rpm command (to see what alsa packages you have installed) is to querry all rpm packages, but put a grep "filter" on so only those with 'alsa' come thru. ... ie:
<span style="font-family:Courier New">rpm -qa | grep alsa</span>
[/b]

The numbers look funny to me as well, but I was not exactly sure what it meant.

# rpm -qa | grep alsa
alsa-utils-1.0.16.hg20080429-1.2
alsa-oss-1.0.14-23
alsa-tools-1.0.16.hg20080122-7.14
alsa-1.0.16.hg20080510-1.1
alsa-plugins-1.0.14-41
alsa-firmware-1.0.16.hg20080314-1.2

I ran into trouble trying to install the alsa-driver-kmp-default, it was asking me to delete my kernel, I will try it again using zypper and post the results.

I ran into trouble trying to install the alsa-driver-kmp-default, it was asking me to delete my kernel, I will try it again using zypper and post the results.[/b]

Good thing to stop when you get those error messages. Well done!

Watch careful so you don't get that again, and if you do, STOP. I tried hard to pick the exact zypper commands to avoid that error, but I can make mistakes.

Per the audio troubleshooting guide, please with your pc connected to the internet, send the following 3 commands from an xterm/konsole with root permissions (I recommend you copy and paste this to get the syntax exact):

zypper ar http://download.opensuse.org/reposit...E_10.3_Update/ multimedia

zypper install alsa alsa-driver-kmp-default alsa-utils alsa-tools alsa-firmware libasound2

zypper rr http://download.opensuse.org/reposit...E_10.3_Update/

Note the above are exactly 3 commands.

Please reboot your PC after this update, and then check your sound.
[/b]

Ok I thought I was smart before and tried doing this trough YaST, and thats when I got the conflict reports. Well per your suggestion, I tried it again today using Zypper...

skipping package 'alsa' (already installed)
skipping package 'libasound2' (already installed)

The following packages are going to be upgraded:
**alsa-tools alsa-utils alsa-firmware 

The following NEW package is going to be installed:
**alsa-driver-kmp-default 

Overall download size: 5.6 M. After the operation, additional 5.5 M will be used.
Continue? [yes/no]: y
Downloading package alsa-driver-kmp-default-1.0.16.hg20080520_2.6.22.17_0.1-1.1.i586, 1.5 M (5.5 M unpacked)
Downloading: alsa-driver-kmp-default-1.0.16.hg20080520_2.6.22.17_0.1-1.1.i586.rpm
* Downloading [100%]
* Installing: alsa-driver-kmp-default-1.0.16.hg20080520_2.6.22.17_0.1-1.1 [100%]
Downloading package alsa-utils-1.0.16.hg20080429-1.3.i586, 898.1 K (1.7 M unpacked)
Downloading: alsa-utils-1.0.16.hg20080429-1.3.i586.rpm
* Downloading [100%]
* Installing: alsa-utils-1.0.16.hg20080429-1.3 [100%]
Downloading package alsa-firmware-1.0.16.hg20080314-1.3.noarch, 3.0 M (7.6 M unpacked)
Downloading: alsa-firmware-1.0.16.hg20080314-1.3.noarch.rpm
* Downloading [100%]
* Installing: alsa-firmware-1.0.16.hg20080314-1.3 [100%]
Downloading package alsa-tools-1.0.16.hg20080122-7.20.i586, 187.9 K (554.4 K unpacked)
Downloading: alsa-tools-1.0.16.hg20080122-7.20.i586.rpm
* Downloading [100%]
* Installing: alsa-tools-1.0.16.hg20080122-7.20 [100%]

seems to have worked, let me remove the repo and reboot, brb with results.

seems to have worked, let me remove the repo and reboot, brb with results.
[/b]

Still no sound, i'll run through the troubleshooting steps. Should I have "alsa-oss-1.0.14-23" installed, could that create a conflict?

Still no sound, i'll run through the troubleshooting steps. Should I have "alsa-oss-1.0.14-23" installed, could that create a conflict?
[/b]

alsa-oss is an alsa emulation of the oss driver.
http://en.opensuse.org/Sound-concepts

Many years ago, oss was the driver for linux, and not alsa. But the author of oss made the oss driver a commercial driver, and hence the opensource community moved away from it, and went for the alsa driver. ... But some (mostly legacy) apps still wanted the oss driver, so the alsa driver comes with an emulator of the oss driver. But its not IMHO needed. (as a note, the oss driver has recently become opensource again, but the community has moved away from that driver and it may not be accepted again to the extent it once was).

Can you check to see if you get sound with root permissions?
ie in a konsole with root permissions, type (copy and paste):
<span style="font-family:Courier New">speaker-test -c2 -Ddefault -twav</span>
... also do the above test as a regular user.

Also, check your mixer to ensure PCM and master volume are up around 70%.