From alsa-user-owner@alsa.jcu.cz  Fri Feb 26 14:43:31 1999
Received: from pc117179.shef.ac.uk (root@pc117179.shef.ac.uk [143.167.117.179])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id OAA05124
	for <alsa-user@alsa.jcu.cz>; Fri, 26 Feb 1999 14:43:08 +0100
Received: by pc117179.shef.ac.uk
	via sendmail from stdin
	id <m10GNDj-0001jvC@pc117179.shef.ac.uk> (Debian Smail3.2.0.102)
	for alsa-user@alsa.jcu.cz; Fri, 26 Feb 1999 13:22:23 +0000 (GMT) 
Date: Fri, 26 Feb 1999 13:22:23 +0000
From: Jose L Gomez Dans <j.l.gomez-dans@sheffield.ac.uk>
To: alsa-user@alsa.jcu.cz
Subject: Re: New woes with ESS Solo1 card!
Message-ID: <19990226132223.C208@shef.ac.uk>
References: <19990224194412.A958@shef.ac.uk> <Pine.LNX.4.04.9902242325150.825-100000@syrjala.pp.sci.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.4.04.9902242325150.825-100000@syrjala.pp.sci.fi>; from Ville Syrjala on Wed, Feb 24, 1999 at 11:28:11PM +0200
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

On Wed, Feb 24, 1999 at 11:28:11PM +0200, Ville Syrjala wrote:
> On Wed, 24 Feb 1999, Jose L Gomez Dans wrote:
> 
> > After the couple of messages that came up last week on ESS Solo1, I guess I
> > have to buy myself a gun and commit suicide...
> > 
> > 	I am running a 2.2.2 kernel (I thought I'd help :D), without sound
> > support, and I have a ess solo1 card. I downloaded the drivers (0.3 pre4),
> 
> You must have sound support in kernel 2.2.x for ALSA to work. Just the
> basic sound support option, none of the soundcard drivers. This module is
> called soundcore.o. Read the ALSA INSTALL file, it explains everything.

	Thanks for the help, that problem is sorted. Curiously enough, I
could bypass such problems by installing 0.3-pre2, and still have my kernel
without sound support :)))))

	My problem now is that I modprobe snd-esssolo1 and snd-pcm1-oss (as
someone mentioned in an earlier message). I turn the master channel on
(i.e., I unmute it), and if I try to play something, the computer crashes.
So far, it has been the only way of crashing Linux, but quite an effective
one :) No marks are left in the logs or anything. The systems just freezes,
and I have to reset it.

	Any further ideas?
		Thanks!
		Jose

-- 
Jose L Gomez Dans			PhD student
					Radar & Communications Group
					Department of Electronic Engineering
					University of Sheffield UK

