VT82C686 Audio Broken: Gutsy to Hardy Beta upgrade

Bug #205588 reported by Linuturk
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Description: Ubuntu hardy (development branch)
Release: 8.04

$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
00:08.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)
00:0a.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
00:0d.0 Mass storage controller: Promise Technology, Inc. PDC20268 (Ultra100 TX2) (rev 02)

I expected the audio supported in Gutsy to work automagically in Hardy. It seems to be an integrated chipset on the motherboard. The motherboard is a MSI K7Turbo

Revision history for this message
Linuturk (linuturk) wrote :
Revision history for this message
Michael Losonsky (michl) wrote :

I have lots of problems with audio in ubuntu -- not the sound,
but recording, microphones, conferencing are all pretty
difficult to set-up and once you have it set-up, the next
update messes things up again. BUT this worked for
me in Hardy, to set everything to Pulseaudio instead of
ALSA. I am using an ATI Radeon card.

Revision history for this message
Linuturk (linuturk) wrote :

Where would I change these settings?

Revision history for this message
Linuturk (linuturk) wrote :

Well, I found those settings. My problem seems to be there is no device to use, according to the gnome control panel.

Revision history for this message
Linuturk (linuturk) wrote :

Please let me know if there is any additional information you need. My terminal is your terminal, as I say.

Revision history for this message
Linuturk (linuturk) wrote :

Some additional information. Per this thread: http://ubuntuforums.org/showthread.php?t=724042&highlight=sound+broke+hardy&page=2

When I boot to an older generic kernel, my sound works, but my nvidia card hates itself.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Linuturk,

On the kernel where sound is broken, care to attach the output of alsa-info.sh which is available here: https://wiki.ubuntu.com/DebuggingSoundProblems . Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Michael Losonsky (michl) wrote :

I just upgraded on a Desktop from Gutsy to Hardy and have the very same
problem. The soundcard is not detected. This hasn't happened during
previous upgrades on this computer, a Dell precision workstation 220.

output of the alsa-info script is:
Your ALSA information is located at http://pastebin.ca/957596

Revision history for this message
Michael Losonsky (michl) wrote :

Other log attached

Michael Losonsky (michl)
Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
Michael Losonsky (michl) wrote :

The thread below discusses this issue and offers a workaround that
worked for me. The problem is that when you upgrade, for some
reason two kernels are installed a 386 kernel and generic. The
sound problems are with the 386 kernel. Unfortunately, after
booting into the 386 kernel, it generates the initramfs file for
386, but messes-up the generic kernel, so you can't boot into
it anymore. (This is exactly what happened to me.) So you need
to run:
sudo update-initramfs -k 2.6.24-12-generic -c
in the terminal, and reboot into generic. The sound worked there for me.
Hope this works for you.

http://ubuntuforums.org/showthread.php?t=729873&highlight=problem+with+sound&page=2

Revision history for this message
Linuturk (linuturk) wrote :

Here is the alsa info you requested.

Revision history for this message
Linuturk (linuturk) wrote :

Thank you Michael Losonsky.

The process he described worked perfectly. My sound is now working.

I've attached a new alsa-info.txt showing the system in the working state. The previous attachment is using the other kernel.

Is it safe to remove the 386 kernel?

Revision history for this message
Linuturk (linuturk) wrote :

Let me elaborate.

Should I uninstall the 386 kernel or just comment out it's entries in /boot/grub/menul.lst ?

Revision history for this message
Igor Zubarev (igor.zubarev) wrote :

I have the same problem after upgrade from Gutsy to Hardy. Intel built-in card on Sony VAIO VGN-FS115.

After apgrade Hardy didn't remove old Gutsy kernel and installed 386 kernel.
The problem with sound resolved:

sudo aptitude remove linux-image-2.6.24-12-386
sudo update-initramfs -k 2.6.24-12-generic -c

Many thanks to guys in http://ubuntuforums.org/showthread.php?t=729873

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Guys,

Unfortunately as you pointed out there were some issues occurring with upgrades where the i386 flavor was being installed instead of the generic flavor. See bug 188579. I'm going to go ahead and mark this as a duplicate of that. Thanks.

Revision history for this message
W.McL (w-mcl) wrote :

The sound issue after an upgrade also exists with 2.6.24-16-generic kernel.
Sound works on 2.6.24-16-386 though, but this breaks various other applications (mainly gnome related apps, so probably a X problem?)

linux-ubuntu-modules-2.6.24 Version: 2.6.24-16.23

uname -a: Linux deepthought 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

'modprobe snd-hda-intel' gives the following message:
WARNING: Error inserting snd_hda_codec (/lib/modules/2.6.24-16-generic/updates/snd-hda-codec.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.24-16-generic/updates/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)

the resulting part in dmesg is:
[ 1801.294658] snd_hda_codec: Unknown symbol snd_ctl_elem_read
[ 1801.294778] snd_hda_codec: Unknown symbol snd_ctl_elem_write
[ 1801.297547] snd_hda_intel: Unknown symbol snd_hda_bus_new
[ 1801.297699] snd_hda_intel: Unknown symbol snd_hda_build_pcms
[ 1801.297775] snd_hda_intel: Unknown symbol snd_hda_codec_new
[ 1801.297922] snd_hda_intel: Unknown symbol snd_hda_queue_unsol_event
[ 1801.298228] snd_hda_intel: Unknown symbol snd_hda_calc_stream_format
[ 1801.298361] snd_hda_intel: Unknown symbol snd_hda_suspend
[ 1801.298502] snd_hda_intel: Unknown symbol snd_hda_codec_remove_notify_all
[ 1801.298653] snd_hda_intel: Unknown symbol snd_hda_resume
[ 1801.298768] snd_hda_intel: Unknown symbol snd_hda_build_controls

Revision history for this message
W.McL (w-mcl) wrote :

My Problem was caused by the proprietary hsfmodem driver which was still present from gutsy and had renamed the original snd-intel-hda module.
Removing the hsfmodem driver solved the problem.

Revision history for this message
Patricio (patricio-stwing) wrote :

patricio@patricio-desktop:~$ uname -a
Linux patricio-desktop 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
I have problems recording, kind of noisy. But I can hear my voice clear when I am recording, then when I reproduce it sounds noisy. I am using "Sound Recorder"
thanks!
Patricio

        *-multimedia
             description: Multimedia audio controller
             product: VT82C686 AC97 Audio Controller
             vendor: VIA Technologies, Inc.
             physical id: 14.5
             bus info: pci@0000:00:14.5
             version: 20
             width: 32 bits
             clock: 33MHz
             capabilities: cap_list
             configuration: driver=VIA 82xx Audio latency=0 module=snd_via82x

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.