Stupid Sound Question
kwall@kurtwerks.com
kwall
Mon May 17 11:39:18 PDT 2004
On Wed, Oct 23, 2002 at 06:15:21PM -0700, Tony Alfrey wrote:
> On Wednesday 23 October 2002 05:42 pm,Net Llama! wrote:
> > So this looks like an OSS thing? At any rate, i'm not aware of this
> > existing under 2.4. the support was never ported to the 2.4.x OSS
> > modules.
>
> Well, since I've got you on the hook, I'm trying to get my Sound
> Blaster card to work under 2.4.x.
>
> It plays CDs.
> kmixer works (I can move the sliders up and down and hear the faint
> noise of the 'steps').
> I cannot play .wav files.
> The card is ISAPNP and I may have an interrupt problem but I cannot
> understand the issue. Here is output from dmesg and cat
> /proc/interrupts:
>
> 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
> 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 7, dma 1, 5
> SB 4.16 detected OK (220)
> sb: Interrupt test on IRQ7 failed - Probable IRQ conflict
> <Sound Blaster 16 (4.16)> at 0x220 irq 7 dma 1,5
> <Sound Blaster 16> at 0x300 irq 7 dma 0,0
> sb: 1 Soundblaster PnP card(s) found.
> ISAPnP reports AWE64 WaveTable at i/o 0x620
> <SoundBlaster EMU8000 (RAM512k)>
>
>
>
> Here are the interrupts:
>
> [root at noname /root]# cat /proc/interrupts
> CPU0
> 0: 38618 XT-PIC timer
> 1: 161 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 5: 6332 XT-PIC ncr53c8xx
> 7: 0 XT-PIC soundblaster
> 9: 0 XT-PIC acpi
> 11: 109 XT-PIC BusLogic BT-958, usb-uhci
> 12: 11654 XT-PIC PS/2 Mouse
> 13: 1 XT-PIC fpu
> 14: 2 XT-PIC ide0
> NMI: 0
> LOC: 0
> ERR: 0
>
>
> cat /proc/interrupts thinks that the soundblaster is irq = 7 but then
> it looks like the module sb is testing irq=7 and failing.
> If you can shed some light on this, I would appreciate it greatly.
> The same isapnp.conf worked in 2.2.x (but it wanted irq=9) so
> something changed from 2.2.x to 2.4.x
So, tell it to use IRQ 9. ISAPNP will do that, won't it? On the other
hand, 2.4 has real PnP support in it, so you may not need ISAPNP.
Kurt
--
Lie, n.:
A very poor substitute for the truth, but the only one
discovered to date.
More information about the Linux-users
mailing list