From: The Source <thesourcehim@gmail.com>
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: SB X-Fi driver fixes (Re: Testers wanted: New SB X-Fi driver)
Date: Tue, 09 Jun 2009 07:50:33 +0400 [thread overview]
Message-ID: <4A2DDC09.3050705@gmail.com> (raw)
In-Reply-To: <s5h63f6f8qo.wl%tiwai@suse.de>
On 09.06.2009 06:20, Takashi Iwai wrote:
> At Mon, 08 Jun 2009 22:16:01 +0200,
> Gernot Kohlhaas wrote:
>
>> Takashi Iwai schrieb:
>>
>>> Please check alsa-driver/HEAD and alsa-driver/alsa-kernel/HEAD
>>> to identify which version you are using. Update to the latest one,
>>> too.
>>> Also, don't forget to enable the debug option via --with-debug=full
>>> to configure script.
>>>
>> alsa-driver-snapshot downloaded today.
>>
>> alsa-driver/HEAD:
>> dae8eb6334cc973b91a29a973108dcbba4ac24bf Fix ctatc.patch
>> f89c50e8a567e1e34931dae07d8adc6cbe08e108 Add linux/math64.h compat header
>> b387a66e3bdf25284ef2f57545d305735e4646e3 Add missing pci/ctxfi/cttimer.c
>> 955ee62b99a82018196b9f668a5ee6606175109e Merge branch 'topic/maya44'
>> 6254b0fa8631a8a2a83fbc3eff36b512d834118d alsa-info.sh: Provide system
>> manufacturer and product name from DMI
>> bbfb14518b44c3caba5c5bc351c9ee340a96d867 Add parsing of def_tristate to
>> mod-deps
>> 93e325ec42cbf842799bfbdf28b17c7f81f8089e Regenerated riptide.patch
>> 5a4737e4e0ef6587e7f6ca84ccdc6f88c54cf18a Add soc/txx9 build stub
>> bf12e88a905bfd49206eb2519a5519564e9a2b94 ctxfi - Fix build with older kernel
>> dfec670bc3bd3351b61dcd40b4c2ced4f95b91d8 ctxfi - Add new PCI ids to
>> pci_ids_compat.h.in
>>
>> alsa-driver/alsa-kernel/HEAD
>> 299c425e12d437bd413aa45381cf035bbc67e545 Merge branch 'topic/ctxfi'
>> 09521d2e3edd0bf02b66e5b8c13f1559f2d6958a ALSA: ctxfi - Fix wrong model
>> id for UAA
>> 549d272ac7d0d98c1fb3419108befb05f88605d7 Merge branch 'topic/ctxfi'
>> 9470195a9cd13e6d90221b8b5d897e9232da8d28 ALSA: ctxfi - Clean up probe
>> routines
>> ec46e1d31cb6ff5bac6333c06b6b79c941368cb4 Merge branch 'topic/hda'
>> f03ecf50534a81b06544c58a713076d59d54baf9 ALSA: hda - Fix the previous
>> tagra-8ch patch
>> 3885e40ccf9629f1cda4aac23f3d6c9c82fb875e Merge branch 'topic/hda'
>> 64a8be74357477558183b43156c5536b642de134 ALSA: hda - Add 7.1 support for
>> MSI GX620
>> 318192e14f80bb883dfd06eb9ea8aa22e7353dd3 Merge branch
>> 'topic/pcm-jiffies-check'
>> c00701101b82f2bc61dfc259748ec6e5288af6a9 ALSA: pcm - A helper function
>> to compose PCM stream name for debug prints
>>
>> The crash happened with alsa-driver-unstable-snapshot from 2009-06-07
>> and with alsa-driver-snapshot from 2009-06-08.
>>
>> Still no usable output. Only dmesg gives me two more lines when loading
>> the module:
>> ALSA /usr/src/alsa-driver/pci/ctxfi/ctatc.c:1248: ctxfi: chip 20K1 model
>> Unknown (1102:002c) is found
>> SB-XFi 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> ALSA
>> /usr/src/alsa-driver/pci/ctxfi/../../alsa-kernel/pci/ctxfi/cttimer.c:419:
>> ctxfi: Use xfi-native timer
>>
>> With debug=full, the sound gets distorted every 1/3 second.
>>
>> The crash only happens in xmms and audacious, when my upmix-device is
>> used (there I use a low pass filter via ladspa). When I use the default
>> device, it just plays fine (but only plain stereo without subwoofer ;) ).
>> I'll try to disable the low pass filter to see, if it works better.
>>
> Also, do you mean that the default output works without 1/3 second
> distortion? Or, the distortion happens regardless of your PCM device
> setup?
>
> I'd like to concentrate on debugging the default setup at first,
> so better to reduce the risk of brokenness of ladspa plugin.
> If you get any severe problems with the default setup, please let me
> know more details.
>
>
> thanks,
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
>
PA now works, thank you. Still 'ticks' with OpenAL though
next prev parent reply other threads:[~2009-06-09 3:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 18:42 Testers wanted: New SB X-Fi driver MonsieurWeller
2009-06-06 9:14 ` Takashi Iwai
[not found] ` <1244376026.6985.5.camel@polo-desktop>
2009-06-07 16:10 ` Takashi Iwai
2009-06-08 12:03 ` SB X-Fi driver fixes (Re: Testers wanted: New SB X-Fi driver) Takashi Iwai
2009-06-08 18:21 ` Gernot Kohlhaas
2009-06-08 19:28 ` Takashi Iwai
2009-06-08 20:16 ` Gernot Kohlhaas
2009-06-09 1:51 ` Takashi Iwai
2009-06-09 2:20 ` Takashi Iwai
2009-06-09 3:50 ` The Source [this message]
2009-06-09 5:32 ` Takashi Iwai
2009-06-09 5:23 ` Gernot Kohlhaas
2009-06-09 5:39 ` Takashi Iwai
2009-06-09 5:44 ` Gernot Kohlhaas
2009-06-09 6:24 ` Takashi Iwai
2009-06-09 9:54 ` Takashi Iwai
2009-06-09 17:11 ` Gernot Kohlhaas
2009-06-15 12:58 ` Takashi Iwai
2009-06-15 16:17 ` Gernot Kohlhaas
2009-06-28 13:07 ` Bjoern Olausson
2009-06-10 2:31 ` Lee Revell
2009-06-10 13:21 ` Sebastian Schneider
2009-06-10 13:33 ` Takashi Iwai
2009-06-10 14:02 ` Sebastian Schneider
2009-06-10 14:04 ` Takashi Iwai
[not found] ` <1244650915.4173.6.camel@polo-desktop>
2009-06-10 17:42 ` Testers wanted: New SB X-Fi driver Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-06-08 18:35 SB X-Fi driver fixes (Re: Testers wanted: New SB X-Fi driver) Gernot Kohlhaas
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=4A2DDC09.3050705@gmail.com \
--to=thesourcehim@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox