Testers wanted: New SB X-Fi driver

Testers wanted: New SB X-Fi driver

[Christian Esken]

Hello,

unfortunately I cannot playback anything (PCM) with the new SB X-Fi driver.
  Driver: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
driver-snapshot.tar.bz2
  Distribution: openSuSE 11.1
  Kernel: 2.6.27.23-0.1-xen

My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The card is 
recognized by the driver, and any mixer (alsamixer, kmix) also recognizes the 
card.

But playing back isn't possible. I tried speaker-test, audacity, amarok and 
aplay. Most applications  hang, some also produce an error in the 
/var/log/messages (see 
below).

I then used "./configure --with-debug=full --with-cards=ctxfi" due to the 
possible hd-audio conflict, but it didn't make a difference.

Is there anything else I could try?

 Christian


--- Console output from speaker-test ---
bash # LANG=en speaker-test

speaker-test 1.0.18

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 512 to 65536
Period size range from 32 to 32768
Using max buffer size 65536
Periods = 4
was set period_size = 16384
was set buffer_size = 65536
 0 - Front Left
Write error: -5,Input/output error
xrun_recovery failed: -5,Input/output error
Transfer failed: Operation not permitted
------------------------------------------------------------------------

--- output in /var/log/messages when running speaker-test ---
Jun 27 12:52:53 firefly kernel: ALSA /home/chris/Desktop/alsa-
driver/acore/../alsa-kernel/core/pcm_lib.c:1693: playback write error (DMA or 
IRQ trouble?)
------------------------------------------------------------------------

---output in /var/log/messages when running amarok with pulseudio ---
 20 11:11:00 firefly pulseaudio[5649]: module-alsa-sink.c: ALSA woke us up to 
write new data to the device, but there was actually nothing to write! Most
likely this is an ALSA driver bug.
------------------------------------------------------------------------



--- Hardware information ---
firefly:~ # lspci -nn  | grep -i audio
00:07.0 Audio device [0403]: nVidia Corporation MCP65 High Definition Audio 
[10de:044a] (rev a1)
01:07.0 Multimedia audio controller [0401]: Cirrus Logic CS 4614/22/24/30 
[CrystalClear SoundFusion Audio Accelerator] [1013:6003] (rev 01)
05:00.0 Audio device [0403]: Creative Labs Device [1102:000b] (rev 03)


--- Hardware information from lshal ---
udi = '/org/freedesktop/Hal/devices/pci_1102_b_sound_card_0'
  info.capabilities = {'sound'} (string list)
  info.category = 'sound'  (string)
  info.parent = '/org/freedesktop/Hal/devices/pci_1102_b'  (string)
  info.product = 'Creative X-Fi 20K2 SB0880 Sound Card'  (string)
  info.subsystem = 'sound'  (string)
  info.udi = '/org/freedesktop/Hal/devices/pci_1102_b_sound_card_0'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'sound'  (string)
  linux.sysfs_path = 
'/sys/devices/pci0000:00/0000:00:0e.0/0000:05:00.0/sound/card0'  (string)
  sound.card = 0  (0x0)  (int)
  sound.card_id = 'Creative X-Fi 20K2 SB0880'  (string)
  sound.originating_device = '/org/freedesktop/Hal/devices/pci_1102_b'  
(string)

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> Hello,
>
> unfortunately I cannot playback anything (PCM) with the new SB X-Fi driver.
>   Driver: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> driver-snapshot.tar.bz2
>   Distribution: openSuSE 11.1
>   Kernel: 2.6.27.23-0.1-xen
>
> My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The card is
> recognized by the driver, and any mixer (alsamixer, kmix) also recognizes
> the card.
>
> But playing back isn't possible. I tried speaker-test, audacity, amarok and
> aplay. Most applications  hang, some also produce an error in the
> /var/log/messages (see
> below).
>
> I then used "./configure --with-debug=full --with-cards=ctxfi" due to the
> possible hd-audio conflict, but it didn't make a difference.
>
> Is there anything else I could try?

I tested the same openSuSE version with a non-Xen 64 bit kernel, and it 
doesn't work either.

And I tried with this:
  Driver: alsa-driver-20090704.tar.bz2
  Distribution: Kubuntu Karmic Alpha-2
  Kernel: 2.6.30  (32 Bit)

Under the latter setup the X-Fi Titanium works (Simple 2 channel test with 
speaker-test, audacity, amarok). :-))

What I now know/believe is this:
- Alsa driver : not responisible (it works)
- My Computer hardware : not responsible (it works)
 - Xen kernel: quite likely not responsible
 - Kernel < 2.6.30: Probably responsible
 - 64 Bit: Probably responsible
- Other less likely stuff like NVIDIA driver (nv vs nvidia): Could be checked

I will now check other combinations. Next will be Kernel 2.6.30 (64 bit), 
using openSUSE 11.2-Milestone3.

   Christian

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sun, 5 Jul 2009 00:19:55 +0200,
Christian Esken wrote:
> 
> Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > Hello,
> >
> > unfortunately I cannot playback anything (PCM) with the new SB X-Fi driver.
> >   Driver: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> > driver-snapshot.tar.bz2
> >   Distribution: openSuSE 11.1
> >   Kernel: 2.6.27.23-0.1-xen
> >
> > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The card is
> > recognized by the driver, and any mixer (alsamixer, kmix) also recognizes
> > the card.
> >
> > But playing back isn't possible. I tried speaker-test, audacity, amarok and
> > aplay. Most applications  hang, some also produce an error in the
> > /var/log/messages (see
> > below).
> >
> > I then used "./configure --with-debug=full --with-cards=ctxfi" due to the
> > possible hd-audio conflict, but it didn't make a difference.
> >
> > Is there anything else I could try?
> 
> I tested the same openSuSE version with a non-Xen 64 bit kernel, and it 
> doesn't work either.
> 
> And I tried with this:
>   Driver: alsa-driver-20090704.tar.bz2
>   Distribution: Kubuntu Karmic Alpha-2
>   Kernel: 2.6.30  (32 Bit)
> 
> Under the latter setup the X-Fi Titanium works (Simple 2 channel test with 
> speaker-test, audacity, amarok). :-))

How many RAM do you have?
Could you boot with the limited memory size?


Takashi

> 
> What I now know/believe is this:
> - Alsa driver : not responisible (it works)
> - My Computer hardware : not responsible (it works)
>  - Xen kernel: quite likely not responsible
>  - Kernel < 2.6.30: Probably responsible
>  - 64 Bit: Probably responsible
> - Other less likely stuff like NVIDIA driver (nv vs nvidia): Could be checked
> 
> I will now check other combinations. Next will be Kernel 2.6.30 (64 bit), 
> using openSUSE 11.2-Milestone3.
> 
>    Christian
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> At Sun, 5 Jul 2009 00:19:55 +0200,
>
> Christian Esken wrote:
> > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > Hello,
> > >
> > > unfortunately I cannot playback anything (PCM) with the new SB X-Fi
> > > driver. Driver:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> > > driver-snapshot.tar.bz2
> > >   Distribution: openSuSE 11.1
> > >   Kernel: 2.6.27.23-0.1-xen
> > >
> > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The card is
> > > recognized by the driver, and any mixer (alsamixer, kmix) also
> > > recognizes the card.
> > >
> > > But playing back isn't possible. I tried speaker-test, audacity, amarok
> > > and aplay. Most applications  hang, some also produce an error in the
> > > /var/log/messages (see
> > > below).
> > >
> > > I then used "./configure --with-debug=full --with-cards=ctxfi" due to
> > > the possible hd-audio conflict, but it didn't make a difference.
> > >
> > > Is there anything else I could try?
> >
> > I tested the same openSuSE version with a non-Xen 64 bit kernel, and it
> > doesn't work either.
> >
> > And I tried with this:
> >   Driver: alsa-driver-20090704.tar.bz2
> >   Distribution: Kubuntu Karmic Alpha-2
> >   Kernel: 2.6.30  (32 Bit)
> >
> > Under the latter setup the X-Fi Titanium works (Simple 2 channel test
> > with speaker-test, audacity, amarok). :-))
>
> How many RAM do you have?
> Could you boot with the limited memory size?

It is just 2GB. So I am not limited by the 32 bit barrier.

So booting with "limited" memory size doesn't make sense, right?

   Christian

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sun, 5 Jul 2009 13:29:48 +0200,
Christian Esken wrote:
> 
> Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > At Sun, 5 Jul 2009 00:19:55 +0200,
> >
> > Christian Esken wrote:
> > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > Hello,
> > > >
> > > > unfortunately I cannot playback anything (PCM) with the new SB X-Fi
> > > > driver. Driver:
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> > > > driver-snapshot.tar.bz2
> > > >   Distribution: openSuSE 11.1
> > > >   Kernel: 2.6.27.23-0.1-xen
> > > >
> > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The card is
> > > > recognized by the driver, and any mixer (alsamixer, kmix) also
> > > > recognizes the card.
> > > >
> > > > But playing back isn't possible. I tried speaker-test, audacity, amarok
> > > > and aplay. Most applications  hang, some also produce an error in the
> > > > /var/log/messages (see
> > > > below).
> > > >
> > > > I then used "./configure --with-debug=full --with-cards=ctxfi" due to
> > > > the possible hd-audio conflict, but it didn't make a difference.
> > > >
> > > > Is there anything else I could try?
> > >
> > > I tested the same openSuSE version with a non-Xen 64 bit kernel, and it
> > > doesn't work either.
> > >
> > > And I tried with this:
> > >   Driver: alsa-driver-20090704.tar.bz2
> > >   Distribution: Kubuntu Karmic Alpha-2
> > >   Kernel: 2.6.30  (32 Bit)
> > >
> > > Under the latter setup the X-Fi Titanium works (Simple 2 channel test
> > > with speaker-test, audacity, amarok). :-))
> >
> > How many RAM do you have?
> > Could you boot with the limited memory size?
> 
> It is just 2GB. So I am not limited by the 32 bit barrier.
> 
> So booting with "limited" memory size doesn't make sense, right?

Supposedly.  Is it emu20k1 or emu20k2?


Takashi

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> At Sun, 5 Jul 2009 13:29:48 +0200,
>
> Christian Esken wrote:
> > Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > > At Sun, 5 Jul 2009 00:19:55 +0200,
> > >
> > > Christian Esken wrote:
> > > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > > Hello,
> > > > >
> > > > > unfortunately I cannot playback anything (PCM) with the new SB X-Fi
> > > > > driver. Driver:
> > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> > > > > driver-snapshot.tar.bz2
> > > > >   Distribution: openSuSE 11.1
> > > > >   Kernel: 2.6.27.23-0.1-xen
> > > > >
> > > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The card
> > > > > is recognized by the driver, and any mixer (alsamixer, kmix) also
> > > > > recognizes the card.
> > > > >
> > > > > But playing back isn't possible. I tried speaker-test, audacity,
> > > > > amarok and aplay. Most applications  hang, some also produce an
> > > > > error in the /var/log/messages (see
> > > > > below).
> > > > >
> > > > > I then used "./configure --with-debug=full --with-cards=ctxfi" due
> > > > > to the possible hd-audio conflict, but it didn't make a difference.
> > > > >
> > > > > Is there anything else I could try?
> > > >
> > > > I tested the same openSuSE version with a non-Xen 64 bit kernel, and
> > > > it doesn't work either.
> > > >
> > > > And I tried with this:
> > > >   Driver: alsa-driver-20090704.tar.bz2
> > > >   Distribution: Kubuntu Karmic Alpha-2
> > > >   Kernel: 2.6.30  (32 Bit)
> > > >
> > > > Under the latter setup the X-Fi Titanium works (Simple 2 channel test
> > > > with speaker-test, audacity, amarok). :-))
> > >
> > > How many RAM do you have?
> > > Could you boot with the limited memory size?
> >
> > It is just 2GB. So I am not limited by the 32 bit barrier.
> >
> > So booting with "limited" memory size doesn't make sense, right?
>
> Supposedly.  Is it emu20k1 or emu20k2?

I checked it again: It is a 20k2 chip. 

/var/log/boot.msg says:
<7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi: chip 
20K2 model SB0880 (1102:0041) is found


http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium 
series [EMU20k2]".

  Christian

Testers wanted: New SB X-Fi driver

[Insaen]

I own a SB x-fi fatality incl. the midi input box witch i realy would
like to use for my bass guitar and use the record options, i run the
card on ubuntu 9.04 and its running well  but can't realy set the jack
system right for software like rosegarden or lmms or any other music
editing software. I know it's got something to do with my alsa config??
is there a forum about this toppick?Simon says have a nice day..2-;

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

On Wednesday 05 August 2009 23:21:53 Christian Esken wrote:

> > All in all, I can produce a working environment with recent 32 and 64 bit
> > kernels. This is good news.  :-)
> >
> > Below is the summary on the tested distributions.
> >
> >   Christian
> >
> >
> > So we got this:
> > Kubuntu Karmic Alpha-2 32 Bit, 2.6.30 (works)
> > Kubuntu Karmic Alpha-2 64 Bit, 2.6.30 (works)
> > SuSE 11.1 64 Bit,  2.6.27 (does not work)
> > SuSE 11.1 64 Bit,  2.6.27 XEN (does not work)
> > SuSE 11.2 Milestone3  64Bit, 2.6.30 (test canceled, due to unrelated
> > problems) => I'll see whether I can redo the SuSE11.2 tests, after doing
> > a bugreport at openSuSE.
OK, that last issue was solved, and I now redid the test:

SuSE 11.2 Milestone6 64Bit, 2.6.31-rc6   (works)

I succesfully tested all analog (5.1) channels, using: speaker-test -D 
surround51 -c 6

I used ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
driver-snapshot.tar.bz2 from 24.08.2009. I am just wondering, whether the new 
ALSA driver is it still planned for the 2.6.31 kernel?!?

  Christian

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 24 Aug 2009 21:43:20 +0200,
Christian Esken wrote:
> 
> On Wednesday 05 August 2009 23:21:53 Christian Esken wrote:
> 
> > > All in all, I can produce a working environment with recent 32 and 64 bit
> > > kernels. This is good news.  :-)
> > >
> > > Below is the summary on the tested distributions.
> > >
> > >   Christian
> > >
> > >
> > > So we got this:
> > > Kubuntu Karmic Alpha-2 32 Bit, 2.6.30 (works)
> > > Kubuntu Karmic Alpha-2 64 Bit, 2.6.30 (works)
> > > SuSE 11.1 64 Bit,  2.6.27 (does not work)
> > > SuSE 11.1 64 Bit,  2.6.27 XEN (does not work)
> > > SuSE 11.2 Milestone3  64Bit, 2.6.30 (test canceled, due to unrelated
> > > problems) => I'll see whether I can redo the SuSE11.2 tests, after doing
> > > a bugreport at openSuSE.
> OK, that last issue was solved, and I now redid the test:
> 
> SuSE 11.2 Milestone6 64Bit, 2.6.31-rc6   (works)
> 
> I succesfully tested all analog (5.1) channels, using: speaker-test -D 
> surround51 -c 6
> 
> I used ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> driver-snapshot.tar.bz2 from 24.08.2009. I am just wondering, whether the new 
> ALSA driver is it still planned for the 2.6.31 kernel?!?

2.6.31 already includes most of X-Fi patches.
And the recent openSUSE 11.2 kernels include all X-Fi patches :)


Takashi

Testers wanted: New SB X-Fi driver

[Frashman]

Hi Takashi,

first of all, thank you for developing this driver.
I tested it today. It works, so far.

But two annoying things. As you mentioned, I got problems, if the 
onboard sound modules are loaded. Then i get no sound out auf my xfi.
If I disable the loading of snd-hda-intel modules while booting, then it 
works.

The second problem is, that SIDE and SURROUND connectors are 
interchanged. I'm absolutly sure, it works fine under windows and the 
connector colors are also correct.

If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
(SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
i'm using speaker-test -c6


Here lspci:

$ lspci
00:00.0 Host bridge: ATI Technologies Inc RD780 Northbridge only dual 
slot PCI-e_GFX and HT1 K8 part
00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge 
(external gfx0 port A)
00:04.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port A)
00:0a.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port F)
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 
4850]
01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
02:00.0 Audio device: Creative Labs X-Fi Titanium series [EMU20k2] (rev 03)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:06.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
Capture (rev 11)
04:06.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture 
(rev 11)
04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 
IEEE-1394a-2000 Controller (PHY/Link)



Thank you so far,
Frashman

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Is there a new driver that was supposed to be referenced in this or
something?

My sb0670 still has the clicks and is unusable with this driver.

Thanks!

On Wed, 2009-07-15 at 12:55 +0200, Frashman wrote:

> Hi Takashi,
> 
> first of all, thank you for developing this driver.
> I tested it today. It works, so far.
> 
> But two annoying things. As you mentioned, I got problems, if the 
> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> If I disable the loading of snd-hda-intel modules while booting, then it 
> works.
> 
> The second problem is, that SIDE and SURROUND connectors are 
> interchanged. I'm absolutly sure, it works fine under windows and the 
> connector colors are also correct.
> 
> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> i'm using speaker-test -c6
> 
> 
> Here lspci:
> 
> $ lspci
> 00:00.0 Host bridge: ATI Technologies Inc RD780 Northbridge only dual 
> slot PCI-e_GFX and HT1 K8 part
> 00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge 
> (external gfx0 port A)
> 00:04.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
> express gpp port A)
> 00:0a.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
> express gpp port F)
> 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
> 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
> 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
> 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
> 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
> 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
> 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
> 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
> 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
> 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
> 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
> HyperTransport Technology Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
> Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
> DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
> Miscellaneous Control
> 01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 
> 4850]
> 01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
> 02:00.0 Audio device: Creative Labs X-Fi Titanium series [EMU20k2] (rev 03)
> 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
> 04:06.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
> Capture (rev 11)
> 04:06.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture 
> (rev 11)
> 04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 
> IEEE-1394a-2000 Controller (PHY/Link)
> 
> 
> 
> Thank you so far,
> Frashman
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 15 Jul 2009 12:55:23 +0200,
Frashman wrote:
> 
> Hi Takashi,
> 
> first of all, thank you for developing this driver.
> I tested it today. It works, so far.
> 
> But two annoying things. As you mentioned, I got problems, if the 
> onboard sound modules are loaded. Then i get no sound out auf my xfi.

It's likely the collision of PCI device ID.
Some X-Fi models support both HD-audio and emu20kx-native modes.  The
modes are switched by some magical sequence.

Anyway, please run alsa-info.sh with --no-upload option, and attach
the generated file.

> If I disable the loading of snd-hda-intel modules while booting, then it 
> works.
> 
> The second problem is, that SIDE and SURROUND connectors are 
> interchanged. I'm absolutly sure, it works fine under windows and the 
> connector colors are also correct.
> 
> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> i'm using speaker-test -c6

So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
are swapped when running with 8 channel mode?


Takashi

Re: Testers wanted: New SB X-Fi driver

[Frashman]

[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]



Takashi Iwai schrieb:
> At Wed, 15 Jul 2009 12:55:23 +0200,
> Frashman wrote:
>  
>> Hi Takashi,
>>
>> first of all, thank you for developing this driver.
>> I tested it today. It works, so far.
>>
>> But two annoying things. As you mentioned, I got problems, if the 
>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>>     
>
> It's likely the collision of PCI device ID.
> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> modes are switched by some magical sequence.
>
> Anyway, please run alsa-info.sh with --no-upload option, and attach
> the generated file.
>   
I let the kernel auto probe all sound modules and generated then the 
alsa-info.txt
It's attached.
>  
>> If I disable the loading of snd-hda-intel modules while booting, then 
>> it works.
>>
>> The second problem is, that SIDE and SURROUND connectors are 
>> interchanged. I'm absolutly sure, it works fine under windows and the 
>> connector colors are also correct.
>>
>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my 
>> REAR (SURROUND) Speakers, while nothing is coming out of my rear 
>> speakers, if i'm using speaker-test -c6
>>     
>
> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> are swapped when running with 8 channel mode?
>   
The REAR and SURROUND channels are swapped in 4, 6 and 8channel mode ... 
so they always swapped. (speaker-test)
AND because there are swapped in 6channel mode too .... there is nothing 
coming out of the rear channels, if I connect everything right. I double 
checked it with windows and with cable colors.


Sincerely,
Frashman
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>   

[-- Attachment #2: alsa-info.txt --]
[-- Type: text/plain, Size: 50875 bytes --]

upload=true&script=true&cardinfo=
!!################################
!!ALSA Information Script v 0.4.57
!!################################

!!Script ran on: Thu Jul 16 10:02:39 UTC 2009


!!Linux Distribution
!!------------------

Arch Linux \r (\n) (\l)


!!DMI Information
!!---------------

Manufacturer:      Gigabyte Technology Co., Ltd.
Product Name:      GA-MA790X-DS4


!!Kernel Information
!!------------------

Kernel release:    2.6.30-ARCH
Operating System:  GNU/Linux
Architecture:      x86_64
Processor:         AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
SMP Enabled:       Yes


!!ALSA Version
!!------------

Driver version:     1.0.20
Library version:    1.0.20
Utilities version:  1.0.20


!!Loaded ALSA modules
!!-------------------

snd_hda_intel
snd_ctxfi
snd_usb_audio
snd_hda_intel
snd_bt87x


!!Sound Servers on this system
!!----------------------------

ESound Daemon:
      Installed - Yes (/usr/bin/esd)
      Running - No

Jack:
      Installed - Yes (/usr/bin/jackd)
      Running - No


!!Soundcards recognised by ALSA
!!-----------------------------

 0 [SB             ]: HDA-Intel - HDA ATI SB
                      HDA ATI SB at 0xfe024000 irq 16
 1 [XFi            ]: SB-XFi - Creative X-Fi
                      Creative X-Fi 20K2 SB0880
 2 [U0x46d0x9a1    ]: USB-Audio - USB Device 0x46d:0x9a1
                      USB Device 0x46d:0x9a1 at usb-0000:00:13.5-3, high speed
 3 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfdffc000 irq 19
 4 [Bt878          ]: Bt87x - Brooktree Bt878
                      Brooktree Bt878 at 0xfdafe000, irq 20


!!PCI Soundcards installed in the system
!!--------------------------------------

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
02:00.0 Audio device: Creative Labs X-Fi Titanium series [EMU20k2] (rev 03)
04:06.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
04:06.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)


!!Advanced information - PCI Vendor/Device/Susbsystem ID's
!!--------------------------------------------------------

00:14.2 0403: 1002:4383
	Subsystem: 1458:a002
--
01:00.1 0403: 1002:aa30
	Subsystem: 1002:aa30
--
02:00.0 0403: 1102:000b (rev 03)
	Subsystem: 1102:0041


!!Loaded sound module options
!!--------------------------

!!Module: snd_hda_intel
	bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1
	enable : Y,Y,Y,Y,Y,Y,Y,Y
	enable_msi : 0
	id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	index : -1,-1,-1,-1,-1,-1,-1,-1
	model : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	patch : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	position_fix : 0,0,0,0,0,0,0,0
	power_save : 0
	power_save_controller : Y
	probe_mask : -1,-1,-1,-1,-1,-1,-1,-1
	probe_only : N,N,N,N,N,N,N,N
	single_cmd : N

!!Module: snd_ctxfi
	enable : Y,Y,Y,Y,Y,Y,Y,Y
	id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	index : -1,-1,-1,-1,-1,-1,-1,-1
	multiple : 2
	reference_rate : 48000
	use_system_timer : N

!!Module: snd_usb_audio
	async_unlink : Y
	device_setup : 0,0,0,0,0,0,0,0
	devpath : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	enable : Y,Y,Y,Y,Y,Y,Y,Y
	id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	ignore_ctl_error : N
	index : -1,-1,-1,-1,-1,-1,-1,-1
	nrpacks : 8
	pid : -1,-1,-1,-1,-1,-1,-1,-1
	vid : -1,-1,-1,-1,-1,-1,-1,-1

!!Module: snd_hda_intel
	bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1
	enable : Y,Y,Y,Y,Y,Y,Y,Y
	enable_msi : 0
	id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	index : -1,-1,-1,-1,-1,-1,-1,-1
	model : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	patch : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	position_fix : 0,0,0,0,0,0,0,0
	power_save : 0
	power_save_controller : Y
	probe_mask : -1,-1,-1,-1,-1,-1,-1,-1
	probe_only : N,N,N,N,N,N,N,N
	single_cmd : N

!!Module: snd_bt87x
	digital_rate : 0,0,0,0,0,0,0,0
	enable : Y,Y,Y,Y,Y,Y,Y,Y
	id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
	index : -2,-2,-2,-2,-2,-2,-2,-2
	load_all : N


!!HDA-Intel Codec information
!!---------------------------
--startcollapse--

Codec: Realtek ALC889A
Address: 3
Function Id: 0x1
Vendor Id: 0x10ec0885
Subsystem Id: 0x1458a002
Revision Id: 0x100101
No Modem Function Group found
Default PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x03 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x04 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x05 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x06 [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x5e0]: 44100 48000 88200 96000 192000
    bits [0x1e]: 16 20 24 32
    formats [0x1]: PCM
Node 0x07 [Audio Input] wcaps 0x10011b: Stereo Amp-In
  Amp-In caps: ofs=0x10, nsteps=0x2e, stepsize=0x03, mute=1
  Amp-In vals:  [0x1c 0x1c]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Connection: 1
     0x24
Node 0x08 [Audio Input] wcaps 0x10011b: Stereo Amp-In
  Amp-In caps: ofs=0x10, nsteps=0x2e, stepsize=0x03, mute=1
  Amp-In vals:  [0x80 0x80]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Connection: 1
     0x23
Node 0x09 [Audio Input] wcaps 0x10011b: Stereo Amp-In
  Amp-In caps: ofs=0x10, nsteps=0x2e, stepsize=0x03, mute=1
  Amp-In vals:  [0x80 0x80]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Connection: 1
     0x22
Node 0x0a [Audio Input] wcaps 0x100391: Stereo Digital
  Converter: stream=0, channel=0
  SDI-Select: 0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0x1e]: 16 20 24 32
    formats [0x1]: PCM
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x1f
Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x80 0x80] [0x97 0x97] [0x97 0x97] [0x80 0x80] [0x17 0x17] [0x97 0x97] [0x97 0x97] [0x97 0x97] [0x97 0x97] [0x97 0x97]
  Connection: 10
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17
Node 0x0c [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x00 0x00]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x28 0x28]
  Connection: 2
     0x02 0x0b
Node 0x0d [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x80 0x80] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x00 0x00]
  Connection: 2
     0x03 0x0b
Node 0x0e [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x80 0x80] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x00 0x00]
  Connection: 2
     0x04 0x0b
Node 0x0f [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x80 0x80] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x00 0x00]
  Connection: 2
     0x05 0x0b
Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x12 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0000373c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x01014410: [Jack] Line-Out at Ext Rear
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x40: OUT VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x15 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0000373c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x01011412: [Jack] Line-Out at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0x2
  Pin-ctls: 0x40: OUT VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c 0x0d* 0x0e 0x0f 0x26
Node 0x16 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0000003c: IN OUT HP Detect
  Pin Default 0x01016411: [Jack] Line-Out at Ext Rear
    Conn = 1/8, Color = Orange
    DefAssociation = 0x1, Sequence = 0x1
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c 0x0d 0x0e* 0x0f 0x26
Node 0x17 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0000003c: IN OUT HP Detect
  Pin Default 0x01012414: [Jack] Line-Out at Ext Rear
    Conn = 1/8, Color = Grey
    DefAssociation = 0x1, Sequence = 0x4
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c 0x0d 0x0e 0x0f* 0x26
Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x0000373c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x01a19c40: [Jack] Mic at Ext Rear
    Conn = 1/8, Color = Pink
    DefAssociation = 0x4, Sequence = 0x0
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x19 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x0000373c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x02a19c50: [Jack] Mic at Ext Front
    Conn = 1/8, Color = Pink
    DefAssociation = 0x5, Sequence = 0x0
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x0000373c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x0181344f: [Jack] Line-In at Ext Rear
    Conn = 1/8, Color = Blue
    DefAssociation = 0x4, Sequence = 0xf
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1b [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0000373c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x02214c20: [Jack] Headphone at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x2, Sequence = 0x0
  Pin-ctls: 0xc0: OUT HP VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1c [Pin Complex] wcaps 0x400001: Stereo
  Pincap 0x00000020: IN
  Pin Default 0x593301f0: [N/A] CD at Int ATAPI
    Conn = ATAPI, Color = Unknown
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
Node 0x1d [Pin Complex] wcaps 0x400000: Mono
  Pincap 0x00000020: IN
  Pin Default 0x4005e601: [N/A] Line-Out at Ext N/A
    Conn = Optical, Color = White
    DefAssociation = 0x0, Sequence = 0x1
  Pin-ctls: 0x20: IN
Node 0x1e [Pin Complex] wcaps 0x400300: Mono Digital
  Pincap 0x00000010: OUT
  Pin Default 0x014b6130: [Jack] SPDIF-Out at Ext Rear
    Conn = Comb, Color = Orange
    DefAssociation = 0x3, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Connection: 1
     0x06
Node 0x1f [Pin Complex] wcaps 0x400200: Mono Digital
  Pincap 0x00000020: IN
  Pin Default 0x01cb7160: [Jack] SPDIF-In at Ext Rear
    Conn = Comb, Color = Yellow
    DefAssociation = 0x6, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono
  Processing caps: benign=0, ncoeff=17
  Processing Coefficient: 0x86a0
  Coefficient Index: 0x03
Node 0x21 [Volume Knob Widget] wcaps 0x600080: Mono
  Volume-Knob: delta=0, steps=32, direct=0, val=0
  Unsolicited: tag=00, enabled=0
  Connection: 0
Node 0x22 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 11
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b
Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 11
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b
Node 0x24 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 11
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b
Node 0x25 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x26 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x40 0x40]
  Connection: 2
     0x25 0x0b
Codec: ATI R6xx HDMI
Address: 0
Function Id: 0x1
Vendor Id: 0x1002aa01
Subsystem Id: 0x00aa0100
Revision Id: 0x100100
No Modem Function Group found
Default PCM:
    rates [0x70]: 32000 44100 48000
    bits [0x2]: 16
    formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x02 [Audio Output] wcaps 0x201: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x00000094: OUT Detect HDMI
  Pin Default 0x18560010: [Jack] Digital-Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x02
--endcollapse--


!!ALSA Device nodes
!!-----------------

crw-rw---- 1 root audio 116,   0 Jul 16 12:00 /dev/snd/controlC0
crw-rw---- 1 root audio 116,  32 Jul 16 12:00 /dev/snd/controlC1
crw-rw---- 1 root audio 116,  64 Jul 16 12:00 /dev/snd/controlC2
crw-rw---- 1 root audio 116,  96 Jul 16 12:00 /dev/snd/controlC3
crw-rw---- 1 root audio 116, 128 Jul 16 12:00 /dev/snd/controlC4
crw-rw---- 1 root audio 116,   7 Jul 16 12:00 /dev/snd/hwC0D3
crw-rw---- 1 root audio 116, 100 Jul 16 12:00 /dev/snd/hwC3D0
crw-rw---- 1 root audio 116,  24 Jul 16 12:00 /dev/snd/pcmC0D0c
crw-rw---- 1 root audio 116,  16 Jul 16 12:00 /dev/snd/pcmC0D0p
crw-rw---- 1 root audio 116,  25 Jul 16 12:00 /dev/snd/pcmC0D1c
crw-rw---- 1 root audio 116,  17 Jul 16 12:00 /dev/snd/pcmC0D1p
crw-rw---- 1 root audio 116,  26 Jul 16 12:00 /dev/snd/pcmC0D2c
crw-rw---- 1 root audio 116,  56 Jul 16 12:00 /dev/snd/pcmC1D0c
crw-rw---- 1 root audio 116,  48 Jul 16 12:00 /dev/snd/pcmC1D0p
crw-rw---- 1 root audio 116,  49 Jul 16 12:00 /dev/snd/pcmC1D1p
crw-rw---- 1 root audio 116,  50 Jul 16 12:00 /dev/snd/pcmC1D2p
crw-rw---- 1 root audio 116,  51 Jul 16 12:00 /dev/snd/pcmC1D3p
crw-rw---- 1 root audio 116,  52 Jul 16 12:00 /dev/snd/pcmC1D4p
crw-rw---- 1 root audio 116,  88 Jul 16 12:00 /dev/snd/pcmC2D0c
crw-rw---- 1 root audio 116, 115 Jul 16 12:00 /dev/snd/pcmC3D3p
crw-rw---- 1 root audio 116, 152 Jul 16 12:00 /dev/snd/pcmC4D0c
crw-rw---- 1 root audio 116, 153 Jul 16 12:00 /dev/snd/pcmC4D1c
crw-rw---- 1 root audio 116,   1 Jul 16 12:00 /dev/snd/seq
crw-rw---- 1 root audio 116,  33 Jul 16 12:00 /dev/snd/timer


!!Aplay/Arecord output
!!------------

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC889A Analog [ALC889A Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC889A Digital [ALC889A Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 1: XFi [Creative X-Fi], device 1: ctxfi [Surround]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 1: XFi [Creative X-Fi], device 2: ctxfi [Center/LFE]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 1: XFi [Creative X-Fi], device 3: ctxfi [Side]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 1: XFi [Creative X-Fi], device 4: ctxfi [IEC958 Non-audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ARECORD

**** List of CAPTURE Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC889A Analog [ALC889A Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC889A Digital [ALC889A Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 2: ALC889A Analog [ALC889A Analog]
  Subdevices: 2/2
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
card 1: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: U0x46d0x9a1 [USB Device 0x46d:0x9a1], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 4: Bt878 [Brooktree Bt878], device 0: Bt87x Digital [Bt87x Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 4: Bt878 [Brooktree Bt878], device 1: Bt87x Analog [Bt87x Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

!!Amixer output
!!-------------

!!-------Mixer controls for card 0 [SB]

Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
  Mixer name	: 'Realtek ALC889A'
  Components	: 'HDA:10ec0885,1458a002,00100101'
  Controls      : 43
  Simple ctrls  : 24
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 64
  Mono: Playback 52 [81%] [-12.00dB] [on]
Simple mixer control 'Headphone',0
  Capabilities: pswitch
  Playback channels: Front Left - Front Right
  Mono:
  Front Left: Playback [on]
  Front Right: Playback [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Front',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 64
  Mono:
  Front Left: Playback 52 [81%] [-12.00dB] [on]
  Front Right: Playback 52 [81%] [-12.00dB] [on]
Simple mixer control 'Front Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 23 [74%] [0.00dB] [off]
  Front Right: Playback 23 [74%] [0.00dB] [off]
Simple mixer control 'Front Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%]
  Front Right: 0 [0%]
Simple mixer control 'Surround',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 64
  Mono:
  Front Left: Playback 0 [0%] [-64.00dB] [off]
  Front Right: Playback 0 [0%] [-64.00dB] [off]
Simple mixer control 'Center',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 64
  Mono: Playback 0 [0%] [-64.00dB] [off]
Simple mixer control 'LFE',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 64
  Mono: Playback 0 [0%] [-64.00dB] [off]
Simple mixer control 'Side',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 64
  Mono:
  Front Left: Playback 0 [0%] [-64.00dB] [off]
  Front Right: Playback 0 [0%] [-64.00dB] [off]
Simple mixer control 'Line',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 23 [74%] [0.00dB] [off]
  Front Right: Playback 23 [74%] [0.00dB] [off]
Simple mixer control 'CD',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 23 [74%] [0.00dB] [on]
  Front Right: Playback 23 [74%] [0.00dB] [on]
Simple mixer control 'Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-34.50dB] [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%]
  Front Right: 0 [0%]
Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined cswitch cswitch-joined
  Playback channels: Mono
  Capture channels: Mono
  Mono: Playback [off] Capture [off]
Simple mixer control 'IEC958 Default PCM',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 46
  Front Left: Capture 28 [61%] [12.00dB] [on]
  Front Right: Capture 28 [61%] [12.00dB] [on]
Simple mixer control 'Capture',1
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 46
  Front Left: Capture 0 [0%] [-16.00dB] [off]
  Front Right: Capture 0 [0%] [-16.00dB] [off]
Simple mixer control 'Capture',2
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 46
  Front Left: Capture 0 [0%] [-16.00dB] [off]
  Front Right: Capture 0 [0%] [-16.00dB] [off]
Simple mixer control 'Beep',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 23 [74%] [0.00dB] [off]
  Front Right: Playback 23 [74%] [0.00dB] [off]
Simple mixer control 'Channel Mode',0
  Capabilities: enum
  Items: '6ch' '8ch'
  Item0: '6ch'
Simple mixer control 'Input Source',0
  Capabilities: cenum
  Items: 'Mic' 'Front Mic' 'Line' 'CD'
  Item0: 'Mic'
Simple mixer control 'Input Source',1
  Capabilities: cenum
  Items: 'Mic' 'Front Mic' 'Line' 'CD'
  Item0: 'Mic'
Simple mixer control 'Input Source',2
  Capabilities: cenum
  Items: 'Mic' 'Front Mic' 'Line' 'CD'
  Item0: 'Mic'

!!-------Mixer controls for card 1 [XFi]

Card hw:1 'XFi'/'Creative X-Fi 20K2 SB0880'
  Mixer name	: '20K2'
  Components	: ''
  Controls      : 29
  Simple ctrls  : 10
Simple mixer control 'Master',0
  Capabilities: pvolume cvolume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 256 Capture 0 - 256
  Front Left: Playback 173 [68%] [-20.75dB] Capture 256 [100%] [0.00dB]
  Front Right: Playback 173 [68%] [-20.75dB] Capture 256 [100%] [0.00dB]
Simple mixer control 'PCM',0
  Capabilities: pvolume cvolume cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 256 Capture 0 - 256
  Front Left: Playback 256 [100%] [0.00dB] Capture 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] Capture 256 [100%] [0.00dB] [on]
Simple mixer control 'Front',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 256
  Mono:
  Front Left: Playback 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] [on]
Simple mixer control 'Surround',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 256
  Mono:
  Front Left: Playback 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] [on]
Simple mixer control 'Center/LFE',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 256
  Mono:
  Front Left: Playback 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] [on]
Simple mixer control 'Side',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 256
  Mono:
  Front Left: Playback 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] [on]
Simple mixer control 'Line-in',0
  Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 256 Capture 0 - 256
  Front Left: Playback 256 [100%] [0.00dB] [on] Capture 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] [on] Capture 256 [100%] [0.00dB] [on]
Simple mixer control 'Mic',0
  Capabilities: pvolume cvolume cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 256 Capture 0 - 256
  Front Left: Playback 256 [100%] [0.00dB] Capture 256 [100%] [0.00dB] [off]
  Front Right: Playback 256 [100%] [0.00dB] Capture 256 [100%] [0.00dB] [off]
Simple mixer control 'S/PDIF-in',0
  Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 256 Capture 0 - 256
  Front Left: Playback 256 [100%] [0.00dB] [off] Capture 256 [100%] [0.00dB] [on]
  Front Right: Playback 256 [100%] [0.00dB] [off] Capture 256 [100%] [0.00dB] [on]
Simple mixer control 'S/PDIF-out',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 256
  Mono:
  Front Left: Playback 256 [100%] [0.00dB] [off]
  Front Right: Playback 256 [100%] [0.00dB] [off]

!!-------Mixer controls for card 2 [U0x46d0x9a1]

Card hw:2 'U0x46d0x9a1'/'USB Device 0x46d:0x9a1 at usb-0000:00:13.5-3, high speed'
  Mixer name	: 'USB Mixer'
  Components	: 'USB046d:09a1'
  Controls      : 2
  Simple ctrls  : 1
Simple mixer control 'Mic',0
  Capabilities: cvolume cvolume-joined cswitch cswitch-joined
  Capture channels: Mono
  Limits: Capture 0 - 3072
  Mono: Capture 1536 [50%] [on]

!!-------Mixer controls for card 3 [HDMI]

Card hw:3 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
  Mixer name	: 'ATI R6xx HDMI'
  Components	: 'HDA:1002aa01,00aa0100,00100100'
  Controls      : 4
  Simple ctrls  : 1
Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]

!!-------Mixer controls for card 4 [Bt878]

Card hw:4 'Bt878'/'Brooktree Bt878 at 0xfdafe000, irq 20'
  Mixer name	: 'Bt87x'
  Components	: ''
  Controls      : 3
  Simple ctrls  : 5
Simple mixer control 'FM',0
  Capabilities: cswitch cswitch-joined cswitch-exclusive
  Capture exclusive group: 0
  Capture channels: Mono
  Mono: Capture [off]
Simple mixer control 'Mic/Line',0
  Capabilities: cswitch cswitch-joined cswitch-exclusive
  Capture exclusive group: 0
  Capture channels: Mono
  Mono: Capture [off]
Simple mixer control 'Capture',0
  Capabilities: cvolume cvolume-joined
  Capture channels: Mono
  Limits: Capture 0 - 15
  Mono: Capture 12 [80%]
Simple mixer control 'Capture Boost',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'TV Tuner',0
  Capabilities: cswitch cswitch-joined cswitch-exclusive
  Capture exclusive group: 0
  Capture channels: Mono
  Mono: Capture [on]


!!Alsactl output
!!-------------

--startcollapse--
state.SB {
	control.1 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Front Playback Volume'
		value.0 52
		value.1 52
	}
	control.2 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Front Playback Switch'
		value.0 true
		value.1 true
	}
	control.3 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Surround Playback Volume'
		value.0 0
		value.1 0
	}
	control.4 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Surround Playback Switch'
		value.0 false
		value.1 false
	}
	control.5 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 1
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Center Playback Volume'
		value 0
	}
	control.6 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 1
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'LFE Playback Volume'
		value 0
	}
	control.7 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Center Playback Switch'
		value false
	}
	control.8 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'LFE Playback Switch'
		value false
	}
	control.9 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Side Playback Volume'
		value.0 0
		value.1 0
	}
	control.10 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Side Playback Switch'
		value.0 false
		value.1 false
	}
	control.11 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Headphone Playback Switch'
		value.0 true
		value.1 true
	}
	control.12 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'CD Playback Volume'
		value.0 23
		value.1 23
	}
	control.13 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'CD Playback Switch'
		value.0 true
		value.1 true
	}
	control.14 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'Line Playback Volume'
		value.0 23
		value.1 23
	}
	control.15 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Line Playback Switch'
		value.0 false
		value.1 false
	}
	control.16 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'Mic Playback Volume'
		value.0 0
		value.1 0
	}
	control.17 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 3'
		comment.dbmin 0
		comment.dbmax 3000
		iface MIXER
		name 'Mic Boost'
		value.0 0
		value.1 0
	}
	control.18 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Mic Playback Switch'
		value.0 false
		value.1 false
	}
	control.19 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'Front Mic Playback Volume'
		value.0 23
		value.1 23
	}
	control.20 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 3'
		comment.dbmin 0
		comment.dbmax 3000
		iface MIXER
		name 'Front Mic Boost'
		value.0 0
		value.1 0
	}
	control.21 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Front Mic Playback Switch'
		value.0 false
		value.1 false
	}
	control.22 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 '6ch'
		comment.item.1 '8ch'
		iface MIXER
		name 'Channel Mode'
		value '6ch'
	}
	control.23 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Capture Switch'
		value.0 true
		value.1 true
	}
	control.24 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Capture Switch'
		index 1
		value.0 false
		value.1 false
	}
	control.25 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Capture Switch'
		index 2
		value.0 false
		value.1 false
	}
	control.26 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 46'
		comment.dbmin -1600
		comment.dbmax 3000
		iface MIXER
		name 'Capture Volume'
		value.0 28
		value.1 28
	}
	control.27 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 46'
		comment.dbmin -1600
		comment.dbmax 3000
		iface MIXER
		name 'Capture Volume'
		index 1
		value.0 0
		value.1 0
	}
	control.28 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 46'
		comment.dbmin -1600
		comment.dbmax 3000
		iface MIXER
		name 'Capture Volume'
		index 2
		value.0 0
		value.1 0
	}
	control.29 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 Mic
		comment.item.1 'Front Mic'
		comment.item.2 Line
		comment.item.3 CD
		iface MIXER
		name 'Input Source'
		value Mic
	}
	control.30 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 Mic
		comment.item.1 'Front Mic'
		comment.item.2 Line
		comment.item.3 CD
		iface MIXER
		name 'Input Source'
		index 1
		value Mic
	}
	control.31 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 Mic
		comment.item.1 'Front Mic'
		comment.item.2 Line
		comment.item.3 CD
		iface MIXER
		name 'Input Source'
		index 2
		value Mic
	}
	control.32 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Con Mask'
		value '0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.33 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		value '0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.34 {
		comment.access 'read write'
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Default'
		value '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.35 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Switch'
		value false
	}
	control.36 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'IEC958 Default PCM Playback Switch'
		value true
	}
	control.37 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'IEC958 Capture Switch'
		value false
	}
	control.38 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Capture Default'
		value '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.39 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'Beep Playback Volume'
		value.0 23
		value.1 23
	}
	control.40 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Beep Playback Switch'
		value.0 false
		value.1 false
	}
	control.41 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 1
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Master Playback Volume'
		value 52
	}
	control.42 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Master Playback Switch'
		value true
	}
	control.43 {
		comment.access 'read write user'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 255'
		comment.tlv '0000000100000008ffffec1400000014'
		comment.dbmin -5100
		comment.dbmax 0
		iface MIXER
		name 'PCM Playback Volume'
		value.0 255
		value.1 255
	}
}
state.XFi {
	control.1 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Master Playback Volume'
		value.0 173
		value.1 173
	}
	control.2 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'PCM Playback Volume'
		value.0 256
		value.1 256
	}
	control.3 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Line-in Playback Volume'
		value.0 256
		value.1 256
	}
	control.4 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Mic Playback Volume'
		value.0 256
		value.1 256
	}
	control.5 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'S/PDIF-in Playback Volume'
		value.0 256
		value.1 256
	}
	control.6 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'S/PDIF-out Playback Volume'
		value.0 256
		value.1 256
	}
	control.7 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Front Playback Volume'
		value.0 256
		value.1 256
	}
	control.8 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Surround Playback Volume'
		value.0 256
		value.1 256
	}
	control.9 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Center/LFE Playback Volume'
		value.0 256
		value.1 256
	}
	control.10 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Side Playback Volume'
		value.0 256
		value.1 256
	}
	control.11 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Master Capture Volume'
		value.0 256
		value.1 256
	}
	control.12 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'PCM Capture Volume'
		value.0 256
		value.1 256
	}
	control.13 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Line-in Capture Volume'
		value.0 256
		value.1 256
	}
	control.14 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Mic Capture Volume'
		value.0 256
		value.1 256
	}
	control.15 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 256'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'S/PDIF-in Capture Volume'
		value.0 256
		value.1 256
	}
	control.16 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'PCM Capture Switch'
		value true
	}
	control.17 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Line-in Capture Switch'
		value true
	}
	control.18 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Mic Capture Switch'
		value false
	}
	control.19 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'S/PDIF-in Capture Switch'
		value true
	}
	control.20 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Line-in Playback Switch'
		value true
	}
	control.21 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'S/PDIF-out Playback Switch'
		value false
	}
	control.22 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'S/PDIF-in Playback Switch'
		value false
	}
	control.23 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Front Playback Switch'
		value true
	}
	control.24 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Surround Playback Switch'
		value true
	}
	control.25 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Center/LFE Playback Switch'
		value true
	}
	control.26 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Side Playback Switch'
		value true
	}
	control.27 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface PCM
		device 4
		name 'IEC958 Playback Mask'
		value ffffffff00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
	}
	control.28 {
		comment.access 'read write'
		comment.type IEC958
		comment.count 1
		iface PCM
		device 4
		name 'IEC958 Playback Default'
		value '0082000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.29 {
		comment.access 'read write'
		comment.type IEC958
		comment.count 1
		iface PCM
		device 4
		name 'IEC958 Playback PCM Stream'
		value '0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
}
state.U0x46d0x9a1 {
	control.1 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Mic Capture Switch'
		value true
	}
	control.2 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 1
		comment.range '0 - 3072'
		iface MIXER
		name 'Mic Capture Volume'
		value 1536
	}
}
state.HDMI {
	control.1 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Con Mask'
		value '0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.2 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		value '0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.3 {
		comment.access 'read write'
		comment.type IEC958
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Default'
		value '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.4 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'IEC958 Playback Switch'
		value false
	}
}
state.Bt878 {
	control.1 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 1
		comment.range '0 - 15'
		iface MIXER
		name 'Capture Volume'
		value 12
	}
	control.2 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Capture Boost'
		value false
	}
	control.3 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 'TV Tuner'
		comment.item.1 FM
		comment.item.2 Mic/Line
		iface MIXER
		name 'Capture Source'
		value 'TV Tuner'
	}
}
--endcollapse--


!!All Loaded Modules
!!------------------

Module
radeon
drm
ipt_REJECT
xt_tcpudp
nf_conntrack_ipv4
nf_defrag_ipv4
xt_state
nf_conntrack
iptable_filter
ip_tables
x_tables
ipv6
joydev
hid_cherry
usbhid
hid
msp3400
usb_storage
snd_seq_dummy
tuner_simple
snd_seq_oss
tuner_types
snd_hda_codec_atihdmi
snd_seq_midi_event
snd_seq
snd_hda_codec_realtek
tuner
snd_pcm_oss
snd_usb_audio
snd_usb_lib
snd_rawmidi
snd_seq_device
uvcvideo
snd_bt87x
snd_ctxfi
snd_hda_intel
snd_hda_codec
bttv
snd_mixer_oss
ir_common
i2c_algo_bit
snd_hwdep
snd_pcm
snd_timer
snd
ohci1394
v4l2_common
videodev
v4l1_compat
v4l2_compat_ioctl32
videobuf_dma_sg
videobuf_core
btcx_risc
i2c_piix4
pcspkr
soundcore
ieee1394
tveeprom
serio_raw
k8temp
i2c_core
sg
ohci_hcd
ehci_hcd
snd_page_alloc
r8169
mii
evdev
thermal
fan
button
battery
ac
usblp
usbcore
fuse
cpufreq_powersave
cpufreq_ondemand
powernow_k8
freq_table
processor
rtc_cmos
rtc_core
rtc_lib
xfs
exportfs
sr_mod
sd_mod
cdrom
pata_acpi
ahci
pata_atiixp
ata_generic
libata
scsi_mod


!!Sysfs Files
!!-----------

/sys/class/sound/hwC0D3/init_pin_configs:
0x14 0x01014410
0x15 0x01011412
0x16 0x01016411
0x17 0x01012414
0x18 0x01a19c40
0x19 0x02a19c50
0x1a 0x0181344f
0x1b 0x02214c20
0x1c 0x593301f0
0x1d 0x4005e601
0x1e 0x014b6130
0x1f 0x01cb7160

/sys/class/sound/hwC0D3/driver_pin_configs:

/sys/class/sound/hwC0D3/user_pin_configs:

/sys/class/sound/hwC0D3/init_verbs:

/sys/class/sound/hwC3D0/init_pin_configs:
0x03 0x18560010

/sys/class/sound/hwC3D0/driver_pin_configs:

/sys/class/sound/hwC3D0/user_pin_configs:

/sys/class/sound/hwC3D0/init_verbs:



[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Frank]

Oh sorry ... I mean ... SIDE and SURROUND (==REAR) are swapped!

Frashman schrieb:
>
>
> Takashi Iwai schrieb:
>> At Wed, 15 Jul 2009 12:55:23 +0200,
>> Frashman wrote:
>>  
>>> Hi Takashi,
>>>
>>> first of all, thank you for developing this driver.
>>> I tested it today. It works, so far.
>>>
>>> But two annoying things. As you mentioned, I got problems, if the 
>>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>>>     
>>
>> It's likely the collision of PCI device ID.
>> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>> modes are switched by some magical sequence.
>>
>> Anyway, please run alsa-info.sh with --no-upload option, and attach
>> the generated file.
>>   
> I let the kernel auto probe all sound modules and generated then the 
> alsa-info.txt
> It's attached.
>>  
>>> If I disable the loading of snd-hda-intel modules while booting, 
>>> then it works.
>>>
>>> The second problem is, that SIDE and SURROUND connectors are 
>>> interchanged. I'm absolutly sure, it works fine under windows and 
>>> the connector colors are also correct.
>>>
>>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my 
>>> REAR (SURROUND) Speakers, while nothing is coming out of my rear 
>>> speakers, if i'm using speaker-test -c6
>>>     
>>
>> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>> are swapped when running with 8 channel mode?
>>   
> The REAR and SURROUND channels are swapped in 4, 6 and 8channel mode 
> ... so they always swapped. (speaker-test)
> AND because there are swapped in 6channel mode too .... there is 
> nothing coming out of the rear channels, if I connect everything 
> right. I double checked it with windows and with cable colors.
>
>
> Sincerely,
> Frashman
>> Takashi
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Frank Roth]

I wrote the patch on my own ... *happy*
it works now ;-)

how to upload?


Greetings,
Frank




Frank schrieb:
> Oh sorry ... I mean ... SIDE and SURROUND (==REAR) are swapped!
>
> Frashman schrieb:
>   
>> Takashi Iwai schrieb:
>>     
>>> At Wed, 15 Jul 2009 12:55:23 +0200,
>>> Frashman wrote:
>>>  
>>>       
>>>> Hi Takashi,
>>>>
>>>> first of all, thank you for developing this driver.
>>>> I tested it today. It works, so far.
>>>>
>>>> But two annoying things. As you mentioned, I got problems, if the 
>>>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>>>>     
>>>>         
>>> It's likely the collision of PCI device ID.
>>> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>>> modes are switched by some magical sequence.
>>>
>>> Anyway, please run alsa-info.sh with --no-upload option, and attach
>>> the generated file.
>>>   
>>>       
>> I let the kernel auto probe all sound modules and generated then the 
>> alsa-info.txt
>> It's attached.
>>     
>>>  
>>>       
>>>> If I disable the loading of snd-hda-intel modules while booting, 
>>>> then it works.
>>>>
>>>> The second problem is, that SIDE and SURROUND connectors are 
>>>> interchanged. I'm absolutly sure, it works fine under windows and 
>>>> the connector colors are also correct.
>>>>
>>>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my 
>>>> REAR (SURROUND) Speakers, while nothing is coming out of my rear 
>>>> speakers, if i'm using speaker-test -c6
>>>>     
>>>>         
>>> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>>> are swapped when running with 8 channel mode?
>>>   
>>>       
>> The REAR and SURROUND channels are swapped in 4, 6 and 8channel mode 
>> ... so they always swapped. (speaker-test)
>> AND because there are swapped in 6channel mode too .... there is 
>> nothing coming out of the rear channels, if I connect everything 
>> right. I double checked it with windows and with cable colors.
>>
>>
>> Sincerely,
>> Frashman
>>     
>>> Takashi
>>> _______________________________________________
>>> Alsa-devel mailing list
>>> Alsa-devel@alsa-project.org
>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>   
>>>       
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>     
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>   

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 20 Jul 2009 14:33:37 +0200,
Frank Roth wrote:
> 
> I wrote the patch on my own ... *happy*
> it works now ;-)
> 
> how to upload?

Please post your patch to ML (and Cc to me).
Give a proper changelog and your sign-off together.
See $LINUX/Documentation/SubmittingPatches for details.


thanks,

Takashi

