public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: tiwai@suse.de, ghrt@dial.kappa.ro, perex@suse.cz,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: No sound from SB live!
Date: Sun, 19 Feb 2006 19:19:07 +0000	[thread overview]
Message-ID: <20060219191907.GA2355@ucw.cz> (raw)
In-Reply-To: <9a8748490602190304w43c32ae6m5b610f2ec9ad46f2@mail.gmail.com>

Hi!

> > I have SB Live! here. I remember it worked long time ago. Now I can't
> > get it to produce any sound :-(.
> >
> > root@hobit:~# cat /proc/asound/cards
> >  0 [Live           ]: EMU10K1 - SBLive! Value [CT4830]
> >                       SBLive! Value [CT4830] (rev.7,
> > serial:0x80261102) at 0x3000, irq 20
> >  1 [Bt878          ]: Bt87x - Brooktree Bt878
> >                       Brooktree Bt878 at 0xd0001000, irq 17
> >
> > root@hobit:~# uname -a
> > Linux hobit 2.6.16-rc4 #1 SMP PREEMPT Sat Feb 18 23:53:41 CET 2006
> > i686 GNU/Linux
> >
> 
> I've got an SB Live! card here as well. Not exactely the same as yours
> (mine's rev. 10, yours is rev. 7), but mine works just fine with
> 2.6.16-rc4, so whatever is wrong it does not seem to effect all SB
> Live! cards...

Strange... My sb live! did not work with linux: all seemed okay,
but no sound, oss or alsa. My brother moved it on windows PC,
and got same failure, then bluescreens on next boots. He reseated the
card, and it started working. I guess it is flakey hw...

-- 
Thanks, Sharp!

  parent reply	other threads:[~2006-02-22 13:52 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 23:14 No sound from SB live! Pavel Machek
2006-02-18 23:27 ` ghrt
2006-02-18 23:48   ` Pavel Machek
2006-02-19  0:33     ` Richard Mittendorfer
2006-02-19 21:42       ` Pavel Machek
2006-02-19 22:07         ` Richard Mittendorfer
2006-02-19  0:58     ` Lee Revell
2006-02-19 21:44       ` Pavel Machek
2006-02-20  0:33         ` Lee Revell
2006-02-20  0:39           ` Pavel Machek
2006-02-20  1:33             ` Alistair John Strachan
2006-02-20 23:55               ` Pavel Machek
2006-02-19 11:04 ` Jesper Juhl
2006-02-19 11:18   ` Nick Warne
2006-02-19 19:29     ` Lee Revell
2006-02-19 20:20       ` Nick Warne
2006-02-19 20:31         ` Lee Revell
2006-02-20 19:18           ` Nick Warne
2006-02-20 19:31             ` D. Hazelton
2006-02-19 20:33         ` Lee Revell
2006-02-19 20:51     ` Nishanth Aravamudan
2006-02-19 21:30       ` Lee Revell
2006-02-19 21:47         ` Pavel Machek
2006-02-19 21:50           ` Lee Revell
2006-02-19 23:23             ` Alistair John Strachan
2006-02-19 23:32               ` Lee Revell
2006-02-19 23:46                 ` Pavel Machek
2006-02-19 23:53                   ` Lee Revell
2006-02-20  0:04                     ` Nishanth Aravamudan
2006-02-20  0:11                       ` Lee Revell
2006-02-20  0:57                         ` Nishanth Aravamudan
2006-02-20  0:26                     ` Pavel Machek
2006-02-20  0:30                       ` Lee Revell
2006-02-20  0:42                         ` Pavel Machek
2006-02-20  0:52                           ` Lee Revell
2006-02-19 23:56                 ` Alistair John Strachan
2006-02-20  0:05                   ` Lee Revell
2006-02-20  0:12                     ` David Lang
2006-02-20  0:16                       ` Alistair John Strachan
2006-02-20  0:17                       ` Lee Revell
2006-02-19 21:49         ` Pavel Machek
2006-02-19 21:54           ` Lee Revell
2006-02-19 22:25             ` Pavel Machek
2006-02-19 22:28               ` Lee Revell
2006-02-19 23:04                 ` Lee Revell
2006-02-20 11:15               ` Takashi Iwai
2006-02-20 11:41                 ` Pavel Machek
2006-02-20 19:50                   ` Vojtech Pavlik
2006-02-20 19:52                     ` Pavel Machek
2006-02-19 19:19   ` Pavel Machek [this message]
2006-02-22 14:05     ` Takashi Iwai

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=20060219191907.GA2355@ucw.cz \
    --to=pavel@suse.cz \
    --cc=ghrt@dial.kappa.ro \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.de \
    /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