SB0160 still not working after blacklisting snd_via82xx and snd_via82xx_modem.

[Lee Linder]

alghurab@alghurab-desktop:~$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
alghurab@alghurab-desktop:~$ apt-cache policy packagename
W: Unable to locate package packagename

Initial problem was no sound. Sound Preferences were set to AutoDetect. After fiddling around with them, got the little test tone after set to multi-channel, but still no sound. Went to "https://wiki.ubuntu.com/DebuggingSoundProblems" and followed troubleshooting directions...

Everybody has permission to use audio.

alghurab@alghurab-desktop:~$ cat /proc/asound/cards
 0 [Audigy ]: Audigy - Audigy 1 ES [SB0160]
                      Audigy 1 ES [SB0160] (rev.3, serial:0x521102) at 0xb400, irq 19
(1 used to be there too with via82xx.)

Checked lsmod and found via82xx everywhere. No control of onboard soundchip available through BIOS. Still no sound after blacklisting the via82 stuff even though the via82 stuff no longer appears in lsmod.

Ran the alsa-info.sh... Here is the URL: http://www.alsa-project.org/db/?f=653bfe99f2918b17a7e25aade5e8f6165b064f6e.

Hoping y'all can help me get past this. Cheers.

[floppy514 (floppy514)]

I had a similar problem (no sound) with SB0160, which is now solved.
The problem was not where I thought it was; not sure your problem is the same, but here it is:

plop@groovy:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION="Ubuntu 8.10"
plop@groovy:~$ cat /proc/asound/cards
 0 [Audigy ]: Audigy - Audigy 1 ES [SB0160]
                      Audigy 1 ES [SB0160] (rev.3, serial:0x521102) at 0xd200, irq 19

It's plugged on a gigabyte ga-ep45-ds5 motherboard, with intel ICH10 chipset integrated sound deactivated within bios setup (hence not seen in the previous command).

The only thing that was missing for me was to unselect "Audigy Analog/Digital Output Jack", in the parameter tab of the gnome volume controller. I found the tip here: http://ubuntuforums.org/showthread.php?p=4301880#post4301880

I guess having both audio controllers (motherboard chipset and audigy) should not be a problem, as long as you have the one you choosed (audigy) as card0, as most applications will only talk to this card, as I've seen somewhere on a forum.

I haven't tried it yet, but here are some descriptions about how to do it:
http://alsa.opensrc.org/index.php/MultipleCards

Mainly, it's all about forcing card numbering in /etc/modprobe.d/alsa-base with the "index=" option.

Hope this helps.

[Lee Linder (alghurab)]

Merci bien! Alf Shuker! Many thanks! You have solved my problem! I
knew it would end up being something simple. Life is so much better
now.

Thanks again.

-----Original Message-----
From: floppy514 <email address hidden>
Reply-to: Bug 316960 <email address hidden>
To: <email address hidden>
Subject: [Bug 316960] Re: SB0160 still not working after blacklisting
snd_via82xx and snd_via82xx_modem.
Date: Tue, 17 Feb 2009 02:22:20 -0000

I had a similar problem (no sound) with SB0160, which is now solved.
The problem was not where I thought it was; not sure your problem is the same, but here it is:

plop@groovy:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION="Ubuntu 8.10"
plop@groovy:~$ cat /proc/asound/cards
 0 [Audigy ]: Audigy - Audigy 1 ES [SB0160]
                      Audigy 1 ES [SB0160] (rev.3, serial:0x521102) at 0xd200, irq 19

It's plugged on a gigabyte ga-ep45-ds5 motherboard, with intel ICH10
chipset integrated sound deactivated within bios setup (hence not seen
in the previous command).

The only thing that was missing for me was to unselect "Audigy
Analog/Digital Output Jack", in the parameter tab of the gnome volume
controller. I found the tip here:
http://ubuntuforums.org/showthread.php?p=4301880#post4301880

I guess having both audio controllers (motherboard chipset and audigy)
should not be a problem, as long as you have the one you choosed
(audigy) as card0, as most applications will only talk to this card, as
I've seen somewhere on a forum.

I haven't tried it yet, but here are some descriptions about how to do it:
http://alsa.opensrc.org/index.php/MultipleCards

Mainly, it's all about forcing card numbering in /etc/modprobe.d/alsa-
base with the "index=" option.

Hope this helps.

[Lee Linder (alghurab)]

That solved it! I knew it would end up being something simple. A thousand thanks!

[Jeremy Foshee (jeremyfoshee)]

Hi Lee,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 316960

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]