All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maximilian Güntner" <beomuex@gmx.de>
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: SB0880 X-Fi Titanium Fatal1ty Pro (with codecgraph)
Date: Mon, 14 Jul 2008 15:59:53 +0200	[thread overview]
Message-ID: <487B5BD9.7090307@gmx.de> (raw)
In-Reply-To: <s5hskubq72c.wl%tiwai@suse.de>

Takashi Iwai wrote:

>> Does this hack only work with the  X-Fi Titanium Fatal1ty Pro, or does 
>> it include support for all X-Fi based cards from Creative Labs?
>>     
>
> It's only for X-Fi with HD-audio compatibility.  It's not for native
> Emu20k stuff.
>   
HD-audio means what exactly?
How can i see whether a card has this feature or not?
The cards you mentioned have all 64 MB X-RAM, mine has only 2 MB.
Is this a indication of missing HD-Audio support ?

> I have got a Creative X-Fi Extreme Music, that gets infact recognized by 
> my system but modprobing the patched source (modprobe snd-hda-intel, i 
> hope this is the right one) does not work.
> Here the lspci if this helps:
>   
>
> Check "lspci -n".  So far, 1102:0009 and 1102:000b are known to be
> HD-audio compatible.
>
>   
This is lspci -nn
01:02.0 Multimedia audio controller [0401]: Creative Labs SB X-Fi 
[1102:0005]

-- beomuex

  reply	other threads:[~2008-07-14 13:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13 21:51 SB0880 X-Fi Titanium Fatal1ty Pro (with codecgraph) Tony "Chainsaw" Vroon
2008-07-14 10:57 ` Takashi Iwai
2008-07-14 13:23   ` Maximilian Güntner
2008-07-14 13:30     ` Takashi Iwai
2008-07-14 13:59       ` Maximilian Güntner [this message]
2008-07-14 14:05         ` Takashi Iwai
2008-07-14 21:35           ` Tony Vroon
2008-07-14 21:29   ` Tony "Chainsaw" Vroon
2008-07-14 23:38   ` Tony "Chainsaw" Vroon
2008-07-15 17:22   ` Tony "Chainsaw" Vroon

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=487B5BD9.7090307@gmx.de \
    --to=beomuex@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    --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 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.