Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Conde Martinez Rodolfo <rconde@ada.fciencias.unam.mx>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64
Date: Mon, 22 Feb 1999 04:24:35 +0000	[thread overview]
Message-ID: <marc-linux-sound-91965813932396@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91965172830159@msgid-missing>

On Mon, 22 Feb 1999, Keith Duthie wrote:

# On Sun, 21 Feb 1999, Conde Martinez Rodolfo wrote:
# 
# > 	With my SB AWE64, i haven't been able to make the
# > Awe wave table work, awe_wave says it doesn't dettect it and i tried
# > uncommenting the lines in awe_config.h about the base io address and the
# > DRAM size, it prints <SoundBlaster EMU..blabla> then i load a font with
# > sfxload and try drvmidi but there isn't any sound, playmidi says something
# > like no playback device found aborting.....What can it be ??...the other
# What is the exact error?
# 
# One thing you could try is to make sure all sound related devices exist in
# /dev. A list of sound related devices can be found in
# /usr/src/linux/Documentation/devices.txt under "14 char".
# Unlikely to be the problem, but unfortunately you haven't exactly given
# much detailed information about the problem.

	

	I went to find out and in the part of 14 char i'm only missing the
following:


		 17 = /dev/patmgr0	Sequencer patch manager
		 33 = /dev/patmgr1	Sequencer patch manager
		  0 = /dev/dos_hda	First BIOS harddrive whole disk
		 64 = /dev/dos_hdb	Second BIOS harddrive whole disk
		128 = /dev/dos_hdc	Third BIOS harddrive whole disk
		192 = /dev/dos_hdd	Fourth BIOS harddrive whole disk



	and /dev/sequencer1 too.....


# 
# Have you tested the card as described in 4.1 of the Soundblaster-AWE
# mini-HOWTO?
# -- 

	Right know i can't do but i will try it and see what happens.....



	Thanks for answering !!!!!!



# .sig under deconstruction. Please watch out for falling stars.
#                           O-        +++ATH0
# 
# 

-------------------------------------------------------------------------------
| Rodolfo Conde Mtz                   Universidad Nacional Autonoma de Mexico |
| ICQ      14757500                   Facultad de Ciencias                    |
| e-mails:                            Ciencias de la Computacion              |
| rconde@ada.fciencias.unam.mx                                                |
| conderodolfo@usa.net                                                        |
-------------------------------------------------------------------------------

  reply	other threads:[~1999-02-22  4:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-22  2:37 AWE64 Conde Martinez Rodolfo
1999-02-22  4:24 ` Conde Martinez Rodolfo [this message]
1999-02-22 21:20 ` AWE64 Keith Duthie
1999-11-18 22:06 ` AWE64 Dave Mielke
1999-11-18 22:38 ` AWE64 Heikki Kallasjoki
1999-11-19  4:29 ` AWE64 Dave Mielke
1999-11-19 14:53 ` AWE64 Heikki Kallasjoki
1999-11-19 18:32 ` AWE64 Paco
1999-11-19 18:49 ` AWE64 Bill Nottingham
1999-11-19 18:57 ` AWE64 Paco
1999-11-19 18:58 ` AWE64 Paco
  -- strict thread matches above, loose matches on Subject: below --
1999-11-18 21:20 AWE64 Great One

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-91965813932396@msgid-missing \
    --to=rconde@ada.fciencias.unam.mx \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox