All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64 initial questions
Date: Wed, 09 Sep 1998 21:03:42 +0000	[thread overview]
Message-ID: <marc-linux-sound-90538694432647@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90515879913606@msgid-missing>

Dave Wreski (dave@nic.com) said: 
> Ok, as it turns out, I did get it going.  I used the sndconfig program found at
> ftp.redhat.com:/pub/sound/ and it generated an /etc/isapnp.conf file identical
> to yours.  Has anyone else used this program, or must I go to
> redhat-sound@redhat.com for questions on this?

Actually, that's sound-list@redhat.com. But no, you don't need to
go there.

> After using 'isapnp /etc/isapnp.conf', how can I tell it worked?  It didn't
> complain, but there was also no information available in the normal /proc files,
> such as /proc/{interrupts,dma,ioports} etc..  Should there be, or only after the
> sound module is installed?

No; the information will only show up in /proc after the resources
have been allocated by the kernel (i.e., the drivers have been loaded).

> > Remember that you have to download a sound font bank to the Wave table
> > with a command like this:
> > 
> > /usr/local/bin/sfxload
> > /win95/Programme/Creative/ctsnd/sfbank/synthgs.sbk
> 
> Where can I find these necessary files?

sfxload is part of the awesfx package, available from
	http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/index.html
There's an RPM in contrib (I haven't tested it, but it should work
fine).

synthgm.sbk/synthgs.sbk should be on your AWE64 driver disk/CD.

Bill

  parent reply	other threads:[~1998-09-09 21:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-07  3:18 AWE64 initial questions Dave Wreski
1998-09-08 20:06 ` Emil Stephan
1998-09-09  5:02 ` Dave Wreski
1998-09-09 14:39 ` Maddog Abel
1998-09-09 15:03 ` Juan Lupion
1998-09-09 19:40 ` Emil Stephan
1998-09-09 20:03 ` Dave Wreski
1998-09-09 21:03 ` Bill Nottingham [this message]
1998-09-09 22:13 ` Dan Hollis
1998-09-10  3:10 ` Dave Wreski
1998-09-10 16:23 ` Juan Lupion
1998-09-10 22:51 ` Dave Wreski
1998-09-10 23:22 ` Dan Hollis
1998-09-11  9:29 ` Hamish Moffatt
1998-09-11  9:31 ` Hamish Moffatt
1998-09-11 14:16 ` Dave Wreski
1998-09-11 18:59 ` Adam Wiggins
1998-09-12 10:11 ` Hamish Moffatt
1998-09-12 19:54 ` rtlynch
1998-09-13  0:51 ` Dave Wreski
1998-09-13  2:04 ` Jim
1998-09-13  2:11 ` llornkcor
1998-09-14 18:51 ` Adam Wiggins
1998-09-14 20:09 ` Dave Wreski
1998-09-15 15:14 ` rtlynch
1998-09-16  1:39 ` Bill Nottingham
1998-09-19 12:59 ` Hamish Moffatt
1998-09-19 13:01 ` Hamish Moffatt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-sound-90538694432647@msgid-missing \
    --to=notting@redhat.com \
    --cc=linux-sound@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.