Comment 5 for bug 9778

Revision history for this message
Todd Maynard (toddmaynard) wrote :

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.