On Wed, 2003-04-02 at 13:18, Adam Jones wrote:
> On 02-Apr-03, Lance A. Brown wrote:
>
> > Man, I thought I was the only one getting this problem. I've got a
> > Santa Cruz Turtle Beach in my system and a GeForce2 MX400 and thought
> > I was having problems with my
On Wed, 2003-04-02 at 15:36, Friedrich Ewaldt wrote:
> Hmm, I also had some lockups with the nvidia drivers.
>
> Download newest nvidia driver + GLX module.
Hmmm. Turns out I'm behind again on this. I'll download tonite and see
what happens.
> Check for the correct driver and GLX version (must
On Tue, 2003-04-01 at 12:37, Romulus Pfeiffer wrote:
> Hi there,
>
> I have a problem with my soundcard. I have a "TERRATEC - DMX
> XFire 1024" (chip CS4624-CQ).
> The problem is that my system hangs up after an undefined
> time but only when the soundcard is in use e.g. when I hear
> music. It ha
On Sat, 2003-03-29 at 22:11, kmberry wrote:
> I went form 8.0 to phoebe, lost crossover plugin, and finally rawhide.
> After messing with 2.5.x kernels and still not getting alsa working I
> got a tarball of 2.4.20 and compiled it and now alsa compiles and loads
> without schedule_work problem.
On Tue, 2003-02-11 at 16:22, Andrew Heil wrote:
> In order to not have to run alsamixer every time I boot into Linux, I
> thought I had to run alsamixer, select the sound levels I want, and then
> run alsactl with the "store" option, but evidently this is wrong! :-)
>
> Would someone be so kind
Greetings,
I just upgraded to ALSA 0.9.0rc6 on my system at home with a Turtle
Beach Santa Cruz (Sound Fusion CS46xx, Cirrus Logic CS4297A rev 4,Cirrus
Logic CS4294 rev 5) and now have a whole LOT more controls in
alsamixer. I checked the TB site but didn't find anything useful about
learning how
