Sound Blaster X-Fi Xtreme Audio PCI-E driver help needed

English Hardware
#1

Hello all-

I have a “Sound Blaster X-Fi Xtreme Audio PCI-E” sound card and I cannot get the drivers to work. I am running openSUSE 11.1 64bit version. I found the right drivers from here but when I try to install I am getting error msg.

Here is what the readme file says:

====================================================================

Sound Blaster X-Fi Linux 32/64-bit Driver Source Release Readme File

September 2008

====================================================================

The purpose of this document is to describe how to build and install the
X-Fi Linux device driver.

Quick install

=============

In terminal,

  1. Goto source directory

  2. Execute make command as root

    make

    make install

Uninstall

=========

In terminal,

  1. Goto source directory

  2. Execute make command as root

    make uninstall

Copyright (c) 2008 Creative Technology Ltd. All rights reserved.

====================================================================

End of Readme File

====================================================================

Here is what my Terminal looks like:

=================================================================
linux-v9qj:/home/art/Desktop # tar -xzf XFiDrv_Linux_Public_US_1.00.tar.gz
linux-v9qj:/home/art/Desktop # cd XFiDrv_Linux_Public_US_1.00/
linux-v9qj:/home/art/Desktop/XFiDrv_Linux_Public_US_1.00 # make
make -C /lib/modules/2.6.27.7-9-default/build M=/home/art/Desktop/XFiDrv_Linux_Public_US_1.00
make[1]: Entering directory /usr/src/linux-2.6.27.7-9-obj/x86_64/default' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory /usr/src/linux-2.6.27.7-9-obj/x86_64/default’
make: *** [all] Error 2
linux-v9qj:/home/art/Desktop/XFiDrv_Linux_Public_US_1.00 #

Can someone please tell me what I am doing wrong?

Thanks!

#2

I thought XFi was not supported in 11.1 ? Support is planned for 11.2. But I don’t really know.

When I look here:
Matrix:Vendor-Creative Labs - AlsaProject
… it notes 1.0.21 of alsa is needed.

openSUSE-11.1 comes with 1.0.17/1.0.18 of alsa and not with 1.0.21 of alsa. But openSUSE-11.2 will likely have 1.0.21 of alsa in the kernel.

I supposed you could try updating alsa to 1.0.21 (per this url where six zypper commands are required Alsa-update - openSUSE ) , or simply wait until 11.2 GM is released.

#3

Sorry to dust off an old thread like this, but I have a very similar card:

lspci
00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2)
00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
01:0a.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)
02:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9500 GT] (rev a1)
03:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
**04:00.0 PCI bridge: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG PCI to PCIe Bridge
05:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG**

It should be noted that this card is not a true X-FI but rather a re-branded audigy.Sadly I can confirm that as of this date it does not work with 11.2 or any other linux distro (to my knowledge). It is being worked on in ALSA, but it has yet to function properly.
I do have an on-board chip though, so I don’t really need it, but I would like to get it working some time soon :(.

#4

Back in March2010, I did a search on the CA0110 and found this:

CA0110 seems buggy for 11.2, yes. It’s also buggy on upstream, too.
Unfortunately, there is no solution yet.

If it’s a X-Fi board with CA0110 (i.e. only HD-audio / Vista mode, no emu20kx
chip), it’s known that it doesn’t work.

Takashi Iwai is an alsa developer, and my view then was if he states it unfortunately does not work yet with Linux, then it likely does not work then with Linux. Any Linux.

There have been some alsa releases since, and I know note this when searching for the CA0110: Changes v1.0.20 v1.0.21 - AlsaProject and its possible that patch did not make it into the 1.0.20/1.0.21 of openSUSE-11.2. Hence you could try updating to 1.0.23 of alsa per guidance here: SDB:Alsa-update - openSUSE . Don’t forget to restart after updating. Note YaST does not yet work with X-Fi so do NOT use YaST when trying to configure. Just reboot and test with NO /etc/modprobe.d/50-sound.conf file. None.

If that fails then you could try writing a bug report on openSUSE-11.2, with guidance here for bug reporting: Submitting Bug Reports - openSUSE … use your opensuse forum username and password to log in to bugzilla. Raise the bug report against component “sound”. Do NOT reference a forum thread but rather put everything in the bug report that is useful. In particular attach to the bug report the /tmp/alsa-info.txt file from running:

/usr/sbin/alsa-info.sh --no-upload

Good luck.