Fedora 11 and Creative Sound Cards (Rant)

jedimasterk · #1 10th June 2009, 12:10 AM

Real good Fedora Team!. I can see why your distributions are just plain Betaware!. Got this reply to a post from the Ubuntu forums about Fedora 11. Real Good!!. What are we suppose to just use onboard sound?!.

"
If you have a Soundblaster Live! or Audigy soundcard (that uses the emu10k1 drivers) you will have a horrible experience with F11. You will have kernel failures. I, and several others, filed at bug report at bugzilla and no one even triaged it. All I hear, weeks after the bug reports, are crickets chirping."

Can't you get anything right for a release?!.

rclark · #2 10th June 2009, 12:17 AM

Interesting if true. That is all I have in both my Linux boxes is the Sound Blaster Live cards as in the past Linux has had trouble with the onboard sound hardware. Linux has always been good to me as long as I used sound blaster technology.... We'll have to see....

**AdamW** · #3 10th June 2009, 12:49 AM

It's not accurate.

The bug has been assigned to the kernel team, whose responsibility it is. The issue only affects S/PDIF output, while the vast majority of people use analog output. If you use analog output you will not be affected by this at all.

Bug is https://bugzilla.redhat.com/show_bug.cgi?id=502698 .

edit - worth noting that there's an intersecting bug where the hardware defaults to digital output, so you have to flip it to analog if that's what you have - see https://fedoraproject.org/wiki/Commo...mu10k1-digital . That one we should get a fix for quite soon.

YeOK · #4 10th June 2009, 07:06 AM

Quote:

Originally Posted by jedimasterk

Real good Fedora Team!. I can see why your distributions are just plain Betaware!. Got this reply to a post from the Ubuntu forums about Fedora 11. Real Good!!. What are we suppose to just use onboard sound?!.

"
If you have a Soundblaster Live! or Audigy soundcard (that uses the emu10k1 drivers) you will have a horrible experience with F11. You will have kernel failures. I, and several others, filed at bug report at bugzilla and no one even triaged it. All I hear, weeks after the bug reports, are crickets chirping."

Can't you get anything right for a release?!.

What a guy, taking up the concerns of the Ubuntu forum and bringing them here to the good people of the Fedora forums.

My Creative Live is working great, once you switch it to analogue the pulseaudio changes shine through. I'm sure the kernel people will have the Digital fixed soon.

#5 10th June 2009, 07:14 AM

Ubungu user stay in your own territory .

if Ubuntu users have complaints let them come here an complain themselves instead of getting a puppet to do it for them

gadgetwiz · #6 10th June 2009, 08:23 AM

Quote:

Originally Posted by AdamW

The bug has been assigned to the kernel team, whose responsibility it is. The issue only affects S/PDIF output, while the vast majority of people use analog output. If you use analog output you will not be affected by this at all.

Thanks.

This the message I get with an original SB (EMU10k1) Live card.

Code:

Kernel failure message 1:
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
fuse init (API version 7.11)


Kernel failure message 2:
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
fuse init (API version 7.11)
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts

Moving to analog on both the input/output had no effect. Guess I'll have to wait for an updated kernel.

Actually, I've had Fedora sound issues since the inclusion of pulseaudio.

Since Fedora 10, the volumes of various applications will reset to 100% or some extremely loud level for no apparent reason. The is no consistency in volume levels from one app to another or any consistency on how those levels are set and controlled.

I seem to be experiencing these same issues with Fedora 11.

jedimasterk · #7 10th June 2009, 10:44 AM

Every time I installed Linux on my system with pulse audio. I have had to remove pulse audio and install esound just to get the sound to work. This has been going on since pulse audio came out. I own a Creative SoundBlaster Audigy Gamer sound card. My question is this?. What soundcards work flawlessly with pulse audio, out of the box?.

#8 10th June 2009, 11:26 AM

look at the pulseaudio wiki site

rookcifer · #9 10th June 2009, 06:14 PM

Quote:

Originally Posted by YeOK

What a guy, taking up the concerns of the Ubuntu forum and bringing them here to the good people of the Fedora forums.

My Creative Live is working great, once you switch it to analogue the pulseaudio changes shine through. I'm sure the kernel people will have the Digital fixed soon.

I am the one who made that post on the Ubuntu forums and, no, I did not send this guy over here (he obviously has a hatred of Fedora for some reason). I have moved to Kubuntu until/if this emu10k1 issue gets solved in Fedora. I do have to admit that I find it odd that this "kernel bug" disappears as soon as Pulseaudio is removed. The problem is that Pulseaudio cannot be removed in F11 like it could in F10 (it can be removed but it doesn't solve my problems like it did in F10). When I remove it in F11, I still have no control over my volume or alsa mixer settings. One would think that if this was a kernel bug that removing Pulseaudio would not stop the kernel failures. But it does.

Fedora is a great distro and it irks me that I have to switch distros over a kernel failure, but such is life.

Quote:

Thanks.

This the message I get with an original SB (EMU10k1) Live card.

Gadgetwiz, I started a bug report about this. Please post over there so we can get as many people complaining about this as possible.

**AdamW** · #10 10th June 2009, 07:50 PM

"One would think that if this was a kernel bug that removing Pulseaudio would not stop the kernel failures. But it does. "

Why would one think that? Software often exposes bugs in other software. There was a bug shortly before Fedora 11 where certain webpages in Firefox would cause the system to nearly hang. Turned out it was because these pages had 15,000 pixel high elements in them, which was causing the graphics card driver to barf. The bug there is in the graphics card driver, exposed by Firefox via the braindead design of the web page in question. Do we therefore say that the bug is in Firefox? No. The bug's in the graphics driver. Firefox just exposed it.

Same deal here - PA is exposing a kernel bug of some kind. When you're getting error messages from the kernel, there's a bug in the kernel. Doesn't matter what software _triggered_ it (except insofar as it helps isolate the issue).

gadgetwiz, are you the same guy who noted it still fails in analog mode on the original bug, or a different guy? This is important, I'm trying to figure out whether it often fails in analog mode too, or whether that's an unusual exception. Multiple people reported it works in analog mode, so something odd's going on there.

Cheval · #11 11th June 2009, 11:39 PM

I'm getting the same thing.

Code:

Kernel failure message 1:
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000



Kernel failure message 2:
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000


Kernel failure message 3:
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2001, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
fuse init (API version 7.11)
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
__ratelimit: 10 callbacks suppressed
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000
ALSA sound/core/pcm_lib.c:166: BUG: stream = 0, pos = 0x2000, buffer size = 0x2000, period size = 0x2000

I have a SBLive in there and am not trying to use digital or anything. This is what it shows after a clean install and first boot without anything touched. I never had problems before (exception: pulseaudio) with previous Fedora versions. I haven't made it far enough to see if Pulseaudio gives everything I watch the usual Tourette's Syndrome but hopefully that's gone in FC11.

Edit: yup any time I go to play something that makes a sound then that kernel failure box appears.

Shunyata · #12 12th June 2009, 04:03 AM

Same problem with a Creative X-Fi Extreme Music using Public US 1.00 Beta Drivers: Worked fine in F10, now I get kernel failures every time I start a program which makes a sound. Deinstalled the driver - no more kernel failures, reinstalled it - problems reappeared (reports sent). The problem that application sound is EXTREMELY LOUD by default appears as well: Especially annoying with flash since you often can't regulate the volume there. Would really appreciate a solution...

#13 12th June 2009, 04:07 AM

solution, buy a different Soundcard an get rid of anything Creative.

gadgetwiz · #14 12th June 2009, 05:37 AM

Quote:

Originally Posted by AdamW

gadgetwiz, are you the same guy who noted it still fails in analog mode on the original bug, or a different guy? This is important, I'm trying to figure out whether it often fails in analog mode too, or whether that's an unusual exception. Multiple people reported it works in analog mode, so something odd's going on there.

Yes, I still received the message after moving to analog mode. I haven't saw the message again but I think I told it not to notify me again, as it was annoying as hell, but I can take a look and post back any logs you direct me to, if that will help.

I do have sound on the system but as Shunyata reports, and I mentioned earlier, the volumes of various applications will reset to 100% or some extremely loud level for no apparent reason (even though the app's volume control is set to 1%). The is very little consistency in volume levels from one app to another or any consistency on how those levels are set and controlled.

mrwinkee · #15 12th June 2009, 07:01 AM

Quote:

Originally Posted by YeOK

What a guy, taking up the concerns of the Ubuntu forum and bringing them here to the good people of the Fedora forums.

My Creative Live is working great, once you switch it to analogue the pulseaudio changes shine through. I'm sure the kernel people will have the Digital fixed soon.

How do you switch it to analog?