Need to run system-config-sound after every boot too make sound work in FC2
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Need to run system-config-sound after every boot too make sound work in FC2
Hi All,
Having just upgraded from FC1 to FC2 and worked through the many niggles it causes, I'm down to just one. To make my soundcard work, I have to run the system-config-soundcard utility at the beginning of every session. Can anyone suggest how to make the configuration permanent?
I've got an integrated soundcard on an NVidia nForce2 DDR socket A mainboard (NF24-ALH). The alsa drivers ARE installed, but I haven't done any manual configuration since the upgrade.
I don't use FC2, I use Slackware, but in slackware you can change the sound settings with alsamixer and save them (as root) with "alsactl store". If FC2 has alsactl you might want to try this.
# Note: for use under 2.4, changes must also be made to modules.conf!
alias usb-controller ohci-hcd
alias usb-controller1 ehci-hcd
alias eth0 nvnet
alias usb-interface usb-ohci
alias snd-card-0 snd-intel8x0
alias char-major-195-* nvidia
install sound-slot-0 /sbin/modprobe --first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :; } ; /sbin/modprobe -r --first-time --ignore-remove sound-slot-0
alias /dev/ttySHCF[0-9]* /dev/ttySHCF
alias /dev/modem /dev/ttySHCF
alias char-major-240 /dev/ttySHCF
alias char-major-240-* /dev/ttySHCF
options hcfpciserial serialmajor=240
alias /dev/hcfpcidiag hcfpciosspec
alias /dev/hcfpcidiag* /dev/hcfpcidiag
alias char-major-242 /dev/hcfpcidiag
alias char-major-242-* /dev/hcfpcidiag
options hcfpciosspec diagmajor=242
install /dev/ttySHCF /sbin/modprobe hcfpcihw
My sound driver is snd-intel8x0. So I should add your alias-soundservice lines?
Whansard: I think your option will just bring up the configuration dialog at every boot won't it?
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
i didn't know it was a dialog config. sorry. i'll have some new distros on my computer soon, and i'll get caught up on the changes over the past few years.
I had a similar problem once. I don't think it's the drivers. What you need to do is to make an empty file called asound.state in /etc and then adjust your settings as you wish. Then run alsactl and reboot. worked for me. The problem is that for some strange reason asound.state doesn't exist so it has nowhere to store the settings
Thanks for the reply- but no, the file does exist. Though maybe I'll try deleting it and replacing it with a blank- perhaps it's remembering some wrong settings or something.......
Originally posted by jrbiochem Thanks to all for your replies,
MobyTurbo : Tried your idea, no change
Syd: Had a look at my version of the file:
Jon
I think you should try adding the lines, yes. I think if you run into any trouble you could set the system to boot into runlevel 3 and do interactive bootup so that you can individually load modprobe.conf lines.
I think it will work, though. As long as you replace sb-awe with your driver.
Originally posted by whansard add it to the end of /etc/rc.d/rc.local
if that file exists. that might do it.
whansard has a good idea. You need to use a different command though. Infact, I had the same problem when I first did the FC1->FC2 upgrade. At the time, I was using a CT5880 (aka, one of the later versions of the Sound Blaster 16 PCI). It used the snd-ens1371 driver. So, all I did was add 'modprobe snd-ens1371' to my /etc/rc.d/rc.local. Your card is obviously going to use a different driver, but the same idea may work; try adding 'modprobe [kernel sound module]' to your rc.local file and see if that takes care of it (making sure to replace '[kernel sound module]' with the kernel module appropriate for your sound card).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.