[feisty] another issue with no sound after 2007-03-16 updates

Bug #93263 reported by gnuboi
114
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Medium
Ubuntu Audio Team

Bug Description

Binary package hint: linux-source-2.6.20

Hi, this is very similar to the report in 92989,

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/92989

except my hardware may be a different. I am running an Asrock K8NF6G-VSTA.

Basically, with kernel 2.6.20-9 I can hear my sound. With kernel 2.6.20-11, the apps report no problems but I cannot hear anything.

sndstat with 2.6.20-9 says I have a mixer Realtek ID 862, but in 2.6.20-11 it says I have a mixer Realtek ALC861-VD. The manufacturer does say I have the ALC883/ALC861VD Audio Codec.

Attached are the sound debugging info while running in 2.6.20-11. Thanks!

Revision history for this message
gnuboi (chunghaulee) wrote :
Revision history for this message
gnuboi (chunghaulee) wrote :
Revision history for this message
Ben Collins (ben-collins) wrote :

Probably fixed in -12 kernel. Please retest, and mark "Fix Released" if things are now working.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-audio
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
gnuboi (chunghaulee) wrote :

I tried the -12 kernel. No different than the -11 kernel as far as my sound is concerned.

My guess is that since the -11 kernel, the audio driver has been identified more accurately. The no sound coming out problem may be an ALSA issue. I have found stories similar to this in which people had to mute certain channels; but they have different hardware. In the -9 kernel, the system uses a different ALSA driver with fewer mixer channels but the sound works.

Revision history for this message
gnuboi (chunghaulee) wrote :
Daniel T Chen (crimsun)
Changed in linux-source-2.6.20:
status: Confirmed → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

gnuboi - Was your issue resolved with a newer kernel at all?

Revision history for this message
gnuboi (chunghaulee) wrote : Re: [Bug 93263] Re: [feisty] another issue with no sound after 2007-03-16 updates

Yes! I have 2.6.20-16-29 installed.

Originally I had to add "options snd-hda-intel model=3stack" to my
/etc/modprobe.d/alsa-base file. I commented it out and the sound
still works! The newer kernel must have fixed the problem.

On 8/28/07, Brian Murray <email address hidden> wrote:
> gnuboi - Was your issue resolved with a newer kernel at all?
>
> --
> [feisty] another issue with no sound after 2007-03-16 updates
> https://bugs.launchpad.net/bugs/93263
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Changed in linux-source-2.6.20:
status: Fix Committed → Fix Released
Revision history for this message
Alex Cornejo (acornejoc) wrote :

Hi,

I have a DELL XPS m1210, and installed the latest gutsy release with all the latest updates. My sound didn't work, the snd_hda_intel module was loaded, but it was aparently unused and alsamixer (or gnome-volume-control) seemed not to detect it at all (it was not even on the list).

Adding snd-hda-intel model=3stack to alsa-base does indeed fix the problem, but this patch needs to go upstream.

Regards,
--
Alex

url: http://www.mit.edu/~acornejo

Revision history for this message
sauronsmatrix (aavindraa) wrote :
Revision history for this message
Ciprian Popovici (cprpop) wrote :

Careful with the "model=" fix. On a Kubuntu 7.04 installation on a Toshiba Satellite A200-14e, using model=3stack resulted in a loud screeching sound in the speakers as soon as mixer levels were restored, and the bootup would freeze soon after.

Unfortunately this was part of a remote walkthrough and I have no further data that would help determine the proper model= value that should've been used. The owner reinstalled with 7.10 soon after.

So this is basically a heads up. Be careful when using obscure kernel module parameters on moody hardware such as laptops.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.