discover init script returns, wreaks havoc

[Todd Maynard]

After rebooting system it appears that alsa is no longer working.

Alsa starts with:

todd@toddlaptop:/var/log $ sudo /etc/init.d/alsa start
Password:
 * Restoring ALSA mixer settings...
alsactl: load_state:1134: No soundcards found...

System Notifications seem to be routed to PC Speaker. I CAN play MP3s through
Rhythmbox (no idea what Rhytmbox uses ALSA/OSS/ESD etc.)

Everything worked fine with Warty install.

What are the next steps to troubleshoot? What additional info is needed?

Thanks

[Matt Zimmerman (mdz)]

None of the relevant packages have changed between Warty and Hoary, and it works
fine on my Hoary systems. What have you changed?

[Todd Maynard (toddmaynard)]

The only I can think of that could be related was that I installed the
lm-sensors package.
There seem to be a few people with related problems on the forums:
http://www.ubuntuforums.org/showthread.php?p=9253

lsmod, dmesg, and lspci look OK to my (somewhat newbie) eyes.

What other info do you need?

[Todd Maynard (toddmaynard)]

Created an attachment (id=663)
dmesg - lsmod - lspci output

dmesg - lsmod - lspci output

[Matt Zimmerman (mdz)]

You have both ALSA and OSS drivers loaded. By default, the ALSA drivers are
loaded automatically by hotplug, and the OSS drivers are explicitly excluded
from that mechanism. If you were not seeing this message before, you must have
changed something to cause the via82cxxx_audio module to be loaded. Undo that,
and you should be fine.

[Todd Maynard (toddmaynard)]

Thanks for the info Matt. I think I understand what is going on now.

on boot, hotplug is loading after discover

todd@toddlaptop:/etc/rcS.d $ ls
README S10checkroot.sh S26lvm S36lm-sensors
S43portmap S70screen-cleanup
S02mountvirtfs S18hwclockfirst.sh S27evms S36mountvirtfs
S45mountnfs.sh S70xfree86-common
S04udev S18ifupdown-clean S30checkfs.sh S38pppd-dns
S48console-screen.sh S75sudo
S05bootlogd S20module-init-tools S30procps.sh S39dns-clean
S50hwclock.sh S80slashem
S05initrd-tools.sh S20modutils S35hotplug S39ifupdown S51ntpdate
S05keymap.sh S25libdevmapper1.00 S35mountall.sh S40hostname.sh
S55bootmisc.sh
S07hdparm S25mdadm-raid S36discover S40networking S55urandom

discover is finding the sound card and loading via82cxxx_audio instead of
snd_via82xx

todd@toddlaptop:/usr/share/discover $ cat pci.lst | grep via82cxxx_audio
        11063058 sound via82cxxx_audio VT82C686 AC97 Audio Controller
        11063059 sound via82cxxx_audio VT8233/A/8235/8237 AC97 Audio
Controller
        11064511 sound via82cxxx_audio AC97 Audio

The hotplug blacklist doesn't get to come into play. I can workaround this by
either

a. deleting/renaming
/lib/modules/2.6.8.1-3-686/kernel/sound/oss/via82cxxx_audio.ko- will be wiped on
kernel upgrade
b. moving hotplug init script to start before discover - probably a bad idea I'm
guessing

I'm gussing the correct thing to do is to have /usr/share/discover/pci.lst load
snd_via82xx instead of via82cxxx_audio.
I'm also gussing that this would have to be done with all of the other OSS
modules/drivers as well.

How far off base am I here? Thanks for the help.

[Matt Zimmerman (mdz)]

Hmm, the init script for discover was disabled in Ubuntu many versions ago for
exactly this reason, but apparently the change was inadvertently dropped during
the recent merge.

[Matt Zimmerman (mdz)]

discover1 (1.7.3ubuntu3) hoary; urgency=low

  * Remove the init script (again), it snuck back in during the merge

 -- Matt Zimmerman <email address hidden> Sun, 31 Oct 2004 16:41:10 -0800

[Matt Zimmerman (mdz)]

*** Bug 9795 has been marked as a duplicate of this bug. ***

[Eddie Man (superman-eddie)]

I think my situation is exactly want you are, but I don't know how to solve this
problem, even I renamed the via82cxxx_audio.ko, my sound card is still not
working, I don't know how to moving the sequence of hotplug script. Can you give
me more advance about this?

[Matt Zimmerman (mdz)]

To clean up if you were affected by this bug:

sudo rm /etc/rc?.d/*discover

[Eddie Man (superman-eddie)]

root@eddienotebook:~ # sudo rm /etc/rc?.d/*discover
rm: cannot remove `/etc/rc?.d/*discover': No such file or directory

The above error message is displayed. Then how can I do?

[Matt Zimmerman (mdz)]

Then you aren't suffering from this bug.