> 
> 
> Greetings,
> Frank
> 
> 
> 
> 
> Frank schrieb:
> > Oh sorry ... I mean ... SIDE and SURROUND (==REAR) are swapped!
> >
> > Frashman schrieb:
> >   
> >> Takashi Iwai schrieb:
> >>     
> >>> At Wed, 15 Jul 2009 12:55:23 +0200,
> >>> Frashman wrote:
> >>>  
> >>>       
> >>>> Hi Takashi,
> >>>>
> >>>> first of all, thank you for developing this driver.
> >>>> I tested it today. It works, so far.
> >>>>
> >>>> But two annoying things. As you mentioned, I got problems, if the 
> >>>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >>>>     
> >>>>         
> >>> It's likely the collision of PCI device ID.
> >>> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >>> modes are switched by some magical sequence.
> >>>
> >>> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >>> the generated file.
> >>>   
> >>>       
> >> I let the kernel auto probe all sound modules and generated then the 
> >> alsa-info.txt
> >> It's attached.
> >>     
> >>>  
> >>>       
> >>>> If I disable the loading of snd-hda-intel modules while booting, 
> >>>> then it works.
> >>>>
> >>>> The second problem is, that SIDE and SURROUND connectors are 
> >>>> interchanged. I'm absolutly sure, it works fine under windows and 
> >>>> the connector colors are also correct.
> >>>>
> >>>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my 
> >>>> REAR (SURROUND) Speakers, while nothing is coming out of my rear 
> >>>> speakers, if i'm using speaker-test -c6
> >>>>     
> >>>>         
> >>> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >>> are swapped when running with 8 channel mode?
> >>>   
> >>>       
> >> The REAR and SURROUND channels are swapped in 4, 6 and 8channel mode 
> >> ... so they always swapped. (speaker-test)
> >> AND because there are swapped in 6channel mode too .... there is 
> >> nothing coming out of the rear channels, if I connect everything 
> >> right. I double checked it with windows and with cable colors.
> >>
> >>
> >> Sincerely,
> >> Frashman
> >>     
> >>> Takashi
> >>> _______________________________________________
> >>> Alsa-devel mailing list
> >>> Alsa-devel@alsa-project.org
> >>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>>   
> >>>       
> >> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel@alsa-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>     
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >   
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Takashi, please, what must I do to get your xfi driver to stop clicking?

On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:

> At Wed, 15 Jul 2009 12:55:23 +0200,
> Frashman wrote:
> > 
> > Hi Takashi,
> > 
> > first of all, thank you for developing this driver.
> > I tested it today. It works, so far.
> > 
> > But two annoying things. As you mentioned, I got problems, if the 
> > onboard sound modules are loaded. Then i get no sound out auf my xfi.
> 
> It's likely the collision of PCI device ID.
> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> modes are switched by some magical sequence.
> 
> Anyway, please run alsa-info.sh with --no-upload option, and attach
> the generated file.
> 
> > If I disable the loading of snd-hda-intel modules while booting, then it 
> > works.
> > 
> > The second problem is, that SIDE and SURROUND connectors are 
> > interchanged. I'm absolutly sure, it works fine under windows and the 
> > connector colors are also correct.
> > 
> > If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> > (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> > i'm using speaker-test -c6
> 
> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> are swapped when running with 8 channel mode?
> 
> 
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[John L. Utz III]

Debug the problem, write code that fixes it and then send in a patch.
That's why this is the alsa *developers* mailing list.

Ted T. Logan wrote:
> Takashi, please, what must I do to get your xfi driver to stop clicking?
> 
> On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> 
>> At Wed, 15 Jul 2009 12:55:23 +0200,
>> Frashman wrote:
>>> Hi Takashi,
>>>
>>> first of all, thank you for developing this driver.
>>> I tested it today. It works, so far.
>>>
>>> But two annoying things. As you mentioned, I got problems, if the 
>>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>> It's likely the collision of PCI device ID.
>> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>> modes are switched by some magical sequence.
>>
>> Anyway, please run alsa-info.sh with --no-upload option, and attach
>> the generated file.
>>
>>> If I disable the loading of snd-hda-intel modules while booting, then it 
>>> works.
>>>
>>> The second problem is, that SIDE and SURROUND connectors are 
>>> interchanged. I'm absolutly sure, it works fine under windows and the 
>>> connector colors are also correct.
>>>
>>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
>>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
>>> i'm using speaker-test -c6
>> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>> are swapped when running with 8 channel mode?
>>
>>
>> Takashi
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Maybe you haven't been following the thread.  I've been trying to debug
the problem.  As I mentioned to Takashi, there's not a point where it
broke, it never worked with this driver.
There have always been clicks.


However, it does not have clicks with the following driver:
XFiDrv_Linux_Public_US_1.00.tar.gz

Sending out condescending messages like this after I was responding to
the "testers wanted" mailer which said all cards should be supported now
is completely unproductive.

On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:

> Debug the problem, write code that fixes it and then send in a patch.
> That's why this is the alsa *developers* mailing list.
> 
> Ted T. Logan wrote:
> > Takashi, please, what must I do to get your xfi driver to stop clicking?
> > 
> > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> > 
> >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >> Frashman wrote:
> >>> Hi Takashi,
> >>>
> >>> first of all, thank you for developing this driver.
> >>> I tested it today. It works, so far.
> >>>
> >>> But two annoying things. As you mentioned, I got problems, if the 
> >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >> It's likely the collision of PCI device ID.
> >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >> modes are switched by some magical sequence.
> >>
> >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >> the generated file.
> >>
> >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >>> works.
> >>>
> >>> The second problem is, that SIDE and SURROUND connectors are 
> >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >>> connector colors are also correct.
> >>>
> >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >>> i'm using speaker-test -c6
> >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >> are swapped when running with 8 channel mode?
> >>
> >>
> >> Takashi
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel@alsa-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sun, 19 Jul 2009 10:35:21 -0500,
Ted T. Logan wrote:
> 
> Maybe you haven't been following the thread.  I've been trying to debug the
> problem.  As I mentioned to Takashi, there's not a point where it broke, it
> never worked with this driver.
> There have always been clicks.
> 
> However, it does not have clicks with the following driver:
> XFiDrv_Linux_Public_US_1.00.tar.gz
> 
> Sending out condescending messages like this after I was responding to the
> "testers wanted" mailer which said all cards should be supported now is
> completely unproductive.

Well, the current situation is that I've got no other report but you
regarding the specific problem.  There is a known issue with openal,
accordingly, but not all apps.  So, this is very likely a different
issue.

Actually, it's still the phase to gather all information to know which
part exactly is problematic.  If you find any other guys that have the
exact same problem, let me know.  It would make easier to find out a
problem pattern, either for finding out the culprit or reproducing the
problem.

Or, you can do trial-and-error by comparing the driver above and the
current one (maybe the first committed version is easier to compare).
This can't be done without the real hardware, so it's actually up to
you how to fix the issue...


Takashi

> 
> On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> 
>     Debug the problem, write code that fixes it and then send in a patch.
>     That's why this is the alsa *developers* mailing list.
>     
>     Ted T. Logan wrote:
>     > Takashi, please, what must I do to get your xfi driver to stop clicking?
>     > 
>     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
>     > 
>     >> At Wed, 15 Jul 2009 12:55:23 +0200,
>     >> Frashman wrote:
>     >>> Hi Takashi,
>     >>>
>     >>> first of all, thank you for developing this driver.
>     >>> I tested it today. It works, so far.
>     >>>
>     >>> But two annoying things. As you mentioned, I got problems, if the 
>     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>     >> It's likely the collision of PCI device ID.
>     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>     >> modes are switched by some magical sequence.
>     >>
>     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
>     >> the generated file.
>     >>
>     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
>     >>> works.
>     >>>
>     >>> The second problem is, that SIDE and SURROUND connectors are 
>     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
>     >>> connector colors are also correct.
>     >>>
>     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
>     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
>     >>> i'm using speaker-test -c6
>     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>     >> are swapped when running with 8 channel mode?
>     >>
>     >>
>     >> Takashi
>     >> _______________________________________________
>     >> Alsa-devel mailing list
>     >> Alsa-devel@alsa-project.org
>     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     > _______________________________________________
>     > Alsa-devel mailing list
>     > Alsa-devel@alsa-project.org
>     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     > 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Thanks.

Basically the driver from creative, the old one, works without clicks:

XFiDrv_Linux_US-1.18.tar.gz
>From April, 2008

and this one works without clicks.

 XFiDrv_Linux_Public_US_1.00.tar.gz


lspci lists it as:
03:03.0 Multimedia audio controller: Creative Labs SB X-Fi

and in xp, it uses the same x-fi drivers as the others.

I have never been able to get any driver you released to work with it.

Can you tell me the first driver you had that you recommend I test it
with?

On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:

> At Sun, 19 Jul 2009 10:35:21 -0500,
> Ted T. Logan wrote:
> > 
> > Maybe you haven't been following the thread.  I've been trying to debug the
> > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> > never worked with this driver.
> > There have always been clicks.
> > 
> > However, it does not have clicks with the following driver:
> > XFiDrv_Linux_Public_US_1.00.tar.gz
> > 
> > Sending out condescending messages like this after I was responding to the
> > "testers wanted" mailer which said all cards should be supported now is
> > completely unproductive.
> 
> Well, the current situation is that I've got no other report but you
> regarding the specific problem.  There is a known issue with openal,
> accordingly, but not all apps.  So, this is very likely a different
> issue.
> 
> Actually, it's still the phase to gather all information to know which
> part exactly is problematic.  If you find any other guys that have the
> exact same problem, let me know.  It would make easier to find out a
> problem pattern, either for finding out the culprit or reproducing the
> problem.
> 
> Or, you can do trial-and-error by comparing the driver above and the
> current one (maybe the first committed version is easier to compare).
> This can't be done without the real hardware, so it's actually up to
> you how to fix the issue...
> 
> 
> Takashi
> 
> > 
> > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> > 
> >     Debug the problem, write code that fixes it and then send in a patch.
> >     That's why this is the alsa *developers* mailing list.
> >     
> >     Ted T. Logan wrote:
> >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     > 
> >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     > 
> >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >> Frashman wrote:
> >     >>> Hi Takashi,
> >     >>>
> >     >>> first of all, thank you for developing this driver.
> >     >>> I tested it today. It works, so far.
> >     >>>
> >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >> It's likely the collision of PCI device ID.
> >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >> modes are switched by some magical sequence.
> >     >>
> >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >> the generated file.
> >     >>
> >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >>> works.
> >     >>>
> >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >>> connector colors are also correct.
> >     >>>
> >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >>> i'm using speaker-test -c6
> >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >> are swapped when running with 8 channel mode?
> >     >>
> >     >>
> >     >> Takashi
> >     >> _______________________________________________
> >     >> Alsa-devel mailing list
> >     >> Alsa-devel@alsa-project.org
> >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     > _______________________________________________
> >     > Alsa-devel mailing list
> >     > Alsa-devel@alsa-project.org
> >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sun, 19 Jul 2009 19:38:59 -0500,
Ted T. Logan wrote:
> 
> Thanks.
> 
> Basically the driver from creative, the old one, works without clicks:
> 
> XFiDrv_Linux_US-1.18.tar.gz
> >From April, 2008

Where is it available?

> and this one works without clicks.
> 
> XFiDrv_Linux_Public_US_1.00.tar.gz

So, do both versions work on yours?
What are the differences between them?

> lspci lists it as:
> 03:03.0 Multimedia audio controller: Creative Labs SB X-Fi
> 
> and in xp, it uses the same x-fi drivers as the others.
> 
> I have never been able to get any driver you released to work with it.
> 
> Can you tell me the first driver you had that you recommend I test it with?

GIT is the easiest way.  For example, look at the page below:
   http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=history;f=sound/pci/ctxfi;h=91c958a7e171313fe68d728a3b4860287ad40aa7;hb=HEAD


Takashi

> On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> 
>     At Sun, 19 Jul 2009 10:35:21 -0500,
>     Ted T. Logan wrote:
>     > 
>     > Maybe you haven't been following the thread.  I've been trying to debug the
>     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
>     > never worked with this driver.
>     > There have always been clicks.
>     > 
>     > However, it does not have clicks with the following driver:
>     > XFiDrv_Linux_Public_US_1.00.tar.gz
>     > 
>     > Sending out condescending messages like this after I was responding to the
>     > "testers wanted" mailer which said all cards should be supported now is
>     > completely unproductive.
>     
>     Well, the current situation is that I've got no other report but you
>     regarding the specific problem.  There is a known issue with openal,
>     accordingly, but not all apps.  So, this is very likely a different
>     issue.
>     
>     Actually, it's still the phase to gather all information to know which
>     part exactly is problematic.  If you find any other guys that have the
>     exact same problem, let me know.  It would make easier to find out a
>     problem pattern, either for finding out the culprit or reproducing the
>     problem.
>     
>     Or, you can do trial-and-error by comparing the driver above and the
>     current one (maybe the first committed version is easier to compare).
>     This can't be done without the real hardware, so it's actually up to
>     you how to fix the issue...
> 
>     Takashi
>     
>     > 
>     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
>     > 
>     >     Debug the problem, write code that fixes it and then send in a patch.
>     >     That's why this is the alsa *developers* mailing list.
>     >     
>     >     Ted T. Logan wrote:
>     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
>     >     > 
>     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
>     >     > 
>     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
>     >     >> Frashman wrote:
>     >     >>> Hi Takashi,
>     >     >>>
>     >     >>> first of all, thank you for developing this driver.
>     >     >>> I tested it today. It works, so far.
>     >     >>>
>     >     >>> But two annoying things. As you mentioned, I got problems, if the 
>     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>     >     >> It's likely the collision of PCI device ID.
>     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>     >     >> modes are switched by some magical sequence.
>     >     >>
>     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
>     >     >> the generated file.
>     >     >>
>     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
>     >     >>> works.
>     >     >>>
>     >     >>> The second problem is, that SIDE and SURROUND connectors are 
>     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
>     >     >>> connector colors are also correct.
>     >     >>>
>     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
>     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
>     >     >>> i'm using speaker-test -c6
>     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>     >     >> are swapped when running with 8 channel mode?
>     >     >>
>     >     >>
>     >     >> Takashi
>     >     >> _______________________________________________
>     >     >> Alsa-devel mailing list
>     >     >> Alsa-devel@alsa-project.org
>     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     > _______________________________________________
>     >     > Alsa-devel mailing list
>     >     > Alsa-devel@alsa-project.org
>     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     > 
>     > 
>     > 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

http://opensource.creative.com/soundcard.html has 1.18


http://ccftp.creative.com/manualdn/Drivers/AVP/10792/0x0343D29A/XFiDrv_Linux_Public_US_1.00.tar.gz

I think the difference is the 1.00 is newer, but just listed at a
different location or something.

On Mon, 2009-07-20 at 07:37 +0200, Takashi Iwai wrote:

> At Sun, 19 Jul 2009 19:38:59 -0500,
> Ted T. Logan wrote:
> > 
> > Thanks.
> > 
> > Basically the driver from creative, the old one, works without clicks:
> > 
> > XFiDrv_Linux_US-1.18.tar.gz
> > >From April, 2008
> 
> Where is it available?
> 
> > and this one works without clicks.
> > 
> > 
> 
> So, do both versions work on yours?
> What are the differences between them?
> 
> > lspci lists it as:
> > 03:03.0 Multimedia audio controller: Creative Labs SB X-Fi
> > 
> > and in xp, it uses the same x-fi drivers as the others.
> > 
> > I have never been able to get any driver you released to work with it.
> > 
> > Can you tell me the first driver you had that you recommend I test it with?
> 
> GIT is the easiest way.  For example, look at the page below:
>    http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=history;f=sound/pci/ctxfi;h=91c958a7e171313fe68d728a3b4860287ad40aa7;hb=HEAD
> 
> 
> Takashi
> 
> > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> > 
> >     At Sun, 19 Jul 2009 10:35:21 -0500,
> >     Ted T. Logan wrote:
> >     > 
> >     > Maybe you haven't been following the thread.  I've been trying to debug the
> >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> >     > never worked with this driver.
> >     > There have always been clicks.
> >     > 
> >     > However, it does not have clicks with the following driver:
> >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     > 
> >     > Sending out condescending messages like this after I was responding to the
> >     > "testers wanted" mailer which said all cards should be supported now is
> >     > completely unproductive.
> >     
> >     Well, the current situation is that I've got no other report but you
> >     regarding the specific problem.  There is a known issue with openal,
> >     accordingly, but not all apps.  So, this is very likely a different
> >     issue.
> >     
> >     Actually, it's still the phase to gather all information to know which
> >     part exactly is problematic.  If you find any other guys that have the
> >     exact same problem, let me know.  It would make easier to find out a
> >     problem pattern, either for finding out the culprit or reproducing the
> >     problem.
> >     
> >     Or, you can do trial-and-error by comparing the driver above and the
> >     current one (maybe the first committed version is easier to compare).
> >     This can't be done without the real hardware, so it's actually up to
> >     you how to fix the issue...
> > 
> >     Takashi
> >     
> >     > 
> >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> >     > 
> >     >     Debug the problem, write code that fixes it and then send in a patch.
> >     >     That's why this is the alsa *developers* mailing list.
> >     >     
> >     >     Ted T. Logan wrote:
> >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     >     > 
> >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     >     > 
> >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >     >> Frashman wrote:
> >     >     >>> Hi Takashi,
> >     >     >>>
> >     >     >>> first of all, thank you for developing this driver.
> >     >     >>> I tested it today. It works, so far.
> >     >     >>>
> >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >     >> It's likely the collision of PCI device ID.
> >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >     >> modes are switched by some magical sequence.
> >     >     >>
> >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >     >> the generated file.
> >     >     >>
> >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >     >>> works.
> >     >     >>>
> >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >     >>> connector colors are also correct.
> >     >     >>>
> >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >     >>> i'm using speaker-test -c6
> >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >     >> are swapped when running with 8 channel mode?
> >     >     >>
> >     >     >>
> >     >     >> Takashi
> >     >     >> _______________________________________________
> >     >     >> Alsa-devel mailing list
> >     >     >> Alsa-devel@alsa-project.org
> >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > _______________________________________________
> >     >     > Alsa-devel mailing list
> >     >     > Alsa-devel@alsa-project.org
> >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > 
> >     > 
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Sorry,

Meant to mention the OSS Drivers from 4front from a while back also
worked without clicking.

On Mon, 2009-07-20 at 07:37 +0200, Takashi Iwai wrote:

> At Sun, 19 Jul 2009 19:38:59 -0500,
> Ted T. Logan wrote:
> > 
> > Thanks.
> > 
> > Basically the driver from creative, the old one, works without clicks:
> > 
> > XFiDrv_Linux_US-1.18.tar.gz
> > >From April, 2008
> 
> Where is it available?
> 
> > and this one works without clicks.
> > 
> > XFiDrv_Linux_Public_US_1.00.tar.gz
> 
> So, do both versions work on yours?
> What are the differences between them?
> 
> > lspci lists it as:
> > 03:03.0 Multimedia audio controller: Creative Labs SB X-Fi
> > 
> > and in xp, it uses the same x-fi drivers as the others.
> > 
> > I have never been able to get any driver you released to work with it.
> > 
> > Can you tell me the first driver you had that you recommend I test it with?
> 
> GIT is the easiest way.  For example, look at the page below:
>    http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=history;f=sound/pci/ctxfi;h=91c958a7e171313fe68d728a3b4860287ad40aa7;hb=HEAD
> 
> 
> Takashi
> 
> > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> > 
> >     At Sun, 19 Jul 2009 10:35:21 -0500,
> >     Ted T. Logan wrote:
> >     > 
> >     > Maybe you haven't been following the thread.  I've been trying to debug the
> >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> >     > never worked with this driver.
> >     > There have always been clicks.
> >     > 
> >     > However, it does not have clicks with the following driver:
> >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     > 
> >     > Sending out condescending messages like this after I was responding to the
> >     > "testers wanted" mailer which said all cards should be supported now is
> >     > completely unproductive.
> >     
> >     Well, the current situation is that I've got no other report but you
> >     regarding the specific problem.  There is a known issue with openal,
> >     accordingly, but not all apps.  So, this is very likely a different
> >     issue.
> >     
> >     Actually, it's still the phase to gather all information to know which
> >     part exactly is problematic.  If you find any other guys that have the
> >     exact same problem, let me know.  It would make easier to find out a
> >     problem pattern, either for finding out the culprit or reproducing the
> >     problem.
> >     
> >     Or, you can do trial-and-error by comparing the driver above and the
> >     current one (maybe the first committed version is easier to compare).
> >     This can't be done without the real hardware, so it's actually up to
> >     you how to fix the issue...
> > 
> >     Takashi
> >     
> >     > 
> >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> >     > 
> >     >     Debug the problem, write code that fixes it and then send in a patch.
> >     >     That's why this is the alsa *developers* mailing list.
> >     >     
> >     >     Ted T. Logan wrote:
> >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     >     > 
> >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     >     > 
> >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >     >> Frashman wrote:
> >     >     >>> Hi Takashi,
> >     >     >>>
> >     >     >>> first of all, thank you for developing this driver.
> >     >     >>> I tested it today. It works, so far.
> >     >     >>>
> >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >     >> It's likely the collision of PCI device ID.
> >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >     >> modes are switched by some magical sequence.
> >     >     >>
> >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >     >> the generated file.
> >     >     >>
> >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >     >>> works.
> >     >     >>>
> >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >     >>> connector colors are also correct.
> >     >     >>>
> >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >     >>> i'm using speaker-test -c6
> >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >     >> are swapped when running with 8 channel mode?
> >     >     >>
> >     >     >>
> >     >     >> Takashi
> >     >     >> _______________________________________________
> >     >     >> Alsa-devel mailing list
> >     >     >> Alsa-devel@alsa-project.org
> >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > _______________________________________________
> >     >     > Alsa-devel mailing list
> >     >     > Alsa-devel@alsa-project.org
> >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > 
> >     > 
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 20 Jul 2009 12:33:24 -0500,
Ted T. Logan wrote:
> 
> Sorry,
> 
> Meant to mention the OSS Drivers from 4front from a while back also worked
> without clicking.

Hm, did it really work even though your device is emu20k2?  
I thought their driver supported only emu20k1.  Maybe added later.

Anyway, you can try the latest snapshot, which now includes the native
timer support on emu20k2.  It was only for emu20k1 until today.


Takashi

> On Mon, 2009-07-20 at 07:37 +0200, Takashi Iwai wrote:
> 
>     At Sun, 19 Jul 2009 19:38:59 -0500,
>     Ted T. Logan wrote:
>     > 
>     > Thanks.
>     > 
>     > Basically the driver from creative, the old one, works without clicks:
>     > 
>     > XFiDrv_Linux_US-1.18.tar.gz
>     > >From April, 2008
>     
>     Where is it available?
>     
>     > and this one works without clicks.
>     > 
>     > XFiDrv_Linux_Public_US_1.00.tar.gz
>     
>     So, do both versions work on yours?
>     What are the differences between them?
>     
>     > lspci lists it as:
>     > 03:03.0 Multimedia audio controller: Creative Labs SB X-Fi
>     > 
>     > and in xp, it uses the same x-fi drivers as the others.
>     > 
>     > I have never been able to get any driver you released to work with it.
>     > 
>     > Can you tell me the first driver you had that you recommend I test it with?
>     
>     GIT is the easiest way.  For example, look at the page below:
>        http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=history;f=sound/pci/ctxfi;h=91c958a7e171313fe68d728a3b4860287ad40aa7;hb=HEAD
> 
>     Takashi
>     
>     > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
>     > 
>     >     At Sun, 19 Jul 2009 10:35:21 -0500,
>     >     Ted T. Logan wrote:
>     >     > 
>     >     > Maybe you haven't been following the thread.  I've been trying to debug the
>     >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
>     >     > never worked with this driver.
>     >     > There have always been clicks.
>     >     > 
>     >     > However, it does not have clicks with the following driver:
>     >     > XFiDrv_Linux_Public_US_1.00.tar.gz
>     >     > 
>     >     > Sending out condescending messages like this after I was responding to the
>     >     > "testers wanted" mailer which said all cards should be supported now is
>     >     > completely unproductive.
>     >     
>     >     Well, the current situation is that I've got no other report but you
>     >     regarding the specific problem.  There is a known issue with openal,
>     >     accordingly, but not all apps.  So, this is very likely a different
>     >     issue.
>     >     
>     >     Actually, it's still the phase to gather all information to know which
>     >     part exactly is problematic.  If you find any other guys that have the
>     >     exact same problem, let me know.  It would make easier to find out a
>     >     problem pattern, either for finding out the culprit or reproducing the
>     >     problem.
>     >     
>     >     Or, you can do trial-and-error by comparing the driver above and the
>     >     current one (maybe the first committed version is easier to compare).
>     >     This can't be done without the real hardware, so it's actually up to
>     >     you how to fix the issue...
>     > 
>     >     Takashi
>     >     
>     >     > 
>     >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
>     >     > 
>     >     >     Debug the problem, write code that fixes it and then send in a patch.
>     >     >     That's why this is the alsa *developers* mailing list.
>     >     >     
>     >     >     Ted T. Logan wrote:
>     >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
>     >     >     > 
>     >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
>     >     >     > 
>     >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
>     >     >     >> Frashman wrote:
>     >     >     >>> Hi Takashi,
>     >     >     >>>
>     >     >     >>> first of all, thank you for developing this driver.
>     >     >     >>> I tested it today. It works, so far.
>     >     >     >>>
>     >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
>     >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>     >     >     >> It's likely the collision of PCI device ID.
>     >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>     >     >     >> modes are switched by some magical sequence.
>     >     >     >>
>     >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
>     >     >     >> the generated file.
>     >     >     >>
>     >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
>     >     >     >>> works.
>     >     >     >>>
>     >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
>     >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
>     >     >     >>> connector colors are also correct.
>     >     >     >>>
>     >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
>     >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
>     >     >     >>> i'm using speaker-test -c6
>     >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>     >     >     >> are swapped when running with 8 channel mode?
>     >     >     >>
>     >     >     >>
>     >     >     >> Takashi
>     >     >     >> _______________________________________________
>     >     >     >> Alsa-devel mailing list
>     >     >     >> Alsa-devel@alsa-project.org
>     >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     >     > _______________________________________________
>     >     >     > Alsa-devel mailing list
>     >     >     > Alsa-devel@alsa-project.org
>     >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     >     > 
>     >     > 
>     >     > 
>     > 
>     > 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

upgraded to latest snapshot:

ftp://kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
just like a metronome:)

click
click
click
click
click
click
click
click




http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447626+1248160986695+28353475&threadId=1163389

that's the card I have.

On Mon, 2009-07-20 at 19:47 +0200, Takashi Iwai wrote:

