[plug] Sound Card prob & list query

[Dave T Burbidge]

Matt,

According to `lsmod`, the kernal has loaded opl3, sb, uart401, sound, soundlow
& soundcore (plus two NIC modules (ne2k-pci & 8390))

`dmesg` reports a conflict on IRQ5 when trying to get sound happenning.
/proc/interrupts lists a 'soundblaster' at IRQ5. /proc/pci doesn't list
anything at IRQ5.

One thought; is the soundblaster the correct module for this card? `dmesg`
does have a note about it trying to install it as a SB Pro (which it certainly
isn't)...
However it does report

SB 3.02 detected OK (220)
sb: Interrupt test on IRQ5 failed - Probable IRQ conflict
.....

DaveB

Matt Kemner wrote:

> On Mon, 6 Mar 2000, Dave T Burbidge wrote:
>
> > The chip on the card says: AD1812 JS - SoundPort 9617
>
> This maybe covered by ad1848.c or pss.c (both of which mention
> "soundport")
>
> > I currently have sound,
>
> So did the kernel load any modules? (ie what does lsmod tell you)
> Is there any information about IRQs etc for the card in your kernel logs
> ("dmesg")
>
> > but it keeps repeating itself ... kind kind of
> > of like like this this :) :)
>
> That often indicates an IRQ conflict.
> You may also be able to find out what IRQ the card uses by looking in
> /proc/interrupts.  /proc/pci or "lspci" should tell you what IRQs your PCI
> cards use - if one of them conflicts, try moving it to another slot.
>
> > Secondly, I occasionally receive mails from the list that don't have
> > "[plug]" in the subject
>
> The list doesn't add [plug] to the subject if the subject contains "Re:"
> so if somebody posts a message that says "Re: <blah>" (perhaps forwarded
> from another list) the [plug] tag won't be added.
>
> > ... which is how I filter the messages
>
> Your best bet for fitering is the "Return-path" header, which for plug
> messages is always set to plug-request at plug.linux.org.au.
>
>  - Matt