From: "Jeffrey H. Ingber" <jhingber@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: [EMU10K1] Bug in EMU10K1
Date: 17 Nov 2001 02:10:50 -0500 [thread overview]
Message-ID: <1005981053.1377.0.camel@Eleusis> (raw)
I'm having difficulty making an E-MU E-Card work with any degree of
success under Linux. Accoring to the notes in the driver, this card is
listed as supported:
drivers/sound/emu10k1/main.c
* 0.3 Fixed mixer routing bug, added APS, joystick support.
* 0.7 Support for the Emu-APS. Bug fixes for voice cache setup, mmaped
sound + poll().
The modules load, mixer loads (but only has controls for 'Master'
and 'DSP'), can use audio applications but don't hear sound. System
crashes (hard-lock, no SysReq, etc.) if audio is stoped and restarted.
I had no trouble making a vanilla Live work with any of these drivers.
Driver is stock RH kernel from 2.4.9-12 with and without SMP - also
tried CVS
driver from Creative (11/02/2001) with same results. System is IBM
NetFinity 5600 with 2x
PIII's @ 666 MHz. Card is an E-MU E-Card without E-Drive.
/sbin/modprobe emu10k1
Nov 17 02:00:31 Eleusis kernel: Creative EMU10K1 PCI Audio Driver,
version 0.7,
18:28:17 Oct 30 2001
Nov 17 02:00:31 Eleusis kernel: emu10k1: EMU10K1 rev 5 model 0x4001
found, IO at
0x2020-0x203f, IRQ 18
/sbin/lspci -v00:0a.0 Multimedia audio controller: Creative Labs SB
Live!
EMU10000 (rev 05)
Subsystem: Creative Labs E-mu APS
Flags: bus master, medium devsel, latency 48, IRQ 18
I/O ports at 2020 [size=32]
Capabilities: [dc] Power Management version 1
00:0a.1 Input device controller: Creative Labs SB Live! (rev 05)
Subsystem: Creative Labs: Unknown device 4001
Flags: bus master, medium devsel, latency 48
I/O ports at 2040 [size=8]
Capabilities: [dc] Power Management version 1
reply other threads:[~2001-11-17 7:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1005981053.1377.0.camel@Eleusis \
--to=jhingber@ix.netcom.com \
--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