AWE32/64 sndconfig/synth0 problem

AWE32/64 sndconfig/synth0 problem

Post by Barry L. Bo » Wed, 27 Feb 2002 06:52:59



Greetings!

     I was running Red Hat Linux 7.1, with kernel 2.4.9 (from
www.kernel.org).  I installed the kernel back in September.  And then, a
couple of weeks ago, I installed 2.4.17.  It's working very well.

     In late November, my system died.  It turned out to need a new power
supply, but also the old motherboard had to be completely replaced with a
new motherboard, so all my bus cards were removed from the system and
placed back in.

     My sound card had worked very well.  I have the Creative Labs AWE64.

     Since I got my system back, it hasn't been working.  I was expecting
I'd have to probably "reconfigure" it.  I have run sndconfig.  The
documentation says it (on Audio interface) is 220H, IRQ 5, DMA 1 and 5,
and the MPU is 330H.  dmesg reports the following regarding my sound card:

<<>>
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: Creative SB AWE64  PnP detected
sb: ISAPnP reports 'Creative SB AWE64  PnP' at i/o 0x220, irq 9, dma 1, 5
SB 4.16 detected OK (220)
sb: Interrupt test on IRQ9 failed - Probable IRQ conflict
sb: 1 Soundblaster PnP card(s) found.
<<>>

     In experimentation, I have set the IRQ to 5 and 9, the first DMA to 1
and the second to 5, according to the documentation from the sound card.

     When running sndconfig, it says a sound sample will now be played to
determine if my sound card has been correctly configured.  I hear what
sounds like the very beginning of a word, but it isn't complete.  And
then, when it goes on to say a MIDI sample will now be played to determine
if my sound card's synth has been correctly configured, I get:

modprobe:  Can't locate module synth0

     I don't seem to have a synth0 anywhere on my system.  I was going to
start BRU (after setting /etc/bruxpat) to see whether synth0 existed on an
old system I had back before September.  However, it seems that now my
Seagate Travan tape drive isn't working.  <sigh>  So, that's another
problem!  :-)

     If I didn't have a synth0, though, I apparently didn't need it before
(as the system ran for about two months just fine before I had the
motherboard replaced)...?

     Can anyone offer any help here?

     Thank you!

     Barry
--
Barry L. Bond, Software Engineer           | Barry L. Bond

72235,1530 (CIS)              <- personal  | KSC, FL  32899

 
 
 

AWE32/64 sndconfig/synth0 problem

Post by John Webe » Wed, 27 Feb 2002 08:59:11



> <<>>
> Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
> sb: Creative SB AWE64  PnP detected
> sb: ISAPnP reports 'Creative SB AWE64  PnP' at i/o 0x220, irq 9, dma 1,
> 5 SB 4.16 detected OK (220)
> sb: Interrupt test on IRQ9 failed - Probable IRQ conflict sb: 1
> Soundblaster PnP card(s) found. <<>>

RH7.1, kernel 2.4.9

Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: Creative SB AWE64 Gold detected
sb: ISAPnP reports 'Creative SB AWE64 Gold' at i/o 0x220, irq 5, dma 1, 5
SB 4.16 detected OK (220)
sb: 1 Soundblaster PnP card(s) found.

I think I had the same problem and it was the usb module conflicting with
the SB. I went into the bios and told it that there was a legacy isa card
using irq 5 and then the usb module decided to go to irq 11 and then it
all worked.

--
John Weber
jweberATmath.cudenver.edu.invalid


 
 
 

AWE32/64 sndconfig/synth0 problem

Post by Vladimir Florinsk » Wed, 27 Feb 2002 11:39:44




> Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
> sb: Creative SB AWE64  PnP detected
> sb: ISAPnP reports 'Creative SB AWE64  PnP' at i/o 0x220, irq 9, dma 1,
> 5 SB 4.16 detected OK (220)
> sb: Interrupt test on IRQ9 failed - Probable IRQ conflict sb: 1
> Soundblaster PnP card(s) found. <<>>

You can get a conflict if a PCI card is using the same IRQ. You can change
the ISA PnP IRQ by writing into /proc/isapnp. There should be
documentation in the kernel describing the process, I don't remember how
to do this exactly, since ISA cards are rarely used these days. To protect
this IRQ, you should also reserve it for ISA in the BIOS.

Quote:> modprobe:  Can't locate module synth0

>      I don't seem to have a synth0 anywhere on my system.  I was going
>      to
> start BRU (after setting /etc/bruxpat) to see whether synth0 existed on
> an old system I had back before September.