> At Mon, 20 Jul 2009 12:33:24 -0500,
> Ted T. Logan wrote:
> > 
> > Sorry,
> > 
> > Meant to mention the OSS Drivers from 4front from a while back also worked
> > without clicking.
> 
> Hm, did it really work even though your device is emu20k2?  
> I thought their driver supported only emu20k1.  Maybe added later.
> 
> Anyway, you can try the latest snapshot, which now includes the native
> timer support on emu20k2.  It was only for emu20k1 until today.
> 
> 
> Takashi
> 
> > On Mon, 2009-07-20 at 07:37 +0200, Takashi Iwai wrote:
> > 
> >     At Sun, 19 Jul 2009 19:38:59 -0500,
> >     Ted T. Logan wrote:
> >     > 
> >     > Thanks.
> >     > 
> >     > Basically the driver from creative, the old one, works without clicks:
> >     > 
> >     > XFiDrv_Linux_US-1.18.tar.gz
> >     > >From April, 2008
> >     
> >     Where is it available?
> >     
> >     > and this one works without clicks.
> >     > 
> >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     
> >     So, do both versions work on yours?
> >     What are the differences between them?
> >     
> >     > lspci lists it as:
> >     > 03:03.0 Multimedia audio controller: Creative Labs SB X-Fi
> >     > 
> >     > and in xp, it uses the same x-fi drivers as the others.
> >     > 
> >     > I have never been able to get any driver you released to work with it.
> >     > 
> >     > Can you tell me the first driver you had that you recommend I test it with?
> >     
> >     GIT is the easiest way.  For example, look at the page below:
> >        http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=history;f=sound/pci/ctxfi;h=91c958a7e171313fe68d728a3b4860287ad40aa7;hb=HEAD
> > 
> >     Takashi
> >     
> >     > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> >     > 
> >     >     At Sun, 19 Jul 2009 10:35:21 -0500,
> >     >     Ted T. Logan wrote:
> >     >     > 
> >     >     > Maybe you haven't been following the thread.  I've been trying to debug the
> >     >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> >     >     > never worked with this driver.
> >     >     > There have always been clicks.
> >     >     > 
> >     >     > However, it does not have clicks with the following driver:
> >     >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     >     > 
> >     >     > Sending out condescending messages like this after I was responding to the
> >     >     > "testers wanted" mailer which said all cards should be supported now is
> >     >     > completely unproductive.
> >     >     
> >     >     Well, the current situation is that I've got no other report but you
> >     >     regarding the specific problem.  There is a known issue with openal,
> >     >     accordingly, but not all apps.  So, this is very likely a different
> >     >     issue.
> >     >     
> >     >     Actually, it's still the phase to gather all information to know which
> >     >     part exactly is problematic.  If you find any other guys that have the
> >     >     exact same problem, let me know.  It would make easier to find out a
> >     >     problem pattern, either for finding out the culprit or reproducing the
> >     >     problem.
> >     >     
> >     >     Or, you can do trial-and-error by comparing the driver above and the
> >     >     current one (maybe the first committed version is easier to compare).
> >     >     This can't be done without the real hardware, so it's actually up to
> >     >     you how to fix the issue...
> >     > 
> >     >     Takashi
> >     >     
> >     >     > 
> >     >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> >     >     > 
> >     >     >     Debug the problem, write code that fixes it and then send in a patch.
> >     >     >     That's why this is the alsa *developers* mailing list.
> >     >     >     
> >     >     >     Ted T. Logan wrote:
> >     >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     >     >     > 
> >     >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     >     >     > 
> >     >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >     >     >> Frashman wrote:
> >     >     >     >>> Hi Takashi,
> >     >     >     >>>
> >     >     >     >>> first of all, thank you for developing this driver.
> >     >     >     >>> I tested it today. It works, so far.
> >     >     >     >>>
> >     >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >     >     >> It's likely the collision of PCI device ID.
> >     >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >     >     >> modes are switched by some magical sequence.
> >     >     >     >>
> >     >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >     >     >> the generated file.
> >     >     >     >>
> >     >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >     >     >>> works.
> >     >     >     >>>
> >     >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >     >     >>> connector colors are also correct.
> >     >     >     >>>
> >     >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >     >     >>> i'm using speaker-test -c6
> >     >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >     >     >> are swapped when running with 8 channel mode?
> >     >     >     >>
> >     >     >     >>
> >     >     >     >> Takashi
> >     >     >     >> _______________________________________________
> >     >     >     >> Alsa-devel mailing list
> >     >     >     >> Alsa-devel@alsa-project.org
> >     >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     >     > _______________________________________________
> >     >     >     > Alsa-devel mailing list
> >     >     >     > Alsa-devel@alsa-project.org
> >     >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     >     > 
> >     >     > 
> >     >     > 
> >     > 
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Tue, 21 Jul 2009 02:23:06 -0500,
Ted T. Logan wrote:
> 
> upgraded to latest snapshot:
> 
> ftp://kernel.org/pub/linux/kernel/people/tiwai/snapshot/
> alsa-driver-snapshot.tar.gz
> just like a metronome:)
> 
> click
> click
> click
> click
> click
> click
> click
> click

This must be a bug I recently introduced.
Now it's fixed in the latest snapshot.  Give it a try again.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

[Please don't do top-posting]

At Tue, 28 Jul 2009 14:50:10 -0500,
Ted T. Logan wrote:
> 
> Just got the latest as of today,
> 
> click
> click
> click
> click
> click
> 
> :(
> mplayer yesterday.mp3

For testing this kind of problem, use aplay and try different
--period-size and --buffer-size options.  mplayer isn't suitable for
primary testing.

If the click period doesn't change regardless of the period size
option value, it implies that the noise doesn't come from the buffer
set up but rather from other routes.  If the noise period changes with
different period size options, the click noise is a buffer setup
issue.

In addition, it'd be better to use aplay with -Dplughw to avoid the
automatic routing to PA.

Also, your description was unclear.  It it only click without other
tone, or repeated sound, or the click noise appear on the normal
playback, or what?  The repeated sound bug with emu20k2 (it didn't
appear with emu20k1) was fixed as I mentioned.  But, if it's click
noise on the normal playback, then I don't know.  Better to ask
Creative guys...


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

I just CANNOT understand this.  I disabled usb and hda-intel, updated to
latest snapshot.

with aplay, i get snaps every 1/2 second.  This blows my mind.

On Mon, 2009-07-20 at 07:37 +0200, Takashi Iwai wrote:

> At Sun, 19 Jul 2009 19:38:59 -0500,
> Ted T. Logan wrote:
> > 
> > Thanks.
> > 
> > Basically the driver from creative, the old one, works without clicks:
> > 
> > XFiDrv_Linux_US-1.18.tar.gz
> > >From April, 2008
> 
> Where is it available?
> 
> > and this one works without clicks.
> > 
> > XFiDrv_Linux_Public_US_1.00.tar.gz
> 
> So, do both versions work on yours?
> What are the differences between them?
> 
> > lspci lists it as:
> > 03:03.0 Multimedia audio controller: Creative Labs SB X-Fi
> > 
> > and in xp, it uses the same x-fi drivers as the others.
> > 
> > I have never been able to get any driver you released to work with it.
> > 
> > Can you tell me the first driver you had that you recommend I test it with?
> 
> GIT is the easiest way.  For example, look at the page below:
>    http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=history;f=sound/pci/ctxfi;h=91c958a7e171313fe68d728a3b4860287ad40aa7;hb=HEAD
> 
> 
> Takashi
> 
> > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> > 
> >     At Sun, 19 Jul 2009 10:35:21 -0500,
> >     Ted T. Logan wrote:
> >     > 
> >     > Maybe you haven't been following the thread.  I've been trying to debug the
> >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> >     > never worked with this driver.
> >     > There have always been clicks.
> >     > 
> >     > However, it does not have clicks with the following driver:
> >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     > 
> >     > Sending out condescending messages like this after I was responding to the
> >     > "testers wanted" mailer which said all cards should be supported now is
> >     > completely unproductive.
> >     
> >     Well, the current situation is that I've got no other report but you
> >     regarding the specific problem.  There is a known issue with openal,
> >     accordingly, but not all apps.  So, this is very likely a different
> >     issue.
> >     
> >     Actually, it's still the phase to gather all information to know which
> >     part exactly is problematic.  If you find any other guys that have the
> >     exact same problem, let me know.  It would make easier to find out a
> >     problem pattern, either for finding out the culprit or reproducing the
> >     problem.
> >     
> >     Or, you can do trial-and-error by comparing the driver above and the
> >     current one (maybe the first committed version is easier to compare).
> >     This can't be done without the real hardware, so it's actually up to
> >     you how to fix the issue...
> > 
> >     Takashi
> >     
> >     > 
> >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> >     > 
> >     >     Debug the problem, write code that fixes it and then send in a patch.
> >     >     That's why this is the alsa *developers* mailing list.
> >     >     
> >     >     Ted T. Logan wrote:
> >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     >     > 
> >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     >     > 
> >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >     >> Frashman wrote:
> >     >     >>> Hi Takashi,
> >     >     >>>
> >     >     >>> first of all, thank you for developing this driver.
> >     >     >>> I tested it today. It works, so far.
> >     >     >>>
> >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >     >> It's likely the collision of PCI device ID.
> >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >     >> modes are switched by some magical sequence.
> >     >     >>
> >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >     >> the generated file.
> >     >     >>
> >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >     >>> works.
> >     >     >>>
> >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >     >>> connector colors are also correct.
> >     >     >>>
> >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >     >>> i'm using speaker-test -c6
> >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >     >> are swapped when running with 8 channel mode?
> >     >     >>
> >     >     >>
> >     >     >> Takashi
> >     >     >> _______________________________________________
> >     >     >> Alsa-devel mailing list
> >     >     >> Alsa-devel@alsa-project.org
> >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > _______________________________________________
> >     >     > Alsa-devel mailing list
> >     >     > Alsa-devel@alsa-project.org
> >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > 
> >     > 
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Takashi,

Fwiw, I reinstalled my kernel to get the old alsa modules back
Linux home 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009
i686 i686 i386 GNU/Linux

and reinstalled this driver:
XFiDrv_Linux_Public_US_1.00

and I am able to use my xfi again without clicks.  Unfortunately, this
driver seems to be no longer developed and has some other issues such as
with skype and pulseaudio.  I'd REALLY prefer to use your driver but I'm
not quite sure what to do.



On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:

> At Sun, 19 Jul 2009 10:35:21 -0500,
> Ted T. Logan wrote:
> > 
> > Maybe you haven't been following the thread.  I've been trying to debug the
> > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> > never worked with this driver.
> > There have always been clicks.
> > 
> > However, it does not have clicks with the following driver:
> > XFiDrv_Linux_Public_US_1.00.tar.gz
> > 
> > Sending out condescending messages like this after I was responding to the
> > "testers wanted" mailer which said all cards should be supported now is
> > completely unproductive.
> 
> Well, the current situation is that I've got no other report but you
> regarding the specific problem.  There is a known issue with openal,
> accordingly, but not all apps.  So, this is very likely a different
> issue.
> 
> Actually, it's still the phase to gather all information to know which
> part exactly is problematic.  If you find any other guys that have the
> exact same problem, let me know.  It would make easier to find out a
> problem pattern, either for finding out the culprit or reproducing the
> problem.
> 
> Or, you can do trial-and-error by comparing the driver above and the
> current one (maybe the first committed version is easier to compare).
> This can't be done without the real hardware, so it's actually up to
> you how to fix the issue...
> 
> 
> Takashi
> 
> > 
> > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> > 
> >     Debug the problem, write code that fixes it and then send in a patch.
> >     That's why this is the alsa *developers* mailing list.
> >     
> >     Ted T. Logan wrote:
> >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     > 
> >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     > 
> >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >> Frashman wrote:
> >     >>> Hi Takashi,
> >     >>>
> >     >>> first of all, thank you for developing this driver.
> >     >>> I tested it today. It works, so far.
> >     >>>
> >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >> It's likely the collision of PCI device ID.
> >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >> modes are switched by some magical sequence.
> >     >>
> >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >> the generated file.
> >     >>
> >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >>> works.
> >     >>>
> >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >>> connector colors are also correct.
> >     >>>
> >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >>> i'm using speaker-test -c6
> >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >> are swapped when running with 8 channel mode?
> >     >>
> >     >>
> >     >> Takashi
> >     >> _______________________________________________
> >     >> Alsa-devel mailing list
> >     >> Alsa-devel@alsa-project.org
> >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     > _______________________________________________
> >     > Alsa-devel mailing list
> >     > Alsa-devel@alsa-project.org
> >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 22 Jul 2009 12:53:49 -0500,
Ted T. Logan wrote:
> 
> Takashi,
> 
> Fwiw, I reinstalled my kernel to get the old alsa modules back
> Linux home 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009 i686
> i686 i386 GNU/Linux
> 
> and reinstalled this driver:
> XFiDrv_Linux_Public_US_1.00
> 
> and I am able to use my xfi again without clicks.  Unfortunately, this driver
> seems to be no longer developed and has some other issues such as with skype
> and pulseaudio.  I'd REALLY prefer to use your driver but I'm not quite sure
> what to do.

Then you should  contact with Creative guys.
They provided the driver after all.
The addresses can be obtained in GIT changelog.


Takashi

> 
> On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> 
>     At Sun, 19 Jul 2009 10:35:21 -0500,
>     Ted T. Logan wrote:
>     > 
>     > Maybe you haven't been following the thread.  I've been trying to debug the
>     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
>     > never worked with this driver.
>     > There have always been clicks.
>     > 
>     > However, it does not have clicks with the following driver:
>     > XFiDrv_Linux_Public_US_1.00.tar.gz
>     > 
>     > Sending out condescending messages like this after I was responding to the
>     > "testers wanted" mailer which said all cards should be supported now is
>     > completely unproductive.
>     
>     Well, the current situation is that I've got no other report but you
>     regarding the specific problem.  There is a known issue with openal,
>     accordingly, but not all apps.  So, this is very likely a different
>     issue.
>     
>     Actually, it's still the phase to gather all information to know which
>     part exactly is problematic.  If you find any other guys that have the
>     exact same problem, let me know.  It would make easier to find out a
>     problem pattern, either for finding out the culprit or reproducing the
>     problem.
>     
>     Or, you can do trial-and-error by comparing the driver above and the
>     current one (maybe the first committed version is easier to compare).
>     This can't be done without the real hardware, so it's actually up to
>     you how to fix the issue...
> 
>     Takashi
>     
>     > 
>     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
>     > 
>     >     Debug the problem, write code that fixes it and then send in a patch.
>     >     That's why this is the alsa *developers* mailing list.
>     >     
>     >     Ted T. Logan wrote:
>     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
>     >     > 
>     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
>     >     > 
>     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
>     >     >> Frashman wrote:
>     >     >>> Hi Takashi,
>     >     >>>
>     >     >>> first of all, thank you for developing this driver.
>     >     >>> I tested it today. It works, so far.
>     >     >>>
>     >     >>> But two annoying things. As you mentioned, I got problems, if the 
>     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>     >     >> It's likely the collision of PCI device ID.
>     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>     >     >> modes are switched by some magical sequence.
>     >     >>
>     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
>     >     >> the generated file.
>     >     >>
>     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
>     >     >>> works.
>     >     >>>
>     >     >>> The second problem is, that SIDE and SURROUND connectors are 
>     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
>     >     >>> connector colors are also correct.
>     >     >>>
>     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
>     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
>     >     >>> i'm using speaker-test -c6
>     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>     >     >> are swapped when running with 8 channel mode?
>     >     >>
>     >     >>
>     >     >> Takashi
>     >     >> _______________________________________________
>     >     >> Alsa-devel mailing list
>     >     >> Alsa-devel@alsa-project.org
>     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     > _______________________________________________
>     >     > Alsa-devel mailing list
>     >     > Alsa-devel@alsa-project.org
>     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     > 
>     > 
>     > 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

I should contact the creative guys about using your driver?

On Wed, 2009-07-22 at 21:33 +0200, Takashi Iwai wrote:

> At Wed, 22 Jul 2009 12:53:49 -0500,
> Ted T. Logan wrote:
> > 
> > Takashi,
> > 
> > Fwiw, I reinstalled my kernel to get the old alsa modules back
> > Linux home 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009 i686
> > i686 i386 GNU/Linux
> > 
> > and reinstalled this driver:
> > XFiDrv_Linux_Public_US_1.00
> > 
> > and I am able to use my xfi again without clicks.  Unfortunately, this driver
> > seems to be no longer developed and has some other issues such as with skype
> > and pulseaudio.  I'd REALLY prefer to use your driver but I'm not quite sure
> > what to do.
> 
> Then you should  contact with Creative guys.
> They provided the driver after all.
> The addresses can be obtained in GIT changelog.
> 
> 
> Takashi
> 
> > 
> > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> > 
> >     At Sun, 19 Jul 2009 10:35:21 -0500,
> >     Ted T. Logan wrote:
> >     > 
> >     > Maybe you haven't been following the thread.  I've been trying to debug the
> >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> >     > never worked with this driver.
> >     > There have always been clicks.
> >     > 
> >     > However, it does not have clicks with the following driver:
> >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     > 
> >     > Sending out condescending messages like this after I was responding to the
> >     > "testers wanted" mailer which said all cards should be supported now is
> >     > completely unproductive.
> >     
> >     Well, the current situation is that I've got no other report but you
> >     regarding the specific problem.  There is a known issue with openal,
> >     accordingly, but not all apps.  So, this is very likely a different
> >     issue.
> >     
> >     Actually, it's still the phase to gather all information to know which
> >     part exactly is problematic.  If you find any other guys that have the
> >     exact same problem, let me know.  It would make easier to find out a
> >     problem pattern, either for finding out the culprit or reproducing the
> >     problem.
> >     
> >     Or, you can do trial-and-error by comparing the driver above and the
> >     current one (maybe the first committed version is easier to compare).
> >     This can't be done without the real hardware, so it's actually up to
> >     you how to fix the issue...
> > 
> >     Takashi
> >     
> >     > 
> >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> >     > 
> >     >     Debug the problem, write code that fixes it and then send in a patch.
> >     >     That's why this is the alsa *developers* mailing list.
> >     >     
> >     >     Ted T. Logan wrote:
> >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     >     > 
> >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     >     > 
> >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >     >> Frashman wrote:
> >     >     >>> Hi Takashi,
> >     >     >>>
> >     >     >>> first of all, thank you for developing this driver.
> >     >     >>> I tested it today. It works, so far.
> >     >     >>>
> >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >     >> It's likely the collision of PCI device ID.
> >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >     >> modes are switched by some magical sequence.
> >     >     >>
> >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >     >> the generated file.
> >     >     >>
> >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >     >>> works.
> >     >     >>>
> >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >     >>> connector colors are also correct.
> >     >     >>>
> >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >     >>> i'm using speaker-test -c6
> >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >     >> are swapped when running with 8 channel mode?
> >     >     >>
> >     >     >>
> >     >     >> Takashi
> >     >     >> _______________________________________________
> >     >     >> Alsa-devel mailing list
> >     >     >> Alsa-devel@alsa-project.org
> >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > _______________________________________________
> >     >     > Alsa-devel mailing list
> >     >     > Alsa-devel@alsa-project.org
> >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     > 
> >     > 
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 22 Jul 2009 14:40:25 -0500,
Ted T. Logan wrote:
> 
> I should contact the creative guys about using your driver?

This isn't *my* driver at all.
The driver code is originally given by Creative guys.


Takashi

> 
> On Wed, 2009-07-22 at 21:33 +0200, Takashi Iwai wrote:
> 
>     At Wed, 22 Jul 2009 12:53:49 -0500,
>     Ted T. Logan wrote:
>     > 
>     > Takashi,
>     > 
>     > Fwiw, I reinstalled my kernel to get the old alsa modules back
>     > Linux home 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009 i686
>     > i686 i386 GNU/Linux
>     > 
>     > and reinstalled this driver:
>     > XFiDrv_Linux_Public_US_1.00
>     > 
>     > and I am able to use my xfi again without clicks.  Unfortunately, this driver
>     > seems to be no longer developed and has some other issues such as with skype
>     > and pulseaudio.  I'd REALLY prefer to use your driver but I'm not quite sure
>     > what to do.
>     
>     Then you should  contact with Creative guys.
>     They provided the driver after all.
>     The addresses can be obtained in GIT changelog.
> 
>     Takashi
>     
>     > 
>     > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
>     > 
>     >     At Sun, 19 Jul 2009 10:35:21 -0500,
>     >     Ted T. Logan wrote:
>     >     > 
>     >     > Maybe you haven't been following the thread.  I've been trying to debug the
>     >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
>     >     > never worked with this driver.
>     >     > There have always been clicks.
>     >     > 
>     >     > However, it does not have clicks with the following driver:
>     >     > XFiDrv_Linux_Public_US_1.00.tar.gz
>     >     > 
>     >     > Sending out condescending messages like this after I was responding to the
>     >     > "testers wanted" mailer which said all cards should be supported now is
>     >     > completely unproductive.
>     >     
>     >     Well, the current situation is that I've got no other report but you
>     >     regarding the specific problem.  There is a known issue with openal,
>     >     accordingly, but not all apps.  So, this is very likely a different
>     >     issue.
>     >     
>     >     Actually, it's still the phase to gather all information to know which
>     >     part exactly is problematic.  If you find any other guys that have the
>     >     exact same problem, let me know.  It would make easier to find out a
>     >     problem pattern, either for finding out the culprit or reproducing the
>     >     problem.
>     >     
>     >     Or, you can do trial-and-error by comparing the driver above and the
>     >     current one (maybe the first committed version is easier to compare).
>     >     This can't be done without the real hardware, so it's actually up to
>     >     you how to fix the issue...
>     > 
>     >     Takashi
>     >     
>     >     > 
>     >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
>     >     > 
>     >     >     Debug the problem, write code that fixes it and then send in a patch.
>     >     >     That's why this is the alsa *developers* mailing list.
>     >     >     
>     >     >     Ted T. Logan wrote:
>     >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
>     >     >     > 
>     >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
>     >     >     > 
>     >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
>     >     >     >> Frashman wrote:
>     >     >     >>> Hi Takashi,
>     >     >     >>>
>     >     >     >>> first of all, thank you for developing this driver.
>     >     >     >>> I tested it today. It works, so far.
>     >     >     >>>
>     >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
>     >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
>     >     >     >> It's likely the collision of PCI device ID.
>     >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
>     >     >     >> modes are switched by some magical sequence.
>     >     >     >>
>     >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
>     >     >     >> the generated file.
>     >     >     >>
>     >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
>     >     >     >>> works.
>     >     >     >>>
>     >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
>     >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
>     >     >     >>> connector colors are also correct.
>     >     >     >>>
>     >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
>     >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
>     >     >     >>> i'm using speaker-test -c6
>     >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
>     >     >     >> are swapped when running with 8 channel mode?
>     >     >     >>
>     >     >     >>
>     >     >     >> Takashi
>     >     >     >> _______________________________________________
>     >     >     >> Alsa-devel mailing list
>     >     >     >> Alsa-devel@alsa-project.org
>     >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     >     > _______________________________________________
>     >     >     > Alsa-devel mailing list
>     >     >     > Alsa-devel@alsa-project.org
>     >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>     >     >     > 
>     >     > 
>     >     > 
>     > 
>     > 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Ah ok, sorry.

I just know that, from what I can see, there are no plans for them to
develop the driver anymore and was looking for something for the future,
that's why I'm hoping to get my card working with your driver. Also, I
get no sound at all with your driver when I tell it to do surround.

On Thu, 2009-07-23 at 07:30 +0200, Takashi Iwai wrote:

> At Wed, 22 Jul 2009 14:40:25 -0500,
> Ted T. Logan wrote:
> > 
> > I should contact the creative guys about using your driver?
> 
> This isn't *my* driver at all.
> The driver code is originally given by Creative guys.
> 
> 
> Takashi
> 
> > 
> > On Wed, 2009-07-22 at 21:33 +0200, Takashi Iwai wrote:
> > 
> >     At Wed, 22 Jul 2009 12:53:49 -0500,
> >     Ted T. Logan wrote:
> >     > 
> >     > Takashi,
> >     > 
> >     > Fwiw, I reinstalled my kernel to get the old alsa modules back
> >     > Linux home 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16 23:11:39 EDT 2009 i686
> >     > i686 i386 GNU/Linux
> >     > 
> >     > and reinstalled this driver:
> >     > XFiDrv_Linux_Public_US_1.00
> >     > 
> >     > and I am able to use my xfi again without clicks.  Unfortunately, this driver
> >     > seems to be no longer developed and has some other issues such as with skype
> >     > and pulseaudio.  I'd REALLY prefer to use your driver but I'm not quite sure
> >     > what to do.
> >     
> >     Then you should  contact with Creative guys.
> >     They provided the driver after all.
> >     The addresses can be obtained in GIT changelog.
> > 
> >     Takashi
> >     
> >     > 
> >     > On Sun, 2009-07-19 at 18:01 +0200, Takashi Iwai wrote:
> >     > 
> >     >     At Sun, 19 Jul 2009 10:35:21 -0500,
> >     >     Ted T. Logan wrote:
> >     >     > 
> >     >     > Maybe you haven't been following the thread.  I've been trying to debug the
> >     >     > problem.  As I mentioned to Takashi, there's not a point where it broke, it
> >     >     > never worked with this driver.
> >     >     > There have always been clicks.
> >     >     > 
> >     >     > However, it does not have clicks with the following driver:
> >     >     > XFiDrv_Linux_Public_US_1.00.tar.gz
> >     >     > 
> >     >     > Sending out condescending messages like this after I was responding to the
> >     >     > "testers wanted" mailer which said all cards should be supported now is
> >     >     > completely unproductive.
> >     >     
> >     >     Well, the current situation is that I've got no other report but you
> >     >     regarding the specific problem.  There is a known issue with openal,
> >     >     accordingly, but not all apps.  So, this is very likely a different
> >     >     issue.
> >     >     
> >     >     Actually, it's still the phase to gather all information to know which
> >     >     part exactly is problematic.  If you find any other guys that have the
> >     >     exact same problem, let me know.  It would make easier to find out a
> >     >     problem pattern, either for finding out the culprit or reproducing the
> >     >     problem.
> >     >     
> >     >     Or, you can do trial-and-error by comparing the driver above and the
> >     >     current one (maybe the first committed version is easier to compare).
> >     >     This can't be done without the real hardware, so it's actually up to
> >     >     you how to fix the issue...
> >     > 
> >     >     Takashi
> >     >     
> >     >     > 
> >     >     > On Thu, 2009-07-16 at 12:20 -0700, John L. Utz III wrote:
> >     >     > 
> >     >     >     Debug the problem, write code that fixes it and then send in a patch.
> >     >     >     That's why this is the alsa *developers* mailing list.
> >     >     >     
> >     >     >     Ted T. Logan wrote:
> >     >     >     > Takashi, please, what must I do to get your xfi driver to stop clicking?
> >     >     >     > 
> >     >     >     > On Thu, 2009-07-16 at 11:22 +0200, Takashi Iwai wrote:
> >     >     >     > 
> >     >     >     >> At Wed, 15 Jul 2009 12:55:23 +0200,
> >     >     >     >> Frashman wrote:
> >     >     >     >>> Hi Takashi,
> >     >     >     >>>
> >     >     >     >>> first of all, thank you for developing this driver.
> >     >     >     >>> I tested it today. It works, so far.
> >     >     >     >>>
> >     >     >     >>> But two annoying things. As you mentioned, I got problems, if the 
> >     >     >     >>> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >     >     >     >> It's likely the collision of PCI device ID.
> >     >     >     >> Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> >     >     >     >> modes are switched by some magical sequence.
> >     >     >     >>
> >     >     >     >> Anyway, please run alsa-info.sh with --no-upload option, and attach
> >     >     >     >> the generated file.
> >     >     >     >>
> >     >     >     >>> If I disable the loading of snd-hda-intel modules while booting, then it 
> >     >     >     >>> works.
> >     >     >     >>>
> >     >     >     >>> The second problem is, that SIDE and SURROUND connectors are 
> >     >     >     >>> interchanged. I'm absolutly sure, it works fine under windows and the 
> >     >     >     >>> connector colors are also correct.
> >     >     >     >>>
> >     >     >     >>> If I run speaker-test -c8 the SIDE Speakers sounds come out of my REAR 
> >     >     >     >>> (SURROUND) Speakers, while nothing is coming out of my rear speakers, if 
> >     >     >     >>> i'm using speaker-test -c6
> >     >     >     >> So, the side channels (channel 7 & 8) and the rear channels (3 & 4)
> >     >     >     >> are swapped when running with 8 channel mode?
> >     >     >     >>
> >     >     >     >>
> >     >     >     >> Takashi
> >     >     >     >> _______________________________________________
> >     >     >     >> Alsa-devel mailing list
> >     >     >     >> Alsa-devel@alsa-project.org
> >     >     >     >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     >     > _______________________________________________
> >     >     >     > Alsa-devel mailing list
> >     >     >     > Alsa-devel@alsa-project.org
> >     >     >     > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >     >     >     > 
> >     >     > 
> >     >     > 
> >     > 
> >     > 
> > 
> > 

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 16 Jul 2009 12:19:15 +0200,
Frashman wrote:
> 
> Takashi Iwai schrieb:
> > At Wed, 15 Jul 2009 12:55:23 +0200,
> > Frashman wrote:
> >   
> >> Hi Takashi,
> >>
> >> first of all, thank you for developing this driver.
> >> I tested it today. It works, so far.
> >>
> >> But two annoying things. As you mentioned, I got problems, if the 
> >> onboard sound modules are loaded. Then i get no sound out auf my xfi.
> >>     
> >
> > It's likely the collision of PCI device ID.
> > Some X-Fi models support both HD-audio and emu20kx-native modes.  The
> > modes are switched by some magical sequence.
> >
> > Anyway, please run alsa-info.sh with --no-upload option, and attach
> > the generated file.
> >   
> I let the kernel auto probe all sound modules and generated then the 
> alsa-info.txt
> It's attached.

The PCI ID looks different from what snd-hda-intel driver supports.
When compiled together with snd-ctxfi, snd-hda-intel only probes
PCI ID 1002:0009.

Are you sure that it's hda-intel that interferes the xfi?
Any relevant kernel messages or asound entry when this happens?


Takashi

Re: Testers wanted: New SB X-Fi driver

[Frank Roth]

Hi

Got it, there was a wrong default entry in
/etc/modprobe.d/50-sound.conf
..made by alsaconf

alias snd-card-0 snd-ctxfi
alias sound-slot-0 snd-ctxfi


moved it now to
/etc/modprobe.d/modprobe.conf
and chanced to:

alias snd-card-0 snd_ctxfi
alias sound-slot-0 snd_ctxfi

now it's fine ... so ... no conflict ... sorry.
but maybe someone could look, why alsaconf had done this.



> 
> The PCI ID looks different from what snd-hda-intel driver supports.
> When compiled together with snd-ctxfi, snd-hda-intel only probes
> PCI ID 1002:0009.
> 
> Are you sure that it's hda-intel that interferes the xfi?
> Any relevant kernel messages or asound entry when this happens?
> 
> 
> Takashi



Found another problem ... maybe it isn't a bug ...

If I raise all volumes in alsamixer to 100% it starts to crackle while playing music ...
If I lower one of the mixer volumes down to 90% it's fine.
Maybe it's just overdriven ... but I'm relative sure, in windows I can gain everything to 100% without to be overdriven.

For now, I've set the PCM volume control to 90%, then I can do whatever I want with the master volume ;-)


Greetings
Frank

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 20 Jul 2009 20:47:55 +0200,
Frank Roth wrote:
> 
> Hi
> 
> Got it, there was a wrong default entry in
> /etc/modprobe.d/50-sound.conf
> ..made by alsaconf
> 
> alias snd-card-0 snd-ctxfi
> alias sound-slot-0 snd-ctxfi
> 
> 
> moved it now to
> /etc/modprobe.d/modprobe.conf
> and chanced to:
> 
> alias snd-card-0 snd_ctxfi
> alias sound-slot-0 snd_ctxfi
> 
> now it's fine ... so ... no conflict ... sorry.
> but maybe someone could look, why alsaconf had done this.

The former file name is the requirement by the recent
module-init-tools.  The question is rather why it doesn't work on your
system.  Maybe modprobe.d/* itself doesn't work?

Anyway, alsaconf is nowadays no longer recommended.  It's good for
detecting some very old ISA devices without PnP, but not for other
normal devices.


Takashi


> > 
> > The PCI ID looks different from what snd-hda-intel driver supports.
> > When compiled together with snd-ctxfi, snd-hda-intel only probes
> > PCI ID 1002:0009.
> > 
> > Are you sure that it's hda-intel that interferes the xfi?
> > Any relevant kernel messages or asound entry when this happens?
> > 
> > 
> > Takashi
> 
> 
> 
> Found another problem ... maybe it isn't a bug ...
> 
> If I raise all volumes in alsamixer to 100% it starts to crackle while playing music ...
> If I lower one of the mixer volumes down to 90% it's fine.
> Maybe it's just overdriven ... but I'm relative sure, in windows I can gain everything to 100% without to be overdriven.
> 
> For now, I've set the PCM volume control to 90%, then I can do whatever I want with the master volume ;-)
> 
> 
> Greetings
> Frank
> 
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Frank Roth]

I play around with my X-Fi now,
I'm wondering if there is a way to support this Headphones/4/5.1/7.1 up-/downmix modes from Windows.
Stereo/Surround ...

And in what I'm much more interested is,
Bass-Redirection ... because I use a Teufel - Concept E Magnum 5.1 speaker system.
It's connected via analogue 5.1 cables. And by default, nothing is coming out of LFE if play usual stereo music.
There is also an option in the windows drivers.


I found out, i could configure .asoundrc to do this, but is this the usual way?



Thanks for help.
Frank

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Tue, 21 Jul 2009 12:52:18 +0200,
Frank Roth wrote:
> 
> I play around with my X-Fi now,
> I'm wondering if there is a way to support this Headphones/4/5.1/7.1 up-/downmix modes from Windows.
> Stereo/Surround ...
> 
> And in what I'm much more interested is,
> Bass-Redirection ... because I use a Teufel - Concept E Magnum 5.1 speaker system.
> It's connected via analogue 5.1 cables. And by default, nothing is coming out of LFE if play usual stereo music.
> There is also an option in the windows drivers.
> 
> 
> I found out, i could configure .asoundrc to do this, but is this the usual way?

Unless any information about the DSP programming on emu20kx is opened,
there is no way to implement in the driver side.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Frank Roth]

Ok thanks.

So you still didn't have specifications from Creative?
Because I red some time ago, creative gave the specs to the opensource community?
How is it possible to write this drivers then? Only reengineering from their opensource drivers?
Impressive!!

So I understand it right, everything is more or less software based right now?
We must change this ... (I would help you out, so far I can)


But thanks again for your work,
I have clear sound to here some music on linux, a first step.

Frank

Takashi Iwai schrieb:
> At Tue, 21 Jul 2009 12:52:18 +0200,
> Frank Roth wrote:
>> I play around with my X-Fi now,
>> I'm wondering if there is a way to support this Headphones/4/5.1/7.1 up-/downmix modes from Windows.
>> Stereo/Surround ...
>>
>> And in what I'm much more interested is,
>> Bass-Redirection ... because I use a Teufel - Concept E Magnum 5.1 speaker system.
>> It's connected via analogue 5.1 cables. And by default, nothing is coming out of LFE if play usual stereo music.
>> There is also an option in the windows drivers.
>>
>>
>> I found out, i could configure .asoundrc to do this, but is this the usual way?
> 
> Unless any information about the DSP programming on emu20kx is opened,
> there is no way to implement in the driver side.
> 
> 
> Takashi

Re: Testers wanted: New SB X-Fi driver

[James Courtier-Dutton]

2009/7/21 Frank Roth <frashman@freenet.de>:
> Ok thanks.
>
> So you still didn't have specifications from Creative?
> Because I red some time ago, creative gave the specs to the opensource community?
> How is it possible to write this drivers then? Only reengineering from their opensource drivers?
> Impressive!!
>
> So I understand it right, everything is more or less software based right now?
> We must change this ... (I would help you out, so far I can)
>

That is correct. I have the datasheets from Creative and they are not
complete data sheets. They do not include the DSP workings of the
card. They simply explain how to configure the card to bypass the DSP
unit.
The datasheet does contain some info regarding how one might use
hardware mixing as this uses a separate "mixing unit" within the chip.
I do not think that this "mixing unit" has been implemented in the
open source driver.
The DSP itself is very complex and as a result, reverse engineering it
will be difficult. It would be possible if one had the time but I
don't have the time.
I consider it a similar task to if one was needing to reverse engineer
the x86 chip without having any of the instruction set.

Kind Regards

James

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
> Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> > At Sun, 5 Jul 2009 13:29:48 +0200,
> >
> > Christian Esken wrote:
> > > Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > > > At Sun, 5 Jul 2009 00:19:55 +0200,
> > > >
> > > > Christian Esken wrote:
> > > > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > > > Hello,
> > > > > >
> > > > > > unfortunately I cannot playback anything (PCM) with the new SB
> > > > > > X-Fi driver. Driver:
> > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-
> > > > > > driver-snapshot.tar.bz2
> > > > > >   Distribution: openSuSE 11.1
> > > > > >   Kernel: 2.6.27.23-0.1-xen
> > > > > >
> > > > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
> > > > > > card is recognized by the driver, and any mixer (alsamixer, kmix)
> > > > > > also recognizes the card.
> > > > > >
> > > > > > But playing back isn't possible. I tried speaker-test, audacity,
> > > > > > amarok and aplay. Most applications  hang, some also produce an
> > > > > > error in the /var/log/messages (see
> > > > > > below).
> > > > > >
> > > > > > I then used "./configure --with-debug=full --with-cards=ctxfi"
> > > > > > due to the possible hd-audio conflict, but it didn't make a
> > > > > > difference.
> > > > > >
> > > > > > Is there anything else I could try?
> > > > >
> > > > > I tested the same openSuSE version with a non-Xen 64 bit kernel,
> > > > > and it doesn't work either.
> > > > >
> > > > > And I tried with this:
> > > > >   Driver: alsa-driver-20090704.tar.bz2
> > > > >   Distribution: Kubuntu Karmic Alpha-2
> > > > >   Kernel: 2.6.30  (32 Bit)
> > > > >
> > > > > Under the latter setup the X-Fi Titanium works (Simple 2 channel
> > > > > test with speaker-test, audacity, amarok). :-))
> > > >
> > > > How many RAM do you have?
> > > > Could you boot with the limited memory size?
> > >
> > > It is just 2GB. So I am not limited by the 32 bit barrier.
> > >
> > > So booting with "limited" memory size doesn't make sense, right?
> >
> > Supposedly.  Is it emu20k1 or emu20k2?
>
> I checked it again: It is a 20k2 chip.
>
> /var/log/boot.msg says:
> <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi: chip
> 20K2 model SB0880 (1102:0041) is found
>
>
> http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
> series [EMU20k2]".

I did now test it with a different 64 Bit Linux distribution, and it works 
correctly:
Driver: alsa-driver-20090712.tar.bz2
Distribution: Kubuntu Karmic Alpha-2
Kernel: 2.6.30  (64 Bit)

All in all, I can produce a working environment with recent 32 and 64 bit 
kernels. This is good news.  :-)

Below is the summary on the tested distributions.

  Christian


So we got this:
Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
SuSE 11.1 64 Bit,  2.0.27 (does not work)
SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated problems)
   => I'll see whether I can redo the SuSE11.2 tests, after doing a bugreport 
at openSuSE.

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

Am Sonntag 12 Juli 2009 16:07:49 schrieb Christian Esken:
> Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
> > Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> > > At Sun, 5 Jul 2009 13:29:48 +0200,
> > >
> > > Christian Esken wrote:
> > > > Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > > > > At Sun, 5 Jul 2009 00:19:55 +0200,
> > > > >
> > > > > Christian Esken wrote:
> > > > > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > > > > Hello,
> > > > > > >
> > > > > > > unfortunately I cannot playback anything (PCM) with the new SB
> > > > > > > X-Fi driver. Driver:
> > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/als
> > > > > > >a- driver-snapshot.tar.bz2
> > > > > > >   Distribution: openSuSE 11.1
> > > > > > >   Kernel: 2.6.27.23-0.1-xen
> > > > > > >
> > > > > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
> > > > > > > card is recognized by the driver, and any mixer (alsamixer,
> > > > > > > kmix) also recognizes the card.
> > > > > > >
> > > > > > > But playing back isn't possible. I tried speaker-test,
> > > > > > > audacity, amarok and aplay. Most applications  hang, some also
> > > > > > > produce an error in the /var/log/messages (see
> > > > > > > below).
> > > > > > >
> > > > > > > I then used "./configure --with-debug=full --with-cards=ctxfi"
> > > > > > > due to the possible hd-audio conflict, but it didn't make a
> > > > > > > difference.
> > > > > > >
> > > > > > > Is there anything else I could try?
> > > > > >
> > > > > > I tested the same openSuSE version with a non-Xen 64 bit kernel,
> > > > > > and it doesn't work either.
> > > > > >
> > > > > > And I tried with this:
> > > > > >   Driver: alsa-driver-20090704.tar.bz2
> > > > > >   Distribution: Kubuntu Karmic Alpha-2
> > > > > >   Kernel: 2.6.30  (32 Bit)
> > > > > >
> > > > > > Under the latter setup the X-Fi Titanium works (Simple 2 channel
> > > > > > test with speaker-test, audacity, amarok). :-))
> > > > >
> > > > > How many RAM do you have?
> > > > > Could you boot with the limited memory size?
> > > >
> > > > It is just 2GB. So I am not limited by the 32 bit barrier.
> > > >
> > > > So booting with "limited" memory size doesn't make sense, right?
> > >
> > > Supposedly.  Is it emu20k1 or emu20k2?
> >
> > I checked it again: It is a 20k2 chip.
> >
> > /var/log/boot.msg says:
> > <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi:
> > chip 20K2 model SB0880 (1102:0041) is found
> >
> >
> > http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
> > series [EMU20k2]".
>
> I did now test it with a different 64 Bit Linux distribution, and it works
> correctly:
> Driver: alsa-driver-20090712.tar.bz2
> Distribution: Kubuntu Karmic Alpha-2
> Kernel: 2.6.30  (64 Bit)
>
> All in all, I can produce a working environment with recent 32 and 64 bit
> kernels. This is good news.  :-)
>
> Below is the summary on the tested distributions.
>
>   Christian
>
>
> So we got this:
> Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
> Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
> SuSE 11.1 64 Bit,  2.0.27 (does not work)
> SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
> SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated
> problems) => I'll see whether I can redo the SuSE11.2 tests, after doing a
> bugreport at openSuSE.

OK, that SuSE11.2 Milestone3  bug has been fixed, but Milestone4 has ALSA (at 
least soundcore)  built in the Kernel - I think I'll just give up further 
testing until that gets "fixed".

Well, in any case this is a postive report: It works with both 32 and 64 bit 
2.0.30 kernels (using Kubuntu Karmic-Alpha-2). 

  Christian

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 5 Aug 2009 23:21:53 +0200,
Christian Esken wrote:
> 
> Am Sonntag 12 Juli 2009 16:07:49 schrieb Christian Esken:
> > Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
> > > Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> > > > At Sun, 5 Jul 2009 13:29:48 +0200,
> > > >
> > > > Christian Esken wrote:
> > > > > Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > > > > > At Sun, 5 Jul 2009 00:19:55 +0200,
> > > > > >
> > > > > > Christian Esken wrote:
> > > > > > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > unfortunately I cannot playback anything (PCM) with the new SB
> > > > > > > > X-Fi driver. Driver:
> > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/als
> > > > > > > >a- driver-snapshot.tar.bz2
> > > > > > > >   Distribution: openSuSE 11.1
> > > > > > > >   Kernel: 2.6.27.23-0.1-xen
> > > > > > > >
> > > > > > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
> > > > > > > > card is recognized by the driver, and any mixer (alsamixer,
> > > > > > > > kmix) also recognizes the card.
> > > > > > > >
> > > > > > > > But playing back isn't possible. I tried speaker-test,
> > > > > > > > audacity, amarok and aplay. Most applications  hang, some also
> > > > > > > > produce an error in the /var/log/messages (see
> > > > > > > > below).
> > > > > > > >
> > > > > > > > I then used "./configure --with-debug=full --with-cards=ctxfi"
> > > > > > > > due to the possible hd-audio conflict, but it didn't make a
> > > > > > > > difference.
> > > > > > > >
> > > > > > > > Is there anything else I could try?
> > > > > > >
> > > > > > > I tested the same openSuSE version with a non-Xen 64 bit kernel,
> > > > > > > and it doesn't work either.
> > > > > > >
> > > > > > > And I tried with this:
> > > > > > >   Driver: alsa-driver-20090704.tar.bz2
> > > > > > >   Distribution: Kubuntu Karmic Alpha-2
> > > > > > >   Kernel: 2.6.30  (32 Bit)
> > > > > > >
> > > > > > > Under the latter setup the X-Fi Titanium works (Simple 2 channel
> > > > > > > test with speaker-test, audacity, amarok). :-))
> > > > > >
> > > > > > How many RAM do you have?
> > > > > > Could you boot with the limited memory size?
> > > > >
> > > > > It is just 2GB. So I am not limited by the 32 bit barrier.
> > > > >
> > > > > So booting with "limited" memory size doesn't make sense, right?
> > > >
> > > > Supposedly.  Is it emu20k1 or emu20k2?
> > >
> > > I checked it again: It is a 20k2 chip.
> > >
> > > /var/log/boot.msg says:
> > > <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi:
> > > chip 20K2 model SB0880 (1102:0041) is found
> > >
> > >
> > > http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
> > > series [EMU20k2]".
> >
> > I did now test it with a different 64 Bit Linux distribution, and it works
> > correctly:
> > Driver: alsa-driver-20090712.tar.bz2
> > Distribution: Kubuntu Karmic Alpha-2
> > Kernel: 2.6.30  (64 Bit)
> >
> > All in all, I can produce a working environment with recent 32 and 64 bit
> > kernels. This is good news.  :-)
> >
> > Below is the summary on the tested distributions.
> >
> >   Christian
> >
> >
> > So we got this:
> > Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
> > Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
> > SuSE 11.1 64 Bit,  2.0.27 (does not work)
> > SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
> > SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated
> > problems) => I'll see whether I can redo the SuSE11.2 tests, after doing a
> > bugreport at openSuSE.
> 
> OK, that SuSE11.2 Milestone3  bug has been fixed, but Milestone4 has ALSA (at 
> least soundcore)  built in the Kernel - I think I'll just give up further 
> testing until that gets "fixed".

FYI, in the latest SUSE kernel, both are fixed: ALSA core is module
again and the latest X-Fi code is already merged there.  So you don't
have to use snapshot version at all for X-Fi.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

I know the creative driver is in the kernel now for x-fi, but are there 
ever plans to at least have as much support for the SB0670 version of 
this product as the xfi drivers from creative?

On 08/06/2009 02:05 AM, Takashi Iwai wrote:
> At Wed, 5 Aug 2009 23:21:53 +0200,
> Christian Esken wrote:
>    
>> Am Sonntag 12 Juli 2009 16:07:49 schrieb Christian Esken:
>>      
>>> Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
>>>        
>>>> Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
>>>>          
>>>>> At Sun, 5 Jul 2009 13:29:48 +0200,
>>>>>
>>>>> Christian Esken wrote:
>>>>>            
>>>>>> Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
>>>>>>              
>>>>>>> At Sun, 5 Jul 2009 00:19:55 +0200,
>>>>>>>
>>>>>>> Christian Esken wrote:
>>>>>>>                
>>>>>>>> Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
>>>>>>>>                  
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> unfortunately I cannot playback anything (PCM) with the new SB
>>>>>>>>> X-Fi driver. Driver:
>>>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/als
>>>>>>>>> a- driver-snapshot.tar.bz2
>>>>>>>>>    Distribution: openSuSE 11.1
>>>>>>>>>    Kernel: 2.6.27.23-0.1-xen
>>>>>>>>>
>>>>>>>>> My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
>>>>>>>>> card is recognized by the driver, and any mixer (alsamixer,
>>>>>>>>> kmix) also recognizes the card.
>>>>>>>>>
>>>>>>>>> But playing back isn't possible. I tried speaker-test,
>>>>>>>>> audacity, amarok and aplay. Most applications  hang, some also
>>>>>>>>> produce an error in the /var/log/messages (see
>>>>>>>>> below).
>>>>>>>>>
>>>>>>>>> I then used "./configure --with-debug=full --with-cards=ctxfi"
>>>>>>>>> due to the possible hd-audio conflict, but it didn't make a
>>>>>>>>> difference.
>>>>>>>>>
>>>>>>>>> Is there anything else I could try?
>>>>>>>>>                    
>>>>>>>> I tested the same openSuSE version with a non-Xen 64 bit kernel,
>>>>>>>> and it doesn't work either.
>>>>>>>>
>>>>>>>> And I tried with this:
>>>>>>>>    Driver: alsa-driver-20090704.tar.bz2
>>>>>>>>    Distribution: Kubuntu Karmic Alpha-2
>>>>>>>>    Kernel: 2.6.30  (32 Bit)
>>>>>>>>
>>>>>>>> Under the latter setup the X-Fi Titanium works (Simple 2 channel
>>>>>>>> test with speaker-test, audacity, amarok). :-))
>>>>>>>>                  
>>>>>>> How many RAM do you have?
>>>>>>> Could you boot with the limited memory size?
>>>>>>>                
>>>>>> It is just 2GB. So I am not limited by the 32 bit barrier.
>>>>>>
>>>>>> So booting with "limited" memory size doesn't make sense, right?
>>>>>>              
>>>>> Supposedly.  Is it emu20k1 or emu20k2?
>>>>>            
>>>> I checked it again: It is a 20k2 chip.
>>>>
>>>> /var/log/boot.msg says:
>>>> <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi:
>>>> chip 20K2 model SB0880 (1102:0041) is found
>>>>
>>>>
>>>> http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
>>>> series [EMU20k2]".
>>>>          
>>> I did now test it with a different 64 Bit Linux distribution, and it works
>>> correctly:
>>> Driver: alsa-driver-20090712.tar.bz2
>>> Distribution: Kubuntu Karmic Alpha-2
>>> Kernel: 2.6.30  (64 Bit)
>>>
>>> All in all, I can produce a working environment with recent 32 and 64 bit
>>> kernels. This is good news.  :-)
>>>
>>> Below is the summary on the tested distributions.
>>>
>>>    Christian
>>>
>>>
>>> So we got this:
>>> Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
>>> Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
>>> SuSE 11.1 64 Bit,  2.0.27 (does not work)
>>> SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
>>> SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated
>>> problems) =>  I'll see whether I can redo the SuSE11.2 tests, after doing a
>>> bugreport at openSuSE.
>>>        
>> OK, that SuSE11.2 Milestone3  bug has been fixed, but Milestone4 has ALSA (at
>> least soundcore)  built in the Kernel - I think I'll just give up further
>> testing until that gets "fixed".
>>      
> FYI, in the latest SUSE kernel, both are fixed: ALSA core is module
> again and the latest X-Fi code is already merged there.  So you don't
> have to use snapshot version at all for X-Fi.
>
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>    

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 11 Nov 2009 16:01:49 -0600,
Ted T. Logan wrote:
> 
> I know the creative driver is in the kernel now for x-fi, but are there 
> ever plans to at least have as much support for the SB0670 version of 
> this product as the xfi drivers from creative?

No plan right now.  We definitely need more information *and* more
testers who have the same problem, in addition to free hours for
development.  All are missing for the time being...


Takashi

> On 08/06/2009 02:05 AM, Takashi Iwai wrote:
> > At Wed, 5 Aug 2009 23:21:53 +0200,
> > Christian Esken wrote:
> >    
> >> Am Sonntag 12 Juli 2009 16:07:49 schrieb Christian Esken:
> >>      
> >>> Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
> >>>        
> >>>> Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> >>>>          
> >>>>> At Sun, 5 Jul 2009 13:29:48 +0200,
> >>>>>
> >>>>> Christian Esken wrote:
> >>>>>            
> >>>>>> Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> >>>>>>              
> >>>>>>> At Sun, 5 Jul 2009 00:19:55 +0200,
> >>>>>>>
> >>>>>>> Christian Esken wrote:
> >>>>>>>                
> >>>>>>>> Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> >>>>>>>>                  
> >>>>>>>>> Hello,
> >>>>>>>>>
> >>>>>>>>> unfortunately I cannot playback anything (PCM) with the new SB
> >>>>>>>>> X-Fi driver. Driver:
> >>>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/als
> >>>>>>>>> a- driver-snapshot.tar.bz2
> >>>>>>>>>    Distribution: openSuSE 11.1
> >>>>>>>>>    Kernel: 2.6.27.23-0.1-xen
> >>>>>>>>>
> >>>>>>>>> My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
> >>>>>>>>> card is recognized by the driver, and any mixer (alsamixer,
> >>>>>>>>> kmix) also recognizes the card.
> >>>>>>>>>
> >>>>>>>>> But playing back isn't possible. I tried speaker-test,
> >>>>>>>>> audacity, amarok and aplay. Most applications  hang, some also
> >>>>>>>>> produce an error in the /var/log/messages (see
> >>>>>>>>> below).
> >>>>>>>>>
> >>>>>>>>> I then used "./configure --with-debug=full --with-cards=ctxfi"
> >>>>>>>>> due to the possible hd-audio conflict, but it didn't make a
> >>>>>>>>> difference.
> >>>>>>>>>
> >>>>>>>>> Is there anything else I could try?
> >>>>>>>>>                    
> >>>>>>>> I tested the same openSuSE version with a non-Xen 64 bit kernel,
> >>>>>>>> and it doesn't work either.
> >>>>>>>>
> >>>>>>>> And I tried with this:
> >>>>>>>>    Driver: alsa-driver-20090704.tar.bz2
> >>>>>>>>    Distribution: Kubuntu Karmic Alpha-2
> >>>>>>>>    Kernel: 2.6.30  (32 Bit)
> >>>>>>>>
> >>>>>>>> Under the latter setup the X-Fi Titanium works (Simple 2 channel
> >>>>>>>> test with speaker-test, audacity, amarok). :-))
> >>>>>>>>                  
> >>>>>>> How many RAM do you have?
> >>>>>>> Could you boot with the limited memory size?
> >>>>>>>                
> >>>>>> It is just 2GB. So I am not limited by the 32 bit barrier.
> >>>>>>
> >>>>>> So booting with "limited" memory size doesn't make sense, right?
> >>>>>>              
> >>>>> Supposedly.  Is it emu20k1 or emu20k2?
> >>>>>            
> >>>> I checked it again: It is a 20k2 chip.
> >>>>
> >>>> /var/log/boot.msg says:
> >>>> <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi:
> >>>> chip 20K2 model SB0880 (1102:0041) is found
> >>>>
> >>>>
> >>>> http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
> >>>> series [EMU20k2]".
> >>>>          
> >>> I did now test it with a different 64 Bit Linux distribution, and it works
> >>> correctly:
> >>> Driver: alsa-driver-20090712.tar.bz2
> >>> Distribution: Kubuntu Karmic Alpha-2
> >>> Kernel: 2.6.30  (64 Bit)
> >>>
> >>> All in all, I can produce a working environment with recent 32 and 64 bit
> >>> kernels. This is good news.  :-)
> >>>
> >>> Below is the summary on the tested distributions.
> >>>
> >>>    Christian
> >>>
> >>>
> >>> So we got this:
> >>> Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
> >>> Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
> >>> SuSE 11.1 64 Bit,  2.0.27 (does not work)
> >>> SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
> >>> SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated
> >>> problems) =>  I'll see whether I can redo the SuSE11.2 tests, after doing a
> >>> bugreport at openSuSE.
> >>>        
> >> OK, that SuSE11.2 Milestone3  bug has been fixed, but Milestone4 has ALSA (at
> >> least soundcore)  built in the Kernel - I think I'll just give up further
> >> testing until that gets "fixed".
> >>      
> > FYI, in the latest SUSE kernel, both are fixed: ALSA core is module
> > again and the latest X-Fi code is already merged there.  So you don't
> > have to use snapshot version at all for X-Fi.
> >
> >
> > Takashi
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >    
> 

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Upon upgrading to fedora core 12 and it's kernel and various libraries,
etc., my sb0670 xfi works with included kernel drivers.





On Thu, 2009-08-06 at 09:05 +0200, Takashi Iwai wrote:

> At Wed, 5 Aug 2009 23:21:53 +0200,
> Christian Esken wrote:
> > 
> > Am Sonntag 12 Juli 2009 16:07:49 schrieb Christian Esken:
> > > Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
> > > > Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> > > > > At Sun, 5 Jul 2009 13:29:48 +0200,
> > > > >
> > > > > Christian Esken wrote:
> > > > > > Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > > > > > > At Sun, 5 Jul 2009 00:19:55 +0200,
> > > > > > >
> > > > > > > Christian Esken wrote:
> > > > > > > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > > > > > > Hello,
> > > > > > > > >
> > > > > > > > > unfortunately I cannot playback anything (PCM) with the new SB
> > > > > > > > > X-Fi driver. Driver:
> > > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/als
> > > > > > > > >a- driver-snapshot.tar.bz2
> > > > > > > > >   Distribution: openSuSE 11.1
> > > > > > > > >   Kernel: 2.6.27.23-0.1-xen
> > > > > > > > >
> > > > > > > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
> > > > > > > > > card is recognized by the driver, and any mixer (alsamixer,
> > > > > > > > > kmix) also recognizes the card.
> > > > > > > > >
> > > > > > > > > But playing back isn't possible. I tried speaker-test,
> > > > > > > > > audacity, amarok and aplay. Most applications  hang, some also
> > > > > > > > > produce an error in the /var/log/messages (see
> > > > > > > > > below).
> > > > > > > > >
> > > > > > > > > I then used "./configure --with-debug=full --with-cards=ctxfi"
> > > > > > > > > due to the possible hd-audio conflict, but it didn't make a
> > > > > > > > > difference.
> > > > > > > > >
> > > > > > > > > Is there anything else I could try?
> > > > > > > >
> > > > > > > > I tested the same openSuSE version with a non-Xen 64 bit kernel,
> > > > > > > > and it doesn't work either.
> > > > > > > >
> > > > > > > > And I tried with this:
> > > > > > > >   Driver: alsa-driver-20090704.tar.bz2
> > > > > > > >   Distribution: Kubuntu Karmic Alpha-2
> > > > > > > >   Kernel: 2.6.30  (32 Bit)
> > > > > > > >
> > > > > > > > Under the latter setup the X-Fi Titanium works (Simple 2 channel
> > > > > > > > test with speaker-test, audacity, amarok). :-))
> > > > > > >
> > > > > > > How many RAM do you have?
> > > > > > > Could you boot with the limited memory size?
> > > > > >
> > > > > > It is just 2GB. So I am not limited by the 32 bit barrier.
> > > > > >
> > > > > > So booting with "limited" memory size doesn't make sense, right?
> > > > >
> > > > > Supposedly.  Is it emu20k1 or emu20k2?
> > > >
> > > > I checked it again: It is a 20k2 chip.
> > > >
> > > > /var/log/boot.msg says:
> > > > <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi:
> > > > chip 20K2 model SB0880 (1102:0041) is found
> > > >
> > > >
> > > > http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
> > > > series [EMU20k2]".
> > >
> > > I did now test it with a different 64 Bit Linux distribution, and it works
> > > correctly:
> > > Driver: alsa-driver-20090712.tar.bz2
> > > Distribution: Kubuntu Karmic Alpha-2
> > > Kernel: 2.6.30  (64 Bit)
> > >
> > > All in all, I can produce a working environment with recent 32 and 64 bit
> > > kernels. This is good news.  :-)
> > >
> > > Below is the summary on the tested distributions.
> > >
> > >   Christian
> > >
> > >
> > > So we got this:
> > > Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
> > > Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
> > > SuSE 11.1 64 Bit,  2.0.27 (does not work)
> > > SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
> > > SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated
> > > problems) => I'll see whether I can redo the SuSE11.2 tests, after doing a
> > > bugreport at openSuSE.
> > 
> > OK, that SuSE11.2 Milestone3  bug has been fixed, but Milestone4 has ALSA (at 
> > least soundcore)  built in the Kernel - I think I'll just give up further 
> > testing until that gets "fixed".
> 
> FYI, in the latest SUSE kernel, both are fixed: ALSA core is module
> again and the latest X-Fi code is already merged there.  So you don't
> have to use snapshot version at all for X-Fi.
> 
> 
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Tue, 17 Nov 2009 17:38:05 -0600,
Ted T. Logan wrote:
> 
> Upon upgrading to fedora core 12 and it's kernel and various libraries,
> etc., my sb0670 xfi works with included kernel drivers.

Interesting.  So, I'm wondering whether this was really a kernel issue.


Takashi


> On Thu, 2009-08-06 at 09:05 +0200, Takashi Iwai wrote:
> 
> > At Wed, 5 Aug 2009 23:21:53 +0200,
> > Christian Esken wrote:
> > > 
> > > Am Sonntag 12 Juli 2009 16:07:49 schrieb Christian Esken:
> > > > Am Sonntag 12 Juli 2009 10:24:35 schrieb Christian Esken:
> > > > > Am Montag 06 Juli 2009 08:26:11 schrieb Takashi Iwai:
> > > > > > At Sun, 5 Jul 2009 13:29:48 +0200,
> > > > > >
> > > > > > Christian Esken wrote:
> > > > > > > Am Sonntag 05 Juli 2009 09:44:33 schrieb Takashi Iwai:
> > > > > > > > At Sun, 5 Jul 2009 00:19:55 +0200,
> > > > > > > >
> > > > > > > > Christian Esken wrote:
> > > > > > > > > Am Samstag 27 Juni 2009 14:05:45 schrieb Christian Esken:
> > > > > > > > > > Hello,
> > > > > > > > > >
> > > > > > > > > > unfortunately I cannot playback anything (PCM) with the new SB
> > > > > > > > > > X-Fi driver. Driver:
> > > > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/als
> > > > > > > > > >a- driver-snapshot.tar.bz2
> > > > > > > > > >   Distribution: openSuSE 11.1
> > > > > > > > > >   Kernel: 2.6.27.23-0.1-xen
> > > > > > > > > >
> > > > > > > > > > My card is a "X-Fi Titanium" (PCI device code: 1102:000b). The
> > > > > > > > > > card is recognized by the driver, and any mixer (alsamixer,
> > > > > > > > > > kmix) also recognizes the card.
> > > > > > > > > >
> > > > > > > > > > But playing back isn't possible. I tried speaker-test,
> > > > > > > > > > audacity, amarok and aplay. Most applications  hang, some also
> > > > > > > > > > produce an error in the /var/log/messages (see
> > > > > > > > > > below).
> > > > > > > > > >
> > > > > > > > > > I then used "./configure --with-debug=full --with-cards=ctxfi"
> > > > > > > > > > due to the possible hd-audio conflict, but it didn't make a
> > > > > > > > > > difference.
> > > > > > > > > >
> > > > > > > > > > Is there anything else I could try?
> > > > > > > > >
> > > > > > > > > I tested the same openSuSE version with a non-Xen 64 bit kernel,
> > > > > > > > > and it doesn't work either.
> > > > > > > > >
> > > > > > > > > And I tried with this:
> > > > > > > > >   Driver: alsa-driver-20090704.tar.bz2
> > > > > > > > >   Distribution: Kubuntu Karmic Alpha-2
> > > > > > > > >   Kernel: 2.6.30  (32 Bit)
> > > > > > > > >
> > > > > > > > > Under the latter setup the X-Fi Titanium works (Simple 2 channel
> > > > > > > > > test with speaker-test, audacity, amarok). :-))
> > > > > > > >
> > > > > > > > How many RAM do you have?
> > > > > > > > Could you boot with the limited memory size?
> > > > > > >
> > > > > > > It is just 2GB. So I am not limited by the 32 bit barrier.
> > > > > > >
> > > > > > > So booting with "limited" memory size doesn't make sense, right?
> > > > > >
> > > > > > Supposedly.  Is it emu20k1 or emu20k2?
> > > > >
> > > > > I checked it again: It is a 20k2 chip.
> > > > >
> > > > > /var/log/boot.msg says:
> > > > > <7>ALSA /home/chris/Desktop/alsa-driver/pci/ctxfi/ctatc.c:1268: ctxfi:
> > > > > chip 20K2 model SB0880 (1102:0041) is found
> > > > >
> > > > >
> > > > > http://pci-ids.ucw.cz/mods/PC/1102/000b shows 1102:0041 as "X-Fi Titanium
> > > > > series [EMU20k2]".
> > > >
> > > > I did now test it with a different 64 Bit Linux distribution, and it works
> > > > correctly:
> > > > Driver: alsa-driver-20090712.tar.bz2
> > > > Distribution: Kubuntu Karmic Alpha-2
> > > > Kernel: 2.6.30  (64 Bit)
> > > >
> > > > All in all, I can produce a working environment with recent 32 and 64 bit
> > > > kernels. This is good news.  :-)
> > > >
> > > > Below is the summary on the tested distributions.
> > > >
> > > >   Christian
> > > >
> > > >
> > > > So we got this:
> > > > Kubuntu Karmic Alpha-2 32 Bit, 2.0.30 (works)
> > > > Kubuntu Karmic Alpha-2 64 Bit, 2.0.30 (works)
> > > > SuSE 11.1 64 Bit,  2.0.27 (does not work)
> > > > SuSE 11.1 64 Bit,  2.0.27 XEN (does not work)
> > > > SuSE 11.2 Milestone3  64Bit, 2.0.30 (test canceled, due to unrelated
> > > > problems) => I'll see whether I can redo the SuSE11.2 tests, after doing a
> > > > bugreport at openSuSE.
> > > 
> > > OK, that SuSE11.2 Milestone3  bug has been fixed, but Milestone4 has ALSA (at 
> > > least soundcore)  built in the Kernel - I think I'll just give up further 
> > > testing until that gets "fixed".
> > 
> > FYI, in the latest SUSE kernel, both are fixed: ALSA core is module
> > again and the latest X-Fi code is already merged there.  So you don't
> > have to use snapshot version at all for X-Fi.
> > 
> > 
> > Takashi
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 
> 
> [2  <text/html; utf-8 (7bit)>]
> 

Testers wanted: New SB X-Fi driver

[Christian Paredes]

Hi everyone,

So I have an Auzentech X-Fi Forte PCI-E card, and I got it to output
sound through the side and center/LFE channels.  When I output sound
through the center channel, it is correctly routed to the center
channel, but when sound is output to the LFE channel, it is output to
both of my front speakers.

I am running on kernel 2.6.28, fresh install of Ubuntu 9.04.  This
also happens on kernel 2.6.30 on Arch Linux.

Let me know what sort of information you guys need!

Thanks,

Christian

Re: Testers wanted: New SB X-Fi driver

[Christian Paredes]

I should probably add that I've used alsa-lib-07112009 and the latest
alsa-driver-unstable snapshot pulled from 07/11/2009.

-- Christian

On Sat, Jul 11, 2009 at 1:39 PM, Christian Paredes<merc248@gmail.com> wrote:
> Hi everyone,
>
> So I have an Auzentech X-Fi Forte PCI-E card, and I got it to output
> sound through the side and center/LFE channels.  When I output sound
> through the center channel, it is correctly routed to the center
> channel, but when sound is output to the LFE channel, it is output to
> both of my front speakers.
>
> I am running on kernel 2.6.28, fresh install of Ubuntu 9.04.  This
> also happens on kernel 2.6.30 on Arch Linux.
>
> Let me know what sort of information you guys need!
>
> Thanks,
>
> Christian
>

Testers wanted: New SB X-Fi driver

[Duke Grable]

Hello!

I stumbled upon these X-Fi drivers recently and ended up giving them a try.
So far they work flawlessly, except for microphone input... I'm wondering if
this is either just unimplemented, or if it's just an issue of
configuration? My sound card is an "X-Fi XtremeGamer" and my distro is the
latest version of openSuSe (2.6.27.23-0.1-default
). Let me know if I'm missing anything!

Thanks,
Duke

Re: Testers wanted: New SB X-Fi driver

[Gernot Kohlhaas]

Hi!
Try to unmute the "Line-In" Playback-device.

Duke Grable schrieb:
> Hello!
> 
> I stumbled upon these X-Fi drivers recently and ended up giving them a try.
> So far they work flawlessly, except for microphone input... I'm wondering if
> this is either just unimplemented, or if it's just an issue of
> configuration? My sound card is an "X-Fi XtremeGamer" and my distro is the
> latest version of openSuSe (2.6.27.23-0.1-default
> ). Let me know if I'm missing anything!
> 
> Thanks,
> Duke
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 


-- 
http://www.gnupp.de/verschluesselung/warum.html
Key ID: 0x4C0B2250
Key: http://home.arcor.de/mr_maniac/ANDERES/public.gpg

Re: Testers wanted: New SB X-Fi driver

[Duke Grable]

It seems like my problem was even stranger than that. For some reason the
only mute option for it under kmix or pulseaudio are through their taskbar
icons. If I remember correctly, I set my mic as master then unmuted it
through the one of icon's menu. That made it possible to hear my mic through
my speaker. Then a program called "gamix" solved my recording issues. Pretty
interesting. Loving these drivers either way though.

Thanks,
Duke

On Sun, Jul 5, 2009 at 5:07 AM, Gernot Kohlhaas <
gernot.kohlhaas@googlemail.com> wrote:

> Hi!
> Try to unmute the "Line-In" Playback-device.
>
> Duke Grable schrieb:
> > Hello!
> >
> > I stumbled upon these X-Fi drivers recently and ended up giving them a
> try.
> > So far they work flawlessly, except for microphone input... I'm wondering
> if
> > this is either just unimplemented, or if it's just an issue of
> > configuration? My sound card is an "X-Fi XtremeGamer" and my distro is
> the
> > latest version of openSuSe (2.6.27.23-0.1-default
> > ). Let me know if I'm missing anything!
> >
> > Thanks,
> > Duke
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
>
>
> --
> http://www.gnupp.de/verschluesselung/warum.html
> Key ID: 0x4C0B2250
> Key: http://home.arcor.de/mr_maniac/ANDERES/public.gpg
>

Re: Testers wanted: New SB X-Fi driver

[Ted T. Logan]

Am I missing something?  I got this new driver and did cvscompile then
make install, but it didn't install any xfi stuff.


# ctxfi
alias snd-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-ctxfi
options snd-ctfxi index=0


what am I missing?  I don't have an ssound dir either.
On Sun, 2009-07-05 at 01:38 -0700, Duke Grable wrote: 

> Hello!
> 
> I stumbled upon these X-Fi drivers recently and ended up giving them a try.
> So far they work flawlessly, except for microphone input... I'm wondering if
> this is either just unimplemented, or if it's just an issue of
> configuration? My sound card is an "X-Fi XtremeGamer" and my distro is the
> latest version of openSuSe (2.6.27.23-0.1-default
> ). Let me know if I'm missing anything!
> 
> Thanks,
> Duke
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Testers wanted: New SB X-Fi driver

[Matthias Diehl]

> At Tue, 30 Jun 2009 16:10:45 +0200,
> Matthias Diehl wrote:
> > 
> > hi,
> > 
> > i guess you dont speak german, do you? well, i'll try it in 
> english ;-)
> > 
> > i tried to install your newest x-fi "hack" in ubuntu 9.04 64bit. 
> it's an x-fi extreme music. i downloaded this snapshot:
>> 
>
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
>
> Use alsa-driver-snapshot.tar.gz instead of the unstable one.
>
> > while the installation process there are some warnings. after 
> replacing the demon.conf and reboot there was no sound. 
> > 
> > then i noticed the sentence "Note that the ctxfi driver might 
> conflict with the HD-audio driver" in the description. i think my
> problem is the hdmi soundchip from my graphics adapter (sapphire 
> radeon hd 4870) which was automatically installed at the 
> ubuntu-installation 
> ("hda intel sound").
>
> You are likely looking at irrelevant things.
>
> There are several variants of X-Fi boards. Many of them are equipped
> with emu20k1 or emu20k2 chip. Some of these models can behave as
> HD-audio compatible, too. These are supported by snd-ctxfi driver.
>
> In addition, there is X-Fi models that are without emu20k1/emu20k2
> chips. Some of them (CA0110-IBG) behave only as a HD-audio device,
> and some others are with CA0106 chip. The former is supported by
> snd-hda-intel driver and the latter by snd-ca0106 driver.
>
> So, they cannot be deactivated. The only question is whether you have
> emu20k1/emu20k2 chip on your board. And this can be checked when you
> load snd-ctxfi driver. If the driver is properly loaded and the
> card instance is created (see /proc/asound/cards), then it's good.
> Otherwise, your board is no such one. You need other drivers.
>
> Please ask further questions on alsa-devel ML (you can add me to Cc,
> though) so that other people with your board can advice better.
>
>
> HTH,
>
> Takashi

hi there,

i now tried to install the stable version, but i have still no sound.
here's what lspci | grep audio says:
01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
05:00.0 Multimedia audio controller: Creative Labs SB X-Fi

lsmod | grep snd says:
snd_hda_intel         557492  1 
snd_pcm_oss            52352  0 
snd_mixer_oss          24960  2 snd_pcm_oss
snd_pcm                99336  2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy          11524  0 
snd_seq_oss            41984  0 
snd_seq_midi           15744  0 
snd_rawmidi            33920  1 snd_seq_midi
snd_seq_midi_event     16512  2 snd_seq_oss,snd_seq_midi
snd_seq                66272  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer              34064  2 snd_pcm,snd_seq
snd_seq_device         16276  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd                    78792  9 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore              16800  2 snd
snd_page_alloc         18704  2 snd_hda_intel,snd_pcm

cat /proc/asound/cards says: 
 0 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xf7dfc000 irq 17

i hope, someone can help me ...
greetings from germany,
matthias

Re: Testers wanted: New SB X-Fi driver

[Christian Esken]

Am Dienstag 30 Juni 2009 19:55:44 schrieb Matthias Diehl:
> > At Tue, 30 Jun 2009 16:10:45 +0200,
> >
> > Matthias Diehl wrote:
> > > hi,
> > >
> > > i guess you dont speak german, do you? well, i'll try it in
> >
> > english ;-)
> >
> > > i tried to install your newest x-fi "hack" in ubuntu 9.04 64bit.

Interesting enough, I don't manage to get it working under 64 ("SuSE 11.1, 64 
Bit, Xen") bit either. Could you check if you also see something in your 
syslog (e.g. /var/log/messages) when running speaker-test ? 

When I tested the same on the same hardware  on "Kubuntu  Karmic alpha 2, 32 
bit", I get sound.

It might be an indication of a either:
- a 32/64 bit issue
- the kernel version (Kubuntu karmic ships with 2.6.30)
- Xen vs non-Xen
- something else

   Christian

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sat, 4 Jul 2009 23:27:04 +0200,
Christian Esken wrote:
> 
> Am Dienstag 30 Juni 2009 19:55:44 schrieb Matthias Diehl:
> > > At Tue, 30 Jun 2009 16:10:45 +0200,
> > >
> > > Matthias Diehl wrote:
> > > > hi,
> > > >
> > > > i guess you dont speak german, do you? well, i'll try it in
> > >
> > > english ;-)
> > >
> > > > i tried to install your newest x-fi "hack" in ubuntu 9.04 64bit.
> 
> Interesting enough, I don't manage to get it working under 64 ("SuSE 11.1, 64 
> Bit, Xen") bit either. Could you check if you also see something in your 
> syslog (e.g. /var/log/messages) when running speaker-test ? 
> 
> When I tested the same on the same hardware  on "Kubuntu  Karmic alpha 2, 32 
> bit", I get sound.
> 
> It might be an indication of a either:
> - a 32/64 bit issue
> - the kernel version (Kubuntu karmic ships with 2.6.30)
> - Xen vs non-Xen
> - something else

The 64bit issue might depend on the card model.
Which model do you have?  You can see in /proc/asound/cards.
What about the patch below?


Takashi

---
diff --git a/sound/pci/ctxfi/cthw20k1.c b/sound/pci/ctxfi/cthw20k1.c
index ad3e1d1..bab0203 100644
--- a/sound/pci/ctxfi/cthw20k1.c
+++ b/sound/pci/ctxfi/cthw20k1.c
@@ -1275,7 +1275,7 @@ static int hw_trn_init(struct hw *hw, const struct trn_conf *info)
 	trnctl = 0x13;  /* 32-bit, 4k-size page */
 	ptp_phys_low = (u32)info->vm_pgt_phys;
 	ptp_phys_high = upper_32_bits(info->vm_pgt_phys);
-	if (sizeof(void *) == 8) /* 64bit address */
+	if (ptp_phys_high) /* 64bit address */
 		trnctl |= (1 << 2);
 #if 0 /* Only 4k h/w pages for simplicitiy */
 #if PAGE_SIZE == 8192
diff --git a/sound/pci/ctxfi/cthw20k2.c b/sound/pci/ctxfi/cthw20k2.c
index 0c4db2d..269c7f1 100644
--- a/sound/pci/ctxfi/cthw20k2.c
+++ b/sound/pci/ctxfi/cthw20k2.c
@@ -1237,7 +1237,7 @@ static int hw_trn_init(struct hw *hw, const struct trn_conf *info)
 	vmctl = 0x80000C0F;  /* 32-bit, 4k-size page */
 	ptp_phys_low = (u32)info->vm_pgt_phys;
 	ptp_phys_high = upper_32_bits(info->vm_pgt_phys);
-	if (sizeof(void *) == 8) /* 64bit address */
+	if (ptp_phys_high) /* 64bit address */
 		vmctl |= (3 << 8);
 	/* Write page table physical address to all PTPAL registers */
 	for (i = 0; i < 64; i++) {

Re: Testers wanted: New SB X-Fi driver

[周吴军]

I also use the ubuntu 904 64bit,and a similar hardware,
 it works for me pretty well .now I can hear 5.1 sound just like the windows
driver  offer

have you intslled soundcard driver?
I use the following install stage
$./configure --with-card=ctxfi
$make
$sudo  make modules install

and then restart(if not the old alsa code will make snd-ctxfi driver module
unloadable)
$sudo modprobe snd-ctxfi

and if it still not work please give some information about $dmesg

here's what lspci | grep audio says:
01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
03:02.0 Multimedia audio controller: Creative Labs SB X-Fi

cat /proc/asound/cards says:
0 [XFi            ]: SB-XFi - Creative X-Fi
                      Creative X-Fi 20K1 Unknown
lsmod|grep xfi
snd_ctxfi             102376  3
snd_pcm                99336  2 snd_ctxfi,snd_pcm_oss
snd                    77256  15
snd_ctxfi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq,snd_timer,snd_seq_device




On Wed, Jul 1, 2009 at 1:55 AM, Matthias Diehl <mdiehl.os@gmx.de> wrote:

> > At Tue, 30 Jun 2009 16:10:45 +0200,
> > Matthias Diehl wrote:
> > >
> > > hi,
> > >
> > > i guess you dont speak german, do you? well, i'll try it in
> > english ;-)
> > >
> > > i tried to install your newest x-fi "hack" in ubuntu 9.04 64bit.
> > it's an x-fi extreme music. i downloaded this snapshot:
> >>
> >
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
> >
> > Use alsa-driver-snapshot.tar.gz instead of the unstable one.
> >
> > > while the installation process there are some warnings. after
> > replacing the demon.conf and reboot there was no sound.
> > >
> > > then i noticed the sentence "Note that the ctxfi driver might
> > conflict with the HD-audio driver" in the description. i think my
> > problem is the hdmi soundchip from my graphics adapter (sapphire
> > radeon hd 4870) which was automatically installed at the
> > ubuntu-installation
> > ("hda intel sound").
> >
> > You are likely looking at irrelevant things.
> >
> > There are several variants of X-Fi boards. Many of them are equipped
> > with emu20k1 or emu20k2 chip. Some of these models can behave as
> > HD-audio compatible, too. These are supported by snd-ctxfi driver.
> >
> > In addition, there is X-Fi models that are without emu20k1/emu20k2
> > chips. Some of them (CA0110-IBG) behave only as a HD-audio device,
> > and some others are with CA0106 chip. The former is supported by
> > snd-hda-intel driver and the latter by snd-ca0106 driver.
> >
> > So, they cannot be deactivated. The only question is whether you have
> > emu20k1/emu20k2 chip on your board. And this can be checked when you
> > load snd-ctxfi driver. If the driver is properly loaded and the
> > card instance is created (see /proc/asound/cards), then it's good.
> > Otherwise, your board is no such one. You need other drivers.
> >
> > Please ask further questions on alsa-devel ML (you can add me to Cc,
> > though) so that other people with your board can advice better.
> >
> >
> > HTH,
> >
> > Takashi
>
> hi there,
>
> i now tried to install the stable version, but i have still no sound.
> here's what lspci | grep audio says:
> 01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
> 05:00.0 Multimedia audio controller: Creative Labs SB X-Fi
>
> lsmod | grep snd says:
> snd_hda_intel         557492  1
> snd_pcm_oss            52352  0
> snd_mixer_oss          24960  2 snd_pcm_oss
> snd_pcm                99336  2 snd_hda_intel,snd_pcm_oss
> snd_seq_dummy          11524  0
> snd_seq_oss            41984  0
> snd_seq_midi           15744  0
> snd_rawmidi            33920  1 snd_seq_midi
> snd_seq_midi_event     16512  2 snd_seq_oss,snd_seq_midi
> snd_seq                66272  6
> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
> snd_timer              34064  2 snd_pcm,snd_seq
> snd_seq_device         16276  5
> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
> snd                    78792  9
> snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
> soundcore              16800  2 snd
> snd_page_alloc         18704  2 snd_hda_intel,snd_pcm
>
> cat /proc/asound/cards says:
>  0 [HDMI           ]: HDA-Intel - HDA ATI HDMI
>                      HDA ATI HDMI at 0xf7dfc000 irq 17
>
> i hope, someone can help me ...
> greetings from germany,
> matthias
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

Testers wanted: New SB X-Fi driver

[Gernot Kohlhaas]

Hi!

I found a little strange thing:
Recording from microphone is only possible, when you unmute the
"Line-In" playback-device (and set microphone as capture device, of course).

Oh, and by the way: Is there any possibility to apply a low pass filter
to the subwoofer-channel without using ladspa (xmms and audacious won't
play songs with my low pass filter. Mplayer, xine and aplay are working
fine).

Thanks again for this driver :)
-- 
http://www.gnupp.de/verschluesselung/warum.html
Key ID: 0x4C0B2250
Key: http://home.arcor.de/mr_maniac/ANDERES/public.gpg

Testers wanted: New SB X-Fi driver

[Gernot Kohlhaas]

Hi and thanks for this driver.
It works great and even 6- and 8-Channel-Output is supported now.

The only two little things I noticed are:
1. Most programs are looking for "surround51" to use for multichannel
sound. But this driver only provides the "default"-Device (in it's
description it says:

aplay -L
default:CARD=XFi
    Creative X-Fi, Front/WaveIn
    Default Audio Device

)

2. I can hear a gentle grumbling out of my speakers. But nothing serious.
-- 
http://www.gnupp.de/verschluesselung/warum.html
Key ID: 0x4C0B2250
Key: http://home.arcor.de/mr_maniac/ANDERES/public.gpg

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sat, 06 Jun 2009 21:02:42 +0200,
Gernot Kohlhaas wrote:
> 
> Hi and thanks for this driver.
> It works great and even 6- and 8-Channel-Output is supported now.
> 
> The only two little things I noticed are:
> 1. Most programs are looking for "surround51" to use for multichannel
> sound. But this driver only provides the "default"-Device (in it's
> description it says:
> 
> aplay -L
> default:CARD=XFi
>     Creative X-Fi, Front/WaveIn
>     Default Audio Device
> 
> )

Use the latest alsa-lib snapshot.  The config file for X-Fi is already
there.


> 2. I can hear a gentle grumbling out of my speakers. But nothing serious.

Do you hear it even with the volume under 60%?
The volume scale seems messy right now.  Don't set it too high.


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Alexey Bazhin]

On Mon, 08 Jun 2009 08:57:31 +0200
Takashi Iwai <tiwai@suse.de> wrote:

> At Sat, 06 Jun 2009 21:02:42 +0200,
> Gernot Kohlhaas wrote:
> > 
> > Hi and thanks for this driver.
> > It works great and even 6- and 8-Channel-Output is supported now.
> > 
> > The only two little things I noticed are:
> > 1. Most programs are looking for "surround51" to use for
> > multichannel sound. But this driver only provides the
> > "default"-Device (in it's description it says:
> > 
> > aplay -L
> > default:CARD=XFi
> >     Creative X-Fi, Front/WaveIn
> >     Default Audio Device
> > 
> > )
> 
> Use the latest alsa-lib snapshot.  The config file for X-Fi is already
> there.
Hmm... I see a definition for iec958 in SB-XFI.conf, but aplay -L
doesn't list it for my card.

root@mayonaka:~# aplay -L
default:CARD=XFi
    Creative X-Fi, Front/WaveIn
    Default Audio Device
front:CARD=XFi,DEV=0
    Creative X-Fi, Front/WaveIn
    Front speakers
surround40:CARD=XFi,DEV=0
    Creative X-Fi, Front/WaveIn
    4.0 Surround output to Front and Rear speakers
surround41:CARD=XFi,DEV=0
    Creative X-Fi, Front/WaveIn
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=XFi,DEV=0
    Creative X-Fi, Front/WaveIn
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=XFi,DEV=0
    Creative X-Fi, Front/WaveIn
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=XFi,DEV=0
    Creative X-Fi, Front/WaveIn
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
null
    Discard all samples (playback) or generate zero samples (capture)


