On Tue, 2002-12-10 at 23:55, Bob Lockie wrote:
> Run the command "alsamixer" and unmute everything you see.
> Note: things will be muted again if you reboot.
you can do
alsactl store
to save alsamixer settings and add
post-install snd-intel8x0 /usr/local/bin/alsactl restore
to modules.conf (ta
>I have multiple CDROM drives on my Redhat machine and alsaplayer seems
> fixated on choosing the one I don't want it to choose to play an audio CD.
> How do I go about configuring alsaplayer, or else Redhat itself, to choose
> the specific CDROM drive I want it to choose?
>
>I was sort of
Strange little app. There was nothing about devices in my config file.
Then I told it to play a CD, and it wrote one path (/dev/cdrom) in the
config file. Then I edited the config file and changed that entry to
/dev/cd2 and then it plays CDs. Strange little app.
Cool. It works File that one aw
> Yes, I had looked by the config file didn't have any obvious device
> settings...
At the end of my ~/.alsaplayer/config file I find this line:
cdda.device=/dev/cdrom
Most probably you can add this to yours with the device of your choice.
-- Fernando
> On Wed, 2002-12-11 at 16:09, Fernando Pa
On Wed, 11 Dec 2002, Uros Bizjak wrote:
> Date: Wed, 11 Dec 2002 08:17:10 +0100
> From: Uros Bizjak <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Alsa-user] Help with equalizer on cs4236
>
> Hello!
>
> > I've included modules.conf and the output of lsmod below. I did not
> > compile
Yes, I had looked by the config file didn't have any obvious device
settings...
Thanks.
On Wed, 2002-12-11 at 16:09, Fernando Pablo Lopez-Lezcano wrote:
> >I have multiple CDROM drives on my Redhat machine and alsaplayer seems
> > fixated on choosing the one I don't want it to choose to play
Hi,
I have multiple CDROM drives on my Redhat machine and alsaplayer seems
fixated on choosing the one I don't want it to choose to play an audio CD.
How do I go about configuring alsaplayer, or else Redhat itself, to choose
the specific CDROM drive I want it to choose?
I was sort of surpris
hi to you all. i, too, have via8235 southbridge, ac97 codec, but i'm using
RH7.3 w/custom kernel 2.4.18. try running alsaconf script from tools or
utils dir of alsa source. that's the easiest way. it'll automatically
configure your card and modules.conf.
___
You're backwards on the pc speaker... this is an INPUT. You connect
your pc speaker to your soundcard through this little plug... then the
pc speaker sound is routed through your soundcard to your speakers... I
highly recommend that you DO NOT do this. It works, but it sounds
terrible... not
I have an SB PCI 128 (ens1371 chip) and I am using the last alsa 0.9
Multiplexing seems to run great, I can listen music on /dev/adsp and play a game on
/dev/dsp.
But, I don't manage to use a microphone on /dev/adsp with TeamSpeak software (it works
with /dev/dsp) I and need to make running my mi
subject says it, Redhat 8.0, pcmcia-cs 3.2.3, not using kernel pcmcia. I
run configure and it does not detect PCMCIA so it does not build
pcmcia/vx/*
any suggestions? I would really like to beta test these drivers?
-asher
--
Asher Yanich
-0- Systems and Network Support -0-
-0- Flo
Hi everybody,
Has anybody compiled ALSA along with kernel 2.4.19? Actually all
the how-tos say I should compile alsa modules separately and put them in
proper directories( do make install ). But I would like to put all the
alsa driver configuration inside kernel config file. So that when I
At Wed, 11 Dec 2002 08:56:06 +0100 (MET),
Clemens Ladisch wrote:
>
> [EMAIL PROTECTED] wrote:
> > > Apparently, the Windows driver did change the firmware.
> > > Does it still work after the Extigy was unplugged?
> >
> > no!
> >
> > > > I wonder what's up with alsamixer?
> > >
> > > Probably some
Sage wrote:
> > I have a Midiman Delta 66 that uses the envy24 alsa driver. The Windows
> > drivers for this card have a feature that enables me to lock the output
> > rate (in kHz) to whatever level I want. If I set it to 96 kHz,
> > everything will be upsampled to 96 kHz before it goes out to the
[EMAIL PROTECTED] wrote:
> > Apparently, the Windows driver did change the firmware.
> > Does it still work after the Extigy was unplugged?
>
> no!
>
> > > I wonder what's up with alsamixer?
> >
> > Probably some problem with old entries in /etc/asound.state. Try deleting
> > it.
>
> I had already
15 matches
Mail list logo