Synth is needed for wavetable MIDI. It should be aliased to awe_wave in
modules.conf, again I don't remember the exact name of the alias, perhaps
the appropriate sound-service or just synth.

--

Vladimir

 
 
 

AWE32/64 sndconfig/synth0 problem

Post by Clive Dov » Fri, 01 Mar 2002 00:10:37



> Greetings!

>      I was running Red Hat Linux 7.1, with kernel 2.4.9 (from
> www.kernel.org).  I installed the kernel back in September.  And then, a
> couple of weeks ago, I installed 2.4.17.  It's working very well.

>      In late November, my system died.  It turned out to need a new power
> supply, but also the old motherboard had to be completely replaced with a
> new motherboard, so all my bus cards were removed from the system and
> placed back in.

>      My sound card had worked very well.  I have the Creative Labs AWE64.

>      Since I got my system back, it hasn't been working.  I was expecting
> I'd have to probably "reconfigure" it.  I have run sndconfig.  The
> documentation says it (on Audio interface) is 220H, IRQ 5, DMA 1 and 5,
> and the MPU is 330H.  dmesg reports the following regarding my sound card:

> <<>>
> Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
> sb: Creative SB AWE64  PnP detected
> sb: ISAPnP reports 'Creative SB AWE64  PnP' at i/o 0x220, irq 9, dma 1, 5
> SB 4.16 detected OK (220)
> sb: Interrupt test on IRQ9 failed - Probable IRQ conflict
> sb: 1 Soundblaster PnP card(s) found.
> <<>>

>      In experimentation, I have set the IRQ to 5 and 9, the first DMA to 1
> and the second to 5, according to the documentation from the sound card.

>      When running sndconfig, it says a sound sample will now be played to
> determine if my sound card has been correctly configured.  I hear what
> sounds like the very beginning of a word, but it isn't complete.  And
> then, when it goes on to say a MIDI sample will now be played to determine
> if my sound card's synth has been correctly configured, I get:

> modprobe:  Can't locate module synth0

>      I don't seem to have a synth0 anywhere on my system.  I was going to
> start BRU (after setting /etc/bruxpat) to see whether synth0 existed on an
> old system I had back before September.  However, it seems that now my
> Seagate Travan tape drive isn't working.  <sigh>  So, that's another
> problem!  :-)

>      If I didn't have a synth0, though, I apparently didn't need it before
> (as the system ran for about two months just fine before I had the
> motherboard replaced)...?

>      Can anyone offer any help here?

>      Thank you!

>      Barry

With a 2.4.x kernel, you probably don't need to play with the isapnp
command. I did not have to under Mandrake 8.1

Try this:
su to a root command prompt.
From a root command prompt:
modprobe sound
insmod uart401
insmod sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
insmod opl3 io=0x388 (that is lower case OPL3)
reboot

Note:
What I do first is to use rmmod to take out all the sound modules then put
them all back as above.

Your values may be different, but the above values are the most likely.

Do not use sndconfig or any other sound configuration utility after
manually loading the modules or your work will be overwritten.
Test au files using "play" and midi files using "kmidi"
Your sample files are probably:
/usr/share/sndconfig/sample.au
/usr/share/sndconfig/sample.midi

Download TiMidity and TiMidity-instruments.
This is a software midi sequencer and a collection of voices for it.
Check your RedHat install disks to see if there are rpm packages for them
there.

 
 
 

AWE32/64 sndconfig/synth0 problem

Post by Barry L. Bo » Tue, 05 Mar 2002 05:06:50


Hi John (and others)

Quote:>I think I had the same problem and it was the usb module conflicting with
>the SB. I went into the bios and told it that there was a legacy isa card
>using irq 5 and then the usb module decided to go to irq 11 and then it
>all worked.

     Thank you!  I went into my BIOS, and found where I could change
"Auto" to "Manual" and choose Legacy ISA, just like you did.  And, when I
booted into Linux, I appear to be "getting there."

     Here is a portion of my dmesg from a bootup:

<<>>

BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000017ff0000 (usable)
 BIOS-e820: 0000000017ff0000 - 0000000017ff3000 (ACPI NVS)
 BIOS-e820: 0000000017ff3000 - 0000000018000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 98288
