From: Prasanna P Subash <psubash@turbolinux.com>
To: Taner Halicioglu <taner@taner.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 and EMU10K1 problems...
Date: Tue, 9 Jan 2001 14:42:24 -0800 [thread overview]
Message-ID: <20010109144224.C410@turbolinux.com> (raw)
In-Reply-To: <20010108135629.S3871@boom.net>
In-Reply-To: <20010108135629.S3871@boom.net>; from Taner Halicioglu on Mon, Jan 08, 2001 at 01:56:29PM -0800
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
remember seeing something about this on the list.
Build it as a module, and not into the kernel and it should work.
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | Actually, what I'd like is a little toy
of a GNU generation -o) | spaceship!!
Kernel 2.4.0-test11 /\\ |
on a i686 _\\_v |
|
------------------------------------------------------------------------
On Mon, Jan 08, 2001 at 01:56:29PM -0800, Taner Halicioglu 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/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-01-09 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 21:56 2.2.18 and EMU10K1 problems Taner Halicioglu
2001-01-08 21:58 ` Taner Halicioglu
2001-01-09 22:42 ` Prasanna P Subash [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 0:32 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010109144224.C410@turbolinux.com \
--to=psubash@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=taner@taner.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox