Re: 2.2.18 and EMU10K1 problems...

Taner Halicioglu (taner@taner.net)
Mon, 8 Jan 2001 13:58:47 -0800


Err, I should have mentioned that the configs I used for .17 and .18 are
identical, too. Machine is a dual celeron 450 on a asus p2b-ds (Adaptec
aic78xx SCSI), via-rhine ethernet, and nvidia tnt2 ultra.

Thanks, again

-Taner

On Mon, Jan 08, 2001 at 01:56:29PM -0800, Taner Halicioglu <taner@taner.net> wrote:

> (please cc me if you reply - thanks :)
>
> I probably missed a message or note or something about this, but when I went
> from 2.2.17 to 2.2.18, my sound card (SB Live!) stopped working. It seems
> that in 2.2.18, it gets detected TWICE:
>
> --------------------------------
> kernel: Linux version 2.2.18
> [...]
> kernel: Creative EMU10K1 PCI Audio Driver, version 0.7, 20:05:23 Jan 7 2001
> kernel: emu10k1: EMU10K1 rev 5 model 0x21 found, IO at 0xb400-0xb41f, IRQ 10
> [... IDE, floppy, SCSI, eth0, partition check ...]
> kernel: Creative EMU10K1 PCI Audio Driver, version 0.7, 20:05:23 Jan 7 2001
> --------------------------------
>
> This is what it normally does:
>
> --------------------------------
> kernel: Linux version 2.2.17
> [...]
> kernel: Creative EMU10K1 PCI Audio Driver, version 0.6, 20:25:53 Jan 7 2001
> kernel: emu10k1: EMU10K1 rev 5 model 0x21 found, IO at 0xb400-0xb41f, IRQ 10
> [...]
> --------------------------------
>
> In the 2.2.18 case, /proc/interrupts doesn't show anything on int 10.
>
> I guess I should (and will) take this up with the EMU10k people, but I was
> just wondering if anyone here has seen this problem before? I'm curious how
> a broken driver would have made it into .18 like that ;-) ...unless I'm the
> one that is broken :)
>
> Thanks,
>
> -Taner
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/