Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
Ben Klein wrote: > 2009/5/1 Susan Cragin : >>> I filed ubuntu bug 369762. >> Ubuntu didn't think much of my bug. They sent me the following recipe to >> cure it, and marked the bug invalid. >> >> 1) Edit /etc/pulse/client.conf, and change "autospawn = yes" to "autospawn = >> no" >> 2) `touch $HOME/.pulse_a11y_nostart' >> 3) `asoundconf list' >> 4) choose the desired card from the previous command's output, and use >> `asoundconf set-default-card CARD', replacing CARD as appropriate >> 5) `killall pulseaudio' >> >> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 >> mentions a recent kernel patch that routes all audio through pulse. I wonder >> if this patch is the culprit? > > It mentions a patch, not a kernel patch. I'd be *very* surprised if > there was anything kernel-side specifically routing audio through There is a kernel patch to reroute character devices to user space; afair that patch is already in. The usage example I have seen given for that patch is to reroute /dev/dsp to pulseaudio. > pulse. More plausibly, it could be a libasound2 patch or even just a > hack to asound.conf/.asoundrc. bye michael
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
2009/5/1 Susan Cragin : >>I filed ubuntu bug 369762. > > Ubuntu didn't think much of my bug. They sent me the following recipe to cure > it, and marked the bug invalid. > > 1) Edit /etc/pulse/client.conf, and change "autospawn = yes" to "autospawn = > no" > 2) `touch $HOME/.pulse_a11y_nostart' > 3) `asoundconf list' > 4) choose the desired card from the previous command's output, and use > `asoundconf set-default-card CARD', replacing CARD as appropriate > 5) `killall pulseaudio' > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 > mentions a recent kernel patch that routes all audio through pulse. I wonder > if this patch is the culprit? It mentions a patch, not a kernel patch. I'd be *very* surprised if there was anything kernel-side specifically routing audio through pulse. More plausibly, it could be a libasound2 patch or even just a hack to asound.conf/.asoundrc.
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
>I filed ubuntu bug 369762. Ubuntu didn't think much of my bug. They sent me the following recipe to cure it, and marked the bug invalid. 1) Edit /etc/pulse/client.conf, and change "autospawn = yes" to "autospawn = no" 2) `touch $HOME/.pulse_a11y_nostart' 3) `asoundconf list' 4) choose the desired card from the previous command's output, and use `asoundconf set-default-card CARD', replacing CARD as appropriate 5) `killall pulseaudio' https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 mentions a recent kernel patch that routes all audio through pulse. I wonder if this patch is the culprit?
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
> I have tested the following and I believe found they were not the problem: --snip-- > (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine? >>> >>> After I started my testing, I did run into problems when I tried to >>> re-install pulseaudio and then remove it, but the PA problem was unrelated. >>> Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, >>> no more problems working with pulseaudio removed. So the whole thing was >>> sort of a red herring. >>> >>> I have re-installed my entire system since that problem went away, and >>> immediately purged pulseaudio, and that's where I'm working from now. Still >>> same problem. >> >>OK, thanks for that clarification. >> >>So you've tracked the problem down to kernel version 2.6.29? What >>version of ALSA drivers are in your working and broken kernels? > >I've actually tracked it to before that. > >Wine's audio last worked with one of Ubuntu's generic kernels, probably >2.6.28-10. >Ubuntu's current repository kernel is 2.6.28-11. That's the one I that caused >the problem. >The experimental bug-fix kernel is 2.6.28-12. That does not solve my problem. >(Here's where I got the kernel: http://kernel.ubuntu.com/~dtchen/test-kernels/ >) > >When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily >stable builds from a couple of weeks ago. >They are 0.1.19 now, today's daily stable build, compiled against >2.6.29-1-rt8-custom, which is what I am running at the moment. > >My 29-rt kernel is showing the same problems as the two kernels mentioned >above. >FWIW, the person who compiled the RT kernel said that he did so without >applying the Ubuntu patches. So that tells me that the change took place >outside the Ubuntu patches. Well, this may be a pulseaudio problem after all. It may not be a wine problem. For the first time this morning, I tried running audacity -- the linux version. (My system has pulseaudio purged.) Audacity behaves the same way under Linux it does under wine, freezing when I stop and re-start the record function. I filed ubuntu bug 369762.
Fw: Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
Whoops. This should have gone to the list. >Susan Cragin wrote: >> I have tested the following and I believe found they were not the >> problem: > --snip-- >> (3) problem with pulseaudio > How did you determine this? I thought you said your version of Ubuntu > was crippled if pulseaudio was removed, so did you use pasuspender? If > so, did you verify there was no pulseaudio process running while you > were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. >>> OK, thanks for that clarification. >>> >>> So you've tracked the problem down to kernel version 2.6.29? What >>> version of ALSA drivers are in your working and broken kernels? >> >> I've actually tracked it to before that. >> >> Wine's audio last worked with one of Ubuntu's generic kernels, probably >> 2.6.28-10. >> Ubuntu's current repository kernel is 2.6.28-11. That's the one I that >> caused the problem. >> The experimental bug-fix kernel is 2.6.28-12. That does not solve my >> problem. >> (Here's where I got the kernel: >> http://kernel.ubuntu.com/~dtchen/test-kernels/ ) >> >> When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily >> stable builds from a couple of weeks ago. >> They are 0.1.19 now, today's daily stable build, compiled against >> 2.6.29-1-rt8-custom, which is what I am running at the moment. >> >> My 29-rt kernel is showing the same problems as the two kernels mentioned >> above. >> FWIW, the person who compiled the RT kernel said that he did so without >> applying the Ubuntu patches. So that tells me that the change took place >> outside the Ubuntu patches. >> >> > >I've had a few users report crashing in steam games as a result of >pulseaudio: https://bugs.launchpad.net/bugs/367379 -- do you think this >is all related? > >Thanks, >Scott Ritchie Maybe. From the bug, it's hard to tell. But here's what I think. I think that the kernel made changes recently that changed how sound relates to the kernel, and tied pulseaudio closer to the kernel (hence those error messages I got under 2.6.28-11, which kernel was acknowledged to be buggy the day it came out). Some of the bugs they either backed out or corrected with 2.6.28-12. It would be interesting to see if they can get steam running with that kernel. If you are working with the steam-bug people ask them to add the below kernel, purge pulseaudio, and test with alsa only. http://kernel.ubuntu.com/~dtchen/test-kernels/ Of course, they need headers, image & restricted modules. Susan
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
Susan Cragin wrote: I have tested the following and I believe found they were not the problem: --snip-- (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. OK, thanks for that clarification. So you've tracked the problem down to kernel version 2.6.29? What version of ALSA drivers are in your working and broken kernels? I've actually tracked it to before that. Wine's audio last worked with one of Ubuntu's generic kernels, probably 2.6.28-10. Ubuntu's current repository kernel is 2.6.28-11. That's the one I that caused the problem. The experimental bug-fix kernel is 2.6.28-12. That does not solve my problem. (Here's where I got the kernel: http://kernel.ubuntu.com/~dtchen/test-kernels/ ) When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily stable builds from a couple of weeks ago. They are 0.1.19 now, today's daily stable build, compiled against 2.6.29-1-rt8-custom, which is what I am running at the moment. My 29-rt kernel is showing the same problems as the two kernels mentioned above. FWIW, the person who compiled the RT kernel said that he did so without applying the Ubuntu patches. So that tells me that the change took place outside the Ubuntu patches. I've had a few users report crashing in steam games as a result of pulseaudio: https://bugs.launchpad.net/bugs/367379 -- do you think this is all related? Thanks, Scott Ritchie
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
I have tested the following and I believe found they were not the problem: >>>--snip-- (3) problem with pulseaudio >>> >>>How did you determine this? I thought you said your version of Ubuntu >>>was crippled if pulseaudio was removed, so did you use pasuspender? If >>>so, did you verify there was no pulseaudio process running while you >>>were testing Wine? >> >> After I started my testing, I did run into problems when I tried to >> re-install pulseaudio and then remove it, but the PA problem was unrelated. >> Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, >> no more problems working with pulseaudio removed. So the whole thing was >> sort of a red herring. >> >> I have re-installed my entire system since that problem went away, and >> immediately purged pulseaudio, and that's where I'm working from now. Still >> same problem. > >OK, thanks for that clarification. > >So you've tracked the problem down to kernel version 2.6.29? What >version of ALSA drivers are in your working and broken kernels? I've actually tracked it to before that. Wine's audio last worked with one of Ubuntu's generic kernels, probably 2.6.28-10. Ubuntu's current repository kernel is 2.6.28-11. That's the one I that caused the problem. The experimental bug-fix kernel is 2.6.28-12. That does not solve my problem. (Here's where I got the kernel: http://kernel.ubuntu.com/~dtchen/test-kernels/ ) When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily stable builds from a couple of weeks ago. They are 0.1.19 now, today's daily stable build, compiled against 2.6.29-1-rt8-custom, which is what I am running at the moment. My 29-rt kernel is showing the same problems as the two kernels mentioned above. FWIW, the person who compiled the RT kernel said that he did so without applying the Ubuntu patches. So that tells me that the change took place outside the Ubuntu patches.
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
2009/4/30 Susan Cragin : >>2009/4/29 Susan Cragin : >>> I have tested the following and I believe found they were not the problem: >>--snip-- >>> (3) problem with pulseaudio >> >>How did you determine this? I thought you said your version of Ubuntu >>was crippled if pulseaudio was removed, so did you use pasuspender? If >>so, did you verify there was no pulseaudio process running while you >>were testing Wine? > > After I started my testing, I did run into problems when I tried to > re-install pulseaudio and then remove it, but the PA problem was unrelated. > Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no > more problems working with pulseaudio removed. So the whole thing was sort of > a red herring. > > I have re-installed my entire system since that problem went away, and > immediately purged pulseaudio, and that's where I'm working from now. Still > same problem. OK, thanks for that clarification. So you've tracked the problem down to kernel version 2.6.29? What version of ALSA drivers are in your working and broken kernels?
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
>2009/4/29 Susan Cragin : >> I have tested the following and I believe found they were not the problem: >--snip-- >> (3) problem with pulseaudio > >How did you determine this? I thought you said your version of Ubuntu >was crippled if pulseaudio was removed, so did you use pasuspender? If >so, did you verify there was no pulseaudio process running while you >were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. Susan
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
2009/4/29 Susan Cragin : > I have tested the following and I believe found they were not the problem: --snip-- > (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine?
Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
I'm changing the name of the thread. Pulseaudio has nothing to do with my current problem. I thought it did back when I started the thread, but my testing turned out to be incomplete. I still don't know what the problem is, but I believe it has to do with the way wine relates to the current Ubuntu configuration. Using the most current kernel, the most current updates (and using tomorrow's kernels and updates) dmix and dsnoop I believe are not recognized properly by wine because I'm not getting any sound through them. And I did file a bug, but I filed it back when I still thought it was a wine regression, so it's been a long and painful process of discovery. I have tested the following and I believe found they were not the problem: (1) wine regression: (2) problem with my experimental sound drivers; (3) problem with pulseaudio; (4) bizarre problem unique to me -- and for this I reinstalled the system an tested with the base before moving on. When I did the last install, with the current Ubuntu Studio, I got the same result using the downloaded Generic kernel. (Studio can use both Generic and Real-time kernels. Linux-rt didn't work for other reasons. It crashed on bootup.) I was informed that both then-current kernels had problems. So I got the linux-generic with current Ubuntu patches and a successful re-compile of the linux-rt without Ubuntu patches. And I still have exactly the same problem. Here are my current kernels: linux-rt: 2.6.29.1-rt8-custom (It doesn't include Ubuntu's patches.) linux-generic 2.6.28-12 (this is from the Ubuntu site and has Ubuntu's patches) When I run audacity through wine, I get the following input choices: MIME: Wine wave in mapper - Input MIME: dsnoop:Generic MIME: dsnoop:Generic Windows DirectSound: Primary Sound Capture Driver Windows DirectSound: dsnoop:Generic Windows DirectSound: dsnoop:Generic When I use the second option (MME: dsnoop:Generic) it works on the first pass, but when I try to stop and start it again -- no go. The second recording area pops up but it seems to "shimmer." The recording meter does not move. And then it freezes. (That is approximately what happens to me training DNS.) When I use the 5th option (Windows DirectSound: dsnoop:generic) it works on the first pass, but when I stop/start it I get the following error message: Error when opening sound device. Please check the input device settings and the project sample rate.