public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Borgerding <mark@borgerding.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ALSA vs. OSS
Date: Tue, 20 Jan 2004 08:18:42 -0500	[thread overview]
Message-ID: <400D2AB2.7030400@borgerding.net> (raw)
In-Reply-To: <200401201046.24172.hus@design-d.de>

Me too.  I cannot get ALSA working on my SB Live.

If I may be so bold as to make a suggestion: Maybe the developer in
charge of ALSA's e-mu driver could work with us poor unfortunates.
There may be some commonality between our systems that causes this
(besides the sound blaster live).

My system:
Sound: SBLive Value
Redhat 7.3 (w/ piecemeal recompiles & upgrades)
Kernel: 2.6.1
CPU: Athlon XP 2100+
Mobo: ASUS (I think it's A7V333. I can confirm this later.)


-- Mark "runnin' dirty and deprecated" Borgerding



Heinz Ulrich Stille wrote:

>On Monday 19 January 2004 19:21, Travis Morgan wrote:
>  
>
>>I have a soundblaster Live Value card. I can no longer control the
>>    
>>
>
>I also have a SB Live!, and it doesn't work with ALSA at all - the AC97
>codec doesn't load. I haven't taken the time to track it down as it does
>work just fine with OSS (under SMP at that).
>
>  
>
>>output level through my digital out. With OSS my PCM volume used to
>>affect both the headphone jack and the digital out. With ALSA it affects
>>only the headphone jack.
>>    
>>
>
>That's a purely firmware thing with this card; you should just have to
>load the right patches. I don't know whether there is a loader utility
>for alsa, though. Perhaps the old utils will work?
>
>Anyway, even if it's not working for me at the moment, it's still the
>superior architecture; just wait until the bugs affecting your specific
>situation are ironed out and userland utilities are available...
>
>MfG, Ulrich
>
>  
>




  reply	other threads:[~2004-01-20 13:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 17:18 ALSA vs. OSS Markus Hästbacka
2004-01-19 17:48 ` Steve Youngs
2004-01-19 18:21   ` Travis Morgan
2004-01-20  8:58     ` Gábor Lénárt
2004-01-20  9:46     ` Heinz Ulrich Stille
2004-01-20 13:18       ` Mark Borgerding [this message]
2004-01-20 14:03         ` Markus Hästbacka
2004-01-20 14:07           ` Takashi Iwai
2004-01-20 14:17             ` Markus Hästbacka
2004-01-20 14:28               ` Takashi Iwai
2004-01-20 14:37                 ` Markus Hästbacka
2004-01-20 14:41                   ` Takashi Iwai
2004-02-25 22:21                     ` Markus Hästbacka
     [not found]                 ` <20040120170658.GB23351@widomaker.com>
2004-01-20 17:35                   ` Takashi Iwai
2004-01-20 14:08         ` Heinz Ulrich Stille
2004-01-20 15:13         ` Alistair John Strachan
2004-01-20 15:19           ` Jaroslav Kysela
2004-01-22 23:53             ` Zephaniah E. Hull
2004-01-23  8:31               ` Jaroslav Kysela
2004-01-20 19:00       ` Eric Sandall
2004-01-21 11:03         ` Dale Weber
2004-01-21 18:06           ` Mike Fedyk
2004-01-24  8:21     ` Travis Morgan
2004-01-20 19:24   ` Brian McGroarty
2004-01-20 19:46     ` Måns Rullgård
2004-01-19 18:08 ` Raphaël RIGO
2004-01-19 19:42 ` Jaroslav Kysela
2004-01-20 14:24   ` Olaf Dabrunz
2004-01-20 14:44     ` Thomas Dodd
     [not found]     ` <Pine.LNX.4.58.0401201524230.2010@pnote.perex-int.cz>
2004-01-20 14:48       ` Olaf Dabrunz
2004-01-20 15:06     ` Takashi Iwai
     [not found] <20040119174543.59620.qmail@web40610.mail.yahoo.com>
2004-01-19 18:06 ` Markus Hästbacka
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21  2:40 Jonathan Boler

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=400D2AB2.7030400@borgerding.net \
    --to=mark@borgerding.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