Creative labs X-Fi sound card unsupported

According to creative their wont be drivers until the first quarter of 2007.

this does not affect "mesa", even though I managed to click on the wrong place and don't know how to undo now... sorry.

Sound card has nothing to do with mesa. Should be a alsa-driver bug instead.

It's Q1 2007 now. Anyone knows how the driver development is going?

from http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Creative_Labs#matrix

"Card delivered to developers. Completely new architecture. Creative actively preventing support due to no datasheets being released to ALSA developers. Reverse engineering work not started due to lack of time."

X-Fi Xtreme Audio Sound Blaster sound cards are not supported under Ubuntu or Linux YET! See http://opensource.creative.com/soundcard.html

A beta sound card driver has just been released from here: http://connect.creativelabs.com/linux/default.aspx

Important notes:
1. Needs < GCC 4.x to compile
2. 64-bit only
3. People seem to be having trouble compiling it

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

OSS 4.0 Build 1013 (released recently) apparently contains basic support: http://4front-tech.com/forum/viewtopic.php?p=7485#7485
Binaries: http://www.opensound.com/download.cgi
Source: http://developer.opensound.com/sources/
Apparently only basic playback works, but still better than silence, right?

Also, according to http://opensource.creative.com/soundcard.html#X-FI "source code for the SB XFi has been released" - whatever that means...

I can confirm that it doesnt work in latest hardy alpha

I think this should have a higher priority? I wouldn't say medium but definitely higher than wishlist. Still does not work in daily hardy build of March 23.

Reassigning "linux" as Åskar is reproducing this in hardy.

<afflux> askand: what version of ubuntu are you running?
<askand> afflux: writing this from hardy daily build
<afflux> askand: so hardy doesn't work? are you using kernel 2.6.24-12?
<askand> afflux: yes 2.6.24-12-generic

I attach output from lspci -vvnn.

I agree with Åskar in that this should have a higher priority - it's a real showstopper for some of us!
Also, I think a friend of mine got en X-Fi Audigy sound card working in Debian - maybe someone over there knows something?

I would say this should be adjusted to Low priority. Sound is more than a "wishlist" item for an OS, I would say, and as others mentioned for users with this card, this is a show stopper issue. If I couldn't have sound in an OS I would certainly switch to another.