-- 
 Alexey Bazhin
  mailto:baz@irc.msk.ru
  ICQ 125125882

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 8 Jun 2009 22:26:44 +0400,
Alexey Bazhin wrote:
> 
> On Mon, 08 Jun 2009 08:57:31 +0200
> Takashi Iwai <tiwai@suse.de> wrote:
> 
> > At Sat, 06 Jun 2009 21:02:42 +0200,
> > Gernot Kohlhaas wrote:
> > > 
> > > Hi and thanks for this driver.
> > > It works great and even 6- and 8-Channel-Output is supported now.
> > > 
> > > The only two little things I noticed are:
> > > 1. Most programs are looking for "surround51" to use for
> > > multichannel sound. But this driver only provides the
> > > "default"-Device (in it's description it says:
> > > 
> > > aplay -L
> > > default:CARD=XFi
> > >     Creative X-Fi, Front/WaveIn
> > >     Default Audio Device
> > > 
> > > )
> > 
> > Use the latest alsa-lib snapshot.  The config file for X-Fi is already
> > there.
> Hmm... I see a definition for iec958 in SB-XFI.conf, but aplay -L
> doesn't list it for my card.

Use the very latest GIT tree.  It's fixed now.


Takashi

Testers wanted: New SB X-Fi driver

[MonsieurWeller]

Hello.
Works fine, but the external rack of the "x-fi fatality" didn't seems to
work. I plug my headphone on it and i have no sound.
Thanks.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 04 Jun 2009 20:42:22 +0200,
MonsieurWeller wrote:
> 
> Hello.
> Works fine, but the external rack of the "x-fi fatality" didn't seems to
> work. I plug my headphone on it and i have no sound.

It's not supported yet.  That's a known issue.
(And don't ask me when it'll be supported -- only Creative guys know :)


Takashi

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sun, 07 Jun 2009 14:00:26 +0200,
MonsieurWeller wrote:
> 
> Thanks for reply. Hope Creative engineers read this :D.
> Two other little things :D:
> - The sound seems really really to loud compared to my audigy2 zs ( for
> the same level: pcm/master/etc... 74 in alsamixer for the audigy vs 26
> for the xfi)

Yes, it's a known issue.  100% doesn't correspond to 0dB but
overdriving. 0dB is about 70% or so, and the volume scale doesn't look 
logarithmic.

> - There's no cursor for bass and treble in alsamixer: not supported?

Not supported.  Some DSP code would be required, which isn't open
yet.


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 10 Jun 2009 18:21:55 +0200,
MonsieurWeller wrote:
> 
> Thanks for reply.
> (Very) last little thing: i've tried to use the x-fi external rack with
> my audigy2ZS (alsa driver 1.0.20 with emu10k1). And it seems to work (i
> have only tried with the headphone jack). Maybe it's the same thing?

Hard to tell, but it's anyway good to know.
Thanks for the information!


Takashi

Testers wanted: New SB X-Fi driver

[gantonop]

I have an X-FI Platinum.Though I hear sound, it is periodically interrupted.
More specifically every half a second an interrupt occurs producing a pause and
a "tsik" :) which of course is annoying.
So this has happened for every sound file I've tried to play.

Testers wanted: New SB X-Fi driver

[jimi o'beirne]

Takashi
Thanks so much for making this driver! Unfortunately, I'm a bit of a
newbie, how would I actually install the driver? I am using Ubuntu
Jaunty with a SB X-Fi card. 

Thanks for your help,

Jim

Testers wanted: New SB X-Fi driver

[Mario Contreras]

Hello, I have this card. Will the unstable version work with my card? I have
read it has a different chipset. I installed it a few days ago, but there
wasn't any sound. I have Ubuntu 9.04. When I test it in sound preferences it
freezes. I would like to test it. If I can be helpful, I'd appreciate you
help me. Than you.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 25 May 2009 09:53:17 +0200,
Mario Contreras wrote:
> 
> Hello, I have this card.

Which card?  There are tons of different variants, so please be specific.

> Will the unstable version work with my card? I have
> read it has a different chipset. I installed it a few days ago, but there
> wasn't any sound. I have Ubuntu 9.04. When I test it in sound preferences it
> freezes. I would like to test it. If I can be helpful, I'd appreciate you
> help me. Than you.

It's now in alsa-driver snapshot below, too.
    ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz

First check whether you install snd-ctxfi module.  If the device isn't
detected by this driver, it might be that yours aren't with emu20kx chip.
Please give lspci and lspci -nv output.


thanks,

Takashi

Testers wanted: New SB X-Fi driver

[Ge-org Brohammer]

Good day

I compiled and installed alsa-lib-1.0.20 and alsa-utils-1.0.20 and then your
driver on ubuntu Jaunty 64 bit.

I have the X-FI Music PCI card and it seems to split the outputs into
separate cards?

This is the output from aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: XFi [Creative X-Fi], device 0: Front/WaveIn [Front/WaveIn]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 1: Rear [Rear]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 2: Center/LFE [Center/LFE]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 3: Surround [Surround]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 4: IEC958 Non-audio [IEC958 Non-audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


This a problem for me because I cannot play all the channels at once either
front side rear, etc...

Let me know if any extra info is required.

Regards

Testers wanted: New SB X-Fi driver

[Marcel Mulders]

Hi Takashi,

I tried the snd-ctxfi driver on Ubuntu Jaunty x64. Seems to work just fine
for me. Audacious and Totem have no problems as far as I can see. Great
work, your efforts are very much appreciated!

I was wondering, is there any chance to get the headphones-output on the
frontpanel working? I don't really need all the other jacks to work, just
plain old analog stereo.. ;-)

In one of the closed-source drivers from Creative from a year ago or so,
version 1.18, that worked fine. In the opensource driver from last February,
the headphones were broken again, just like with the latest snapshot alsa
drivers. Can you comment on this maybe?

Thanks in advance.

Marcel

Testers wanted: New SB X-Fi driver

[Daniel Bankmann]

Hi!

I just tested the newest driver version with Open Suse 11.1 and
pae-kernel. I seems not to work probably, although the latest "official"
driver by Creative worked more or less good.

The problem is, that always, when hearing some music or any other sound,
the signal gets interrupted every few seconds. At the other side, the
startup jingle for example is accompanied by a knock every few seconds.

Any idea, or what information do you need to fix this?

Testers wanted: New SB X-Fi driver

[Ralf Koslowski]

hi Takashi..my Sound Blaster X-Fi XtremeMusic works fine with ubuntu x86-64 9.10 alpha 1! but no 5.1;-(.either front, rear or center but not 	altogether...

All the best! from germany

thanks, 
Ralf
-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Tue, 19 May 2009 00:35:56 +0200,
Ralf Koslowski wrote:
> 
> hi Takashi..my Sound Blaster X-Fi XtremeMusic works fine with ubuntu x86-64 9.10 alpha 1! but no 5.1;-(.either front, rear or center but not 	altogether...

It'd be possible either via the h/w routing or bundling the PCM streams.
But right now there is no setup done for such.
So, no bug but a feature for the time being :)


Takashi

Testers wanted: New SB X-Fi driver

[Noel Bourke]

Hi Takashi,

I set this up with an Auzentech X-Fi Prelude.
Driver works OK but sound seemed a bit off.
According to speaker-test I seem to only
have one audio channel!

Any thoughts?

Regards,
             Noel

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 18 May 2009 23:26:47 +0100,
Noel Bourke wrote:
> 
> Hi Takashi,
> 
> I set this up with an Auzentech X-Fi Prelude.
> Driver works OK but sound seemed a bit off.
> According to speaker-test I seem to only
> have one audio channel!
> 
> Any thoughts?

Please run alsa-info.sh with --no-upload option, and attach the
generated file.  This will show a bit more detailed driver
information.


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Noel Bourke]

I'm getting the following output from that script...
I took a look and couldn't find the problem.

alsa-info.sh: 365: [[: not found
ALSA Information Script v 0.4.56
--------------------------------

This script will collect information about your ALSA installation and sound
related hardware, to help diagnose your problem.

Do you want to run this script? [y/n] : read: 365: Illegal option -e

Thank you for using the ALSA-Info Script


On Tue, May 19, 2009 at 08:11, Takashi Iwai <tiwai@suse.de> wrote:

> At Mon, 18 May 2009 23:26:47 +0100,
> Noel Bourke wrote:
> >
> > Hi Takashi,
> >
> > I set this up with an Auzentech X-Fi Prelude.
> > Driver works OK but sound seemed a bit off.
> > According to speaker-test I seem to only
> > have one audio channel!
> >
> > Any thoughts?
>
> Please run alsa-info.sh with --no-upload option, and attach the
> generated file.  This will show a bit more detailed driver
> information.
>
>
> thanks,
>
> Takashi
>

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 20 May 2009 18:21:04 +0100,
Noel Bourke wrote:
> 
> I'm getting the following output from that script...
> I took a look and couldn't find the problem.
> 
> alsa-info.sh: 365: [[: not found

You must be using a shell that doesn't support it.
The script is supposed to run with bash.   (OK, we need to fix it...)


Takashi

> ALSA Information Script v 0.4.56
> --------------------------------
> 
> This script will collect information about your ALSA installation and sound
> related hardware, to help diagnose your problem.
> 
> Do you want to run this script? [y/n] : read: 365: Illegal option -e
> 
> Thank you for using the ALSA-Info Script
> 
> On Tue, May 19, 2009 at 08:11, Takashi Iwai <tiwai@suse.de> wrote:
> 
>     At Mon, 18 May 2009 23:26:47 +0100,
>     Noel Bourke wrote:
>     >
>     > Hi Takashi,
>     >
>     > I set this up with an Auzentech X-Fi Prelude.
>     > Driver works OK but sound seemed a bit off.
>     > According to speaker-test I seem to only
>     > have one audio channel!
>     >
>     > Any thoughts?
>    
>     Please run alsa-info.sh with --no-upload option, and attach the
>     generated file.  This will show a bit more detailed driver
>     information.
> 
>     thanks,
>    
>     Takashi
> 
> 

Re: Testers wanted: New SB X-Fi driver

[Noel Bourke]

Yep, ran it in bash. I thought it might be something simple but the line in
question barring the comment is just "fi"

On Wed, May 20, 2009 at 18:51, Takashi Iwai <tiwai@suse.de> wrote:

> At Wed, 20 May 2009 18:21:04 +0100,
> Noel Bourke wrote:
> >
> > I'm getting the following output from that script...
> > I took a look and couldn't find the problem.
> >
> > alsa-info.sh: 365: [[: not found
>
> You must be using a shell that doesn't support it.
> The script is supposed to run with bash.   (OK, we need to fix it...)
>
>
> Takashi
>
> > ALSA Information Script v 0.4.56
> > --------------------------------
> >
> > This script will collect information about your ALSA installation and
> sound
> > related hardware, to help diagnose your problem.
> >
> > Do you want to run this script? [y/n] : read: 365: Illegal option -e
> >
> > Thank you for using the ALSA-Info Script
> >
> > On Tue, May 19, 2009 at 08:11, Takashi Iwai <tiwai@suse.de> wrote:
> >
> >     At Mon, 18 May 2009 23:26:47 +0100,
> >     Noel Bourke wrote:
> >     >
> >     > Hi Takashi,
> >     >
> >     > I set this up with an Auzentech X-Fi Prelude.
> >     > Driver works OK but sound seemed a bit off.
> >     > According to speaker-test I seem to only
> >     > have one audio channel!
> >     >
> >     > Any thoughts?
> >
> >     Please run alsa-info.sh with --no-upload option, and attach the
> >     generated file.  This will show a bit more detailed driver
> >     information.
> >
> >     thanks,
> >
> >     Takashi
> >
> >
>

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Wed, 20 May 2009 20:19:07 +0100,
Noel Bourke wrote:
> 
> Yep, ran it in bash. I thought it might be something simple but the line in
> question barring the comment is just "fi"

Hm, but the error message (no command "[[") implies that it's no bash...
Puzzling.


Takashi

> 
> On Wed, May 20, 2009 at 18:51, Takashi Iwai <tiwai@suse.de> wrote:
> 
>     At Wed, 20 May 2009 18:21:04 +0100,
>     Noel Bourke wrote:
>     >
>     > I'm getting the following output from that script...
>     > I took a look and couldn't find the problem.
>     >
>     > alsa-info.sh: 365: [[: not found
>    
>     You must be using a shell that doesn't support it.
>     The script is supposed to run with bash.   (OK, we need to fix it...)
> 
>     Takashi
>    
>     > ALSA Information Script v 0.4.56
>     > --------------------------------
>     >
>     > This script will collect information about your ALSA installation and
>     sound
>     > related hardware, to help diagnose your problem.
>     >
>     > Do you want to run this script? [y/n] : read: 365: Illegal option -e
>     >
>     > Thank you for using the ALSA-Info Script
>     >
>     > On Tue, May 19, 2009 at 08:11, Takashi Iwai <tiwai@suse.de> wrote:
>     >
>     >     At Mon, 18 May 2009 23:26:47 +0100,
>     >     Noel Bourke wrote:
>     >     >
>     >     > Hi Takashi,
>     >     >
>     >     > I set this up with an Auzentech X-Fi Prelude.
>     >     > Driver works OK but sound seemed a bit off.
>     >     > According to speaker-test I seem to only
>     >     > have one audio channel!
>     >     >
>     >     > Any thoughts?
>     >
>     >     Please run alsa-info.sh with --no-upload option, and attach the
>     >     generated file.  This will show a bit more detailed driver
>     >     information.
>     >
>     >     thanks,
>     >
>     >     Takashi
>     >
>     >
> 
> 

Testers wanted: New SB X-Fi driver

[daedra]

One more question, any chance of the driver in the future supporting 
soundfonts since the X-fi has a built in midi synthesizer?

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 18 May 2009 14:42:59 -0700,
daedra wrote:
> 
> One more question, any chance of the driver in the future supporting 
> soundfonts since the X-fi has a built in midi synthesizer?

Theoretically possible, but it's not implemented yet.
The technical information how to handle the effect parameters is
missing.


Takashi

Testers wanted: New SB X-Fi driver

[daedra]

Is this driver the same source that creative released a few months back 
or has it been updated to support more features?  Just Curious.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sun, 17 May 2009 14:41:22 -0700,
daedra wrote:
> 
> Is this driver the same source that creative released a few months back 
> or has it been updated to support more features?  Just Curious.

It has a few fixes / improvements since then, but no big functionality
changes.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Brendan Pike]

On Mon, 18 May 2009 11:30:59 +0200
Takashi Iwai <tiwai@suse.de> wrote:

> At Sun, 17 May 2009 14:41:22 -0700,
> daedra wrote:
> > 
> > Is this driver the same source that creative released a few months back 
> > or has it been updated to support more features?  Just Curious.
> 
> It has a few fixes / improvements since then, but no big functionality
> changes.
> 
> 
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

The only big change is 7.1 support.

Re: Testers wanted: New SB X-Fi driver

[William Pitcock]

[-- Attachment #1.1: Type: text/plain, Size: 569 bytes --]

Hi,

On Sun, 2009-05-17 at 14:41 -0700, daedra wrote:
> Is this driver the same source that creative released a few months back 
> or has it been updated to support more features?  Just Curious.

The ctxfi code supports all of the hardware PCM features, as far as I
know anyway.  "Features" like the Crystalizer are done in the windows
driver code itself, possibly uploading code to the DSP, but more likely
done in software.

I do not know if MIDI is implemented yet.  Maybe a project for the
summer if not.  MIDI should be similar to emu10k1.

William

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Testers wanted: New SB X-Fi driver

[Takashi Iwai]

Hi,

after some communications with Creative, I finally got a mergeable
version of their X-Fi driver.  It's not my crappy hack but by genuine
Creative :)

The patch is now merged into sound-unstable GIT tree topic/ctxfi
branch:
  git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git

The corresponding alsa-driver snapshot tarball is:
  ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz

The driver module is named as snd-ctxfi.

I tested only the driver builds with recent kernels, but unfortunately
I have no test hardware now, so it'd be helpful if anyone can test
it with a real hardware.

Note that the ctxfi driver might conflict with the HD-audio driver.
So it'd be nice if you save the output of lspci before loading the
drivers and let me know if any problem happens.  Also, at testing,
please check the kernel message.  If this conflict really happens, try
to build without hd-audio, that is, run configure with
--with-cards=ctxfi option in addition to others, and test whether it
works with this workaround (better after reboot to reset the board
info by BIOS).

Once after I get positive feedbacks (or fix after negative ones), I'm
going to merge it to the main tree so that it'll be in the next
kernel.  So, a quick test report would be greatly appreciated.


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Takashi Iwai wrote:
> Hi,
>
> after some communications with Creative, I finally got a mergeable
> version of their X-Fi driver.  It's not my crappy hack but by genuine
> Creative :)
>
> The patch is now merged into sound-unstable GIT tree topic/ctxfi
> branch:
>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
>
> The corresponding alsa-driver snapshot tarball is:
>   ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
Woo, worked first go! :)

I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled 
against Intrepid's current kernel (2.6.28-11).

I have only recently subscribed to the list and was just about to ask 
what the deal was with the X-Fi driver.

So mplayer, aplay and audacious all play things.  Clearly works 
perfectly then :)

Does alsa have some sort of test suite or similar that I can run the 
card through?

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 22:07:33 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> > Hi,
> >
> > after some communications with Creative, I finally got a mergeable
> > version of their X-Fi driver.  It's not my crappy hack but by genuine
> > Creative :)
> >
> > The patch is now merged into sound-unstable GIT tree topic/ctxfi
> > branch:
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
> >
> > The corresponding alsa-driver snapshot tarball is:
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
> Woo, worked first go! :)
> 
> I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled 
> against Intrepid's current kernel (2.6.28-11).
> 
> I have only recently subscribed to the list and was just about to ask 
> what the deal was with the X-Fi driver.
> 
> So mplayer, aplay and audacious all play things.  Clearly works 
> perfectly then :)

Great.

> Does alsa have some sort of test suite or similar that I can run the 
> card through?

The way you tested should suffice as primary tests.
You can also try speaker-test for multi-channels.


Thanks!

Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Michael (Micksa) Slade wrote:
> Takashi Iwai wrote:
>   
>> Hi,
>>
>> after some communications with Creative, I finally got a mergeable
>> version of their X-Fi driver.  It's not my crappy hack but by genuine
>> Creative :)
>>
>> The patch is now merged into sound-unstable GIT tree topic/ctxfi
>> branch:
>>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
>>
>> The corresponding alsa-driver snapshot tarball is:
>>   ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
>>     
> Woo, worked first go! :)
>
> I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled 
> against Intrepid's current kernel (2.6.28-11).
>
> I have only recently subscribed to the list and was just about to ask 
> what the deal was with the X-Fi driver.
>
> So mplayer, aplay and audacious all play things.  Clearly works 
> perfectly then :)
>
> Does alsa have some sort of test suite or similar that I can run the 
> card through?
>   
Oh, doesn't survive suspend/resume, and doesn't appear to work at 24bit.

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 22:22:11 +1000,
Michael (Micksa) Slade wrote:
> 
> Michael (Micksa) Slade wrote:
> 
>     Takashi Iwai wrote:
> 
>         Hi,
>         
>         after some communications with Creative, I finally got a mergeable
>         version of their X-Fi driver.  It's not my crappy hack but by genuine
>         Creative :)
>         
>         The patch is now merged into sound-unstable GIT tree topic/ctxfi
>         branch:
>           git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
>         
>         The corresponding alsa-driver snapshot tarball is:
>           ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
> 
>     Woo, worked first go! :)
>     
>     I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled 
>     against Intrepid's current kernel (2.6.28-11).
>     
>     I have only recently subscribed to the list and was just about to ask 
>     what the deal was with the X-Fi driver.
>     
>     So mplayer, aplay and audacious all play things.  Clearly works 
>     perfectly then :)
>     
>     Does alsa have some sort of test suite or similar that I can run the 
>     card through?
> 
> Oh, doesn't survive suspend/resume,

It's expected.  PM isn't supported yet with this driver.

> and doesn't appear to work at 24bit.

That's bad.  How did you test it?


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Takashi Iwai wrote:
> At Thu, 14 May 2009 22:22:11 +1000,
> Michael (Micksa) Slade wrote:
>   
>>     Woo, worked first go! :)
>>     
>>     I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled 
>>     against Intrepid's current kernel (2.6.28-11).
>>     
>>     I have only recently subscribed to the list and was just about to ask 
>>     what the deal was with the X-Fi driver.
>>     
>>     So mplayer, aplay and audacious all play things.  Clearly works 
>>     perfectly then :)
>>     
>>     Does alsa have some sort of test suite or similar that I can run the 
>>     card through?
>>
>> Oh, doesn't survive suspend/resume,
>>     
>
> It's expected.  PM isn't supported yet with this driver.
>
>   
>> and doesn't appear to work at 24bit.
>>     
>
> That's bad.  How did you test it?
>   
Swtiched audacious to 24bit.  It very quietly plays a badly distorted 
version of the song :)

How might I get a copy of the specs?  I want to try my hand at kernel 
coding.  I hear it gets you chicks.

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 22:34:09 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> 
>     At Thu, 14 May 2009 22:22:11 +1000,
>     Michael (Micksa) Slade wrote:
> 
>             Woo, worked first go! :)
>             
>             I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled 
>             against Intrepid's current kernel (2.6.28-11).
>             
>             I have only recently subscribed to the list and was just about to ask 
>             what the deal was with the X-Fi driver.
>             
>             So mplayer, aplay and audacious all play things.  Clearly works 
>             perfectly then :)
>             
>             Does alsa have some sort of test suite or similar that I can run the 
>             card through?
>         
>         Oh, doesn't survive suspend/resume,
> 
>     It's expected.  PM isn't supported yet with this driver.
> 
>         and doesn't appear to work at 24bit.
> 
>     That's bad.  How did you test it?
> 
> Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
> of the song :)

What about aplay with 32bit samples?

> How might I get a copy of the specs?

Unfortunately I have no spec, too.
I just got source codes and contact with guys.


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Takashi Iwai wrote:
> At Thu, 14 May 2009 22:34:09 +1000,
> Michael (Micksa) Slade wrote:
>   
>> Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
>> of the song :)
>>     
>
> What about aplay with 32bit samples?
>   
Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.

I'm going to play around with all this stuff more in my spare time so 
hopefully in a while I'll start sounding like I know what I'm doing.

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 23:07:59 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> 
>     At Thu, 14 May 2009 22:34:09 +1000,
>     Michael (Micksa) Slade wrote:
> 
>         Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
>         of the song :)
> 
>     What about aplay with 32bit samples?
> 
> Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.

It's possible that audacious tries to access 24bit, not 32bit format, 
and ctxfi driver has a bug around that.

Could you try the patch below?


Takashi

===
diff --git a/sound/pci/ctxfi/ctpcm.c b/sound/pci/ctxfi/ctpcm.c
index a64cb0e..aae9eb1 100644
--- a/sound/pci/ctxfi/ctpcm.c
+++ b/sound/pci/ctxfi/ctpcm.c
@@ -30,7 +30,6 @@ static struct snd_pcm_hardware ct_pcm_playback_hw = {
 				   SNDRV_PCM_FMTBIT_S16_LE |
 				   SNDRV_PCM_FMTBIT_U16_LE |
 				   SNDRV_PCM_FMTBIT_S24_3LE |
-				   SNDRV_PCM_FMTBIT_S24_LE |
 				   SNDRV_PCM_FMTBIT_S32_LE),
 	.rates			= (SNDRV_PCM_RATE_CONTINUOUS |
 				   SNDRV_PCM_RATE_8000_192000),
@@ -81,7 +80,6 @@ static struct snd_pcm_hardware ct_pcm_capture_hw = {
 				   SNDRV_PCM_FMTBIT_S16_LE |
 				   SNDRV_PCM_FMTBIT_U16_LE |
 				   SNDRV_PCM_FMTBIT_S24_3LE |
-				   SNDRV_PCM_FMTBIT_S24_LE |
 				   SNDRV_PCM_FMTBIT_S32_LE),
 	.rates			= (SNDRV_PCM_RATE_CONTINUOUS |
 				   SNDRV_PCM_RATE_8000_96000),

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Takashi Iwai wrote:
> At Thu, 14 May 2009 23:07:59 +1000,
> Michael (Micksa) Slade wrote:
>   
>> Takashi Iwai wrote:
>>
>>     At Thu, 14 May 2009 22:34:09 +1000,
>>     Michael (Micksa) Slade wrote:
>>
>>         Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
>>         of the song :)
>>
>>     What about aplay with 32bit samples?
>>
>> Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.
>>     
>
> It's possible that audacious tries to access 24bit, not 32bit format, 
> and ctxfi driver has a bug around that.
>
> Could you try the patch below?
>   
[snip]

aplay still works in 24 and 32bit, audacious freezes (but you can still 
switch back to 16bit and it will play without having to kill and restart it)

What does that mean? :)

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 23:37:20 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> 
>     At Thu, 14 May 2009 23:07:59 +1000,
>     Michael (Micksa) Slade wrote:
> 
>         Takashi Iwai wrote:
>         
>             At Thu, 14 May 2009 22:34:09 +1000,
>             Michael (Micksa) Slade wrote:
>         
>                 Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
>                 of the song :)
>         
>             What about aplay with 32bit samples?
>         
>         Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.
> 
>     It's possible that audacious tries to access 24bit, not 32bit format, 
>     and ctxfi driver has a bug around that.
>     
>     Could you try the patch below?
> 
> [snip]
> 
> aplay still works in 24 and 32bit, audacious freezes (but you can still switch
> back to 16bit and it will play without having to kill and restart it)
> 
> What does that mean? :)

Hrm, I don't know what it's doing exactly...
Or, removing S24_3LE there might help?

I don't know exactly that audacious is doing.  Anyway, it's no
critical bug as a showstopper :)


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[William Pitcock]

[-- Attachment #1.1: Type: text/plain, Size: 752 bytes --]

Hi,

On Thu, 2009-05-14 at 15:28 +0200, Takashi Iwai wrote:
> At Thu, 14 May 2009 23:07:59 +1000,
> Michael (Micksa) Slade wrote:
> > 
> > Takashi Iwai wrote:
> > 
> >     At Thu, 14 May 2009 22:34:09 +1000,
> >     Michael (Micksa) Slade wrote:
> > 
> >         Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
> >         of the song :)
> > 
> >     What about aplay with 32bit samples?
> > 
> > Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.
> 
> It's possible that audacious tries to access 24bit, not 32bit format, 
> and ctxfi driver has a bug around that.

Audacious indeed uses 24bit formats.  We will add proper 32bit support
in the 2.1 merge window.

William


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 18 May 2009 21:38:52 -0500,
William Pitcock wrote:
> 
> Hi,
> 
> On Thu, 2009-05-14 at 15:28 +0200, Takashi Iwai wrote:
> > At Thu, 14 May 2009 23:07:59 +1000,
> > Michael (Micksa) Slade wrote:
> > > 
> > > Takashi Iwai wrote:
> > > 
> > >     At Thu, 14 May 2009 22:34:09 +1000,
> > >     Michael (Micksa) Slade wrote:
> > > 
> > >         Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
> > >         of the song :)
> > > 
> > >     What about aplay with 32bit samples?
> > > 
> > > Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.
> > 
> > It's possible that audacious tries to access 24bit, not 32bit format, 
> > and ctxfi driver has a bug around that.
> 
> Audacious indeed uses 24bit formats.

OK, thanks.  Is it 24bit 3-bytes format, or 24bit in 4bytes format?


Takashi

Re: Testers wanted: New SB X-Fi driver

[William Pitcock]

[-- Attachment #1.1: Type: text/plain, Size: 1677 bytes --]

On Tue, 2009-05-19 at 07:34 +0200, Takashi Iwai wrote:
> At Mon, 18 May 2009 21:38:52 -0500,
> William Pitcock wrote:
> > 
> > Hi,
> > 
> > On Thu, 2009-05-14 at 15:28 +0200, Takashi Iwai wrote:
> > > At Thu, 14 May 2009 23:07:59 +1000,
> > > Michael (Micksa) Slade wrote:
> > > > 
> > > > Takashi Iwai wrote:
> > > > 
> > > >     At Thu, 14 May 2009 22:34:09 +1000,
> > > >     Michael (Micksa) Slade wrote:
> > > > 
> > > >         Swtiched audacious to 24bit.  It very quietly plays a badly distorted version
> > > >         of the song :)
> > > > 
> > > >     What about aplay with 32bit samples?
> > > > 
> > > > Seems to work fine.  Also 24bit.  Guess it's audacious' fault.  Probably.
> > > 
> > > It's possible that audacious tries to access 24bit, not 32bit format, 
> > > and ctxfi driver has a bug around that.
> > 
> > Audacious indeed uses 24bit formats.
> 
> OK, thanks.  Is it 24bit 3-bytes format, or 24bit in 4bytes format?

24bit 3-bytes format.

This is a table of supported formats:

static alsaplug_format_mapping_t alsaplug_format_conv_tbl[] = {
    {FMT_S24_LE, SND_PCM_FORMAT_S24_LE},
    {FMT_S24_BE, SND_PCM_FORMAT_S24_BE},
    {FMT_S24_NE, SND_PCM_FORMAT_S24},
    {FMT_U24_LE, SND_PCM_FORMAT_U24_LE},
    {FMT_U24_BE, SND_PCM_FORMAT_U24_BE},
    {FMT_U24_NE, SND_PCM_FORMAT_U24},
    {FMT_S16_LE, SND_PCM_FORMAT_S16_LE},
    {FMT_S16_BE, SND_PCM_FORMAT_S16_BE},
    {FMT_S16_NE, SND_PCM_FORMAT_S16},
    {FMT_U16_LE, SND_PCM_FORMAT_U16_LE},
    {FMT_U16_BE, SND_PCM_FORMAT_U16_BE},
    {FMT_U16_NE, SND_PCM_FORMAT_U16},
    {FMT_U8, SND_PCM_FORMAT_U8},
    {FMT_S8, SND_PCM_FORMAT_S8},
};

William

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[James Courtier-Dutton]

2009/5/14 Takashi Iwai <tiwai@suse.de>:
> Hi,
>
> after some communications with Creative, I finally got a mergeable
> version of their X-Fi driver.  It's not my crappy hack but by genuine
> Creative :)
>

It is good news that you managed to have productive communications
with Creative.
I did have a very good relationship with Creative and EMU until all my
contacts left the company.
It took me years to build up the relationship, but I did not have the
time to start again from scratch.
If you manage to get the open source NDA signed with them, ask them to
contact me, informing me of such, and I can then pass all the
datasheets I have on to you. I do need direct contact from them before
I can do this though.
The datasheets cover almost all Creative and EMU sound cards.

Kind Regards

James

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 14:05:06 +0100,
James Courtier-Dutton wrote:
> 
> 2009/5/14 Takashi Iwai <tiwai@suse.de>:
> > Hi,
> >
> > after some communications with Creative, I finally got a mergeable
> > version of their X-Fi driver.  It's not my crappy hack but by genuine
> > Creative :)
> >
> 
> It is good news that you managed to have productive communications
> with Creative.
> I did have a very good relationship with Creative and EMU until all my
> contacts left the company.
> It took me years to build up the relationship, but I did not have the
> time to start again from scratch.
> If you manage to get the open source NDA signed with them, ask them to
> contact me, informing me of such, and I can then pass all the
> datasheets I have on to you. I do need direct contact from them before
> I can do this though.
> The datasheets cover almost all Creative and EMU sound cards.

Thanks.  I still don't sign any NDA for Creative, so I've been just a
bridge between them and us.  But, if I do, certainly I'll ask you to
gather all stuff ;)


Takashi

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Thu, 14 May 2009 12:52:17 +0200,
I wrote:
> 
> Hi,
> 
> after some communications with Creative, I finally got a mergeable
> version of their X-Fi driver.  It's not my crappy hack but by genuine
> Creative :)
> 
> The patch is now merged into sound-unstable GIT tree topic/ctxfi
> branch:
>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
> 
> The corresponding alsa-driver snapshot tarball is:
>   ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
> 
> The driver module is named as snd-ctxfi.
> 
> I tested only the driver builds with recent kernels, but unfortunately
> I have no test hardware now, so it'd be helpful if anyone can test
> it with a real hardware.
> 
> Note that the ctxfi driver might conflict with the HD-audio driver.
> So it'd be nice if you save the output of lspci before loading the
> drivers and let me know if any problem happens.  Also, at testing,
> please check the kernel message.  If this conflict really happens, try
> to build without hd-audio, that is, run configure with
> --with-cards=ctxfi option in addition to others, and test whether it
> works with this workaround (better after reboot to reset the board
> info by BIOS).
> 
> Once after I get positive feedbacks (or fix after negative ones), I'm
> going to merge it to the main tree so that it'll be in the next
> kernel.  So, a quick test report would be greatly appreciated.

It seems that there is no critical issues, so far.
Thus I merged X-fi patch to sound GIT tree.  It'll appear in the
normal alsa-driver snapshot below, too.
    ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz

Any positive / negative feedback reports are still appreciated.


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Takashi Iwai wrote:
> It seems that there is no critical issues, so far.
> Thus I merged X-fi patch to sound GIT tree.  It'll appear in the
> normal alsa-driver snapshot below, too.
>     ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
>   
Should the hda driver still have the X-fi PCI ids?

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Sat, 16 May 2009 19:34:28 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> > It seems that there is no critical issues, so far.
> > Thus I merged X-fi patch to sound GIT tree.  It'll appear in the
> > normal alsa-driver snapshot below, too.
> >     ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
> >   
> Should the hda driver still have the X-fi PCI ids?

Yes, it looks like that not all models are supported by ctxfi driver.

The question is whether we get real conflicts.  If any, let me know.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

Takashi Iwai wrote:
> At Sat, 16 May 2009 19:34:28 +1000,
> Michael (Micksa) Slade wrote:
>   
>> Takashi Iwai wrote:
>>     
>>> It seems that there is no critical issues, so far.
>>> Thus I merged X-fi patch to sound GIT tree.  It'll appear in the
>>> normal alsa-driver snapshot below, too.
>>>     ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
>>>   
>>>       
>> Should the hda driver still have the X-fi PCI ids?
>>     
>
> Yes, it looks like that not all models are supported by ctxfi driver.
>
> The question is whether we get real conflicts.  If any, let me know.
>   
Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi 
could get to it.  Does that count as a conflict?

Mick.

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 18 May 2009 13:43:36 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> 
>     At Sat, 16 May 2009 19:34:28 +1000,
>     Michael (Micksa) Slade wrote:
> 
>         Takashi Iwai wrote:
> 
>             It seems that there is no critical issues, so far.
>             Thus I merged X-fi patch to sound GIT tree.  It'll appear in the
>             normal alsa-driver snapshot below, too.
>                 ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
> 
>         Should the hda driver still have the X-fi PCI ids?
> 
>     Yes, it looks like that not all models are supported by ctxfi driver.
>     
>     The question is whether we get real conflicts.  If any, let me know.
> 
> Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi could get
> to it.  Does that count as a conflict?

Yes.  That's what I mentioned as a "conflict".

Could you run alsa-info.sh with --no-upload option, and attach the
    generated file?  The script is found at
    http://www.alsa-project.org/alsa-info.sh


thanks,

Takashi

Re: Testers wanted: New SB X-Fi driver

[wodor]

Hi,

When this driver will support USB X-Fi Surround 5.1 ?


best regards,
 Patryk Kowalczyk

> At Mon, 18 May 2009 13:43:36 +1000,
> Michael (Micksa) Slade wrote:
>>
>> Takashi Iwai wrote:
>>
>>     At Sat, 16 May 2009 19:34:28 +1000,
>>     Michael (Micksa) Slade wrote:
>>
>>         Takashi Iwai wrote:
>>
>>             It seems that there is no critical issues, so far.
>>             Thus I merged X-fi patch to sound GIT tree.  It'll appear in
>> the
>>             normal alsa-driver snapshot below, too.
>>                 ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
>>
>>         Should the hda driver still have the X-fi PCI ids?
>>
>>     Yes, it looks like that not all models are supported by ctxfi
>> driver.
>>
>>     The question is whether we get real conflicts.  If any, let me know.
>>
>> Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi
>> could get
>> to it.  Does that count as a conflict?
>
> Yes.  That's what I mentioned as a "conflict".
>
> Could you run alsa-info.sh with --no-upload option, and attach the
>     generated file?  The script is found at
>     http://www.alsa-project.org/alsa-info.sh
>
>
> thanks,
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
>

-- 
 Patryk Kowalczyk
 jid/email: wodor@wodor.org

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 18 May 2009 08:06:27 +0200 (CEST),
wodor@wodor.org wrote:
> 
> Hi,
> 
> When this driver will support USB X-Fi Surround 5.1 ?

USB is a completely different device and has nothing to do with PCI
X-Fi.  Don't be fooled by marketing :)


Takashi

> 
> 
> best regards,
>  Patryk Kowalczyk
> 
> > At Mon, 18 May 2009 13:43:36 +1000,
> > Michael (Micksa) Slade wrote:
> >>
> >> Takashi Iwai wrote:
> >>
> >>     At Sat, 16 May 2009 19:34:28 +1000,
> >>     Michael (Micksa) Slade wrote:
> >>
> >>         Takashi Iwai wrote:
> >>
> >>             It seems that there is no critical issues, so far.
> >>             Thus I merged X-fi patch to sound GIT tree.  It'll appear in
> >> the
> >>             normal alsa-driver snapshot below, too.
> >>                 ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
> >>
> >>         Should the hda driver still have the X-fi PCI ids?
> >>
> >>     Yes, it looks like that not all models are supported by ctxfi
> >> driver.
> >>
> >>     The question is whether we get real conflicts.  If any, let me know.
> >>
> >> Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi
> >> could get
> >> to it.  Does that count as a conflict?
> >
> > Yes.  That's what I mentioned as a "conflict".
> >
> > Could you run alsa-info.sh with --no-upload option, and attach the
> >     generated file?  The script is found at
> >     http://www.alsa-project.org/alsa-info.sh
> >
> >
> > thanks,
> >
> > Takashi
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
> >
> 
> -- 
>  Patryk Kowalczyk
>  jid/email: wodor@wodor.org
> 
> 
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

Re: Testers wanted: New SB X-Fi driver

[William Pitcock]

[-- Attachment #1.1: Type: text/plain, Size: 200 bytes --]

Hi,

On Mon, 2009-05-18 at 08:06 +0200, wodor@wodor.org wrote:
> Hi,
> 
> When this driver will support USB X-Fi Surround 5.1 ?

Never.  That would be supported by snd-usb-audio.

William


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Patryk Kowalczyk]

On Mon, 18 May 2009 21:42:45 -0500
William Pitcock <nenolod@sacredspiral.co.uk> wrote:

> Hi,
> 
> On Mon, 2009-05-18 at 08:06 +0200, wodor@wodor.org wrote:
> > Hi,
> > 
> > When this driver will support USB X-Fi Surround 5.1 ?
> 
> Never.  That would be supported by snd-usb-audio.
> 
> William
> 
> 
Hi,

So. When will snd-usb-audio support channels clonning or some mixer
for this sound card? Now I`m clonning channels by alsa plugins but it`s
taking much CPU time. 

best regards,
	Patryk Kowalczyk

--
jid / email : wodor at wodor dot org
homepage: wodor dot org

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Tue, 19 May 2009 17:09:05 +0200,
Patryk Kowalczyk wrote:
> 
> On Mon, 18 May 2009 21:42:45 -0500
> William Pitcock <nenolod@sacredspiral.co.uk> wrote:
> 
> > Hi,
> > 
> > On Mon, 2009-05-18 at 08:06 +0200, wodor@wodor.org wrote:
> > > Hi,
> > > 
> > > When this driver will support USB X-Fi Surround 5.1 ?
> > 
> > Never.  That would be supported by snd-usb-audio.
> > 
> > William
> > 
> > 
> Hi,
> 
> So. When will snd-usb-audio support channels clonning or some mixer
> for this sound card? Now I`m clonning channels by alsa plugins but it`s
> taking much CPU time. 

I don't think the hardware does such a thing.
Almost all usb-audio devices don't do any fancy effects or channel
setups.  They are mostly a dumb playback / recording device.
All other effects are implemented in software secretly.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Michael (Micksa) Slade]

[-- Attachment #1: Type: text/plain, Size: 207 bytes --]

Takashi Iwai wrote:
> Could you run alsa-info.sh with --no-upload option, and attach the
>     generated file?  The script is found at
>     http://www.alsa-project.org/alsa-info.sh
>
>   
Attached.

Mick.


[-- Attachment #2: mickpc-alsa-info.txt --]
[-- Type: text/plain, Size: 16227 bytes --]

upload=true&script=true&cardinfo=
!!################################
!!ALSA Information Script v 0.4.56
!!################################

!!Script ran on: Mon May 18 10:07:32 UTC 2009


!!Linux Distribution
!!------------------

Ubuntu 9.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 9.04"


!!Kernel Information
!!------------------

Kernel release:    2.6.28-11-generic
Operating System:  GNU/Linux
Architecture:      x86_64
Processor:         unknown
SMP Enabled:       Yes


!!ALSA Version
!!------------

Driver version:     1.0.20
Library version:    1.0.18
Utilities version:  1.0.18


!!Loaded ALSA modules
!!-------------------

snd_ctxfi
snd_usb_audio
snd_usb_audio


!!Sound Servers on this system
!!----------------------------

Pulseaudio:
      Installed - Yes (/usr/bin/pulseaudio)
      Running - Yes

ESound Daemon:
      Installed - Yes (/usr/bin/esd)
      Running - No

Jack:
      Installed - Yes (/usr/bin/jackd)
      Running - No


!!Soundcards recognised by ALSA
!!-----------------------------

 0 [XFi            ]: SB-XFi - Creative X-Fi
                      Creative ALSA Driver X-Fi
 1 [Cable          ]: USB-Audio - USB Midi Cable
                      USB Midi Cable at usb-0000:00:12.2-3.1, full speed
 2 [PCR            ]: USB-Audio - PCR
                      EDIROL PCR at usb-0000:00:12.2-3.2, full speed


!!PCI Soundcards installed in the system
!!--------------------------------------

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
02:00.0 Audio device: Creative Labs [X-Fi Titanium series] EMU20k2 (rev 03)


!!Advanced information - PCI Vendor/Device/Susbsystem ID's
!!--------------------------------------------------------

00:14.2 0403: 1002:4383
	Subsystem: 1458:a022
--
02:00.0 0403: 1102:000b (rev 03)
	Subsystem: 1102:0043


!!Modprobe options (Sound related)
!!--------------------------------

snd-atiixp-modem: index=-2
snd-intel8x0m: index=-2
snd-via82xx-modem: index=-2
snd-usb-audio: index=-2
snd-usb-us122l: index=-2
snd-usb-usx2y: index=-2
snd-usb-caiaq: index=-2
snd-cmipci: mpu_port=0x330 fm_port=0x388
snd-pcsp: index=-2


!!Loaded sound module options
!!--------------------------

!!Module: snd_ctxfi
multiple : 2
reference_rate : 48000

!!Module: snd_usb_audio
async_unlink : Y
device_setup : 0,0,0,0,0,0,0,0
devpath : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
enable : Y,Y,Y,Y,Y,Y,Y,Y
id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
ignore_ctl_error : N
index : -2,-1,-1,-1,-1,-1,-1,-1
nrpacks : 8
pid : -1,-1,-1,-1,-1,-1,-1,-1
vid : -1,-1,-1,-1,-1,-1,-1,-1

!!Module: snd_usb_audio
async_unlink : Y
device_setup : 0,0,0,0,0,0,0,0
devpath : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
enable : Y,Y,Y,Y,Y,Y,Y,Y
id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
ignore_ctl_error : N
index : -2,-1,-1,-1,-1,-1,-1,-1
nrpacks : 8
pid : -1,-1,-1,-1,-1,-1,-1,-1
vid : -1,-1,-1,-1,-1,-1,-1,-1


!!ALSA Device nodes
!!-----------------

crw-rw----+ 1 root audio 116,  0 May 18 20:03 /dev/snd/controlC0
crw-rw----+ 1 root audio 116, 32 May 16 16:27 /dev/snd/controlC1
crw-rw----+ 1 root audio 116, 64 May 15 19:36 /dev/snd/controlC2
crw-rw----+ 1 root audio 116, 40 May 16 16:27 /dev/snd/midiC1D0
crw-rw----+ 1 root audio 116, 72 May 15 19:36 /dev/snd/midiC2D0
crw-rw----+ 1 root audio 116, 24 May 18 20:03 /dev/snd/pcmC0D0c
crw-rw----+ 1 root audio 116, 16 May 18 20:04 /dev/snd/pcmC0D0p
crw-rw----+ 1 root audio 116, 17 May 18 20:03 /dev/snd/pcmC0D1p
crw-rw----+ 1 root audio 116, 18 May 18 20:03 /dev/snd/pcmC0D2p
crw-rw----+ 1 root audio 116, 19 May 18 20:03 /dev/snd/pcmC0D3p
crw-rw----+ 1 root audio 116, 20 May 18 20:03 /dev/snd/pcmC0D4p
crw-rw----+ 1 root audio 116,  1 May 15 19:36 /dev/snd/seq
crw-rw----+ 1 root audio 116, 33 May 15 19:36 /dev/snd/timer


!!Aplay/Arecord output
!!------------

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: XFi [Creative X-Fi], device 0: Front/WaveIn [Front/WaveIn]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 1: Rear [Rear]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 2: Center/LFE [Center/LFE]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 3: Surround [Surround]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: XFi [Creative X-Fi], device 4: IEC958 Non-audio [IEC958 Non-audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ARECORD

**** List of CAPTURE Hardware Devices ****
card 0: XFi [Creative X-Fi], device 0: Front/WaveIn [Front/WaveIn]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

!!Amixer output
!!-------------

!!-------Mixer controls for card 0 [XFi]

Card hw:0 'XFi'/'Creative ALSA Driver X-Fi'
  Mixer name	: '20K2'
  Components	: ''
  Controls      : 29
  Simple ctrls  : 10
Simple mixer control 'Master',0
  Capabilities: pvolume cvolume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 43690 Capture 0 - 43690
  Front Left: Playback 21845 [50%] Capture 34913 [80%]
  Front Right: Playback 21845 [50%] Capture 34913 [80%]
Simple mixer control 'PCM',0
  Capabilities: pvolume cvolume cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 43690 Capture 0 - 43690
  Front Left: Playback 34461 [79%] Capture 34913 [80%] [on]
  Front Right: Playback 34461 [79%] Capture 34913 [80%] [on]
Simple mixer control 'Front',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 43690
  Mono:
  Front Left: Playback 34913 [80%] [on]
  Front Right: Playback 34913 [80%] [on]
Simple mixer control 'Surround',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 43690
  Mono:
  Front Left: Playback 32525 [74%] [off]
  Front Right: Playback 32525 [74%] [off]
Simple mixer control 'Center/LFE',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 43690
  Mono:
  Front Left: Playback 32525 [74%] [off]
  Front Right: Playback 32525 [74%] [off]
Simple mixer control 'Line-in',0
  Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 43690 Capture 0 - 43690
  Front Left: Playback 32525 [74%] [off] Capture 32525 [74%] [on]
  Front Right: Playback 32525 [74%] [off] Capture 32525 [74%] [on]
Simple mixer control 'Mic',0
  Capabilities: pvolume cvolume cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 43690 Capture 0 - 43690
  Front Left: Playback 0 [0%] Capture 0 [0%] [off]
  Front Right: Playback 0 [0%] Capture 0 [0%] [off]
Simple mixer control 'Rear',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 43690
  Mono:
  Front Left: Playback 32525 [74%] [off]
  Front Right: Playback 32525 [74%] [off]
Simple mixer control 'S/PDIF-in',0
  Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 43690 Capture 0 - 43690
  Front Left: Playback 32525 [74%] [off] Capture 32525 [74%] [on]
  Front Right: Playback 32525 [74%] [off] Capture 32525 [74%] [on]
Simple mixer control 'S/PDIF-out',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 43690
  Mono:
  Front Left: Playback 32525 [74%] [off]
  Front Right: Playback 32525 [74%] [off]

!!-------Mixer controls for card 1 [Cable]

Card hw:1 'Cable'/'USB Midi Cable at usb-0000:00:12.2-3.1, full speed'
  Mixer name	: 'USB Mixer'
  Components	: 'USB15ca:0101'
  Controls      : 0
  Simple ctrls  : 0

!!-------Mixer controls for card 2 [PCR]

Card hw:2 'PCR'/'EDIROL PCR at usb-0000:00:12.2-3.2, full speed'
  Mixer name	: ''
  Components	: 'USB0582:0033'
  Controls      : 0
  Simple ctrls  : 0


!!Alsactl output
!!-------------

--startcollapse--
state.XFi {
	control.1 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Master Playback Volume'
		value.0 21845
		value.1 21845
	}
	control.2 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'PCM Playback Volume'
		value.0 34461
		value.1 34461
	}
	control.3 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Line-in Playback Volume'
		value.0 32525
		value.1 32525
	}
	control.4 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Mic Playback Volume'
		value.0 0
		value.1 0
	}
	control.5 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'S/PDIF-in Playback Volume'
		value.0 32525
		value.1 32525
	}
	control.6 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'S/PDIF-out Playback Volume'
		value.0 32525
		value.1 32525
	}
	control.7 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Front Playback Volume'
		value.0 34913
		value.1 34913
	}
	control.8 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Rear Playback Volume'
		value.0 32525
		value.1 32525
	}
	control.9 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Center/LFE Playback Volume'
		value.0 32525
		value.1 32525
	}
	control.10 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Surround Playback Volume'
		value.0 32525
		value.1 32525
	}
	control.11 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Master Capture Volume'
		value.0 34913
		value.1 34913
	}
	control.12 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'PCM Capture Volume'
		value.0 34913
		value.1 34913
	}
	control.13 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Line-in Capture Volume'
		value.0 32525
		value.1 32525
	}
	control.14 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'Mic Capture Volume'
		value.0 0
		value.1 0
	}
	control.15 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 43690 (step 128)'
		iface MIXER
		device 5
		name 'S/PDIF-in Capture Volume'
		value.0 32525
		value.1 32525
	}
	control.16 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'PCM Capture Switch'
		value true
	}
	control.17 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Line-in Capture Switch'
		value true
	}
	control.18 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Mic Capture Switch'
		value false
	}
	control.19 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'S/PDIF-in Capture Switch'
		value true
	}
	control.20 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Line-in Playback Switch'
		value false
	}
	control.21 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'S/PDIF-out Playback Switch'
		value false
	}
	control.22 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'S/PDIF-in Playback Switch'
		value false
	}
	control.23 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Front Playback Switch'
		value true
	}
	control.24 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Rear Playback Switch'
		value false
	}
	control.25 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Center/LFE Playback Switch'
		value false
	}
	control.26 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		device 5
		name 'Surround Playback Switch'
		value false
	}
	control.27 {
		comment.access read
		comment.type IEC958
		comment.count 1
		iface PCM
		device 4
		name 'IEC958 Playback Mask'
		value ffffffff00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
	}
	control.28 {
		comment.access 'read write'
		comment.type IEC958
		comment.count 1
		iface PCM
		device 4
		name 'IEC958 Playback Default'
		value '0082000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
	control.29 {
		comment.access 'read write'
		comment.type IEC958
		comment.count 1
		iface PCM
		device 4
		name 'IEC958 Playback PCM Stream'
		value '0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
	}
}
state.Cable {
	control {
	}
}
state.PCR {
	control {
	}
}
--endcollapse--


!!All Loaded Modules
!!------------------

Module
snd_ctxfi
isofs
udf
crc_itu_t
nfs
lockd
nfs_acl
sunrpc
binfmt_misc
bridge
stp
bnep
video
output
input_polldev
nls_iso8859_1
nls_cp437
vfat
fat
lp
snd_hda_codec_ca0110
snd_hda_codec_realtek
snd_usb_audio
snd_usb_lib
snd_seq_dummy
snd_seq_oss
snd_hda_codec
snd_pcm_oss
snd_mixer_oss
snd_seq_midi
snd_rawmidi
snd_seq_midi_event
ppdev
snd_seq
snd_hwdep
snd_pcm
parport_pc
i2c_piix4
pcspkr
snd_timer
snd_seq_device
snd_page_alloc
parport
psmouse
k8temp
nvidia
serio_raw
snd
soundcore
ohci1394
ieee1394
r8169
mii
fbcon
tileblit
font
bitblit
softcursor



[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Testers wanted: New SB X-Fi driver

[Takashi Iwai]

At Mon, 18 May 2009 20:10:46 +1000,
Michael (Micksa) Slade wrote:
> 
> Takashi Iwai wrote:
> > Could you run alsa-info.sh with --no-upload option, and attach the
> >     generated file?  The script is found at
> >     http://www.alsa-project.org/alsa-info.sh
> >
> >   
> Attached.

Thanks.  Fixed now.


Takashi

Re: Testers wanted: New SB X-Fi driver

[Alexey Bazhin]

On Thu, 14 May 2009 12:52:17 +0200
Takashi Iwai <tiwai@suse.de> wrote:

> Once after I get positive feedbacks (or fix after negative ones), I'm
> going to merge it to the main tree so that it'll be in the next
> kernel.  So, a quick test report would be greatly appreciated.
As for me:

aplay works fine with 16bit samples (doesn't tested 24bit)

mplayer plays first open stream glitchy, but if i open one more mplayer, and
then close the first - it plays fine but prints error:
[AO_ALSA] alsa-lib: pcm_hw.c:1321:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Invalid argument
[AO_ALSA] alsa-lib: pcm_dmix.c:1058:(snd_pcm_dmix_open) unable to open slave
[AO_ALSA] Playback open error: Invalid argument

Also ac3-passthrough works with this driver (finally!), but prints errors too:
mplayer -ac hwac3 -ao alsa:device=hw=0.4 test.ac3
[AO_ALSA] alsa-lib: conf.c:3843:(parse_args) Unknown parameter AES0
[AO_ALSA] alsa-lib: conf.c:3969:(snd_config_expand) Parse arguments error: No such file or directory
[AO_ALSA] alsa-lib: pcm.c:2196:(snd_pcm_open_noupdate) Unknown PCM hw:0,4,AES0=6

-- 
 Alexey Bazhin
  mailto:baz@irc.msk.ru
  ICQ 125125882

Re: Testers wanted: New SB X-Fi driver

[Alexey Bazhin]

On Sun, 17 May 2009 00:52:51 +0400
Alexey Bazhin <baz@irc.msk.ru> wrote:

> mplayer plays first open stream glitchy, but if i open one more
> mplayer, and then close the first - it plays fine but prints error:
> [AO_ALSA] alsa-lib: pcm_hw.c:1321:(snd_pcm_hw_open)
> open /dev/snd/pcmC0D0p failed: Invalid argument [AO_ALSA] alsa-lib:
> pcm_dmix.c:1058:(snd_pcm_dmix_open) unable to open slave [AO_ALSA]
> Playback open error: Invalid argument
disregard this part - buggy dmix configuration was left from previous
experiments...

-- 
 Alexey Bazhin
  mailto:baz@irc.msk.ru
  ICQ 125125882

Re: Testers wanted: New SB X-Fi driver

[Alexey Bazhin]

On Sun, 17 May 2009 00:52:51 +0400
Alexey Bazhin <baz@irc.msk.ru> wrote:

> On Thu, 14 May 2009 12:52:17 +0200
> Takashi Iwai <tiwai@suse.de> wrote:
> 
> > Once after I get positive feedbacks (or fix after negative ones),
> > I'm going to merge it to the main tree so that it'll be in the next
> > kernel.  So, a quick test report would be greatly appreciated.
> As for me:
> 
One more thing - using digital output (with maximum volume in mixer)
resulting volume of sound is much higher than with my other cards, so
some additional processing added so even playing sound sample with
native card rate is not bit accurate. Is it how it's supposed to be?

-- 
 Alexey Bazhin
  mailto:baz@irc.msk.ru
  ICQ 125125882