From: Takashi Iwai <tiwai@suse.de>
To: bernhard.posselt@gmx.at
Cc: alsa-devel@alsa-project.org
Subject: Re: No sound with Creative Labs CA0106 Soundblaster
Date: Fri, 17 Apr 2009 09:07:17 +0200 [thread overview]
Message-ID: <s5hvdp3ahcq.wl%tiwai@suse.de> (raw)
In-Reply-To: <200904162323.55158.bernhard.posselt@gmx.at>
At Thu, 16 Apr 2009 23:23:55 +0200,
Bernhard Posselt wrote:
>
> Am Donnerstag 16 April 2009 16:10:29 schrieben Sie:
> > At Wed, 15 Apr 2009 04:00:26 +0200,
> >
> > Bernhard Posselt wrote:
> > > Hi, some months ago i bought a new soundcard for my PC which costed 20€.
> > > This card is not working.
> > >
> > > Im using Kubuntu Jaunty Beta, its a fresh install from the beta iso. I
> > > also upgraded the alsadrivers with this package
> > > http://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-
> > >snapshot.tar.bz2
> > >
> > > Still no sound
> >
> > Please show your alsa-info.sh output (run with --no-upload option).
> >
> > If it's an unknown model, try to pass some serial number via subsystem
> > module option, such as,
> >
> > # modprobe snd-ca0106 subsystem=0x10131102
> >
> > The available numbers are found in ca0106_chip_details[] list in
> > ca0106/ca0106_main.c.
> >
> >
> > Takashi
>
> It's an Audigy Soundblaster LE, or better was. I guess you thought that i
> would be using the SE model.
No, I just thought you are using a model that isn't listed in the
ca0106 driver's white list, no matter which one. Createive tends to
ship quite lots of variants with different SSIDs although many are
compatible.
Takashi
next prev parent reply other threads:[~2009-04-17 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 2:00 No sound with Creative Labs CA0106 Soundblaster Bernhard Posselt
2009-04-16 14:10 ` Takashi Iwai
[not found] ` <200904162323.55158.bernhard.posselt@gmx.at>
2009-04-17 7:07 ` Takashi Iwai [this message]
2009-04-28 12:51 ` James Courtier-Dutton
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=s5hvdp3ahcq.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=bernhard.posselt@gmx.at \
/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