AWE64

AWE64

[Conde Martinez Rodolfo]

	Hi all, i'm new here, heard about the list and here i'm with a
problem with SB AWE64 PnP (i guess i'm not the first one to ask about it) 

	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
modules load well and detect the card, Could it be that the card has
enabled the mpu-401 uart, i read in the manuall that it's disabled setting
a jumpper ??? Acording to OSS/Comercial my card is a Creative SB AWE64 PnP
type 4


	About the PnP think i have used first the bios to configure
devices, it works ok with the modem know, and with the Sb it configures it
too....supposed because everythink works but the wave table, and then i
tried isapnptools with the three io's required for the table but didn't
work :( Any ideas would be apreciated.....

 

	Thanks for your answers !!!!!



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

Re: AWE64

[Conde Martinez Rodolfo]

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

Re: AWE64

[Keith Duthie]

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.

Have you tested the card as described in 4.1 of the Soundblaster-AWE
mini-HOWTO?
-- 
.sig under deconstruction. Please watch out for falling stars.
                          O-        +++ATH0

AWE64

[Great One]

i'm using Red Hat Linux 6.0
and i can't install sound blaster awe64 here
when i run kernel configuration everything
appears to be ok. the option creative sb awe32/64
is checked but it doesn't work.

does anybody know how to solve this problem ?

thank you

    

Re: AWE64

[Dave Mielke]

[quoted lines by Great One on November 18, 1999, at 21:54]

>i'm using Red Hat Linux 6.0
>and i can't install sound blaster awe64 here
>when i run kernel configuration everything
>appears to be ok. the option creative sb awe32/64
>is checked but it doesn't work.
>
>does anybody know how to solve this problem ?

Have you run the RedHat tool "sndconfig" yet? It'll put all the right stuff
into "/etc/conf.modules", which you'll need or your sound card will not work.
If you've done that already, then let me know and I'll help you check out your
kernel configuration. Attaching a copy of your ".config" file to your next
reply would be helpful.

-- 
Dave Mielke           | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2B 6G3   | if you're concerned about Hell.

Re: AWE64

[Heikki Kallasjoki]

On 18.11.99, at 17:06, Dave Mielke wrote with subject 'Re: AWE64':
> >i'm using Red Hat Linux 6.0
> >and i can't install sound blaster awe64 here
> >when i run kernel configuration everything
> >appears to be ok. the option creative sb awe32/64
> >is checked but it doesn't work.
> >
> >does anybody know how to solve this problem ?

> Have you run the RedHat tool "sndconfig" yet? It'll put all the right stuff
> into "/etc/conf.modules", which you'll need or your sound card will not work.
> If you've done that already, then let me know and I'll help you check out your
> kernel configuration. Attaching a copy of your ".config" file to your next
> reply would be helpful.

Here's not a solution to the situation where the card would not work at
all, but to a common problem that the audio playing features work fine but
the wavetable-driver refuses to find the card. The beginning of the next
chapter doesn't sound like it would belong there, but that's just because
I wrote it first and then this 'introduction', or something.

Another possible problem with sbAWE64, that many people seem to have, is
the fact that pnpdump fails to recognize correctly those IO-ports for the
wavetable part of the card. I have never used Red Hat personally, so I
don't know much about how configuring it goes, but when you get the card
working so that sound can be heard, if you then notice that the wavetable
driver doesn't find the card, and it is a PnP version, (is there a
non-PnP-awe64?) the cause might be this.

Usually isapnp's configuration file is /etc/isapnp.conf, and when created
with pnpdump like it's usually done, there's lines like:
--clip--
(CONFIGURE CTL00e4/297738542 (LD 2
#     ANSI string -->WaveTable<--
#..comments..
(IO 0 (BASE 0x0620))
--clap--

Now, AWE64 uses also ports 0xA20 and 0xE20 in addition to 0x620, and all
implementations of pnpdump I've seen have been unable to detect that. So,
one should replace the line
(IO 0 (BASE 0x0620))
with something like
--clip--
(IO 0 (BASE 0x0620))
(IO 1 (BASE 0x0A20))
(IO 2 (BASE 0x0E20))
--clap--
in /etc/isapnp.conf.

This isn't a reason why the card would not work at all, but this is often
a reason for the wavetable-synth to not function. As I said, I haven't
seen Red Hat much, so I don't know if they had fixed this problem
somehow. Anyway, I thought that this should once again be mentioned here,
because so many people keep asking about it.

 --fiz.
-------------------
"Darkness brushes its steelcold wings
and wipes the raintears off our shadows
Flies through our minds and leaves a burning black track
And we cling to whats in the gloom, empty and shallow"
      ------------------

Re: AWE64

[Dave Mielke]

[quoted lines by Heikki Kallasjoki on November 19, 1999, at 00:38]

>Another possible problem with sbAWE64, that many people seem to have, is
>the fact that pnpdump fails to recognize correctly those IO-ports for the
>wavetable part of the card. I have never used Red Hat personally, so I
>don't know much about how configuring it goes, but when you get the card
>working so that sound can be heard, if you then notice that the wavetable
>driver doesn't find the card, and it is a PnP version, (is there a
>non-PnP-awe64?) the cause might be this.

I have a RedHat system, and RedHat's "sndconfig" works just fine with my PNP
AWE64 card. Even the wave tables work.

The relevant part of "/etc/conf.modules" is:

   alias sound sb
   pre-install sound insmod sound dmabuf=1
   options opl3 io=0x388
   alias midi awe_wave
   post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
   options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330

The relevant parts of "/etc/isapnp.conf" are:

   (CONFIGURE CTL00c5/63091016 (LD 0
   #     ANSI string -->Audio<--
     (INT 0 (IRQ 5 (MODE +E)))
     (DMA 0 (CHANNEL 1))
     (DMA 1 (CHANNEL 5))
     (IO 0 (SIZE 16) (BASE 0x0220))
     (IO 1 (SIZE 2) (BASE 0x0330))
     (IO 2 (SIZE 4) (BASE 0x0388))
    (NAME "CTL00c5/63091016[0]{Audio               }")
     (ACT Y)
   ))
   (CONFIGURE CTL00c5/63091016 (LD 2
   #     ANSI string -->WaveTable<--
   (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
    (NAME "CTL00c5/63091016[2]{WaveTable           }")
     (ACT Y)
   ))

>Now, AWE64 uses also ports 0xA20 and 0xE20 in addition to 0x620, and all
>implementations of pnpdump I've seen have been unable to detect that. 

As you can see from tyhe above, REdHat's "sndconfig" utility did find all of
the ports just fine.

-- 
Dave Mielke           | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2B 6G3   | if you're concerned about Hell.

Re: AWE64

[Heikki Kallasjoki]

On 18.11.99, at 23:29, Dave Mielke wrote with subject 'Re: AWE64':
>    (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
...
> As you can see from tyhe above, REdHat's "sndconfig" utility did find all of
> the ports just fine.

Oh, that's great. At least it reduces the amounts of people I know who
will ask me about this.

As a comparison, the 'pnpdump' which came with the new Slackware-7.0
didn't find the ports. ..RedHat seems to have done something to
that. Thanks to them.


 --fiz.
-------------------
"Dying souls / Consumed by the evil lust,
Casting in / Darkness wins / Destroys all hope and their trust;"
      ------------------

Re: AWE64

[Paco]

On Fri, 19 Nov 1999, Heikki Kallasjoki wrote:

> On 18.11.99, at 23:29, Dave Mielke wrote with subject 'Re: AWE64':
> >    (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
> ...
> > As you can see from tyhe above, REdHat's "sndconfig" utility did find all of
> > the ports just fine.
> 
> Oh, that's great. At least it reduces the amounts of people I know who
> will ask me about this.
> 
> As a comparison, the 'pnpdump' which came with the new Slackware-7.0
> didn't find the ports. ..RedHat seems to have done something to
> that. Thanks to them.
> 

Actually, the "sndconfig" is not a RedHat utility at all.  It's the
configuration tool that comes with the OSS sound drivers, and it *does*
recognize all the ports on the AWE64.

regards,
-Paco

SuSE6.2 w/ OSS-free drivers

Re: AWE64

[Bill Nottingham]

Paco (paco@OhKeePa.Net) said: 
> Actually, the "sndconfig" is not a RedHat utility at all.  It's the
> configuration tool that comes with the OSS sound drivers, and it *does*
> recognize all the ports on the AWE64.

Umm.... no. Unless OSS is shipping something else that happens to
have the same name, which is entirely possible.

Bill

Re: AWE64

[Paco]

On Fri, 19 Nov 1999, Bill Nottingham wrote:

> Paco (paco@OhKeePa.Net) said: 
> > Actually, the "sndconfig" is not a RedHat utility at all.  It's the
> > configuration tool that comes with the OSS sound drivers, and it *does*
> > recognize all the ports on the AWE64.
> 
> Umm.... no. Unless OSS is shipping something else that happens to
> have the same name, which is entirely possible.
> 

I think that RedHat just includes the OSS drivers with it's distribution,
and uses them as the default drivers instead of the (inferior) kernel
"standard" drivers.

My roommate uses RH6.1, and his "sndconfig" utility looks and functions
exactly like the "sndconfig" utility that comes with OSS.

Just my observations...

peace,
-Paco

Re: AWE64

[Paco]

Nevermind... I guess someone at redhat.com would know a little more than
me.

peace,
-Paco

On Fri, 19 Nov 1999, Bill Nottingham wrote:

> Paco (paco@OhKeePa.Net) said: 
> > Actually, the "sndconfig" is not a RedHat utility at all.  It's the
> > configuration tool that comes with the OSS sound drivers, and it *does*
> > recognize all the ports on the AWE64.
> 
> Umm.... no. Unless OSS is shipping something else that happens to
> have the same name, which is entirely possible.
> 
> Bill
>