From alsa-user-owner@alsa.jcu.cz  Tue Jul 28 15:39:29 1998
Received: from entry.jcu.cz (perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.8.8/8.8.8) with SMTP id PAA14186;
	Tue, 28 Jul 1998 15:35:30 +0200
Date: Tue, 28 Jul 1998 15:35:30 +0200 (MET DST)
From: Jaroslav Kysela <perex@jcu.cz>
To: William Yongwoo Jhun <wjhun@Glue.umd.edu>
cc: alsa-user@alsa.jcu.cz
Subject: Re: YMF715B
In-Reply-To: <Pine.GSO.3.95q.980728091223.13270B-100000@rac1.wam.umd.edu>
Message-ID: <Pine.LNX.3.96.980728153049.13314F-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

On Tue, 28 Jul 1998, William Yongwoo Jhun wrote:

> Hello. I just tried compiling/installing the 0.2.0-pre2 ALSA driver with
> my notebook (which has an OPL3-SAx or the YMF715(B?) soundchip). At first

YMF715 is OPL3-SA3 chip..

> I get complaints about init_module and snd already being in use, and tried
> pnpdump/isapnptools. But this chip is actually not in PnP mode. My laptop
> has specific configuration settings for the audio chip in the BIOS (all
> the addresses, DMAs and the one IRQ). BIOS even has an option to "lock"
> the settings so that they cannot be changed. I tried changing it back to
> "Auto" mode (PnP?) with no success; pnpdump doesn't find any isapnp
> devices.
> 
> So I am guessing that this chip is already configured when I bootup. I
> specified the port/dma/irq settings as described in the INSTALL text by
> placing the correct lines in conf.modules (I don't have the lines with me,
> sorry.) This seems to have little effect. I still get the two "resource"
> errors. Sorry I don't have a little more detailed information at the
> moment ... just wondering if this rings a bell with anyone. I read through
> all the docs but can't seem to find the solution...

I need to know if some lines are in /var/log/messages file from ALSA
driver. Have you specified all i/o ports? ALSA can't detect ports for
OPL3-SA3 chip automaticaly.

You can also try configure and compile driver with 'configure
--with-debug=detect'. ALSA driver shows more messages if something is
wrong with detection of OPL3-SA3 chip..

Driver is only tested with OPL3-SA3 in PnP mode (initialized via
isapnptools) integrated on motherboard from Intel (I don't remember
name, but it's an Pentium II motherboard).

					Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


