This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: sound card
From: Victor Tsaran <vtsaran@nimbus.ocis.temple.edu>
Date: Mon, 6 Dec 1999 17:01:27 -0500 (EST)
cedric writes:
> We are making progress... I think.
>
> sndconfig gives me the following:
> /lib/modules/2.2.5-15/misc/op13sa2.0:init_module: device or resource
> busy
>
> Is this a device conflict?
This is most likely esource conflict. By the way, how old is your
card? Is it plug-and-play?
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Mon, 6 Dec 1999 14:35:33 -0500
On Mon, 06 Dec 1999, Victor Tsaran wrote:
> Hi,
> This is most likely esource conflict. By the way, how old is your
> card? Is it plug-and-play?
> Regards,
> Vic
>
Let's say it's about one year old.
Yes, it is plug n' play.
That why I do not understand when sndconfig starts, it does not find
the card.
The manual for it says it's default is IRQ 7 under dos.
Would it be the same under Linux?
If so, why does it not show with cat /proc/interrupts?
Also, cat /proc/pci show IRQ 10 and 14 in use but they do not show
with cat /proc/interrupts either.
Any ideas on how to solve this conflict?
===
Subject: Re: sound card
From: "John P. Verel" <jverel@home.com>
Date: Mon, 06 Dec 1999 23:56:26 -0500
At 02:35 PM 12/06/99 , you wrote:
>Any ideas on how to solve this conflict?
Cedric,
You might try the following:
If your card is configured and running under Windows, go into Control
Panel|System. Select the top of the device tree and hit print. This will
generate a resource summary report, showing all irq, dma and io assignments
for your machine. With this in hand, open /etc/modules.conf. Add the
following two lines:
alias sound=sb
options sb io=0x220 irq=9 DMA=1 DMA=16=5
NOTE: The values in the options line are the values for my
machine. Substitute for yours based on what your system report tells
you. Save, close and reboot.
Let us know what happens.
===
Subject: Re: sound card
From: Victor Tsaran <vtsaran@nimbus.ocis.temple.edu>
Date: Tue, 7 Dec 1999 00:42:42 -0500 (EST)
cedric writes:
> On Mon, 06 Dec 1999, Victor Tsaran wrote:
> > Hi,
> > This is most likely esource conflict. By the way, how old is your
> > card? Is it plug-and-play?
> > Regards,
> > Vic
> >
> Let's say it's about one year old.
> Yes, it is plug n' play.
> That why I do not understand when sndconfig starts, it does not find
> the card.
>
> The manual for it says it's default is IRQ 7 under dos.
> Would it be the same under Linux?
> If so, why does it not show with cat /proc/interrupts?
> Also, cat /proc/pci show IRQ 10 and 14 in use but they do not show
> with cat /proc/interrupts either.
>
> Any ideas on how to solve this conflict?
You know this is really strange. If you do
cat /proc/pci
you should get some sort of list of devices that Linux identified on
your system. Can you tell us more about your system? I mean, did you
compile kernel yourself?
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 05:16:46 -0500
On Tue, 07 Dec 1999, Victor Tsaran wrote:
> Hi,
> You know this is really strange. If you do
>
> cat /proc/pci
>
> you should get some sort of list of devices that Linux identified on
> your system. Can you tell us more about your system? I mean, did you
> compile kernel yourself?
> Regards,
> Vic
>
I do get a list. I recognize the video card because S3 Inc. ViRGE is there.
It uses IRQ 10. USB controller uses IRQ 11 but those are the only two that say
what IRQ they use. I do not recognize anything regarding sound on the others.
No, I installed directly off a Red Hat CD.
I hate to say this, but the plug n' play works fine with W95.
My box is home made. PCI main board with AMD K6/2 450.
64M mem, 5.4G hda and 1.6G hdb, LS120 super drive.
ATAPI CD-ROM, Brother HL-720 (which does not work, yet)
I also installed another parallel port and do not know if Linux
sees it. My ImageWave parallel scanner is hooked up to it.
This does not work and I understand it may never work.
I am trying to rid myself of MS.
I do use AutoCadd so I can't flush MS entirely, or I would.
As a writer of fiction, I need this Linux box working.
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 06:05:45 -0500
On Mon, 06 Dec 1999, John P. Verel wrote:
> At 02:35 PM 12/06/99 , you wrote:
> >Any ideas on how to solve this conflict?
> Cedric,
>
> You might try the following:
>
> If your card is configured and running under Windows, go into Control
> Panel|System. Select the top of the device tree and hit print. This will
> generate a resource summary report, showing all irq, dma and io assignments
> for your machine. With this in hand, open /etc/modules.conf. Add the
> following two lines:
> alias sound=sb
> options sb io=0x220 irq=9 DMA=1 DMA=16=5
> NOTE: The values in the options line are the values for my
> machine. Substitute for yours based on what your system report tells
> you. Save, close and reboot.
>
> Let us know what happens.
>
> John
This looks weird to me.
IRQ Usage Summary:
05 - YAMAHA OPL3-SA Sound System
05 - OPL3-SA Legacy Board
09 - YAMAHA OPL3-SA Sound System
09 - OPL3-SA Legacy Board
I/O Port Usage Summary:
0201h-0201h - YAMAHA OPL3-SA Sound System
0201h-0201h - OPL3-SA Legacy Board
0220h-022fh - YAMAHA OPL3-SA Sound System
0220h-022fh - OPL3-SA Legacy Board
0330h-0331h - YAMAHA OPL3-SA Sound System
0330h-0331h - OPL3-SA Legacy Board
The same for 0338h-038fh, 0530h-0537h and 0f86h-0f87h
DMA Channel1 Usage Summary:
Both 00 and 01 show YAMAHA OPL3-SA Sound System
and OPL3-SA Legacy Board.
What's goin on?
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 06:54:23 -0500
On Mon, 06 Dec 1999, John P. Verel wrote:
> At 02:35 PM 12/06/99 , you wrote:
> >Any ideas on how to solve this conflict?
> Cedric,
>
> You might try the following:
>
> If your card is configured and running under Windows, go into Control
> Panel|System. Select the top of the device tree and hit print. This will
> generate a resource summary report, showing all irq, dma and io assignments
> for your machine. With this in hand, open /etc/modules.conf. Add the
> following two lines:
> alias sound=sb
> options sb io=0x220 irq=9 DMA=1 DMA=16=5
> NOTE: The values in the options line are the values for my
> machine. Substitute for yours based on what your system report tells
> you. Save, close and reboot.
>
> Let us know what happens.
>
> John
>
This is /etc/conf.modules
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
options opl3sa io=0x530 irq=5 dma=0 dma2=0 mpu_io=0x330 mpu_irq=5
post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
options adlib_card io=0x388
alias sound opl3sa2
pre-install sound insmod sound dmabuf=1
alias midi opl3
options opl3 io=0x388
options opl3sa2 mss_io=0x534 irq=7 dma=0 dma2=0 mpu_io=0x330 io=0x370
===
Subject: Re: PCI audio (es1371) broken??? Kernel 2.2.12
From: "Eric J. Gerney" <egerney@grci.com>
Date: Mon, 6 Dec 1999 17:49:18 -0500 (EST)
On Wed, 1 Dec 1999, mgalgoci@redhat.com wrote:
> > Thanks for the info, I will determine if the irq is being shared and
> > then change it if necessary.
> >
> > However, would attempting to share IRQs
> > with other pci devices cause the "dma timing out???" message in the logs?
>
> Now that you mention it, that is exactly the error message that I saw. The
> conflict was between an intel eepro pci nic and the es1371 card.
>
> The message repeated in the kernel message memory something like ten times
> before failing.
>
> It took me a while to figure out why it was happening, but after moving
> the nic, it went away.
>
> That's why I like going to installfests. You see stuff happen that you
> otherwise would have a tough time believing if you hadn't seen it in
> person. You also see a *lot* of weird hardware too.
I had a look at the IRQ's and other system settings. I can clearly see
that the es1371 card's resources are not being shared with anything else.
Do you have any other thoughts? Should I just wait until kernel 2.2.14
hits the streets?
The only other thing I can think of is that, this es1371 could be a
different version of the same sound card. I've read of many instances
where this is the case.
===
Subject: Sound Card can't work
From: Zhongbo Cao <zbcao@platform.com.cn>
Date: Tue, 07 Dec 1999 10:02:03 +0800
Hi,
My Sound Card can't work in Redhat 6.1,sndconfig can automaticly detect
my pnp sound card,AZT 1008 pnp sound device.but I can't hear the sample
sound,and sndconfig reports that the configuration file "isapnp.conf"
has some errors when playing the sample sound.
>From windows 95,I can get all the configuration from my sound card:
SB: I/O port 0220-022F,0338-038F,0534-0537
INT: 05
DMA: 01 and 03.
Gameport: 0200-0207
MPU-401: I/O :0330-0331,
INT:09
===========================================
cat /proc/pci:
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel 440BX - 82443BX Host (rev 3).
Medium devsel. Master Capable. Latency=64.
Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
Bus 0, device 1, function 0:
PCI bridge: Intel 440BX - 82443BX AGP (rev 3).
Medium devsel. Master Capable. Latency=64. Min Gnt=136.
Bus 0, device 7, function 0:
ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
Medium devsel. Fast back-to-back capable. Master Capable. No
bursts.
Bus 0, device 7, function 1:
IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=64.
I/O at 0xf000 [0xf001].
Bus 0, device 7, function 2:
USB Controller: Intel 82371AB PIIX4 USB (rev 1).
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Late
ncy=64.
I/O at 0xe000 [0xe001].
Bus 0, device 7, function 3:
Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
Medium devsel. Fast back-to-back capable.
Bus 0, device 13, function 0:
"pci" 34 lines, 1752 characters
============================
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0300-030f : 3c509
0376-0376 : ide1
0388-038b : Yamaha OPL3
03c0-03df : vga+
03f0-03f5 : floppy
03f6-03f6 : ide0
03f7-03f7 : floppy DIR
03f8-03ff : serial(auto)
e400-e47f : eth1
f000-f007 : ide0
f008-f00f : ide1
===
Subject: Re: sound card
From: Bill Nottingham <notting@redhat.com>
Date: Tue, 7 Dec 1999 20:58:56 -0500
cedric (cedric@pacifier.com) said:
> 05 - YAMAHA OPL3-SA Sound System
> 05 - OPL3-SA Legacy Board
> 09 - YAMAHA OPL3-SA Sound System
> 09 - OPL3-SA Legacy Board
>
> I/O Port Usage Summary:
> 0201h-0201h - YAMAHA OPL3-SA Sound System
> 0201h-0201h - OPL3-SA Legacy Board
> 0220h-022fh - YAMAHA OPL3-SA Sound System
> 0220h-022fh - OPL3-SA Legacy Board
> 0330h-0331h - YAMAHA OPL3-SA Sound System
> 0330h-0331h - OPL3-SA Legacy Board
> The same for 0338h-038fh, 0530h-0537h and 0f86h-0f87h
>
> DMA Channel1 Usage Summary:
> Both 00 and 01 show YAMAHA OPL3-SA Sound System
> and OPL3-SA Legacy Board.
>
> What's goin on?
That is odd that they're in there twice; but I don't
debug Windows problems. ;) In any case, if those are
the settings it's using, you'd want the following:
alias sound opl3sa2
options opl3sa2 mss_io=0x534 irq=5 dma=1 dma2=0 mpu_io=0x330 io=0x200
Does putting that in /etc/conf.modules, and then running
'modprobe opl3sa2' succeed?
===
Subject: Re: sound card
From: Bill Nottingham <notting@redhat.com>
Date: Tue, 7 Dec 1999 21:03:51 -0500
Bill Nottingham (notting@redhat.com) said:
> > I/O Port Usage Summary:
> > 0201h-0201h - YAMAHA OPL3-SA Sound System
> > 0201h-0201h - OPL3-SA Legacy Board
> > 0220h-022fh - YAMAHA OPL3-SA Sound System
> > 0220h-022fh - OPL3-SA Legacy Board
> > 0330h-0331h - YAMAHA OPL3-SA Sound System
> > 0330h-0331h - OPL3-SA Legacy Board
> > The same for 0338h-038fh, 0530h-0537h and 0f86h-0f87h
>
> alias sound opl3sa2
> options opl3sa2 mss_io=0x534 irq=5 dma=1 dma2=0 mpu_io=0x330 io=0x200
>
> Does putting that in /etc/conf.modules, and then running
> 'modprobe opl3sa2' succeed?
Check that, the 0x200 is probably the game port. Try 0x370 or 0xf86
for the 'io' setting.
===
Subject: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 20:21:39 -0500
This is my /etc/conf.modules
Seems to me like there is too much 'stuff' in here.
'modprobe' results in device busy as before even after changing the last line.
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
options opl3sa io=0x530 irq=5 dma=0 dma2=0 mpu_io=0x330 mpu_irq=5
post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
options adlib_card io=0x388
alias sound opl3sa2
pre-install sound insmod sound dmabuf=1
alias midi opl3
options opl3 io=0x388
options opl3sa2 mss_io=0x534 irq=5 dma=1 dma2=0 mpu_io=0x330 io=0x200
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 20:45:04 -0500
Bill,
Scratch my last e-mail. I had not received your last e-mail when
I sent the other.
I change the last io to 0xf86 and did 'modprobe opl3sa2.'
I heard a loud click out of the speakers.
I ran it again and got the divice busy garbage again.
I went back and checked /etc/conf.modules and they had not changed.
Below is the current /etc/conf.module:
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
options opl3sa io=0x530 irq=5 dma=0 dma2=0 mpu_io=0x330 mpu_irq=5
post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
options adlib_card io=0x388
alias sound opl3sa2
pre-install sound insmod sound dmabuf=1
alias midi opl3
options opl3 io=0x388
options opl3sa2 mss_io=0x534 irq=5 dma=1 dma2=0 mpu_io=0x330 io=0xf86
I checked 'modprob opl3sa2' seconds before sending this with the same results.
===
Subject: Re: sound card
From: Bill Nottingham <notting@redhat.com>
Date: Wed, 8 Dec 1999 00:07:28 -0500
cedric (cedric@pacifier.com) said:
> Bill,
>
> Scratch my last e-mail. I had not received your last e-mail when
> I sent the other.
>
> I change the last io to 0xf86 and did 'modprobe opl3sa2.'
> I heard a loud click out of the speakers.
Um, that usually means the module loaded at least mostly
correctly. What does 'lsmod' and
'cat /dev/sndstat' say?
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 21:32:15 -0500
I am assuming you want:
soundlow 300 0
soundcore 2372 0
cat /dev/sndstat:
no such device
/etc/conf.modules is still 0xf86
/etc/conf.modules.bak is still 0xf86
/etc/conf.modules~ is 0x370
What's going on here?
===
Subject: Re: sound card
From: Bill Nottingham <notting@redhat.com>
Date: Wed, 8 Dec 1999 00:48:06 -0500
cedric (cedric@pacifier.com) said:
> I am assuming you want:
> soundlow 300 0
> soundcore 2372 0
>
> cat /dev/sndstat:
> no such device
>
> /etc/conf.modules is still 0xf86
> /etc/conf.modules.bak is still 0xf86
> /etc/conf.modules~ is 0x370
>
> What's going on here?
Hmm... this is after you did 'modprobe opl3sa2' and heard the click?
That's really strange. Was there any error messages after the time
you heard the click?
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Tue, 7 Dec 1999 21:59:17 -0500
On Wed, 08 Dec 1999, Bill Nottingham wrote:
> cedric (cedric@pacifier.com) said:
> > I am assuming you want:
> > soundlow 300 0
> > soundcore 2372 0
> >
> > cat /dev/sndstat:
> > no such device
> >
> > /etc/conf.modules is still 0xf86
> > /etc/conf.modules.bak is still 0xf86
> > /etc/conf.modules~ is 0x370
> >
> > What's going on here?
>
> Hmm... this is after you did 'modprobe opl3sa2' and heard the click?
> That's really strange. Was there any error messages after the time
> you heard the click?
>
> Bill
No, no error message about anything.
I did modprobe opl3sa2 again and the 'device busy' error returned.
Also, I found this while researching the printing how to:
According to Brian Gough, for the SoundBlaster cards which use DMA
channel 1 there is a potential conflict with the QIC-02 tape driver,
which also uses DMA 1, causing "device busy" errors. If you are using
FTAPE, you may have this driver enabled. According to the FTAPE-HOWTO
the QIC-02 driver is not essential for the use of FTAPE; only the
QIC-117 driver is required. Reconfiguring the kernel to use QIC-117
but not QIC-02 allows FTAPE and the sound-driver to coexist.
I do not have a tape drive though.
Also, I read but could not find again, that PCI mainboards (that's what I have)
has problems with DMA speed or something.
dmesg tells me:
PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00)
Activating ISA DMA hang work arounds.
I have no idea what this means.
===
Subject: Re: sound card
From: Bill Nottingham <notting@redhat.com>
Date: Wed, 8 Dec 1999 02:02:50 -0500
cedric (cedric@pacifier.com) said:
> > Hmm... this is after you did 'modprobe opl3sa2' and heard the click?
> > That's really strange. Was there any error messages after the time
> > you heard the click?
> >
> > Bill
>
> No, no error message about anything.
OK, that implies that the module did load successfully; does
lsmod still show only sound, soundlow, soundcore after
this happens?
> I did modprobe opl3sa2 again and the 'device busy' error returned.
That makes sense; if it loaded successfully, it won't be able
to load again on top of itself.
> Also, I read but could not find again, that PCI mainboards (that's what I have)
> has problems with DMA speed or something.
>
> dmesg tells me:
>
> PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00)
> Activating ISA DMA hang work arounds.
>
> I have no idea what this means.
It means that you have one of the broken VIA DMA controllers. The
kernel is enabling a workaround so that using sound & the floppy
driver (or hard drive, or other things using DMA) don't lock
the machine up.
===
Subject: Re: sound card
From: cedric <cedric@pacifier.com>
Date: Wed, 8 Dec 1999 06:40:34 -0500
> OK, that implies that the module did load successfully; does
> lsmod still show only sound, soundlow, soundcore after
> this happens?
>
lsmod shows soundlow, soundcore but no sound.
>
> It means that you have one of the broken VIA DMA controllers. The
> kernel is enabling a workaround so that using sound & the floppy
> driver (or hard drive, or other things using DMA) don't lock
> the machine up.
>
Does this mean the mainboard is defective. I just bought it along with an
AMD K6/2 450 and another 6.4G hd. That was sure a pain changing a motherboard.
Do you know of a list where I can get help with my printer?
===
Subject: Re: sound card
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Wed, 8 Dec 1999 15:53:08 +0000 (GMT)
> > driver (or hard drive, or other things using DMA) don't lock
> > the machine up.
> >
> Does this mean the mainboard is defective. I just bought it along with an
> AMD K6/2 450 and another 6.4G hd. That was sure a pain changing a motherboard.
The chipset has a slight bug. All chipsets have bugs. Your bios fixes some,
the kernel knows about oddities with triton chipsets, the VIA ones and other
stuff. Other than the "worked around" message you'll never know about the
problem
===
Subject: sound working - oops
From: cedric <cedric@pacifier.com>
Date: Wed, 8 Dec 1999 21:20:31 -0500
Well, it was great while it lasted.
Sound worked in root.
Logged on as 'cedric' and sound did not work.
Went back to 'root and sound no longer worked.
modprobe opl3sa told me mpu was wrong.
change mpu from mpu=irq5 to mpu_io=0xf86 and sound worked.
Went back to cedric and sound did not work.
Went back to root and sound does not work until AFTER modprobe opl3sa.
modprobe opl3 gives device busy error.
However, when mpu was set to mpu=irq5 modprobe opl3 gave me a device busy error
but AFTER doing modprobe opl3sa, modprobe opl3 did not give me an error. NOW,
with mpu_io=0xf86, it does not matter if I do a modprobe opl3sa or not, opl3
gives a device error anyway.
This is where things stand now.
===