From: Thomas Graham <lkthomas@hkicable.com>
To: rui.p.m.sousa@clix.pt
Cc: Thunder from the hill <schemins@netscape.net>,
linux-kernel@vger.kernel.org,
emu10k1-devel@opensource.creative.com
Subject: Re: emu10k1 driver breakdown in 2.4.9?
Date: Mon, 27 Aug 2001 20:45:33 +0800 (HKT) [thread overview]
Message-ID: <200108271245.UAA12261@alto.i-cable.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
> On Sat, 25 Aug 2001, Thunder from the hill wrote:
>
> Can you strace the player giving you trouble?
> Do you see any kernel oops in /var/log/messages?
>
> Rui Sousa
>
> >
> > ---------4f17ff67523f7284f17ff67523f728
> > Content-Type: text/plain; charset=iso-8859-1
> > Content-Transfer-Encoding: 8bit
> > Content-Disposition: inline
> >
> > Hi,
> >
> > I am running Linux 2.4.9 compiled on gcc-2.95.2 with K6-II optimization and support for the emu10k1 cards, as I'm using a SB Live!. But whenever I play something that does not go straight to the soundcard (e.g. mp3), the program receives a SIGSEGV. No matter which program.
> > It all worked fine on Linux-2.4.2, so it seems not the players fault.
> >
> > config.h appended.
> >
> > Thunder
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
How to run K6-II optimization ?
and if I am using emu10k1 driver from creative ( not use kernel one ) , only 2speaker are work fine ( I have creative FPS2000 speaker ), why ?
next reply other threads:[~2001-08-27 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 12:45 Thomas Graham [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-25 8:23 emu10k1 driver breakdown in 2.4.9? Thunder from the hill
2001-08-27 9:31 ` rui.p.m.sousa
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=200108271245.UAA12261@alto.i-cable.com \
--to=lkthomas@hkicable.com \
--cc=emu10k1-devel@opensource.creative.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.p.m.sousa@clix.pt \
--cc=schemins@netscape.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