From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830 Description of problem: I've just installed RHv8.0. Next, I installed a (new) SB16 PCI sound card.Then I ran sndconfig to setup/test the sound card. Everything works ok, the modules.conf file is configured as shown below... [doug@localhost etc]$ cat modules.conf alias parport_lowlevel parport_pc alias eth0 tulip alias usb-controller usb-ohci alias usb-controller1 usb-uhci alias sound-slot-0 es1371 post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || : pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || : [doug@localhost etc]$ Here's the problem...after I reboot the system the sound card does not work. I have to rerun sndconfig to get it working again. BTW. When I run the redhat-config-soundcard program I get the following information... Vendor - Ensoniq Model - 5880 AudioPCI Module - es1371 Doug Young Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Reboot 2.Test sound card - no sound 3.Run sndconfig - now sound works Actual Results: No sound through the speakers after a reboot. Expected Results: Sound card should work after booting system. Additional info: I have never been able to get the sound working on this installation of RH.
Hm, that's a PCI card, so it should work out of the box. Perhaps it's a driver issue?
I agree, it should work out of the box. If it's a driver problem then why would the soundcard work after I run the sndconfig utility? Whatever this utility does to enable the soundcard is needed in the system startup. Since I'm still a newbie to Linux I'm struggling to learn the system level programs/procedures. One question...is there any reason to believe compiling this module into the kernel would correct the problem? I really don't think it would help but I'm not too sure. Doug
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/