I have taken the latest steps suggested by James Gregory, as I will outline below (in case others experience similar difficulties) and they were unsuccessful. However, in the meantime I managed to suceed on my second front, so I won't be pursuing this further - see my posting RedHat 9.0/Linux 2.4 broken mouse.
>Did you try using "alsamixer -c1"? Anyway, it sounds like the problem is >your modprobe.conf. I tried the alsamixer-c business earlier and showed the audigy card as the first and the onboard as the second card. >How is xmms configured? Are you using the alsa output plugin? the esd >one? >If you configure it to use alsa (by right clicking on xmms and going to >preferences in the options menu), the 'configure' button on that screen >will take you to a dialog that lets you choose the device to output to. On >my installation it is nice enough to name the output device that it's >going to use here. It also shows you alsa's numbering of the sound cards. >I suspect you will have esd running, so if it says it can't open the sound >device, then run 'killall esd', which should shut down any running esd >processes. You may need to install an xmms-alsa package (or similar) to >make the alsa option appear in that menu. I don't remember the FC2 name >for that package (my FC2 box isn't accessible right now), but it should be >reasonably obvious when you're looking through the list of xmms-* >packages. I switched to Alsa. Found that I had three options Default (onboard), Sound Blaster Audigy: EMU10K1 (hw:0,0), and Sound Blaster Audigy: EMU10K1 FX 8010 (hw:0,3). Chose the second, applied, stopped and played XMMS, still happy to play but no sound (by the way at least now all mixers leave the sound sliders up). Chose the third and got the can't open sound device message and did the killall esd and retied and got the same message. returned to option 2, having done the killall, and xmms was once again happy to play, but still no sound. >I'm curious, what do you mean by rebooting to redhat 9? do you have two >concurrent installations? Before upgrading from RedHat 9.0 to Fedora Core 2 I had four kernels in the grub, two RedHat 8 and two RedHat 9, one each for smp and not smp. Upon upgrade, Fedora left me with the default of these four, 2.4...smp, removed the others and added its own two kernels, 2.6 and 2.6...smp. Now when I boot 2.4, the advertising tells me I'm running Fedora Core 2. Everything works fine except the mouse - see my posting RedHat 9.0/Linux 2.4 broken mouse. > The contents of /etc/modprobe.conf are: > #Note: for use under 2.4, changes must also be made to > # modules.conf! > alias char-major-61-* lirc_sir > alias usb-controller ehci-hcd > alias usb-controller1 uhci-hcd > alias ieee1394-controller ohci1394 > alias snd-card-0 snd-emu10k1 >I don't think it makes any difference, but suggest you change that to >'sound-slot-0', just to be consistent. I had tried changing this - no impact. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
