All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hubbell <richard.hubbell@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: sound problems in 2.6.8.1 w/ EMU10K1
Date: Tue, 12 Oct 2004 12:05:34 -0700	[thread overview]
Message-ID: <c25b25320410121205586f32f4@mail.gmail.com> (raw)

I compiled a 2.6.8.1 kernel and something has changed so that sound
works much differently.
At first I thought that it wasn't working at all, but with a bunch of
fiddling around I found I could get sound.  It's not clear to me if
this is an ALSA problem, kernel problem or both.  The first thing I
discovered was that with programs like xmms I had to change the device
to be hw:0,3 instead of the usual default of hw:0,0 .  Let's see if I
can provide some more context....

 All the devices look correct in /dev/snd/*, I use no modules but
rather compile all into the kernel.  Everything in /proc/asound looks
as it should.  (Of I never really had to look there
in previous kernels where sound was working).  The EMU10K1 (SBLive)
appears as card 0 and device 0 (as well as the other devices on that
card).  My ALSA lib versions match the kernel version.

My problems:

1.  default sound isn't working,  to make some apps work I created an
~/.asound file
     to specifiy the default to be  hw:0,3  (i.e. card0, device3 or pcmC0D3p)

2.  I can no longer play mono 8000 Hz sounds, attempting to do so hard locks
     the machine and requires a power cycle to recover.

I can provide more context if you think it will help.  Should this go
to ALSA instead?

Thanks in advance,
Richard

             reply	other threads:[~2004-10-12 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 19:05 Richard Hubbell [this message]
2004-10-12 19:33 ` sound problems in 2.6.8.1 w/ EMU10K1 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=c25b25320410121205586f32f4@mail.gmail.com \
    --to=richard.hubbell@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.