On Tue, 2004-06-22 at 11:15 +1000, [EMAIL PROTECTED] wrote: > I tried setting the volume with the alsamixer. It defaulted to the > Audigy card and I used it to set the volume to max; still no sound.
Did you try using "alsamixer -c1"? Anyway, it sounds like the problem is
your modprobe.conf.
> I have again run XMMS, which believes it is making a sound but still
> no sound.
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 don't know which driver the audigy card should use under alsa, can
someone who's using this please mail and let us know? I think you should
put something like this:
alias sound-slot-0 <the audigy driver>
You will need to have some other lines in order to load the oss
emulation, but wait till you get alsa working with xmms to tinker with
that. That line alone should be enough to make sound work. Be aware that
with only that line, only the alsa utils and apps will work. aumix will
not work, but alsamixer will. Likewise, you need to use the xmms-alsa
output plugin.
>
> I changed references to audigy in modules.conf to emu10k1; no effect.
> So I set them back and changed references to emu10k1 in modprobe.conf
> to audigy; no effect. So I changed these back.
modules.conf will have no effect in FC2. It uses a 2.6 kernel. The 2.6
kernel does not read that file. I don't have an 'audigy' driver in my
2.6 kernel. It sounds like that's an OSS driver (deprecated in 2.6), so
it also won't work.
>
> Still whenever I boot RedHat 9.0/Linux 2.4 the sound works, except
> when I changed modules.conf to refer to emu10k1.
I'm curious, what do you mean by rebooting to redhat 9? do you have two
concurrent installations?
> 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.
> alias eth0 e1000
> 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 scsi_hostadapter sata_sil
HTH,
James.
--
James Gregory <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