zone(0): 4096 pages.
zone(1): 94192 pages.
zone(2): 0 pages.
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Kernel command line: auto BOOT_IMAGE=new_linux ro root=811 BOOT_FILE=/boot/vmlinuz-2.4.17
Initializing CPU#0
Detected 451.031 MHz processor.
.
.
.
isapnp: Scanning for PnP cards...
isapnp: Calling quirk for 01:00
isapnp: SB audio device quirk - increasing port range
isapnp: Calling quirk for 01:02
isapnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB AWE64  PnP'
isapnp: 1 Plug & Play card detected total
<<>>

     I don't have sound yet, but I am getting closer.  (This boot is
actually a fresh bootup from a kernel I configured just this morning.)

     RealPlayer works now, although I don't have sound.  (Before, it hung
at about the two-second mark, probably because it didn't sense any sound
card.)

     Now, I'm guessing that I don't have it configured in my kernel...  I
did choose Sound, and choose OSS and 100% soundblaster and even the
synth/MIDI choice, but I'm not finding sound yet.  I do have a /dev/dsp
file.

     Anyway, I'm now working to figure out what to try/configure next for
sound, but I at least have the sound card being recognized now, thanks to
your help!  Thank you very much!

     Barry
--
Barry L. Bond, Software Engineer           | Barry L. Bond

72235,1530 (CIS)              <- personal  | KSC, FL  32899

 
 
 

AWE32/64 sndconfig/synth0 problem

Post by Barry L. Bo » Tue, 05 Mar 2002 05:07:04


Hi Vladimir!

Quote:>You can get a conflict if a PCI card is using the same IRQ. You can change
>the ISA PnP IRQ by writing into /proc/isapnp. There should be
>documentation in the kernel describing the process, I don't remember how
>to do this exactly, since ISA cards are rarely used these days. To protect
>this IRQ, you should also reserve it for ISA in the BIOS.

     Thank you very much!  I wound up going into the BIOS and setting a
Legacy ISA card, and, while I don't have sound yet, that helped
tremendously!  :-)  At least, it recognizes the sound card now!

Quote:>Synth is needed for wavetable MIDI. It should be aliased to awe_wave in
>modules.conf, again I don't remember the exact name of the alias, perhaps
>the appropriate sound-service or just synth.

     Okay... thank you.  I'll remember this and keep it in mind as I get
to the point where I'm hearing some sound.

     Here is a portion of my dmesg from a bootup:

<<>>

BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000017ff0000 (usable)
 BIOS-e820: 0000000017ff0000 - 0000000017ff3000 (ACPI NVS)
 BIOS-e820: 0000000017ff3000 - 0000000018000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 98288
zone(0): 4096 pages.
zone(1): 94192 pages.
zone(2): 0 pages.
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Kernel command line: auto BOOT_IMAGE=new_linux ro root=811 BOOT_FILE=/boot/vmlinuz-2.4.17
Initializing CPU#0
Detected 451.031 MHz processor.
.
.
.
isapnp: Scanning for PnP cards...
isapnp: Calling quirk for 01:00
isapnp: SB audio device quirk - increasing port range
isapnp: Calling quirk for 01:02
isapnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB AWE64  PnP'
isapnp: 1 Plug & Play card detected total
<<>>

     I don't have sound yet, but I am getting closer.  (This boot is
actually a fresh bootup from a kernel I configured just this morning.)

     RealPlayer works now, although I don't have sound.  (Before, it hung
at about the two-second mark, probably because it didn't sense any sound
card.)

     I really want to get RealPlayer working, because I can listen to the
Space Shuttle mission via RealPlayer!  :-)  (I work at Kennedy Space
Center.)

     Now, I'm guessing that I don't have it configured in my kernel...  I
did choose Sound, and choose OSS and 100% soundblaster and even the
synth/MIDI choice, but I'm not finding sound yet.  I do have a /dev/dsp
file.

     Anyway, I'm now working to figure out what to try/configure next for
sound, but I at least have the sound card being recognized now, thanks to
your help!  Thank you very much!

     Barry
--
Barry L. Bond, Software Engineer           | Barry L. Bond

72235,1530 (CIS)              <- personal  | KSC, FL  32899

 
 
 

AWE32/64 sndconfig/synth0 problem

Post by Barry L. Bo » Tue, 05 Mar 2002 05:07:19


Hi Clive!

     Thank you very much for trying to help me!

Quote:>With a 2.4.x kernel, you probably don't need to play with the isapnp
>command. I did not have to under Mandrake 8.1

     I wound up going into the BIOS and setting Legacy ISA card, and I'm
getting a lot closer!  Although, it's still using isapnp... here is a
portion of my dmesg from a bootup this morning:

<<>>

BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000017ff0000 (usable)
 BIOS-e820: 0000000017ff0000 - 0000000017ff3000 (ACPI NVS)
 BIOS-e820: 0000000017ff3000 - 0000000018000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 98288
zone(0): 4096 pages.
zone(1): 94192 pages.
zone(2): 0 pages.
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Kernel command line: auto BOOT_IMAGE=new_linux ro root=811 BOOT_FILE=/boot/vmlinuz-2.4.17
Initializing CPU#0
Detected 451.031 MHz processor.
.
.
.
isapnp: Scanning for PnP cards...
isapnp: Calling quirk for 01:00
isapnp: SB audio device quirk - increasing port range
isapnp: Calling quirk for 01:02
isapnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB AWE64  PnP'
isapnp: 1 Plug & Play card detected total
<<>>

     I don't have sound yet, but I am getting closer.  (This boot is
actually a fresh bootup from a kernel I configured just this morning.)

     RealPlayer works now, although I don't have sound.  (Before, it hung
at about the two-second mark, probably because it didn't sense any sound
card.)  I really want to get RealPlayer working again, because I can hear
the Space Shuttle mission (up now) if it works.  (I work at Kennedy Space
Center.)  :-)

     Now, I'm guessing that I don't have it configured in my kernel...  I
did choose Sound, and choose OSS and 100% soundblaster and even the
synth/MIDI choice, but I'm not finding sound yet.  I do have a /dev/dsp
file.

Quote:>Try this:
>su to a root command prompt.
>From a root command prompt:
>modprobe sound

     I did, and I get:

<<>>

/lib/modules/2.4.17/kernel/drivers/sound/sb.o: too many values for dma (max 1)
/lib/modules/2.4.17/kernel/drivers/sound/sb.o: insmod /lib/modules/2.4.17/kernel/drivers/sound/sb.o failed
/lib/modules/2.4.17/kernel/drivers/sound/sb.o: insmod sound failed
<<>>

Quote:>insmod uart401

     This doesn't work, either.  I get:

<<>>

Using /lib/modules/2.4.17/kernel/drivers/sound/uart401.o
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol sound_unload_mididev
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_hw_control
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_panning
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol sound_alloc_mididev
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol conf_printf
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_ioctl
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_start_note
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_kill_note
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol sequencer_init
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_devs
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_reset
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_aftertouch
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_close
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_set_instr
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_send_sysex
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_controller
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_bender
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_open
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_setup_voice
/lib/modules/2.4.17/kernel/drivers/sound/uart401.o: unresolved symbol midi_synth_load_patch
<<>>

Quote:>insmod sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
>insmod opl3 io=0x388 (that is lower case OPL3)
>reboot
>Note:
>What I do first is to use rmmod to take out all the sound modules then put
>them all back as above.
>Your values may be different, but the above values are the most likely.

     Thank you!  I am going to "digest" the information I'm seeing now and
try to figure out what I need to do next.  I am getting closer, I think!
:-)

     Barry
--
Barry L. Bond, Software Engineer           | Barry L. Bond

72235,1530 (CIS)              <- personal  | KSC, FL  32899

 
 
 

1. Problems compiling Awe32/64 support

Hi . I  hope some one can help me in setting up My Awe64 under linux ,
as i seem to be doing something majorly wrong.

I have followed all the intructions as per the howto and the faq.

The problem that i seem to be having , is that even though i select
sound support as a module using xconfig , it doesnt seem to be getting
compiled asa module.So if i do a modprobe -a sound , it says cant loctae
module sound.

These are the things that ive done to compile sound support

ive edited my isapnp.conf file , to refelct my Awe64's settings
ive chosen sound to be loaded as a module using xconfig
ive done make dep and make clean
then make modules and make modules_install

Even though ive enabled module support for the sound , this last part
doesnt show sound as a module

Does anyone know what im doing wrong

2. Was the Pentium CREATED or EVOLVED?

3. sndconfig error, AWE 64

4. scanner Artec AM12S (scsi)

5. sndconfig, SB-AWE32, and RedHat 5

6. Mach 64 and X

7. AWE32/64 setup

8. --> [Q] Linux and IBM RS6000 ??

9. RedHat6.1 & Soundblaster card AWE32/64

10. 64 bit Unix (esp. 64 bit IO)

11. host mastered 64 bit wide transfers to 64 bit PCI slot?

12. ATI MAch 64 vs STB PowerGraph 64

13. FWD: 64 Days to 64-bit x86 Computing!