1:22 p.m.
I've been using F11 since it came out and it works great. But I haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
$ uname -a
Linux localhost.localdomain 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16
23:11:39 EDT 2009 i686 i686 i386 GNU/Linux
$lsmod | grep snd
snd_hda_codec_idt 50560 1
snd_hda_intel 23920 3
snd_hda_codec 54264 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 6580 1 snd_hda_codec
snd_pcm 62556 2 snd_hda_intel,snd_hda_codec
snd_timer 17896 1 snd_pcm
snd 49044 12
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 5404 1 snd
snd_page_alloc 7572 2 snd_hda_intel,snd_pcm
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ yum list pulseaudio\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
pulseaudio-libs.i586 0.9.15-14.fc11 @updates
pulseaudio-libs-glib2.i586 0.9.15-14.fc11 @updates
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.18a.
yum list alsa\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
alsa-lib.i586 1.0.20-1.fc11 installed
alsa-lib-devel.i586 1.0.20-1.fc11 installed
alsa-oss.i586 1.0.17-3.fc11 installed
alsa-oss-devel.i586 1.0.17-3.fc11 installed
alsa-oss-libs.i586 1.0.17-3.fc11 installed
alsa-utils.i586 1.0.20-3.fc11 installed
I've run alsamixer -c0 and all the levels are set to their maximums.
I've removed pulseaudio and mplayer and removed the .mplayer folder and
then reinstalled mplayer.
How should I proceed from here ?
Thanks
6:32 p.m.
Marko Vojinovic wrote:
On Saturday 25 July 2009 01:48:05 Jeff Spaleta wrote:
> I will say that in this case..that a fresh install would be extremely
> advisable. Following lots of well-meaning troubleshooting from lots of
> different people for days and weeks to solve the same problem ends up
> leaving your system in a very strange state.
Precisely!
I haven't checked it first-hand, but I do have a hunch that people who
experience problems with sound are mainly the people who did an upgrade from
F10, while previously fiddled with F10 configuration in order to get the sound
working.
All of my six (so far) systems using FC11 were clean installs, four from LiveCD,
one from DVD, one from DVD image NFS mounted. Oh, and a test install from USB
made from the snapshot DVD, on one of those machines later reinstalled.
Four of six had simple output to the laptop speakers work after install, the two
desktops had two channel from the sound card, no setting I've found will
enable the other speakers from any source, even on hardware which had 5.1 with
Windows and FC6.
While people on the list may or may not know what settings you have
fiddled
around while troubleshooting, anaconda *definitely* cannot handle such
strangely configured systems while upgrading. AFAIK, it assumes a more-or-less
default F10 installation, where under-the-hood things haven't been customized
beyond some sane level.
So the first thing I would ask when troubleshooting F11 audio problems is "did
you do an upgrade from F10?" and if yes, "was PA working for you out-of-the-
box in F10?". This is just a hunch, but I bet 90% of people with problems
would fail to answer yes to the latter question. In that case, the only sane
thing to assume is that their system had broken configuration to begin with,
when upgrading to F11. And anaconda tries to *keep* any custom-configured
things in the system (which is the whole point of upgrading), and thus create
even more problems.
Your point about upgrade is well taken, three of the six worked worse after
upgrade from the install media to "current" using either yum (cli) or the update
menu item. Go figure.
There is a simple test to these kind of situations --- boot off a F11
Live CD,
check all mixer levels, and see if sound works out-of-the-box. If it does,
you've been bitten by your own previous configuration settings, and I would
advise a reformat and clean install of F11. If it doesn't, *then* try to
troubleshoot and whine on the list, while remembering that it is not
pulseaudio that is always the culprit. I have seen more bugs boiling down to
problems with alsa or userspace apps than problems with pa. The presence of pa
on the system mainly just reveals bugs of other components.
HTH.
Best, :-)
Marko
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
6 p.m.
On Sunday 26 July 2009 22:29:32 Bill Davidsen wrote:
The scary thing is that you don't see anything wrong with this
picture,
seven volume control, mixers, and device selectors, and also two config
files.
Have you ever visited a radio station studio or a TV studio? Do you know how
many mixer tables and boards are there, and how complicated they can be?
I, for one, would *want* to have a volume control and mixer app for every
sound card I have on the system, and in addition another set of such apps for
every sound source app I use. That way, I can fine-tune all the
playback/recording I might wish for.
If you want simplistic setup (the one-volume-knob-for-all setup), go install
Windows and click the small speaker image in its system tray --- a single
slider will show up for you to turn the volume up or down. That is simplistic.
Fedora (and Linux in general) is about ability to *have choice*, and that
comes with the price of complexity. One could also ask the same question for
the X window system --- why do we need a full-blown network-capable multi-user
multi-output multi-this multi-that video server? An average user has one
graphics card, one monitor, and doesn't use X over network. So one could say
it would be better to have some lightweight graphics server that only does the
typical stuff, while advanced users could install X optionally.
But this did not and will not happen in Linux, at least not in Fedora, because
Fedora users *like* to have a full-fledged complicated server as default at
their disposal to tweak as they see fit. Think pulseaudio. Think X. Think
sendmail. Think apache. Think selinux. Think udev, hal, pam, ssh... All these
complicated servers have more simplistic alternatives, but these more
simplistic ones also limit the user's ability to configure complicated setups.
And having this ability is what Linux is all about.
Imagine someone who has trouble setting up resolution or other parameters in X
for his particular hardware. And he comes to the list and bitches that X is
bullshit, way too complicated, lacks documentation, and should be installed
only optionally, for users that have a need for it. Would you support him and
advocate the removal of X from the default distro? I know I wouldn't.
Ditto for pulseaudio. It does have a steep learning curve, but so does X if
you want to mess with it. And please don't tell me that X has only one config
file.
Best, :-)
Marko
9:25 a.m.
On Thu, 30 Jul 2009 11:20:57 +0200
Michael Schwendt <mschwendt(a)gmail.com> wrote:
On Sat, 25 Jul 2009 19:39:25 -0700, stan wrote:
> I'm probably not the person to be defending pulse, because I leave it
> installed but disabled.
Is there a bullet-proof way to do that? Disabling PulseAudio is a FAQ for
Well, I *thought* there was, but yesterday I was using gnash to listen to sound samples on
http://www.freesound.org and I noticed that pulseaudio was running. Looks like I will
have to log in and download the samples I want to listen to. Better anyway because then
there is no distortion from mp3. ;-)
Fedora, openSUSE, and Ubuntu, too. The suggested "setting
autospawn = no
in /etc/pulse/client.conf" plus running "pulseaudio -k" plus
"configuring
audio players to use alsa drivers" doesn't work for all users. Last time I
tried it myself, I got socket errors and no audio. I had to run "yum -y
remove pulseaudio" as a work-around to actually remove several deps, too.
In addition to the steps you took, it is necessary to go into the directory /etc/alsa and
(re)move the file
pulse-default.conf. That file sets pulse to be the default alsa audio device, thus
spawning it anytime some
application tries to use the alsa default device, even when the application is set to
alsa. That would explain your
errors if pulse isn't available. Note that it is reinstalled anytime pulse is
updated.
With this additional step, I find that I can use alsa for audio with pulse still
installed. I don't use system sounds as I find them an annoyance rather than an aid,
so pulse isn't being spawned all the time.
However, I notice a trend that windowing interfaces are expecting to use pulse exclusively
for any sound applications they include. System sounds, gnash, etc. are designed without
alsa access as an option. So my fallback plan is to have two sound devices. Use the
onboard, not so great sound device for pulse. Use my more sophisticated card strictly
with alsa (leave pulse ignorant of it). When I work with sound I want exclusive sound,
sound configured explicitly, and having a dedicated device allows this.
My take is that pulse has its place for some people and situations, but it isn't for
serious sound. There it just introduces another layer to deal with, and doesn't
provide any benefit. It reminds me of an MS windows application, providing reasonable
functionality without much effort, and some cool factor or whiz bang. The equivalent of
desktop effects, except for sound. And there is a user base for that.
I'm not sure if there aren't other ways of doing things, or if the developers just
aren't creative, but linux seems to just copy MS windows in its development. Pulse
seems to be a part of this trend, so I'll have to learn to live with it.
7:45 a.m.
Michael Schwendt wrote:
On Sat, 25 Jul 2009 19:39:25 -0700, stan wrote:
> I'm probably not the person to be defending pulse, because I leave it
> installed but disabled.
Is there a bullet-proof way to do that? Disabling PulseAudio is a FAQ for
Fedora, openSUSE, and Ubuntu, too. The suggested "setting autospawn = no
in /etc/pulse/client.conf" plus running "pulseaudio -k" plus
"configuring
audio players to use alsa drivers" doesn't work for all users. Last time I
tried it myself, I got socket errors and no audio. I had to run "yum -y
remove pulseaudio" as a work-around to actually remove several deps, too.
How about going to the list of programs that are started when you
log in, and unchecking PA? I have not tried it, as PA works for me,
but it should work.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
5:35 a.m.
On Thursday 30 July 2009 10:20:57 Michael Schwendt wrote:
On Sat, 25 Jul 2009 19:39:25 -0700, stan wrote:
> I'm probably not the person to be defending pulse, because I leave it
> installed but disabled.
Is there a bullet-proof way to do that? Disabling PulseAudio is a FAQ for
Fedora, openSUSE, and Ubuntu, too. The suggested "setting autospawn = no
in /etc/pulse/client.conf" plus running "pulseaudio -k" plus
"configuring
audio players to use alsa drivers" doesn't work for all users. Last time I
tried it myself, I got socket errors and no audio. I had to run "yum -y
remove pulseaudio" as a work-around to actually remove several deps, too.
How about starting pasuspender in a clever way somewhere in, say, .login? It
would need some dummy never-ending process as a mandatory argument, but I'm
sure that can be figured out easily.
man pasuspender
I mean, if you are determined to hack your system to not use pa for sound, the
cleanest way would be to use the "off switch" provided by the pa itself, right?
However, I believe you still need to manually configure audio players to use
alsa drivers.
HTH, :-)
Marko
4:20 a.m.
On Sat, 25 Jul 2009 19:39:25 -0700, stan wrote:
I'm probably not the person to be defending pulse, because I
leave it
installed but disabled.
Is there a bullet-proof way to do that? Disabling PulseAudio is a FAQ for
Fedora, openSUSE, and Ubuntu, too. The suggested "setting autospawn = no
in /etc/pulse/client.conf" plus running "pulseaudio -k" plus
"configuring
audio players to use alsa drivers" doesn't work for all users. Last time I
tried it myself, I got socket errors and no audio. I had to run "yum -y
remove pulseaudio" as a work-around to actually remove several deps, too.
5:58 p.m.
Bill Davidsen wrote:
Mikkel L. Ellertson wrote:
>
> Yes, it can get complicated, especially if you have several sound
> cards, and you want to direct different sources to different cards.
> But I think the flexibility is worth it.
>
If this was optional I might agree, but the assumption that the standard
sound config should use seven sound tools and two config files when the
typical user has been playing one source to two speakers since
1.2.13/oss days is divorced from reality.
Well, if you don't want it, you can turn it off on a per user basis
by un-checking one check box, unless you set it up as system wide
service, instead of hte default per user server.
The thing is, the typical user wants to do a lot more then that now
days. Things like a video from a web site in a web browser, an alert
when they get an IM, new mail, or an incoming call. Or they may be
playing an incoming audio stream. There are users who have surround
sound or digital output connected. Then you have the people that
that want to redirect the audio from one computer over the network
to another computer.
Sound usage is changing, and the software is changing to meet the
new demands. All the arguments and complaints reminds me of the
change to udev. I heard a lot of the same complaints.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
5:43 p.m.
Bill Davidsen wrote:
The scary thing is that you don't see anything wrong with this
picture,
seven volume control, mixers, and device selectors, and also two config
files.
I have always had more then one volume control. The fact that they
control the same device is beside the point. One thing I think you
are overlooking is that if you are using only sound source, you only
need the Alsa mixer. You can leave the PA controls at max. When you
start mixing more then one source through the same output, then you
may have to adjust the input for each source. When you are
outputting to more then one card, you may need to adjust the volume
on each output.
As far as config files, you probably have more then two. I know I
have the Alsa config, the PA config, and config for various players.
Then again, if you want to see complicated, look at all the config
files you need for networking. Or look at all the config files for
Gnome, KDE, or the collection of window managers. Even Posfix has
more then one config file. What would bother me is if they tried to
combine all the config files into one file. Windows uses that
method, and you know what a mess the registry is.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
4:42 p.m.
Craig White wrote:
On Sat, 2009-07-25 at 19:34 -0400, Bill Davidsen wrote:
> Craig White wrote:
>> On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
>>> If it doesn't work out of the box there are no tools to ever make it
>>> work, which
>>> is why PA should be in the toybox, not the default.
>> ----
>> ignoring the reality that PA works for most people out of the box, I
>> would agree with you but I can't ignore the reality. It works for me. It
>> has worked for me on every computer I have installed Fedora on. It works
>> for me on every computer I have installed Ubuntu on.
>>
> So tools to correct the cases which don't work out of the box and can't be
made
> to work are not needed because it works most of the time? What do we need this
> Linux for anyway, after all Windows works most of the time...
----
you make less sense every time you get deeper into this discussion.
If you think Windows is less trouble, you should use Windows. I don't
have a problem with that.
If you think pulse audio is a problem, then don't use it. I have no
problem with that.
pulse audio is little more than a collection layer for audio from
various sources. I am fairly convinced that most of the griping I see on
this list about pulse audio has less to do with pulse audio than people
having trouble getting their Intel motherboard audio to work properly.
Pulseaudio just seems to be a convenient spot to focus one's blame.
When sound worked with FC4 and FC6 (and in some cases FC9) and no Intel boards
are involved I think you're trying hard to sweep this udner the rug.
I recognize that it is frustrating to have problems, even
regressions
with new releases of Fedora but you have to keep in mind that the
kernel, the kernel modules and of course the underlying software is
still in a rapid state of change and the way to make it work for
yourself and everyone else behind you is to perform diligent bug
reports.
I keep in mind that this has been getting worse, not better, since PA was
introduced. I care not that it exists, only that it is standard rather than some
collection of optional stuff people can install if they need it.
If you think that I don't understand these issues, I have had
bug
reports about not being able to boot Optiplex 320's via grub since
Fedora 7.
The problem with open source, when people have no reward for giving the user
what they want rather than what the developer wants and taking the attitude that
"it's free if you don't like it don't use it." Also the attitude
that developers
write code and lesser beings write documentation. PA is a solution most people
don't need, in search of a problem most people don't have.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
4:33 p.m.
Mikkel L. Ellertson wrote:
Bill Davidsen wrote:
> Craig White wrote:
>> On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
>>> If it doesn't work out of the box there are no tools to ever make it
>>> work, which is why PA should be in the toybox, not the default.
>> ----
>> ignoring the reality that PA works for most people out of the box, I
>> would agree with you but I can't ignore the reality. It works for me. It
>> has worked for me on every computer I have installed Fedora on. It works
>> for me on every computer I have installed Ubuntu on.
>>
> So tools to correct the cases which don't work out of the box and can't
> be made to work are not needed because it works most of the time? What
> do we need this Linux for anyway, after all Windows works most of the
> time...
>
There are tools, but they are not really dedicated Pulse Audio
tools. You have to go to the Pulse Audio web side that read the
documentation there. (I don't have the link handy, but I posted it
in this thread already.) The one time I had problems, it was an Alsa
configuration problem after an upgrade... (/etc/asound.conf problem.)
There are things like the Pulse Audio volume meters that can tell
you if the signal is getting to pa. The pa volume control can tell
you a lot more about what is going on. For a lot more information,
but harder to understand, there is the device chooser and audio manager.
When you drop down to the Alsa layer, there are tools like aplay and
amixer. There is also alsa-info. System-config-sound mostly works
with this layer. Then there are the assorted volume controls. I use
the standard Gnome volume control, and it offers different sets of
mixer controls, depending on what level/card you are trying to control.
Yes, it can get complicated, especially if you have several sound
cards, and you want to direct different sources to different cards.
But I think the flexibility is worth it.
If this was optional I might agree, but the assumption that the standard sound
config should use seven sound tools and two config files when the typical user
has been playing one source to two speakers since 1.2.13/oss days is divorced
from reality.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
4:29 p.m.
Mikkel L. Ellertson wrote:
Bill Davidsen wrote:
> Four of six had simple output to the laptop speakers work after install,
> the two desktops had two channel from the sound card, no setting I've
> found will enable the other speakers from any source, even on hardware
> which had 5.1 with Windows and FC6.
>
You may want to look at:
http://pulseaudio.org/wiki/FAQ#Troubleshooting
I have a surround sound card, but PulseAudio uses just the front
speakers!
Many people have a surround card, but have speakers for just two
channels, so PulseAudio can't really default to a surround setup. To
enable all the channels, edit /etc/pulse/daemon.conf: uncomment the
default-sample-channels line (i.e. remove the semicolon from the
beginning of the line) and set the value to 6 if you have a 5.1
setup, or 8 if you have 7.1 setup etc. After doing the edit, restart
pulseaudio.
The scary thing is that you don't see anything wrong with this picture, seven
volume control, mixers, and device selectors, and also two config files.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
9:39 p.m.
On Sat, 25 Jul 2009 18:56:59 -0700
Markus Kesaromous <remotestar(a)live.com> wrote:
On Sat, 2009-07-25 at 19:34 -0400, Bill Davidsen wrote:
> Craig White wrote:
> pulse audio is little more than a collection layer for audio from
> various sources. I am fairly convinced that most of the griping I
> see on this list about pulse audio has less to do with pulse audio
> than people having trouble getting their Intel motherboard audio to
> work properly. Pulseaudio just seems to be a convenient spot to
> focus one's blame.
Well, not entirely true. I had to stop pulseaudio because it was
slowing down my machine quiet a lot. Top showed it was using between
20 and 38% of cpu bandwidth. Believe it or not, even after the audio
track stopped playing!! I DO NOT need a CPU killer audio deamon,
thank you.
I'm probably not the person to be defending pulse, because I leave it
installed but disabled. However, a sound server like pulse will
*always* have the potential to use a lot of cpu because it has to
ensure that all sounds it mixes match the frame rate of the device at
the rate for which it has opened it. This can require on-the-fly rate
conversion, which, while getting faster, is still compute intensive if
done to any quality level. If the sound server is at 44100 Hz (CD
quality) and you are playing 48000 Hz (movie) sound, this is going to
require conversion. So, if you don't want pulse to use a lot of cpu,
make sure you only play sounds at the frame rate of the sound
server. :-^
I can't explain the fact it did this after the track stopped though.
Did you check after a few seconds of stoppage. It should have cleaned
up at that point and gone back to sleep.
8:56 p.m.
----------------------------------------
From: craigwhite(a)azapple.com
To: fedora-list(a)redhat.com
Date: Sat, 25 Jul 2009 18:48:37 -0700
Subject: Re: From the top... how do I get sound working in F11 ?
On Sat, 2009-07-25 at 19:34 -0400, Bill Davidsen wrote:
> Craig White wrote:
>> On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
>>> If it doesn't work out of the box there are no tools to ever make it
>>> work, which
>>> is why PA should be in the toybox, not the default.
>> ----
>> ignoring the reality that PA works for most people out of the box, I
>> would agree with you but I can't ignore the reality. It works for me. It
>> has worked for me on every computer I have installed Fedora on. It works
>> for me on every computer I have installed Ubuntu on.
>>
> So tools to correct the cases which don't work out of the box and can't be
made
> to work are not needed because it works most of the time? What do we need this
> Linux for anyway, after all Windows works most of the time...
----
you make less sense every time you get deeper into this discussion.
If you think Windows is less trouble, you should use Windows. I don't
have a problem with that.
If you think pulse audio is a problem, then don't use it. I have no
problem with that.
pulse audio is little more than a collection layer for audio from
various sources. I am fairly convinced that most of the griping I see on
this list about pulse audio has less to do with pulse audio than people
having trouble getting their Intel motherboard audio to work properly.
Pulseaudio just seems to be a convenient spot to focus one's blame.
Well, not entirely true. I had to stop pulseaudio because it was slowing
down my machine quiet a lot. Top showed it was using between 20 and 38%
of cpu bandwidth. Believe it or not, even after the audio track stopped
playing!! I DO NOT need a CPU killer audio deamon, thank you.
I recognize that it is frustrating to have problems, even regressions
with new releases of Fedora but you have to keep in mind that the
kernel, the kernel modules and of course the underlying software is
still in a rapid state of change and the way to make it work for
yourself and everyone else behind you is to perform diligent bug
reports.
If you think that I don't understand these issues, I have had bug
reports about not being able to boot Optiplex 320's via grub since
Fedora 7.
Griping on this list is for losers.
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
_________________________________________________________________
Windows Live™ SkyDrive™: Store, access, and share your photos. See how.
http://windowslive.com/Online/SkyDrive?ocid=TXT_TAGLM_WL_CS_SD_photos_072009
8:48 p.m.
On Sat, 2009-07-25 at 19:34 -0400, Bill Davidsen wrote:
Craig White wrote:
> On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
>> If it doesn't work out of the box there are no tools to ever make it
>> work, which
>> is why PA should be in the toybox, not the default.
> ----
> ignoring the reality that PA works for most people out of the box, I
> would agree with you but I can't ignore the reality. It works for me. It
> has worked for me on every computer I have installed Fedora on. It works
> for me on every computer I have installed Ubuntu on.
>
So tools to correct the cases which don't work out of the box and can't be made
to work are not needed because it works most of the time? What do we need this
Linux for anyway, after all Windows works most of the time...
----
you make less sense every time you get deeper into this discussion.
If you think Windows is less trouble, you should use Windows. I don't
have a problem with that.
If you think pulse audio is a problem, then don't use it. I have no
problem with that.
pulse audio is little more than a collection layer for audio from
various sources. I am fairly convinced that most of the griping I see on
this list about pulse audio has less to do with pulse audio than people
having trouble getting their Intel motherboard audio to work properly.
Pulseaudio just seems to be a convenient spot to focus one's blame.
I recognize that it is frustrating to have problems, even regressions
with new releases of Fedora but you have to keep in mind that the
kernel, the kernel modules and of course the underlying software is
still in a rapid state of change and the way to make it work for
yourself and everyone else behind you is to perform diligent bug
reports.
If you think that I don't understand these issues, I have had bug
reports about not being able to boot Optiplex 320's via grub since
Fedora 7.
Griping on this list is for losers.
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
8:09 p.m.
On Saturday 25 July 2009, Bill Davidsen wrote:
Craig White wrote:
> On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
>> If it doesn't work out of the box there are no tools to ever make it
>> work, which
>> is why PA should be in the toybox, not the default.
>
> ----
> ignoring the reality that PA works for most people out of the box, I
> would agree with you but I can't ignore the reality. It works for me. It
> has worked for me on every computer I have installed Fedora on. It works
> for me on every computer I have installed Ubuntu on.
So tools to correct the cases which don't work out of the box and can't be
made to work are not needed because it works most of the time? What do we
need this Linux for anyway, after all Windows works most of the time...
+1000, spot on as usual Bill.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>
In the future, you're going to get computers as prizes in breakfast cereals.
You'll throw them out because your house will be littered with them.
7:29 p.m.
Bill Davidsen wrote:
Four of six had simple output to the laptop speakers work after install,
the two desktops had two channel from the sound card, no setting I've
found will enable the other speakers from any source, even on hardware
which had 5.1 with Windows and FC6.
You may want to look at:
http://pulseaudio.org/wiki/FAQ#Troubleshooting
I have a surround sound card, but PulseAudio uses just the front
speakers!
Many people have a surround card, but have speakers for just two
channels, so PulseAudio can't really default to a surround setup. To
enable all the channels, edit /etc/pulse/daemon.conf: uncomment the
default-sample-channels line (i.e. remove the semicolon from the
beginning of the line) and set the value to 6 if you have a 5.1
setup, or 8 if you have 7.1 setup etc. After doing the edit, restart
pulseaudio.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
7:27 p.m.
Bill Davidsen wrote:
Mikkel L. Ellertson wrote:
> I would probably start at:
> http://pulseaudio.org/wiki/Documentation
>
> There is a nice menu on the right side that serves as a table of
> contents, as well as pointing to where to find information on things
> like userland programs.
>
A list of tools is nice, much like giving someone a car which doesn't
work and packing list for a big set of auto tools, complete with notes
on what the individual tool does, and letting that someone fix the car.
What is lacking is some procedure for finding the problems, diagnostics,
not the tools to fix them.
All I find is lists of tools, and people who say it works for them so
"it must be your hardware" even thought it works with FC6. And people
who see no problem holding the conflicting concepts that it "works right
off the bat" and "you have it set up wrong."
Did you actually visit the site? It is much more then a list of
tools. And the links to the tools is a like to directions on how to
use them. You may find this link helpful...
http://pulseaudio.org/wiki/FAQ#Troubleshooting
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
7:20 p.m.
Bill Davidsen wrote:
Craig White wrote:
> On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
>> If it doesn't work out of the box there are no tools to ever make it
>> work, which is why PA should be in the toybox, not the default.
> ----
> ignoring the reality that PA works for most people out of the box, I
> would agree with you but I can't ignore the reality. It works for me. It
> has worked for me on every computer I have installed Fedora on. It works
> for me on every computer I have installed Ubuntu on.
>
So tools to correct the cases which don't work out of the box and can't
be made to work are not needed because it works most of the time? What
do we need this Linux for anyway, after all Windows works most of the
time...
There are tools, but they are not really dedicated Pulse Audio
tools. You have to go to the Pulse Audio web side that read the
documentation there. (I don't have the link handy, but I posted it
in this thread already.) The one time I had problems, it was an Alsa
configuration problem after an upgrade... (/etc/asound.conf problem.)
There are things like the Pulse Audio volume meters that can tell
you if the signal is getting to pa. The pa volume control can tell
you a lot more about what is going on. For a lot more information,
but harder to understand, there is the device chooser and audio manager.
When you drop down to the Alsa layer, there are tools like aplay and
amixer. There is also alsa-info. System-config-sound mostly works
with this layer. Then there are the assorted volume controls. I use
the standard Gnome volume control, and it offers different sets of
mixer controls, depending on what level/card you are trying to control.
Yes, it can get complicated, especially if you have several sound
cards, and you want to direct different sources to different cards.
But I think the flexibility is worth it.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
6:54 p.m.
Mikkel L. Ellertson wrote:
Bill Davidsen wrote:
> Craig White wrote:
>> Fedora was expecting to use PulseAudio but you removed that as your
>> predicate. That puts you with a vocal minority who would rather gripe
>> about pulse audio than make it work so it will be up to them to tell
>> you how to solve the sound issues that you 'fixed' by removing
>> pulseaudio package.
>>
> Good, then point us to the documentation which describes how to make the
> alsamixer, advanced mixer, PA volume and tabs, and anything else which
> might clarify how to use the four or five sound apps which all interact
> with each other in such a way that sound works without days of fiddling
> which stop working at the next upgrade. PA is too damn fragile to use
> unless you are one of the few who has it work out of the box.
>
I would probably start at:
http://pulseaudio.org/wiki/Documentation
There is a nice menu on the right side that serves as a table of
contents, as well as pointing to where to find information on things
like userland programs.
A list of tools is nice, much like giving someone a car which doesn't work and
packing list for a big set of auto tools, complete with notes on what the
individual tool does, and letting that someone fix the car. What is lacking is
some procedure for finding the problems, diagnostics, not the tools to fix them.
All I find is lists of tools, and people who say it works for them so "it must
be your hardware" even thought it works with FC6. And people who see no problem
holding the conflicting concepts that it "works right off the bat" and "you
have
it set up wrong."
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
6:34 p.m.
Craig White wrote:
On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
> If it doesn't work out of the box there are no tools to ever make it
> work, which
> is why PA should be in the toybox, not the default.
----
ignoring the reality that PA works for most people out of the box, I
would agree with you but I can't ignore the reality. It works for me. It
has worked for me on every computer I have installed Fedora on. It works
for me on every computer I have installed Ubuntu on.
So tools to correct the cases which don't work out of the box and can't be
made
to work are not needed because it works most of the time? What do we need this
Linux for anyway, after all Windows works most of the time...
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
12:11 p.m.
On Sat, 2009-07-25 at 09:46 +0100, Anne Wilson wrote:
I have three very different systems where PA has worked
perfectly out-of-the-box.
Same here.
I'm not denying that some people have problems, but
going by my experience there must be many that don't.
And again.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
5:37 a.m.
On Saturday 25 July 2009 01:48:05 Jeff Spaleta wrote:
I will say that in this case..that a fresh install would be
extremely
advisable. Following lots of well-meaning troubleshooting from lots of
different people for days and weeks to solve the same problem ends up
leaving your system in a very strange state.
Precisely!
I haven't checked it first-hand, but I do have a hunch that people who
experience problems with sound are mainly the people who did an upgrade from
F10, while previously fiddled with F10 configuration in order to get the sound
working.
While people on the list may or may not know what settings you have fiddled
around while troubleshooting, anaconda *definitely* cannot handle such
strangely configured systems while upgrading. AFAIK, it assumes a more-or-less
default F10 installation, where under-the-hood things haven't been customized
beyond some sane level.
So the first thing I would ask when troubleshooting F11 audio problems is "did
you do an upgrade from F10?" and if yes, "was PA working for you out-of-the-
box in F10?". This is just a hunch, but I bet 90% of people with problems
would fail to answer yes to the latter question. In that case, the only sane
thing to assume is that their system had broken configuration to begin with,
when upgrading to F11. And anaconda tries to *keep* any custom-configured
things in the system (which is the whole point of upgrading), and thus create
even more problems.
There is a simple test to these kind of situations --- boot off a F11 Live CD,
check all mixer levels, and see if sound works out-of-the-box. If it does,
you've been bitten by your own previous configuration settings, and I would
advise a reformat and clean install of F11. If it doesn't, *then* try to
troubleshoot and whine on the list, while remembering that it is not
pulseaudio that is always the culprit. I have seen more bugs boiling down to
problems with alsa or userspace apps than problems with pa. The presence of pa
on the system mainly just reveals bugs of other components.
HTH.
Best, :-)
Marko
7:48 p.m.
On Fri, Jul 24, 2009 at 3:52 PM, Craig White<craigwhite(a)azapple.com> wrote:
ignoring the reality that PA works for most people out of the box, I
would agree with you but I can't ignore the reality. It works for me. It
has worked for me on every computer I have installed Fedora on. It works
for me on every computer I have installed Ubuntu on.
I'm in the same boat. I'd love to help people troubleshoot..but since
I haven't experienced any noticeable problems on my hardware that were
attributable to pulseaudio I don't have enough experience breaking and
unbreaking my own system's pulseaudio configurations to intuit answers
concerning other people's systems.
I will say that in this case..that a fresh install would be extremely
advisable. Following lots of well-meaning troubleshooting from lots of
different people for days and weeks to solve the same problem ends up
leaving your system in a very strange state.
What people like Linuxguy123 seem to forget is that most advice from
peer users on a list like this is predicated on the assumption that
the system in question is close to a unperturbed configuration. Most
people who are willing to help are not themselves experts in the
details of the subsystem operation which is malfunctioning. The more
configuration changes made, the more you undemine the validity of the
underlying assumptions that people are holding in their minds
concerning the system state and the more frustrating it becomes for
everyone involved in diagnosing the system. I may not know how to fix
every possible problem with a modern linux system..but I sure know how
to cause difficult to diagnose problems by twiddling configurations
without making detailed notes about what changes I've made.
-jef"pulseaudio support for bluetooth headset pairing is great"spaleta
7:30 p.m.
Bill Davidsen wrote:
Craig White wrote:
> Fedora was expecting to use PulseAudio but you removed that as your
> predicate. That puts you with a vocal minority who would rather gripe
> about pulse audio than make it work so it will be up to them to tell
> you how to solve the sound issues that you 'fixed' by removing
> pulseaudio package.
>
Good, then point us to the documentation which describes how to make the
alsamixer, advanced mixer, PA volume and tabs, and anything else which
might clarify how to use the four or five sound apps which all interact
with each other in such a way that sound works without days of fiddling
which stop working at the next upgrade. PA is too damn fragile to use
unless you are one of the few who has it work out of the box.
I would probably start at:
http://pulseaudio.org/wiki/Documentation
There is a nice menu on the right side that serves as a table of
contents, as well as pointing to where to find information on things
like userland programs.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
6:52 p.m.
On Fri, 2009-07-24 at 19:31 -0400, Bill Davidsen wrote:
If it doesn't work out of the box there are no tools to ever make
it
work, which
is why PA should be in the toybox, not the default.
----
ignoring the reality that PA works for most people out of the box, I
would agree with you but I can't ignore the reality. It works for me. It
has worked for me on every computer I have installed Fedora on. It works
for me on every computer I have installed Ubuntu on.
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
6:31 p.m.
Craig White wrote:
Linuxguy123 wrote:
> On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
>
>> On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com>
>> wrote:
>>
>>> I've been using F11 since it came out and it works great. But I
haven't
>>> had any sound since I did the upgrade. Sound worked great in F10. Its
>>> getting old not having sound. How do I get it working ?
>>>
>>>
> What is Fedora expecting us to use and what do we need to do to get it
> working ?
>
> Thanks
----
Fedora was expecting to use PulseAudio but you removed that as your
predicate. That puts you with a vocal minority who would rather gripe
about pulse audio than make it work so it will be up to them to tell you
how to solve the sound issues that you 'fixed' by removing pulseaudio
package.
Good, then point us to the documentation which describes how to make the
alsamixer, advanced mixer, PA volume and tabs, and anything else which might
clarify how to use the four or five sound apps which all interact with each
other in such a way that sound works without days of fiddling which stop working
at the next upgrade. PA is too damn fragile to use unless you are one of the few
who has it work out of the box.
PA should have been an option for whoever has the bizarre obscure problem PA
solves. And I have not been able to get any reasonable input from mic or line
with PA on any of five systems, three of which work with SuSE, or Ubuntu, or
Slackware (that's what the users changed to).
If it doesn't work out of the box there are no tools to ever make it work, which
is why PA should be in the toybox, not the default.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
6:21 p.m.
Linuxguy123 wrote:
On Tue, 2009-07-14 at 17:21 -0500, Jud Craft wrote:
> You could try yum reinstalling PulseAudio.
>
> If you had tried a fresh install of F11 on a small side partition, you
> could figure out whether "F11 sound is the problem" or "my
upgrade"
> was the problem, since Fedora upgrades seem to have bugs of their own
> quite often, and the Linux sound infrastructure did go through changes
> between F10 and F11; wouldn't surprise me to hear that a plain upgrade
> wouldn't work right.
>
> I'd try reinstalling PulseAudio.
I've already tried that. It doesn't work.
> Then I'd try a clean install of Fedora.
Don't ever suggest that re installing an operating system is the
solution to a problem. It isn't. It would take me several days to
re-install. Re installing is a stab in the dark at best.
Clue - boot from a Live-CD and see if sound works there, should take less than
several days.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
8:30 a.m.
2009/7/15 <gilpel(a)altern.org>:
> Fedora was expecting to use PulseAudio but you removed that as
your
predicate. That puts you with a vocal minority who would rather gripe
about pulse audio than make it work so it will be up to them to tell you
how to solve the sound issues that you 'fixed' by removing pulseaudio
package.
I didn't remove pulseaudio:
yum install pulseaudio
Loaded plugins: refresh-packagekit
Setting up Install Process
Package pulseaudio-0.9.15-14.fc11.x86_64 already installed and latest version
Nothing to do
Since I find my volume is too low, I tried pavucontrol as suggested. (No
pamixer available from yum.)
I receive:
Connection failed: Connection refused
try this killall pulseaudio
rm -rf /tmp/puls*
pulseaudio -D (to restart)
I remember getting stale pulseaudio file in /tmp back in F9 days and
this cured it
I can see the settings for output devices are set to 100% in the
interface
but since the connection fails, I can't be sure the figure is correct and
I can't change it.
One thing is sure: it isn't possible to get as much juice from my preamp
as SMplayer delivers. By default, the sound is rather weak, even with
alsamixer set to max.
Also, I removed Totem and installed Mplayer because I couldn't watch
features at Radio-Canada with Totem. I'm not sure how this would work with
Totem, but I can't set the system so that it plays the DVD just by
clicking on the icon.
System - Preferences - File Management - Media finds "no application" to
play video DVDs and there is no way to enter preferred applications. For
audio CDs, XMMS which, I believe is the default for the GNOME
installation, is still installed and it's "no application again", no way
to enter any.
For playing DVDs, SMPlayer does a good job so, we're not talking about a
major glitch here, mainly if you put an icon for SMPlayer in the panel.
But if people come from the Mac world, they'll really find it terrible if
you can't start a DVD by clicking on it.
I would be better if this was fixed. Even though the default volume I now
have is not unbearably low, it would also be prefereable if there was a
way to adjust it with pavucontrol. (Maybe this works on 32 bit systems. I
have no idea.)
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
5:19 p.m.
On Tue, 2009-07-14 at 23:37 -0700, john wendel wrote:
On 07/14/2009 10:02 PM, Linuxguy123 wrote:
> On Tue, 2009-07-14 at 20:31 -0700, john wendel wrote:
>> Looks like our junk is similar - Intel chip
>>
>> I had lots of sound problems until I moved to a 2.6.30 kernel. You'll
>> note that all the sound modules have very different sizes from yours.
>> And your driver version is 1.0.18a while mine is 1.0.20.
>>
>> I dumped pulse when I was having the sound problems, but it made no
>> difference.
>>
>> I'd recommend a kernel upgrade.
>
> Exactly which kernel did you use ? Did you build it or did you get it
> from an unstable repository ? (a yum command here would be
> appreciated...)
>
> I haven't built a custom kernel since Redhat 9...
>
> Thanks
>
>
I built 2.6.30.1 from kernel.org. I suspect that there are pre-built
2.6.30 kernels in rawhide or whatever, but I'd rather roll my own. Once
you get a working config file, it only takes a few minutes. I started
with the fedora config file (in /boot) and removed all the things I
don't use, saves a few megabytes.
I installed kernel-2.6.31-0.69.rc3.fc12.i586.rpm from here:
http://koji.fedoraproject.org:80/koji/buildinfo?buildID=114595
My sound still doesn't work.
LG
10:20 a.m.
On Wed, 2009-07-15 at 10:55 -0400, William Case wrote:
Hi Linuxguy123;
On Tue, 2009-07-14 at 12:22 -0600, Linuxguy123 wrote:
> I've been using F11 since it came out and it works great. But I haven't
> had any sound since I did the upgrade. Sound worked great in F10. Its
> getting old not having sound. How do I get it working ?
>
<snip>
>
> How should I proceed from here ?
I have very much the same problem.
I have filed a bug regarding it.
The bug is https://bugzilla.redhat.com/show_bug.cgi?id=511178
Check /var/log/messages and see if you can find a warning or error
similar to:
"
...
pulseaudio[2182]: alsa-sink.c: Increasing minimal latency to 1.00ms
pulseaudio[2182]: alsa-sink.c: Increasing minimal
latency to 2.00 ms
pulseaudio[2182]: alsa-sink.c: Increasing minimal
latency to 4.00 ms
pulseaudio[2182]: alsa-sink.c: ALSA woke us up to
write new data to the device, but there was actually nothing to write!
pulseaudio[2182]: alsa-sink.c: Most likely this is
a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to
the ALSA developers.
pulseaudio[2182]: alsa-sink.c: We were woken up with POLLOUT set --
however a subsequent snd_pcm_avail() returned 0 or another value <
min_avail.
...
"
If so, it matches my bug. A bug search on Alsa, pulseaudio and alsa-lib
shows many recent similar problems.
I filed bug 511178 two days ago but have received no response yet. If
it is appropriate (i.e. the same issue) I would appreciate your adding a
comment to the bug.
I think my situation is a bit different.
From /var/log/messages:
========================================================================
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: ALSA woke us up
to write new data to the device, but there was actually nothing to
write!
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: We were woken
up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0
or another value < min_avail.
Jul 15 06:38:14 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
Jul 15 06:38:20 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: ALSA woke us
up to read new data from the device, but there was actually nothing to
read!
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: We were woken
up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or
another value < min_avail.
Jul 15 06:38:33 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
===========================================================================
I am wondering if your problem wouldn't be solved by manually setting
the latency times as they do in the following post:
http://forums.fedoraforum.org/showthread.php?t=225660
9:55 a.m.
Hi Linuxguy123;
On Tue, 2009-07-14 at 12:22 -0600, Linuxguy123 wrote:
I've been using F11 since it came out and it works great. But I
haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
$ uname -a
Linux localhost.localdomain 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16
23:11:39 EDT 2009 i686 i686 i386 GNU/Linux
$lsmod | grep snd
snd_hda_codec_idt 50560 1
snd_hda_intel 23920 3
snd_hda_codec 54264 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 6580 1 snd_hda_codec
snd_pcm 62556 2 snd_hda_intel,snd_hda_codec
snd_timer 17896 1 snd_pcm
snd 49044 12
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 5404 1 snd
snd_page_alloc 7572 2 snd_hda_intel,snd_pcm
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ yum list pulseaudio\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
pulseaudio-libs.i586 0.9.15-14.fc11 @updates
pulseaudio-libs-glib2.i586 0.9.15-14.fc11 @updates
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.18a.
yum list alsa\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
alsa-lib.i586 1.0.20-1.fc11 installed
alsa-lib-devel.i586 1.0.20-1.fc11 installed
alsa-oss.i586 1.0.17-3.fc11 installed
alsa-oss-devel.i586 1.0.17-3.fc11 installed
alsa-oss-libs.i586 1.0.17-3.fc11 installed
alsa-utils.i586 1.0.20-3.fc11 installed
I've run alsamixer -c0 and all the levels are set to their maximums.
I've removed pulseaudio and mplayer and removed the .mplayer folder and
then reinstalled mplayer.
How should I proceed from here ?
I have very much the same problem.
I have filed a bug regarding it.
The bug is https://bugzilla.redhat.com/show_bug.cgi?id=511178
Check /var/log/messages and see if you can find a warning or error
similar to:
"
...
pulseaudio[2182]: alsa-sink.c: Increasing minimal latency to 1.00ms
pulseaudio[2182]: alsa-sink.c: Increasing minimal
latency to 2.00 ms
pulseaudio[2182]: alsa-sink.c: Increasing minimal
latency to 4.00 ms
pulseaudio[2182]: alsa-sink.c: ALSA woke us up to
write new data to the device, but there was actually nothing to write!
pulseaudio[2182]: alsa-sink.c: Most likely this is
a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to
the ALSA developers.
pulseaudio[2182]: alsa-sink.c: We were woken up with POLLOUT set --
however a subsequent snd_pcm_avail() returned 0 or another value <
min_avail.
...
"
If so, it matches my bug. A bug search on Alsa, pulseaudio and alsa-lib
shows many recent similar problems.
I filed bug 511178 two days ago but have received no response yet. If
it is appropriate (i.e. the same issue) I would appreciate your adding a
comment to the bug.
--
Regards Bill
Fedora 11, Gnome 2.26.2
Evo.2.26.2, Emacs 22.3.1
8:24 a.m.
On Wed, 2009-07-15 at 01:05 -0700, Craig White wrote:
Linuxguy123 wrote:
> On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
>
>> On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com>
wrote:
>>
>>> I've been using F11 since it came out and it works great. But I
haven't
>>> had any sound since I did the upgrade. Sound worked great in F10. Its
>>> getting old not having sound. How do I get it working ?
>>>
>>>
> What is Fedora expecting us to use and what do we need to do to get it
> working ?
>
> Thanks
----
Fedora was expecting to use PulseAudio but you removed that as your
predicate. That puts you with a vocal minority who would rather gripe
about pulse audio than make it work so it will be up to them to tell you
how to solve the sound issues that you 'fixed' by removing pulseaudio
package.
Is this an accidental repost ?
As I stated in a reply to this yesterday, this is not the case at all.
3:05 a.m.
Linuxguy123 wrote:
On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
> On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com> wrote:
>
>> I've been using F11 since it came out and it works great. But I haven't
>> had any sound since I did the upgrade. Sound worked great in F10. Its
>> getting old not having sound. How do I get it working ?
>>
>>
What is Fedora expecting us to use and what do we need to do to get it
working ?
Thanks
----
Fedora was expecting to use PulseAudio but you removed that as your
predicate. That puts you with a vocal minority who would rather gripe
about pulse audio than make it work so it will be up to them to tell you
how to solve the sound issues that you 'fixed' by removing pulseaudio
package.
good luck
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
12:12 a.m.
Fedora was expecting to use PulseAudio but you removed that as your
predicate. That puts you with a vocal minority who would rather gripe
about pulse audio than make it work so it will be up to them to tell you
how to solve the sound issues that you 'fixed' by removing pulseaudio
package.
I didn't remove pulseaudio:
yum install pulseaudio
Loaded plugins: refresh-packagekit
Setting up Install Process
Package pulseaudio-0.9.15-14.fc11.x86_64 already installed and latest version
Nothing to do
Since I find my volume is too low, I tried pavucontrol as suggested. (No
pamixer available from yum.)
I receive:
Connection failed: Connection refused
I can see the settings for output devices are set to 100% in the interface
but since the connection fails, I can't be sure the figure is correct and
I can't change it.
One thing is sure: it isn't possible to get as much juice from my preamp
as SMplayer delivers. By default, the sound is rather weak, even with
alsamixer set to max.
Also, I removed Totem and installed Mplayer because I couldn't watch
features at Radio-Canada with Totem. I'm not sure how this would work with
Totem, but I can't set the system so that it plays the DVD just by
clicking on the icon.
System - Preferences - File Management - Media finds "no application" to
play video DVDs and there is no way to enter preferred applications. For
audio CDs, XMMS which, I believe is the default for the GNOME
installation, is still installed and it's "no application again", no way
to enter any.
For playing DVDs, SMPlayer does a good job so, we're not talking about a
major glitch here, mainly if you put an icon for SMPlayer in the panel.
But if people come from the Mac world, they'll really find it terrible if
you can't start a DVD by clicking on it.
I would be better if this was fixed. Even though the default volume I now
have is not unbearably low, it would also be prefereable if there was a
way to adjust it with pavucontrol. (Maybe this works on 32 bit systems. I
have no idea.)
1:37 a.m.
On 07/14/2009 10:02 PM, Linuxguy123 wrote:
On Tue, 2009-07-14 at 20:31 -0700, john wendel wrote:
> Looks like our junk is similar - Intel chip
>
> I had lots of sound problems until I moved to a 2.6.30 kernel. You'll
> note that all the sound modules have very different sizes from yours.
> And your driver version is 1.0.18a while mine is 1.0.20.
>
> I dumped pulse when I was having the sound problems, but it made no
> difference.
>
> I'd recommend a kernel upgrade.
Exactly which kernel did you use ? Did you build it or did you get it
from an unstable repository ? (a yum command here would be
appreciated...)
I haven't built a custom kernel since Redhat 9...
Thanks
I built 2.6.30.1 from kernel.org. I suspect that there are pre-built
2.6.30 kernels in rawhide or whatever, but I'd rather roll my own. Once
you get a working config file, it only takes a few minutes. I started
with the fedora config file (in /boot) and removed all the things I
don't use, saves a few megabytes.
-rwxr-xr-x. 1 root root 3033520 2009-06-16 20:32
vmlinuz-2.6.29.5-191.fc11.i586
-rw-r--r--. 1 root root 1348832 2009-07-03 18:58 vmlinuz-2.6.30.1
Regards,
John
12:07 a.m.
On Tue, 2009-07-14 at 21:47 -0600, Linuxguy123 wrote:
On Tue, 2009-07-14 at 22:13 -0400, fred smith wrote:
> On Tue, Jul 14, 2009 at 12:22:15PM -0600, Linuxguy123 wrote:
> > I've been using F11 since it came out and it works great. But I
haven't
> > had any sound since I did the upgrade. Sound worked great in F10. Its
> > getting old not having sound. How do I get it working ?
> >
snip
> there's a thorough-looking guide on the fedora forums at:
> http://forums.fedoraforum.org/showthread.php?t=225660
>
> Please note that I have not tried it, so I will assume no responsibility
> if it makes your computer fly around the room. :)
Its better than anything else I've seen. Everything worked until I ran
the pulse audio device chooser, which didn't run at all. Even when run
from the command line. There is no error output whatsoever. It just
hangs. The GUI never appears.
I now see 3 pulse audio applets in my system tray. Yes, 3 of them. On
them I can set the default server, sink and source to... default, like
to Fedora Forum instructions say. However, I still get no sound. I
even logged into a gnome session and tried the system-config-soundcard
application... no joy, however I am still playing with settings.
12:02 a.m.
On Tue, 2009-07-14 at 20:31 -0700, john wendel wrote:
Looks like our junk is similar - Intel chip
I had lots of sound problems until I moved to a 2.6.30 kernel. You'll
note that all the sound modules have very different sizes from yours.
And your driver version is 1.0.18a while mine is 1.0.20.
I dumped pulse when I was having the sound problems, but it made no
difference.
I'd recommend a kernel upgrade.
Exactly which kernel did you use ? Did you build it or did you get it
from an unstable repository ? (a yum command here would be
appreciated...)
I haven't built a custom kernel since Redhat 9...
Thanks
10:47 p.m.
On Tue, 2009-07-14 at 22:13 -0400, fred smith wrote:
On Tue, Jul 14, 2009 at 12:22:15PM -0600, Linuxguy123 wrote:
> I've been using F11 since it came out and it works great. But I haven't
> had any sound since I did the upgrade. Sound worked great in F10. Its
> getting old not having sound. How do I get it working ?
>
snip
there's a thorough-looking guide on the fedora forums at:
http://forums.fedoraforum.org/showthread.php?t=225660
Please note that I have not tried it, so I will assume no responsibility
if it makes your computer fly around the room. :)
Its better than anything else I've seen. Everything worked until I ran
the pulse audio device chooser, which didn't run at all. Even when run
from the command line. There is no error output whatsoever. It just
hangs. The GUI never appears.
10:16 p.m.
On 07/14/2009 10:13 PM, fred smith wrote:
On Tue, Jul 14, 2009 at 12:22:15PM -0600, Linuxguy123 wrote:
> I've been using F11 since it came out and it works great. But I haven't
> had any sound since I did the upgrade. Sound worked great in F10. Its
> getting old not having sound. How do I get it working ?
>
> $ uname -a
> Linux localhost.localdomain 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16
> 23:11:39 EDT 2009 i686 i686 i386 GNU/Linux
>
> $lsmod | grep snd
> snd_hda_codec_idt 50560 1
> snd_hda_intel 23920 3
> snd_hda_codec 54264 2 snd_hda_codec_idt,snd_hda_intel
> snd_hwdep 6580 1 snd_hda_codec
> snd_pcm 62556 2 snd_hda_intel,snd_hda_codec
> snd_timer 17896 1 snd_pcm
> snd 49044 12
> snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
> soundcore 5404 1 snd
> snd_page_alloc 7572 2 snd_hda_intel,snd_pcm
>
> $ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
> $ yum list pulseaudio\*
> Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
> refresh-packagekit
> 1 packages excluded due to repository priority protections
> Installed Packages
> pulseaudio-libs.i586 0.9.15-14.fc11 @updates
> pulseaudio-libs-glib2.i586 0.9.15-14.fc11 @updates
>
> $ cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.18a.
>
>
> yum list alsa\*
> Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
> refresh-packagekit
> 1 packages excluded due to repository priority protections
> Installed Packages
> alsa-lib.i586 1.0.20-1.fc11 installed
> alsa-lib-devel.i586 1.0.20-1.fc11 installed
> alsa-oss.i586 1.0.17-3.fc11 installed
> alsa-oss-devel.i586 1.0.17-3.fc11 installed
> alsa-oss-libs.i586 1.0.17-3.fc11 installed
> alsa-utils.i586 1.0.20-3.fc11 installed
>
> I've run alsamixer -c0 and all the levels are set to their maximums.
>
> I've removed pulseaudio and mplayer and removed the .mplayer folder and
> then reinstalled mplayer.
>
> How should I proceed from here ?
>
> Thanks
there's a thorough-looking guide on the fedora forums at:
http://forums.fedoraforum.org/showthread.php?t=225660
Please note that I have not tried it, so I will assume no responsibility
if it makes your computer fly around the room. :)
I've tried it and it works. You also get pamixer which can show you
whether or not PA sees your audio card. Unfortunately, I have a
different Intel chip than you, mine is the AD198x.
9:13 p.m.
On Tue, Jul 14, 2009 at 12:22:15PM -0600, Linuxguy123 wrote:
I've been using F11 since it came out and it works great. But I
haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
$ uname -a
Linux localhost.localdomain 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16
23:11:39 EDT 2009 i686 i686 i386 GNU/Linux
$lsmod | grep snd
snd_hda_codec_idt 50560 1
snd_hda_intel 23920 3
snd_hda_codec 54264 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 6580 1 snd_hda_codec
snd_pcm 62556 2 snd_hda_intel,snd_hda_codec
snd_timer 17896 1 snd_pcm
snd 49044 12
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 5404 1 snd
snd_page_alloc 7572 2 snd_hda_intel,snd_pcm
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ yum list pulseaudio\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
pulseaudio-libs.i586 0.9.15-14.fc11 @updates
pulseaudio-libs-glib2.i586 0.9.15-14.fc11 @updates
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.18a.
yum list alsa\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
alsa-lib.i586 1.0.20-1.fc11 installed
alsa-lib-devel.i586 1.0.20-1.fc11 installed
alsa-oss.i586 1.0.17-3.fc11 installed
alsa-oss-devel.i586 1.0.17-3.fc11 installed
alsa-oss-libs.i586 1.0.17-3.fc11 installed
alsa-utils.i586 1.0.20-3.fc11 installed
I've run alsamixer -c0 and all the levels are set to their maximums.
I've removed pulseaudio and mplayer and removed the .mplayer folder and
then reinstalled mplayer.
How should I proceed from here ?
Thanks
there's a thorough-looking guide on the fedora forums at:
http://forums.fedoraforum.org/showthread.php?t=225660
Please note that I have not tried it, so I will assume no responsibility
if it makes your computer fly around the room. :)
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
The Lord detests the way of the wicked
but he loves those who pursue righteousness.
----------------------------- Proverbs 15:9 (niv) -----------------------------
9:02 p.m.
On Tue, 2009-07-14 at 18:40 -0700, Kam Leo wrote:
On Tue, Jul 14, 2009 at 6:35 PM, Bruno Wolff
III<bruno(a)wolff.to> wrote:
> On Tue, Jul 14, 2009 at 18:45:06 -0500,
> Jud Craft <craftjml(a)gmail.com> wrote:
>> Considering your install wasn't a fresh one to begin with, and Fedora
>> makes releases twice a year that don't always cleanly upgrade between
>> each other, I think reinstalling isn't an unreasonable suggestion.
>> But it was just my suggestion.
>
> There are tools (e.g. package-cleanup and rpm -Va) that can be used to
> check out that an install was made properly without do a reinstall.
> The *.rpm??? confige files can be checked to see if anything needs to
> be done related to them.
>
Been there. Done that. Does not work. All packages got installed properly.
Biggest problem with F11 sound is that Fedora developers dropped
system-config-soundcard and did not provide other means to fix
hardware issues. If PA does not see a soundcard you are hosed.
So how does one check if PA is "seeing" the soundcard ?
Thanks
8:40 p.m.
On Tue, Jul 14, 2009 at 6:35 PM, Bruno Wolff III<bruno(a)wolff.to> wrote:
On Tue, Jul 14, 2009 at 18:45:06 -0500,
Jud Craft <craftjml(a)gmail.com> wrote:
> Considering your install wasn't a fresh one to begin with, and Fedora
> makes releases twice a year that don't always cleanly upgrade between
> each other, I think reinstalling isn't an unreasonable suggestion.
> But it was just my suggestion.
There are tools (e.g. package-cleanup and rpm -Va) that can be used to
check out that an install was made properly without do a reinstall.
The *.rpm??? confige files can be checked to see if anything needs to
be done related to them.
Been there. Done that. Does not work. All packages got installed properly.
Biggest problem with F11 sound is that Fedora developers dropped
system-config-soundcard and did not provide other means to fix
hardware issues. If PA does not see a soundcard you are hosed.
8:39 p.m.
On Tue, 2009-07-14 at 20:35 -0500, Bruno Wolff III wrote:
On Tue, Jul 14, 2009 at 18:45:06 -0500,
Jud Craft <craftjml(a)gmail.com> wrote:
> Considering your install wasn't a fresh one to begin with, and Fedora
> makes releases twice a year that don't always cleanly upgrade between
> each other, I think reinstalling isn't an unreasonable suggestion.
> But it was just my suggestion.
There are tools (e.g. package-cleanup and rpm -Va) that can be used to
check out that an install was made properly without do a reinstall.
The *.rpm??? confige files can be checked to see if anything needs to
be done related to them.
Thanks for reminding us of that. I'll keep it in mind as we move
forward troubleshooting this issue.
8:35 p.m.
On Tue, Jul 14, 2009 at 18:45:06 -0500,
Jud Craft <craftjml(a)gmail.com> wrote:
Considering your install wasn't a fresh one to begin with, and
Fedora
makes releases twice a year that don't always cleanly upgrade between
each other, I think reinstalling isn't an unreasonable suggestion.
But it was just my suggestion.
There are tools (e.g. package-cleanup and rpm -Va) that can be used to
check out that an install was made properly without do a reinstall.
The *.rpm??? confige files can be checked to see if anything needs to
be done related to them.
8:24 p.m.
On Wed, 2009-07-15 at 01:05 -0700, Craig White wrote:
Linuxguy123 wrote:
> On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
>
>> On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com>
wrote:
>>
>>> I've been using F11 since it came out and it works great. But I
haven't
>>> had any sound since I did the upgrade. Sound worked great in F10. Its
>>> getting old not having sound. How do I get it working ?
>>>
>>>
> What is Fedora expecting us to use and what do we need to do to get it
> working ?
>
> Thanks
----
Fedora was expecting to use PulseAudio but you removed that as your
predicate. That puts you with a vocal minority who would rather gripe
about pulse audio than make it work so it will be up to them to tell you
how to solve the sound issues that you 'fixed' by removing pulseaudio
package.
I have absolutely NO beef with pulseaudio whatsoever. I did not gripe
about its existence. As long as it works, fine by me. I only removed
it because people on this list suggested that its removal would cure my
problem.
I have just reinstalled pulseaudio. My sound still doesn't work. How
should I proceed ?
# yum list pulseaudio\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
pulseaudio.i586 0.9.15-14.fc11 @updates
pulseaudio-libs.i586 0.9.15-14.fc11 @updates
pulseaudio-libs-glib2.i586 0.9.15-14.fc11 @updates
6:45 p.m.
Considering your install wasn't a fresh one to begin with, and Fedora
makes releases twice a year that don't always cleanly upgrade between
each other, I think reinstalling isn't an unreasonable suggestion.
But it was just my suggestion.
You could always set aside a small partition and do a fresh install.
That would at least confirm if F11 sound works at all on your machine.
It's not a stab in the dark; it actually -rules- out possibilities
that you need to consider, would tell you if getting F11 sound working
at all is possible, and instead help you focus on how to repair your
upgraded environment, or tell you immediately if it was futile.
On Tue, Jul 14, 2009 at 6:05 PM, Linuxguy123<linuxguy123(a)gmail.com> wrote:
On Tue, 2009-07-14 at 17:21 -0500, Jud Craft wrote:
> You could try yum reinstalling PulseAudio.
>
> If you had tried a fresh install of F11 on a small side partition, you
> could figure out whether "F11 sound is the problem" or "my
upgrade"
> was the problem, since Fedora upgrades seem to have bugs of their own
> quite often, and the Linux sound infrastructure did go through changes
> between F10 and F11; wouldn't surprise me to hear that a plain upgrade
> wouldn't work right.
>
> I'd try reinstalling PulseAudio.
I've already tried that. It doesn't work.
> Then I'd try a clean install of Fedora.
Don't ever suggest that re installing an operating system is the
solution to a problem. It isn't. It would take me several days to
re-install. Re installing is a stab in the dark at best.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
6:05 p.m.
On Tue, 2009-07-14 at 17:21 -0500, Jud Craft wrote:
You could try yum reinstalling PulseAudio.
If you had tried a fresh install of F11 on a small side partition, you
could figure out whether "F11 sound is the problem" or "my upgrade"
was the problem, since Fedora upgrades seem to have bugs of their own
quite often, and the Linux sound infrastructure did go through changes
between F10 and F11; wouldn't surprise me to hear that a plain upgrade
wouldn't work right.
I'd try reinstalling PulseAudio.
I've already tried that. It doesn't work.
Then I'd try a clean install of Fedora.
Don't ever suggest that re installing an operating system is the
solution to a problem. It isn't. It would take me several days to
re-install. Re installing is a stab in the dark at best.
5:21 p.m.
You could try yum reinstalling PulseAudio.
If you had tried a fresh install of F11 on a small side partition, you
could figure out whether "F11 sound is the problem" or "my upgrade"
was the problem, since Fedora upgrades seem to have bugs of their own
quite often, and the Linux sound infrastructure did go through changes
between F10 and F11; wouldn't surprise me to hear that a plain upgrade
wouldn't work right.
I'd try reinstalling PulseAudio. Then I'd try a clean install of Fedora.
4:18 p.m.
On Tue, Jul 14, 2009 at 1:18 PM, Linuxguy123<linuxguy123(a)gmail.com> wrote:
On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
> On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com> wrote:
> > I've been using F11 since it came out and it works great. But I haven't
> > had any sound since I did the upgrade. Sound worked great in F10. Its
> > getting old not having sound. How do I get it working ?
> >
>
> [snip]
>
> > I've removed pulseaudio and mplayer and removed the .mplayer folder and
> > then reinstalled mplayer.
> >
> > How should I proceed from here ?
> >
> > Thanks
>
> Sound also failed for me when I upgraded my virtual machine from F10.
> It also failed on a new virtual machine install of F11. Status for
> sound is as follows:
>
> VM upgrade of F10 to F11:
>
> Removed PA.
> Unable to remove Alsa because of dependency hell. (Most
> everything is tied to it.)
> Download and installed Open Sound System driver rpm:
> http://www.4front-tech.com/download.cgi
>
> Got sound and a mixer but no master volume control for Gnome taskbar.
>
> VM F11 install:
>
> No sound device. PA Manager/Device Chooser and find device or
> defaults to null.
> Removed PA
> Enabled OSS sound support in /etc/modprobe.d/dist-oss.conf
>
> After restart: Sound card detected. Alsa mixer works. No master
> volume control for Gnome.
>
>
> I also have virtual machine instances of openSUSE 11.1 and Ubuntu 9.04
> installed on the same machine. Sound works in both. As far as I am
> aware both distros use Pulse Audio. So, where or how did Fedora
> developers get off track and derail sound?
Thanks for detailing your process, but I can't help but notice its for a
VM instead of an actual installation like I am running. Does anyone
have tips for a non VM installation ?
Why did you have to download the oss driver from a non Fedora location ?
Fedora no longer supports OSS.
What is Fedora expecting us to use and what do we need to do to get
it
working ?
Good question.
3:46 p.m.
2009/7/14 Linuxguy123 <linuxguy123(a)gmail.com>:
I've been using F11 since it came out and it works great. But I
haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
I've had a whole bunch of sound problems so I'll throw some
suggestions in... I've found that in a few situations I can only get
sound working with the flash plugin and VLC. There's obviously
something wrong with one or more of the backends to the various apps
(gstreamer, xine, phonon). It's worth figuring out whether you're
getting no sound at all (which would suggest there's something wrong
with the config of your output device), or whether you're getting
output from certain apps but not others (which would suggest some or
all of the backends are failing for some reason).
I seem to recall reading some of your threads about KDE 4.0 so I guess
you're running KDE now. In that case, you're probably running audio
apps which go through phonon, which is part of Qt4. I've had problems
with the xine backend of phonon at times. When I removed the xine
backend things sprung into life (maybe try "rpm -qa | grep phonon" for
clues as to the package to remove).
HTH, Chris.
3:27 p.m.
On 07/14/2009 04:18 PM, Linuxguy123 wrote:
On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
> On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com> wrote:
>> I've been using F11 since it came out and it works great. But I haven't
>> had any sound since I did the upgrade. Sound worked great in F10. Its
>> getting old not having sound. How do I get it working ?
>>
> [snip]
>
>> I've removed pulseaudio and mplayer and removed the .mplayer folder and
>> then reinstalled mplayer.
>>
>> How should I proceed from here ?
>>
>> Thanks
> Sound also failed for me when I upgraded my virtual machine from F10.
> It also failed on a new virtual machine install of F11. Status for
> sound is as follows:
>
> VM upgrade of F10 to F11:
>
> Removed PA.
> Unable to remove Alsa because of dependency hell. (Most
> everything is tied to it.)
> Download and installed Open Sound System driver rpm:
> http://www.4front-tech.com/download.cgi
>
> Got sound and a mixer but no master volume control for Gnome taskbar.
>
> VM F11 install:
>
> No sound device. PA Manager/Device Chooser and find device or
> defaults to null.
> Removed PA
> Enabled OSS sound support in /etc/modprobe.d/dist-oss.conf
>
> After restart: Sound card detected. Alsa mixer works. No master
> volume control for Gnome.
>
>
> I also have virtual machine instances of openSUSE 11.1 and Ubuntu 9.04
> installed on the same machine. Sound works in both. As far as I am
> aware both distros use Pulse Audio. So, where or how did Fedora
> developers get off track and derail sound?
Thanks for detailing your process, but I can't help but notice its for a
VM instead of an actual installation like I am running. Does anyone
have tips for a non VM installation ?
Why did you have to download the oss driver from a non Fedora location ?
What is Fedora expecting us to use and what do we need to do to get it
working ?
Thanks
I had no sound until I found the tip to run alsamixer -c0 and make sure
the appropriate levels were maxed, then PA was fine.
3:18 p.m.
On Tue, 2009-07-14 at 12:15 -0700, Kam Leo wrote:
On Tue, Jul 14, 2009 at 11:22 AM,
Linuxguy123<linuxguy123(a)gmail.com> wrote:
> I've been using F11 since it came out and it works great. But I haven't
> had any sound since I did the upgrade. Sound worked great in F10. Its
> getting old not having sound. How do I get it working ?
>
[snip]
> I've removed pulseaudio and mplayer and removed the .mplayer folder and
> then reinstalled mplayer.
>
> How should I proceed from here ?
>
> Thanks
Sound also failed for me when I upgraded my virtual machine from F10.
It also failed on a new virtual machine install of F11. Status for
sound is as follows:
VM upgrade of F10 to F11:
Removed PA.
Unable to remove Alsa because of dependency hell. (Most
everything is tied to it.)
Download and installed Open Sound System driver rpm:
http://www.4front-tech.com/download.cgi
Got sound and a mixer but no master volume control for Gnome taskbar.
VM F11 install:
No sound device. PA Manager/Device Chooser and find device or
defaults to null.
Removed PA
Enabled OSS sound support in /etc/modprobe.d/dist-oss.conf
After restart: Sound card detected. Alsa mixer works. No master
volume control for Gnome.
I also have virtual machine instances of openSUSE 11.1 and Ubuntu 9.04
installed on the same machine. Sound works in both. As far as I am
aware both distros use Pulse Audio. So, where or how did Fedora
developers get off track and derail sound?
Thanks for detailing your process, but I can't help but notice its for a
VM instead of an actual installation like I am running. Does anyone
have tips for a non VM installation ?
Why did you have to download the oss driver from a non Fedora location ?
What is Fedora expecting us to use and what do we need to do to get it
working ?
Thanks
2:20 p.m.
On Tue, Jul 14, 2009 at 12:15 PM, Kam Leo<kam.leo(a)gmail.com> wrote:
On Tue, Jul 14, 2009 at 11:22 AM,
Linuxguy123<linuxguy123(a)gmail.com> wrote:
> I've been using F11 since it came out and it works great. But I haven't
> had any sound since I did the upgrade. Sound worked great in F10. Its
> getting old not having sound. How do I get it working ?
>
[snip]
> I've removed pulseaudio and mplayer and removed the .mplayer folder and
> then reinstalled mplayer.
>
> How should I proceed from here ?
>
> Thanks
Sound also failed for me when I upgraded my virtual machine from F10.
It also failed on a new virtual machine install of F11. Status for
sound is as follows:
VM upgrade of F10 to F11:
Removed PA.
Unable to remove Alsa because of dependency hell. (Most
everything is tied to it.)
Download and installed Open Sound System driver rpm:
http://www.4front-tech.com/download.cgi
Got sound and a mixer but no master volume control for Gnome taskbar.
VM F11 install:
No sound device. PA Manager/Device Chooser and find device or
^
*** Gmail editor bug.*** Should be "can not"
defaults to null.
Removed PA
Enabled OSS sound support in /etc/modprobe.d/dist-oss.conf
After restart: Sound card detected. Alsa mixer works. No master
volume control for Gnome.
I also have virtual machine instances of openSUSE 11.1 and Ubuntu 9.04
installed on the same machine. Sound works in both. As far as I am
aware both distros use Pulse Audio. So, where or how did Fedora
developers get off track and derail sound?
2:15 p.m.
On Tue, Jul 14, 2009 at 11:22 AM, Linuxguy123<linuxguy123(a)gmail.com> wrote:
I've been using F11 since it came out and it works great. But I
haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
[snip]
I've removed pulseaudio and mplayer and removed the .mplayer
folder and
then reinstalled mplayer.
How should I proceed from here ?
Thanks
Sound also failed for me when I upgraded my virtual machine from F10.
It also failed on a new virtual machine install of F11. Status for
sound is as follows:
VM upgrade of F10 to F11:
Removed PA.
Unable to remove Alsa because of dependency hell. (Most
everything is tied to it.)
Download and installed Open Sound System driver rpm:
http://www.4front-tech.com/download.cgi
Got sound and a mixer but no master volume control for Gnome taskbar.
VM F11 install:
No sound device. PA Manager/Device Chooser and find device or
defaults to null.
Removed PA
Enabled OSS sound support in /etc/modprobe.d/dist-oss.conf
After restart: Sound card detected. Alsa mixer works. No master
volume control for Gnome.
I also have virtual machine instances of openSUSE 11.1 and Ubuntu 9.04
installed on the same machine. Sound works in both. As far as I am
aware both distros use Pulse Audio. So, where or how did Fedora
developers get off track and derail sound?
3:46 a.m.
On Saturday 25 July 2009 00:31:09 Bill Davidsen wrote:
PA is too damn fragile to use unless you are one of the few
who has it work out of the box.
It's a funny thing, but I have three very different systems where PA has worked
perfectly out-of-the-box. I'm not denying that some people have problems, but
going by my experience there must be many that don't. Of course you never
hear from them ;-)
Anne
11:22 p.m.
Linuxguy123 wrote:
On Wed, 2009-07-15 at 10:55 -0400, William Case wrote:
> Hi Linuxguy123;
>
> On Tue, 2009-07-14 at 12:22 -0600, Linuxguy123 wrote:
>> I've been using F11 since it came out and it works great. But I haven't
>> had any sound since I did the upgrade. Sound worked great in F10. Its
>> getting old not having sound. How do I get it working ?
>>
<snip>
>> How should I proceed from here ?
> I have very much the same problem.
>
> I have filed a bug regarding it.
> The bug is https://bugzilla.redhat.com/show_bug.cgi?id=511178
>
> Check /var/log/messages and see if you can find a warning or error
> similar to:
>
> "
> ...
> pulseaudio[2182]: alsa-sink.c: Increasing minimal latency to 1.00ms
> pulseaudio[2182]: alsa-sink.c: Increasing minimal
> latency to 2.00 ms
> pulseaudio[2182]: alsa-sink.c: Increasing minimal
> latency to 4.00 ms
> pulseaudio[2182]: alsa-sink.c: ALSA woke us up to
> write new data to the device, but there was actually nothing to write!
> pulseaudio[2182]: alsa-sink.c: Most likely this is
> a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to
> the ALSA developers.
> pulseaudio[2182]: alsa-sink.c: We were woken up with POLLOUT set --
> however a subsequent snd_pcm_avail() returned 0 or another value <
> min_avail.
> ...
> "
> If so, it matches my bug. A bug search on Alsa, pulseaudio and alsa-lib
> shows many recent similar problems.
>
> I filed bug 511178 two days ago but have received no response yet. If
> it is appropriate (i.e. the same issue) I would appreciate your adding a
> comment to the bug.
I think my situation is a bit different.
>From /var/log/messages:
========================================================================
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: ALSA woke us up
to write new data to the device, but there was actually nothing to
write!
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: We were woken
up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0
or another value < min_avail.
Jul 15 06:38:14 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
Jul 15 06:38:20 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: ALSA woke us
up to read new data from the device, but there was actually nothing to
read!
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: We were woken
up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or
another value < min_avail.
Jul 15 06:38:33 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
===========================================================================
I am wondering if your problem wouldn't be solved by manually setting
the latency times as they do in the following post:
http://forums.fedoraforum.org/showthread.php?t=225660
This is the most readable thing I've seen on PA, until I've tried it on
all my
machines I don't want to comment on how well it works, or doesn't, because old
drivers which worked in 2.6.22 are long gone.
Great job of writing this up, in any case!
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
10:31 p.m.
On 07/14/2009 11:22 AM, Linuxguy123 wrote:
I've been using F11 since it came out and it works great. But I
haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
$ uname -a
Linux localhost.localdomain 2.6.29.5-191.fc11.i586 #1 SMP Tue Jun 16
23:11:39 EDT 2009 i686 i686 i386 GNU/Linux
$lsmod | grep snd
snd_hda_codec_idt 50560 1
snd_hda_intel 23920 3
snd_hda_codec 54264 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 6580 1 snd_hda_codec
snd_pcm 62556 2 snd_hda_intel,snd_hda_codec
snd_timer 17896 1 snd_pcm
snd 49044 12
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 5404 1 snd
snd_page_alloc 7572 2 snd_hda_intel,snd_pcm
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ yum list pulseaudio\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
pulseaudio-libs.i586 0.9.15-14.fc11 @updates
pulseaudio-libs-glib2.i586 0.9.15-14.fc11 @updates
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.18a.
yum list alsa\*
Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities,
refresh-packagekit
1 packages excluded due to repository priority protections
Installed Packages
alsa-lib.i586 1.0.20-1.fc11 installed
alsa-lib-devel.i586 1.0.20-1.fc11 installed
alsa-oss.i586 1.0.17-3.fc11 installed
alsa-oss-devel.i586 1.0.17-3.fc11 installed
alsa-oss-libs.i586 1.0.17-3.fc11 installed
alsa-utils.i586 1.0.20-3.fc11 installed
I've run alsamixer -c0 and all the levels are set to their maximums.
I've removed pulseaudio and mplayer and removed the .mplayer folder and
then reinstalled mplayer.
How should I proceed from here ?
Thanks
Looks like our junk is similar - Intel chip
I had lots of sound problems until I moved to a 2.6.30 kernel. You'll
note that all the sound modules have very different sizes from yours.
And your driver version is 1.0.18a while mine is 1.0.20.
I dumped pulse when I was having the sound problems, but it made no
difference.
I'd recommend a kernel upgrade.
Regards,
John
uname -a
Linux godzilla2 2.6.30.1 #1 SMP Fri Jul 3 18:26:47 PDT 2009 i686 i686
i386 GNU/Linux
lsmod | grep snd
snd_hda_codec_idt 34948 1
snd_hda_intel 12852 0
snd_hda_codec 35060 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 2840 1 snd_hda_codec
snd_pcm 32024 2 snd_hda_intel,snd_hda_codec
snd_timer 10144 1 snd_pcm
snd 22976 6
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 344 1 snd
snd_page_alloc 4152 2 snd_hda_intel,snd_pcm
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.20.
Installed Packages
alsa-lib.i586 1.0.20-1.fc11
installed
alsa-utils.i586 1.0.20-3.fc11
installed
5403
days inactive
5419
days old
59 comments
22 participants
participants (22)
-
Anne Wilson -
Bill Case -
Bill Davidsen -
Bruno Wolff III -
Chris -
Craig White -
Fred Smith -
Gene Heskett -
gilpel＠altern.org -
Jef Spaleta -
John Wendel -
Jud Craft -
Kam Leo -
linux guy -
Marko Vojinovic -
Markus Kesaromous -
Michael Schwendt -
Mike Martin -
Mikkel -
Shannon McMackin -
stan -
Tim