Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shayne O'Connor <forums@machinehasnoagenda.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: emu10k1 driver broken in CVS
Date: Wed, 16 Mar 2005 15:48:40 +1100	[thread overview]
Message-ID: <4237BAA8.3020405@machinehasnoagenda.com> (raw)
In-Reply-To: <1110947679.19739.3.camel@mindpipe>

Lee Revell wrote:

>With current ALSA CVS and the following hardware (an old SBLive
>platinum):
>
>0000:00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 05)
>        Subsystem: Creative Labs CT4760 SBLive!
>
>the emu10k1 driver locks up the machine as soon as you try to play
>anything.  I tried both JACK and aplay.  I am doing a binary search to
>find the problem.
>  
>
i had the same sort of problem with alsa cvs earlier on today, with my
son's computer (i think it's exactly the same card you describe, Lee) ...

after compiling, i tried inserting the alsa modules and got a whole
bunch of errors ... when rebooting back into xfce4.2, it just froze at
the splash screen ... had to boot into an earlier kernel and re-install
the Planet CCRMA alsa modules.

shayne


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-16  4:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16  4:34 emu10k1 driver broken in CVS Lee Revell
2005-03-16  4:48 ` Shayne O'Connor [this message]
2005-03-16  4:46   ` Lee Revell
2005-03-16  4:59     ` Lee Revell
2005-03-16  5:09       ` Lee Revell

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=4237BAA8.3020405@machinehasnoagenda.com \
    --to=forums@machinehasnoagenda.com \
    --cc=alsa-devel@lists.sourceforge.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