From alsa-user-owner@alsa.jcu.cz  Wed Jul 29 00:07:32 1998
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id AAA14865
	for <alsa-user@jcu.cz>; Wed, 29 Jul 1998 00:07:20 +0200
Received: from rac8.wam.umd.edu ((IDENT root)@rac8.wam.umd.edu [128.8.10.148])
	by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id SAA01531
	for <alsa-user@jcu.cz>; Tue, 28 Jul 1998 18:07:18 -0400 (EDT)
Received: from rac8.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1])
	by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id SAA03925
	for <alsa-user@jcu.cz>; Tue, 28 Jul 1998 18:07:17 -0400 (EDT)
Received: from localhost by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id SAA03920
	for <alsa-user@jcu.cz>; Tue, 28 Jul 1998 18:07:16 -0400 (EDT)
Date: Tue, 28 Jul 1998 18:07:15 -0400 (EDT)
From: William Yongwoo Jhun <wjhun@wam.umd.edu>
To: alsa-user@jcu.cz
Subject: Re: YMF715B
In-Reply-To: <Pine.LNX.3.96.980728153049.13314F-100000@entry.jcu.cz>
Message-ID: <Pine.GSO.3.95q.980728180049.3643A-100000@rac8.wam.umd.edu>
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, Jaroslav Kysela wrote:

> 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.

I have specified all ports in conf.modules. I believe there's an error (I
could be wrong) in the INSTALL file: snd_mpu_port was undefined, so I
tried snd_midi_port and it accepted it.

Anyhow, the same problem remained, and the following lines are in
messages:

Jul 28 18:00:03 ashley kernel: snd: OPL3-SA [0x100] detect (0) = 0x83
Jul 28 18:00:03 ashley kernel: snd: Yamaha OPL3-SA soundcard #1 not found
at 0x100 or device busy
Jul 28 18:00:03 ashley kernel: snd: Yamaha OPL3-SA soundcard not found or
device busy

Before I changed it to snd_midi_port, it complained:
Jul 28 17:42:04 ashley kernel: snd: probing for Yamaha OPL3-SA isn't
supported
Jul 28 17:42:04 ashley kernel: snd: port = 0x100, wss_port = 0x530,
fm_port = 0x388, midi_port = 0xff
Jul 28 17:42:04 ashley kernel: snd: Yamaha OPL3-SA soundcard #1 not found
at 0x100 or device busy
Jul 28 17:42:04 ashley kernel: snd: Yamaha OPL3-SA soundcard not found or
device busy


However, these are the *exact* settings as specified in the notebook BIOS.
I'm sure it's configured and no longer in PnP mode - pnpdump reports
absolutely nothing. port should be the "control port", correct?

I'll keep playing with it and see what comes up. What does detect (0) =
0x83 mean? I tried changing port to the sb port and the wss port, but in
both cases I get back 0xFF instead of 0x83.

Please excuse my ignorace...I'm still trying to figure out how these
drivers generally work.

Thanks again,
William

> 
> 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
> 
> ------
> To unsubscribe from <alsa-user@alsa.jcu.cz> mailing list send message
> 'unsubscribe' in the body of message to <alsa-user-request@alsa.jcu.cz>.
> 


