sound doesn't work (via 8233/ac97)

As suggested by the syslog, I've tried "modprobe snd-via82xx dxs_support=5". It made no difference. I tried the same with "dxs_support=4, =3, =2, =1, and =0, all with no difference.

I kind of wonder if modprobe doesn't pass module options along or something, since "modprobe snd-via82xx dxsbloaga=saldksadsa" yielded the exact same behavior.

Ah-ha! rmmodding all relevant modules and then "modprobe via82cxxx_audio" works! Except the sound is very quiet. Presumably I can fix that in a mixer somewhere.

So the bug is (a) alsa drivers don't work with this chip, and (b) the alsa driver modules get loaded.

Here is the result of lsmod with no sound modules loaded:

Module Size Used by
af_packet 20232 2
agpgart 32328 1 via_agp
apm 19308 1
bitblit 5248 1 fbcon
capability 5000 0
cdrom 33952 1 ide_cd
cfbcopyarea 4480 1 vesafb
cfbfillrect 3840 1 vesafb
cfbimgblt 2944 1 vesafb
commoncap 6784 1 capability
dm_mod 50364 1
ehci_hcd 29448 0
evdev 9088 0
ext3 115976 1
fbcon 34176 0
font 8448 1 fbcon
i2c_core 19728 1 i2c_viapro
i2c_viapro 7696 0
ide_cd 36996 0
ide_core 125268 4 ide_cd,ide_disk,ide_generic,via82cxxx
ide_disk 16128 3
ide_generic 1664 0
ipv6 217408 8
jbd 48536 1 ext3
libata 47876 1 sata_via
lp 11460 0
md 40656 0
mii 5248 1 via_rhine
mousedev 10912 1
ohci_hcd 18564 0
parport 32072 2 parport_pc,lp
parport_pc 31812 0
pci_hotplug 24628 0
processor 23100 0
psmouse 26116 0
sata_via 8836 0
scsi_mod 124872 1 libata
softcursor 2432 1 vesafb
tileblit 2560 1 fbcon
tsdev 7616 0
uhci_hcd 28048 0
unix 24624 14
usbcore 104316 3 uhci_hcd,ohci_hcd,ehci_hcd
vesafb 8088 0
via82cxxx 12188 1
via_agp 9472 1
via_rhine 20356 0

Here is the result of lsmod with snd-via82xx loaded (the alsa module):

Module Size Used by
af_packet 20232 2
agpgart 32328 1 via_agp
apm 19308 1
bitblit 5248 1 fbcon
capability 5000 0
cdrom 33952 1 ide_cd
cfbcopyarea 4480 1 vesafb
cfbfillrect 3840 1 vesafb
cfbimgblt 2944 1 vesafb
commoncap 6784 1 capability
dm_mod 50364 1
ehci_hcd 29448 0
evdev 9088 0
ext3 115976 1
fbcon 34176 0
font 8448 1 fbcon
gameport 14472 1 snd_via82xx
i2c_core 19728 1 i2c_viapro
i2c_viapro 7696 0
ide_cd 36996 0
ide_core 125268 4 ide_cd,ide_disk,ide_generic,via82cxxx
ide_disk 16128 3
ide_generic 1664 0
ipv6 217408 8
jbd 48536 1 ext3
libata 47876 1 sata_via
lp 11460 0
md 40656 0
mii 5248 1 via_rhine
mousedev 10912 1
ohci_hcd 18564 0
parport 32072 2 parport_pc,lp
parport_pc 31812 0
pci_hotplug 24628 0
processor 23100 0
psmouse 26116 0
sata_via 8836 0
scsi_mod 124872 1 libata
snd 48644 11 snd_seq_oss,snd_seq,snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
snd_ac97_codec 72188 1 snd_via82xx
snd_mixer_oss 16128 1 snd_pcm_oss
snd_mpu401_uart 6784 1 snd_via82xx
snd_page_alloc 10120 2 snd_via82xx,snd_pcm
snd_pcm 78344 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss
snd_pcm_oss 46368 0
snd_rawmidi 22816 2 snd_seq_midi,snd_mpu401_uart
snd_seq 44688 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_seq_device 8204 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
snd_seq_dummy 3844 0
snd_seq_midi 8608 0
snd_seq_midi_event 6656 2 snd_seq_oss,snd_seq_midi
snd_seq_oss 29440 0
snd_timer 21764 2 snd_seq,snd_pcm
snd_via82xx 25792 0
softcursor 2432 1 vesafb
soundcore 9184 1 snd
tileblit 2560 1 fbcon
tsdev 7616 0
uhci_hcd 28048 0
unix 24624 14
usbcore 104316 3 uhci_hcd,ohci_hcd,ehci_hcd
vesafb 8088 0
via82cxxx 12188 1
via_agp 9472 1
via_rhine 20356 0