Is the Linux Driver Project (http://www.linuxdriverproject.org/twiki/bin/view) still active, and if so can we collaborate with them?

Hello, I have recently joined the Ubuntu forums (URL for this topic: http://ubuntuforums.org/showthread.php?t=734400). I would like to post a comment to this bug report.

System OS: Dual-boot Hardy 8.04 LTS beta and MS Windows XP.
CPU: AMD64 4800+ dual core
Sound Card: Creative Labs X-Fi Fatal1ty with front-panel I/O connections (headphone jack)
Video Card: NVidia GeForce 7900 GTX, DVI output

As Mike Rooney just posted, I am the user who will be running MS Windows because Linux does not support my sound card. Thanks to the latest OSS beta driver in Hardy, I am running Linux (except for MS Windows applications).

Today, I can not get sound from my front-panel headphone jack. I think a driver should support everything that the hardware can do. My applications require this support, which is supplied today by an OS that is not Linux.

My vote as a user is to have a higher priority.

I think this should have a higher priority, too.
I have an ASUS computer, for which there are numerous Hardy sound problems, some of them related to the decision to use pulse, which doesn't work correctly with WINE.
These issues are going to be resolved only gradually.
The new computers don't have PCMCIA any more, they have those new slots, for which only this card works.
Sound isn't an option for me, it's a necessity.
I have RMI and use Dragon NaturallySpeaking with WINE to enter text.
Getting good sound is my highest priority..

I have heard that drivers are available for 64-bit systems only. The wikipedia article mentions them. If they can be made for 64, then they can be made for 32 also, without too much trouble.
Third parties have done work on this.

I have been told that this cant get a higher priority since it has never worked before, if it had worked before and somehow stopped working it had been given a higher priority. OSS is having betasupport for this card but OSS will not be used in Ubuntu, and alsa can not make a driver for the card if Creative does not give them the sources and Creative dont want to do that. Thwy want to develop a restricted driver, and that has been made for 64bit systems, however it didnt work for many people and I think it will take a long time before Creative give this a high priority. Sadly.

Anyone have any updates on this yet? I have also heard this seems to work via ALSA/OSS on 64 bit systems (and confirmed it myself via a 64 bit install); however, it still does NOT function on a 32-bit install and/or system (one in the same, sorry for the clarified sentence...).

Any ideas? It's been well over a year since this issue has surfaced. Dell is starting to use this card lien (X-Fi) in mostly ALL Dell XPS systems (710/720/730s) and I really ALSA/OSS might have the heat on for getting it supported in their 32 bit versions (if even for that). As far as I can tell, there is no work around (because I have tried everything!).

Clarification added:
Hardy Daily Build
Current Kernel
Up-to-Date ALSA (have tried OSS patches as well)

Posted on Dell's board at:

http://www.dellcommunity.com/supportforums/board/message?board.id=sw_linux&message.id=13546

Just an FYI for this.

I would say that this has a 'severe impact on a small portion of Ubuntu users' (those with an X-Fi card cannot get any sound - I'd say that would classify as "severe impact"). According to https://wiki.ubuntu.com/Bugs/Importance that means this bug should have "High importance" - someone should change this.

I agree, specially since the X-Fi is now one of the main selling cards for the Sound Blaster trademark and no matter what store you go into (Micro Center, BestBuy, Circuit City) or even buy your P.C. directly from Dell like I did (the XPS series!), it comes with an X-Fi card.

This should be reclassified with a more urgent priority as soon as possible...

* This is affecting many, many users on many levels (from switching, to staying to having to go out and buy new sound cards...).

* It will also affect the move to Ubuntu (and LINUX as a WHOLE) from Windows or Mac OS...

I agree with Mads's comment in regards to importance. Wishlist I believe is an inappropriate importance for this bug due to the medium-severe impact it has on a non-trivial number of users. Medium is the minimum importance I believe this should have, with High perhaps being more appropriate, due to the importance of sound in many domains and the complete lack of sound for users with this card.

In regards to Askar's comment, I am not sure who said that something must be a regression to count as more than wishlist; I am unaware of any policy remotely resembling this.

I will do my best to increase the importance of this, and I encourage others to provide their input here on what they believe the importance of this bug to be, either way, making sure to keep in mind the policies here: https://wiki.ubuntu.com/Bugs/Importance. I expect we will see this escalated to Medium or High within a week.

Here is why it should be supported.
The most numerous group of disabled persons that Linux supports is those that have minor Repetitive Motion Injuries. These persons (and I am one) can type and mouse somewhat, but cannot complete a long document without discomfort.
Enter WINE running Dragon NaturallySpeaking 9.0 Preferred. Suddenly text entry is easy and fun. Continuous speech recognition works in Linux, and works well.
But it DNS depends on EXCELLENT sound quality, which all of a sudden Ubuntu does not provide.
And I bought a brand-new ASUS with 3GB RAM just so I would have enough computing power not to worry.

Susan has also made yet another excellent point why this bug should be classified as High or Urgent as soon as possible.

We should help the ALSA project fix this if we can (I would even be willing to send them a donated card or two) -- or to our developers. Let me know if you require this. I am willing to assist in this manner.

xq

I just want to add that I was able to get basic sound out of my X-Fi card on hardy beta using this guide: http://ubuntu-utah.ubuntuforums.org/showthread.php?t=571656
This uses OSS, not ALSA, but I wonder if the ALSA developers could use it for something...

Problem is it's for 64 bit systems...

No, xq, not method 1. I used method 1 (the OSS driver) to enable sound, and I'm running 32bit.

Didn't work for me and I tried a while back, unfortunately.

I have also used the OSS-driver sucessfully on 32bit systems so it works, but this is not a good place to discuss that I think

X-Fi series
April 16, 2008 X-Fi 32-bit / 64-bit BETA Linux drivers are now available.

from: http://connect.creativelabs.com/opensource/Wiki/SoundCard%20Support.aspx

Thanks for the news, ExitDust, and congrats to Creative if this works. Hopefully some users here can try this out and report back. Also of note is the "Sound Blaster X-Fi Linux Beta Driver Feedback Program" which is linked to on that page. I think they want users to report any problems they have with it there.

Yes and hopefully soon ALSA can get this tested and integrated ASAP and we can get it into the stream...

I downloaded the drivers, downloaded the kernel source and alsa source, and have successfully configured alsa but not a kernel.
What's the easiest way to configure the kernel source?

Documentation regarding building the kernel can be found at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild , however you will want to disregard steps 1 through 5.

Will we be able to get this into Hardy?

Who has been assigned to this bug out of curiosity's sake? Is it only assigned to ALSA at this point and no one in the Ubuntu project?

Someone reporting to the kernel project is working on it and, using one of his unstable driver demos, I have gotten mine to work.
Susan

-----Original Message-----
>From: Craig Huffstetler <email address hidden>
>Sent: Feb 21, 2009 2:31 PM
>To: <email address hidden>
>Subject: [Bug 63352] Re: Creative labs X-Fi sound card unsupported
>
>Who has been assigned to this bug out of curiosity's sake? Is it only
>assigned to ALSA at this point and no one in the Ubuntu project?
>
>--
>Creative labs X-Fi sound card unsupported
>https://bugs.launchpad.net/bugs/63352
>You received this bug notification because you are a direct subscriber
>of the bug.

Is the unstable patch available for download & testing? I am running Jaunty Alpha (current).

>Is the unstable patch available for download & testing? I am running
>Jaunty Alpha (current).

Yes. It's the unstable snapshot in the link below.
BE VERY CAREFUL. AN EARLIER VERSION MAY HAVE MADE MY MACHINE UNSTABLE.
I lost some files.
And although this is just the "drivers," work has progressed on other parts of alsa.
http://www.kernel.org/pub/linux/kernel/people/tiwai/alsa/alsa-driver/

With a clean install of Jaunty RC1, and install (make, make install) of the Creative drivers, this is working for me now!
I did nothing other then the clean install -- an upgrade from 804 did not work (with "newer" alsa drivers) fwiw.

Stuart

Since the drivers are being developed for later kernel versions, this makes a good deal of sense. You probably must have the latest kernel and headers available. Also better with later alsa-libs.

NOTE: As of 20-Apr, Tashaki has added Creative drivers to the stable alsa-drivers version, so it's better to use stable than unstable. Just get the latest stable version as of the date you download.
Right now there is one small glitch. Recording settings are not saved. They return to the default (mute) with each boot. But that should change soon.

It does work with compiling the proprietary drivers from Creative since Jaunty Alpha 3, I believe. However, there are a few small glitches as Susan has pointed out.

I can't wait until I don't have to use the proprietary drivers. The other problem is, as usual, every time there is a kernel upgrade you must reinstall the drivers; however, this is to be expected.

Finally, A Creative X-Fi Driver Going Into ALSA

http://www.phoronix.com/scan.php?page=news_item&px=NzI3MA

USE THE LATEST VERSION OF ALSA:
http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-ubuntu-jaunty-904/

THEN LOAD THE XFI DRIVER:
http://wiki.debian.org/X-Fi OR http://www.kernel.org/pub/linux/kernel/people/tiwai/snapshot/

NOW I AM GETTING 7.1 SURROUND ON UBUNTU 9.04

@DR. VIMAL HURRY

I can confirm it worked for me. I've also got sound working.

09:02.0 Multimedia audio controller: Creative Labs SB X-Fi

Advanced Linux Sound Architecture Driver Version 1.0.20.
Compiled on Jul 10 2009 for kernel 2.6.28-13-generic (SMP).

$ modinfo snd_ctxfi
filename: /lib/modules/2.6.28-13-generic/updates/alsa/pci/ctxfi/snd-ctxfi.ko
license: GPL v2
description: X-Fi driver version 1.03
author: Creative Technology Ltd
srcversion: 74C99322454BCB3AA53A50C
alias: pci:v00001102d0000000Bsv*sd*bc*sc*i*
alias: pci:v00001102d00000005sv*sd*bc*sc*i*
depends: snd-pcm,snd
vermagic: 2.6.28-13-generic SMP mod_unload modversions
parm: use_system_timer:Foce to use system-timer (bool)
parm: reference_rate:Reference rate (default=48000) (uint)
parm: multiple:Rate multiplier (default=2) (uint)
parm: index:Index value for Creative X-Fi driver (array of int)
parm: id:ID string for Creative X-Fi driver (array of charp)
parm: enable:Enable Creative X-Fi driver (array of bool)

The latest kernel has that soundcard activated. I did not even have to download or compile anything.
In addition, if you do compile your own drivers, the X-fi has been moved to the "stable" branch, and it's better to use that.

susan@ubuntu:~$ modinfo snd_ctxfi
filename: /lib/modules/2.6.31-2-generic/kernel/sound/pci/ctxfi/snd-ctxfi.ko
license: GPL v2
description: X-Fi driver version 1.03
author: Creative Technology Ltd
srcversion: CE1ADD8B30CDCAC0CEDC62D
alias: pci:v00001102d0000000Bsv*sd*bc*sc*i*
alias: pci:v00001102d00000005sv*sd*bc*sc*i*
depends: snd-pcm,snd
vermagic: 2.6.31-2-generic SMP mod_unload modversions 586
parm: use_system_timer:Foce to use system-timer (bool)
parm: reference_rate:Reference rate (default=48000) (uint)
parm: multiple:Rate multiplier (default=2) (uint)
parm: index:Index value for Creative X-Fi driver (array of int)
parm: id:ID string for Creative X-Fi driver (array of charp)
parm: enable:Enable Creative X-Fi driver (array of bool)
susan@ubuntu:~$

Is this bug fixed for the "linux" task then? In what kernel does it
start working out of the box?

I think in mine, that is 2.6.31-2.
I don't think it worked in the one before that.

Not to sound like a complete retard, but how do you get that newer kernel? I'm on jaunty and stuck with OSS because ALSA doesn't speak X-Fi on kernel 2.6.28-13

in terminal:
sudo synaptic
from drop-down menu, "updates," activate all repositories, especially backports.
Reload
Mark all Upgrades
(see if it's listed.)
Install

I think this kernel has been backported to Jaunty, but I'm not sure, and I can't test because I'm on Karmic. It wouldn't be in the main repository. If it hasn't been backported, I'm not sure whether you can install it separately or would be better off doing a dist-upgrade into karmic.
In karmic, it's in the main repository.
HTH

On Fri, Jul 10, 2009 at 7:19 AM, Mads Peter
Rommedahl<email address hidden> wrote:
> Not to sound like a complete retard, but how do you get that newer
> kernel? I'm on jaunty and stuck with OSS because ALSA doesn't speak X-Fi
> on kernel 2.6.28-13

It is definitely not a stupid question :) The best option is to wait
until the next release and upgrade then, which will be 9.10 (Karmic
Koala ) this October.

If anyone else can confirm that it works out of the box on a Karmic
alpha (install the daily build or wait until July 23rd when
http://www.ubuntu.com/testing/karmic/alpha3 will be up) then I'll mark
as fixed!

I have just upgraded to karmic and I still don't have sound using ALSA (karmic also broke my OSS so right now I have no sound at all).
Please advice.

Go to the Ubuntu sound problems web site and follow instructions.
http://ubuntuforums.org/showthread.php?t=205449

If that doesn't work, try the following:

sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils alsa-source
sudo apt-get install build-essential linux-headers-$(uname -r) module-assistant alsa-source
sudo dpkg-reconfigure alsa-source
sudo module-assistant a-i alsa-source
reboot

If there is one thing that is typical of Linux problems then it is that they automagically fix themselves just when I'm about to file a bug report... I don't know what happened, but now sound works. Totally cool.

I'm marking it as fixed as it seems the ALSA shipped with karmic alpha3 (and probably alpha2 as well) detects the X-Fi (at last!!!)
It's good to have this fixed - better late than never :)

If anyone still have trouble just reopen the bug.

Hi,

So this is fixed for the Karmic alphas but still broken for Hardy and Jaunty? or are they fixed by messing with kernels?

Thanks, good luck and regards from
Tom :)

AFAIK it is still broken in both Hardy and Jaunty. I don't think the new kernel will be backported, so it's likely that they will remain broken (although I have no idea).

(as the original poster of this bug report)

I confirm that the Creative Labs X-Fi works fine on Ubuntu Karmic.

Confirmed working as well as of A3.

Are there any plans for a backport to both Jaunty/Hardy now?

Im pretty sure that there won't be any backporting of this to jaunty. I seem to recall reading a statement from a dev somewhere that backporting the kernel for this would require too much work (it's not really a *blocker* per se) - and with karmic only a few months away I doubt that it is worth the hassle.

I've waited for this for several years - I can wait two more months (or, well, I can't, but that's what alpha builds are for, right? :)

Has anyone attempted recording with this card? In past products record did not work.

Yes, I have recorded audio with it.

This is just a little FYI...
The card works pretty good (great recording) except that when you open alsamixer a slider adjustments under "record" is missing. I don't remember what it was. It wasn't the volume control.
I reported that on the alsa developer list and someone else said there was another, related, minor problem with the driver. He planned to look at these issues.
So, although now the card is considered substantially functional, and is available with the standard Karmic distro, you might be pleasantly surprised in a few weeks to find out that functionality gets a bit better.
Then again, you might not. I forget which word they used to describe the underlying code, but its meaning encompassed the terms "Byzantine" and "nutty."

Can someone tell me if X-FI support (ALSA) in Karmic Koala only concern X-FI EMU20K1 based card (xtreme music and upper) or if it works also with my X-FI Xtreme Audio pcie (Audigy SE based).

Thanks,

Mine's a pcie. Uses hda-codec-ca0110, if that's the one you're referring to.

Fresh install of 9.10 AMD64 - Ubuntu recognises the card and shows the sound card in the Sound Preferences Control Panel as:
   [SB X-Fi Xtreme Audio] CA0110-IBG but doesn't work.

I have the same card. It worked pretty well for a while but it has developed a bug. Sound just stops working at odd times. There may have been a regression.
Rob... try the following
modprobe snd-hda-codec
modprobe snd-hda-codec-ca0110
lsmod
Are your modules there? You may need snh-hda-intel too.
Remove the card.
Shut down the computer.
Put the card back in.
Turn on the computer.
Remember, these type of cards (for the moment) are not recognized by the system when they are plugged in. They have to be present on boot.
So, when mine stops working, I have to "tell" the machine that the card's been removed, and then turn it off, put the card in, then turn it back on.

Erhm... My X-Fi card is working flawlessly with ALSA in lucid. Why is this bug still open?

My card is almost working flawlessly.
It is recognized on startup and when I unplug and plug it in. And the recognition doesn't "die" on me like it used to do, occasionally.
However, when I use it and then close the application, about one time in four the card is not recognized when I re-open the application. It has to do with multiple sound instances. For instance, if I open and run a sound application using wine, then open and close a video file in Firefox, then try to re-open the wine sound application, it doesn't work.
Does anyone else have this problem? I'll try it today with audacity and firefox.

I am struggling with this card X-FI with the PCI-E connection. Is this the cause of the problem?

Reinstalled again and again now running ubuntu studio 10.04. Card detected with lspci:

4: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

Tried in a earlier installation to upgrade to latest alsa, also no sound.

I was a fan of ubuntu, but now i am really sad that this bug still exists for already more than a year.

it seems that no one is willing to take responsibility to fix this bug.

It is nice that the card seems to run on sertain systems but the internet is full with messages about failing X-FI cards on ubuntu

The default soundcard in the system is disabled in the system setup (bios) may be this onboard card causes the problem?

Plse find the output of system test below:

cat /proc/asound/card*/codec#*

Codec: Nvidia ID d
Address: 0
Function Id: 0x1
Vendor Id: 0x10de000d
Subsystem Id: 0x10de0101
Revision Id: 0x100100
No Modem Function Group found
Default PCM:
    rates [0x0]:
    bits [0x0]:
    formats [0x0]:
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x04 [Audio Output] wcaps 0x72b1: 8-Channels Digital Stripe CP
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000
    bits [0xe]: 16 20 24
    formats [0x5]: PCM AC3
  Unsolicited: tag=00, enabled=0
Node 0x05 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP
  Pincap 0x09000094: OUT Detect HDMI
  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x00:
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x04
Codec: Nvidia ID d
Address: 1
Function Id: 0x1
Vendor Id: 0x10de000d
Subsystem Id: 0x10de0101
Revision Id: 0x100100
No Modem Function Group found
Default PCM:
    rates [0x0]:
    bits [0x0]:
    formats [0x0]:
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x04 [Audio Output] wcaps 0x72b1: 8-Channels Digital Stripe CP
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000
    bits [0xe]: 16 20 24
    formats [0x5]: PCM AC3
  Unsolicited: tag=00, enabled=0
Node 0x05 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP
  Pincap 0x09000094: OUT Detect HDMI
  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x00:
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x04
Codec: Nvidia ID d
Address: 2
Function Id: 0x1
Vendor Id: 0x10de000d
Subsystem Id: 0x10de0101
Revision Id: 0x100100
No Modem Function Group found
Default PCM:
    rates [0x0]:
    bits [0x0]:
    formats [0x0]:
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x04 [Audio Output] wcaps 0x72b1: 8-Channels Digital Stripe CP
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000
    bits [0xe]: 16 20 24
    formats [0x5]: PCM AC3
  Unsolicited: tag=00, enabled=0
Node 0x05 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP
  Pincap 0x09000094: OUT Detect HDMI
  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x00:
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x04
Codec: Nvidia ID d
Address: 3
Function Id: 0x1
Vendor Id: 0x10de000d
Subsystem Id: 0x10de0101
Revision Id: 0x100100
No Modem Function Group found
Default PCM:
    rates [0x0]:
    bits [0x0]:
    formats [0x0]:
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=0, o=0, i=0...

@tneijsel, the internet is full of messages about failing X-Fi cards, yes, but they're all likely to be several years old, and all the problems have since been fixed. That's a strange argument.
Anyway, judging from your lspci, the card is detected correctly - this bug was/is about X-Fi cards not being detected at all. Obviously, that problem is solved.
I suspect that your problems have nothing to do with this bug. But hey, maybe ALSA is the problem - have you tried OSS?

lsmod gave gthe following output, it looks everything is there, but no sound and sound is not muted.

Module Size Used by
tda10048 11153 1
saa7134_dvb 22167 0
videobuf_dvb 5175 1 saa7134_dvb
dvb_core 86142 1 videobuf_dvb
saa7134_alsa 10380 1
snd_hda_codec_ca0110 6162 1
binfmt_misc 6587 1
ppdev 5259 0
tda18271 35267 2
tda8290 12092 1
tuner 20412 1
snd_usb_audio 75765 1
snd_hda_intel 21877 3
snd_hda_codec 74201 2 snd_hda_codec_ca0110,snd_hda_intel
snd_pcm_oss 35308 0
snd_mixer_oss 13746 1 snd_pcm_oss
snd_usb_lib 15658 1 snd_usb_audio
snd_hwdep 5412 2 snd_usb_audio,snd_hda_codec
snd_pcm 70662 6 saa7134_alsa,snd_usb_audio,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 1338 0
snd_seq_oss 26726 0
snd_seq_midi 4557 0
snd_rawmidi 19056 2 snd_usb_lib,snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47263 9 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
saa7134 143391 2 saa7134_dvb,saa7134_alsa
fbcon 35102 71
tileblit 2031 1 fbcon
font 7557 1 fbcon
bitblit 4707 1 fbcon
snd_timer 19098 2 snd_pcm,snd_seq
snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
nvidia 9932176 28
ir_common 38875 1 saa7134
v4l2_common 15431 2 tuner,saa7134
softcursor 1189 1 bitblit
uvcvideo 56990 0
snd 54148 24 saa7134_alsa,snd_hda_codec_ca0110,snd_usb_audio,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_hwdep,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
lp 7028 0
videodev 34361 4 tuner,saa7134,v4l2_common,uvcvideo
v4l1_compat 13251 2 uvcvideo,videodev
videobuf_dma_sg 10782 3 saa7134_dvb,saa7134_alsa,saa7134
videobuf_core 16356 3 videobuf_dvb,saa7134,videobuf_dma_sg
tveeprom 11102 1 saa7134
psmouse 63245 0
serio_raw 3978 0
parport 32635 2 ppdev,lp
agpgart 31724 1 nvidia
vga16fb 11385 1
vgastate 8961 1 vga16fb
soundcore 6620 1 snd
snd_page_alloc 7076 2 snd_hda_intel,snd_pcm
shpchp 28820 0
usb_storage 39425 0
usbhid 36110 0
hid 67032 1 usbhid
ohci1394 26950 0
ieee1394 81181 1 ohci1394
r8169 33980 0
mii 4381 1 r8169
ahci 32008 4

Oh, yes may be important. If I start the ubu 10.04 live disk there is sound. after installation ubu on the system there is no sound.

tneijsel / Mads Peter,
     Please don't discuss unrelated bug issues in closed bugs. It creates spam for subscribers. tneijsel, Please open a new bug for your issue and take the conversation there.

Thanks!

~JFo