public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Taner Halicioglu <taner@taner.net>
To: linux-kernel@vger.kernel.org
Subject: 2.2.18 and EMU10K1 problems...
Date: Mon, 8 Jan 2001 13:56:29 -0800	[thread overview]
Message-ID: <20010108135629.S3871@boom.net> (raw)

(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/

             reply	other threads:[~2001-01-08 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 21:56 Taner Halicioglu [this message]
2001-01-08 21:58 ` 2.2.18 and EMU10K1 problems Taner Halicioglu
2001-01-09 22:42 ` Prasanna P Subash
  -- 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=20010108135629.S3871@boom.net \
    --to=taner@taner.net \
    --cc=linux-kernel@vger.kernel.org \
    /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