Here is the result of lsmod with via82cxxx_audio loaded (the oss module, that works)

Module Size Used by
ac97_codec 17420 1 via82cxxx_audio
af_packet 20232 2
agpgart 32328 1 via_agp
apm 19308 1
bitblit 5248 1 fbcon
capability 5000 0
cdrom 33952 1 ide_cd
cfbcopyarea 4480 1 vesafb
cfbfillrect 3840 1 vesafb
cfbimgblt 2944 1 vesafb
commoncap 6784 1 capability
dm_mod 50364 1
ehci_hcd 29448 0
evdev 9088 0
ext3 115976 1
fbcon 34176 0
font 8448 1 fbcon
i2c_core 19728 1 i2c_viapro
i2c_viapro 7696 0
ide_cd 36996 0
ide_core 125268 4 ide_cd,ide_disk,ide_generic,via82cxxx
ide_disk 16128 3
ide_generic 1664 0
ipv6 217408 8
jbd 48536 1 ext3
libata 47876 1 sata_via
lp 11460 0
md 40656 0
mii 5248 1 via_rhine
mousedev 10912 1
ohci_hcd 18564 0
parport 32072 2 parport_pc,lp
parport_pc 31812 0
pci_hotplug 24628 0
processor 23100 0
psmouse 26116 0
sata_via 8836 0
scsi_mod 124872 1 libata
softcursor 2432 1 vesafb
sound 70444 2 via82cxxx_audio,uart401
soundcore 9184 2 via82cxxx_audio,sound
tileblit 2560 1 fbcon
tsdev 7616 0
uart401 11204 1 via82cxxx_audio
uhci_hcd 28048 0
unix 24624 14
usbcore 104316 3 uhci_hcd,ohci_hcd,ehci_hcd
vesafb 8088 0
via82cxxx 12188 1
via82cxxx_audio 25096 0
via_agp 9472 1
via_rhine 20356 0

Just to be clear, modprobing the ALSA module (snd-via82xx) results in sporadic audio. modprobing the OSS module (via82cxxx_audio) results in working audio. Next I will figure out how to configure the system to not even load snd-via82xx...

In Dapper, sound on my Dell laptop with i810/AC97 isn't working at all (sound *did* work with Breezy). For a while sound would work via the OSS compatibility layer, but a few weeks ago that stopped working too. I've filed a bug about it here:

 https://bugzilla.ubuntu.com/show_bug.cgi?id=21281

and one other person reported having the same problem.

Let me know if there is anything I can do to help!

Problem still occurs with 2.6.15-11-686.

I'm wondering if this has anything to do with the current alsa-utils having version 1.0.9a-4ubuntu while alsa-base has version 1.10-3.

I noted this on Bug 27366 too -- my problem was a module setting on my machine which is no longer used in ALSA... This fix has sound running fine on my Dapper laptop.

I had a file (not sure if I added it myself some years ago, or if it was automatically deposited...)

 /etc/modprobe.d/sound

That contained the line:

 options snd device_mode=0660

Some googling located the information that this option is no longer used in alsa. Removing this line, caused the 'snd' module to become loadable on my system, and thus sound works once again.

Okay, re-tested on dapper with different, but still bad results.

To wit:

I booted the Breezy live cd, observed that sound worked, but was extremely quiet. I had to turn my amplifier up to max (which is dangerous, as other input might cause it to blast and damage my childrens' hearing) in order to hear the sound.

Then I re-installed from scratch using the Breezy install cd. Now sound does *not* work at all, as described in great detail earlier in this thread. Interesting that it works in live cd but not after install, eh?

Then I dist-upgraded to current dapper and rebooted. Now sound works, but again too quietly to be usable.

Then, I messed with the volume controls. I enabled all the various strangely-named controls and turned them all up to max. No change.

Then I unmuted the one called "center" and the one called "LFE". This killed the sound (totem was in the middle of playing an ogg file while I did it, and immediately everything went silent even though totem thought it was still playing). The sound could not be repaired either by re-muting those two controls, running "sudo /etc/init.d/alsa-utils restart", restarting totem.

So I rebooted. I observed this time (now that my amplifier is turned up to max) that the startup sound that comes with the Ubuntu splash screen is scratchy and cuts out, which is exactly the same behavior that I have always observed.

Always, that is, since I upgraded from Warty Warthog, which Just Worked.

So please re-open this bug.

Meanwhile, perhaps I'll re-install Warty Warthog on this system so that my son can have sound in his games.

Regards,

Zooko

Err, when I wrote "Warty" above I meant Hoary.

There is no bug in alsa-utils here, and this bug is already attached to the kernel where it belongs

Zooko, please test a live cd of Dapper Flight 6 (just released), and attach the output from ``lspci -v && lspci -nv && tail -2 /proc/asound/oss/sndstat && amixer -c0''.

confirmed in Acer Travelmate 3210wxci

http://hwdb.ubuntu.com/?xml=2b00f9148c5cb73ce824366acd436e7a

@manuel: Please /attach/ (don't inline) the output from ``lspci -nv && lsmod && cat /proc/asound/cards && amixer''.

This machine was working well w/ dapper until some of latest kernell

@manuel: output from ``lspci -nv &&
lsmod && cat /proc/asound/cards && amixer''.

Hopping this will help,
Manuel

@manuel: Your issue may not be related to the original poster's. Yours is easily fixed by:

$ amixer set 'PCM' on && amixer set 'IEC958 Playback AC97-SPSA' 0

The kernel update isn't responsible for making your sound inaudible; some other application fiddled with those mixer settings.

Manuel's result

It work's. Some peoples post sounds problems in ubuntu-es after moving to dapper. I did post this solution hopping help others.

@Zooko O'Whielacronx: Can you attach your amixer output from a live cd boot of poor (low-volume) sound?

I have had this problem with my Averatec 3715-EH1 Laptop. Using both Ubuntu 5.10 and only recently in 6.06 (LTS). I don't use hibernate or suspend (largely because if this bug) and seldom 'reboot.' It is usually just a shutdown/restart. My initial 5.10 install was dual-boot with windows, and a reboot into, and log out of Windows would fix it with an audible tick or pop.

Installed 6.06(LTS) from the CD replacing the 5.10 install (due to a failed windows upgrade mucking up the MBR), and had it set up to dual-boot for a while too, but did not experience the problem so I wiped the Windows install and installed 6.06 (LTS) as the only OS and it worked well for near 2 weeks and recently the problem has resurfaced.

I have checked the alsamixer settings and recently installed the latest kernel package for the k7 in an attempt to fix it. My next steps were going to be roll a custom kernel to see if perhaps there were some driver conflicts, OR reinstall via the same CD and do the upgrades/updates and see what might possibly be breaking it there.

I think it is important to note that I had near a month of use without problem from the 6.06 (LTS) install. It only returned early this week (near 8/270/06). Also that again I don't use hbernate/suspend. Lastly I'm not convinced it might be the power management somehow. I really think it quits working while the machine is still 'on' sometimes.

I can confirm I have the same problem with my Averatec 3715-ED1 (using via 8233/ac97). I am dual booting XP pro and dapper. It seems as though as long as ubuntu is initially booted before xp (I generally hibernate rather than restarting) it works. but if for instance xp is hibernated and ubuntu is restarted i will get no sound at all. I haven't done alot of testing on this hypothesis, but that seems to be the case.

Has any new info on this bug surfaced? My above hypothesis is wrong. I can't seem to notice a definite pattern in when it works and when it doesn't. It works probably 30-40% of the times i restart the computer. Once it is working it stays working until i shut off/restart/hibernate the computer. if their is anymore information i can provide ask and ill try my best, as i would love to have working sound.
--travis

FYI, I'm about to test sound again on my son's computer, and then upgrade to edgy and try again.

I'm still experiencing this issue with 8233 driver and there aren't any solutions on ubuntu forums. I'm using a fresh install of edgy. Did anyone ever figure it out?

I upgraded my son's computer to edgy (by setting the /apt/sources.list and running apt-get update && apt-get dist-upgrade), and sound doesn't work at all after the upgrade. I haven't had time to experiment with it.

I could resolve this after upgrade to 7.04 by setting the rear jack from "Rear Output" to "Mixed Output". Maybe this does also resolve it in previous releases.
Seems to me it did work all along but the standard setting just doesn't playback Front and Center Audio Which is in most cases no sond. This also explains, why many hear only very silent Audio for the 3D Pre or Post Mixing will mix Front and Center Audio into Rear Output but at very low volume.

cheers

I have to correct myself, The settings which work for me for Stero Sound playback are to set Front and Rear Jack to Front Output (or Mixed); though Front Output results in good quality Audio at perfect volume. Hope this helps some. The main solution still stands: simply configure the correct output for the front/rear jack (Front only makes sence if the computer has front Audio attached to mainboard, though setting this wrong results in no Audio at all as far as i tested which was only as long as it took me to get Audio to work and NEVER TOUCH IT AGAIN :D ).

cheers
Simba

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks, Markus

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.