FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having a problem with sound on my Fedora 9 box. I did a fresh install over F8, which worked fine.
The sound plays too fast. Just barely enough to notice. I timed a song that was supposed to take 3:15 to complete, but it did it in right about 3 minutes flat. I first noticed it when playing the Star Wars theme mp3, which I had naturally heard hundreds of times and it just sounded a little off. Of course it is annoying that my music is playing too fast, but xine can actually tell this and inserts a slight blank spot in the song every 3 - 5 seconds to compensate for this. It sounds like playing a really scratched up CD. When I play a song with verbose=9 in xine it gives me this every time there is a jump in the song (one line per jump):
audio_out: inserting 7535 0-frames to fill a gap of 15402 pts
audio_out: inserting 7562 0-frames to fill a gap of 15457 pts
audio_out: inserting 7545 0-frames to fill a gap of 15423 pts
audio_out: inserting 7539 0-frames to fill a gap of 15410 pts
But if I use an app that uses gstreamer it plays fast without the skipping.
Does anybody have a clue what would be causing this? Or even where I could begin to start diagnosing this?
It is very annoying and I will probably go back to Fedora 8 if I can't fix this (not that anybody really cares what I do).
I am experiencing the same audio problem after loading Fedora 9. There is a blank/skip every couple seconds when playing audio using Xine or VLC. However ,this blanking does not occur when playing the same audio using Mplayer, mpg123, Realplayer 11, and xmms, but the audio plays too fast. I did not experience this issue on any of the previous Fedora releases (Fedora 3 through 8). The problem seems to be associated with the sound driver in Fedora 9 for the Intel 82801 AC'97 integrated sound chip that is in my system. I have an external Sound Blaster MP3+ card which I tried (after disabling the Legacy sound chip in BIOS setup), and the audio plays correctly with no blanks/skips in Xine or VLC, and at the proper speed in Mplayer, mpg123, Realplayer 11, and xmms.
I have a integrated sound chip that I believe would be intel as well. I just decided to go back to Fedora 8. I use it for music and video too much for there to be any major issues. I'll just have to wait for Fedora 10. Unless I hear that the problem gets fixed later on, that is...
Yesterday, I found some a post about some issues on Dell computers related to the clock source and the tickless kernel mode.
I found the clock sources available with the command:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
And then changed the clock source on the fly with the command:
echo acpi_pm > /sys/devices/system/clocksource/clocksource0/current_clocksource
Nothing seemed to happen immediately but two or three hours later I opened Amarok and all the music started playing fine!!!.
Today I opened Amarok to play some music and found the problem again, even when I wrote clocksource=acpi_pm in grub.conf the day before.
So, I don't know if the clock source change did something yesterday to fix it or if something related to the updates applied during the day did the trick...
Anyway... it seems to be a there's a way to fix it.
Hi there. Just registered to post the (my) solution, cause I was having the same problem.
I went to ALSA's official site and downloaded alsa-driver-1.0.17rc1, uncompressed it and made a simple ./configure, make and make install. The problemm, after a reboot, disapeared.
ok.. I am still relatively new and been self learning linux. i have 4 kids so expenses for buying a soundcard for pleasure just aint in the budget regardless of the price. i tried to muck my way thru this and research and am getting no where. im hoping someone here can help me try the fix that Sergio89 posted here.
when i try the ./configure this is what I am getting
[gil@armourws alsa-driver-1.0.17]$ ./configure
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /home/gil/Download/alsa-driver-1.0.17
checking cross compile...
checking for directory with kernel source... ./configure: line 4685: cd: /lib/modules/2.6.25.10-86.fc9.i686/source: No such file or directory
/lib/modules/2.6.25.10-86.fc9.i686/source
checking for directory with kernel build... /lib/modules/2.6.25.10-86.fc9.i686/build
checking for kernel linux/version.h... no
The file /include/linux/version.h does not exist.
Please install the package with full kernel sources for your distribution
or use --with-kernel=dir option to specify another directory with kernel
sources (default is /lib/modules/2.6.25.10-86.fc9.i686/source).
It would be greatly appreciated if I get some help in breaking down what I need to do to get beyond this.
Ok update to this. I tried to follow the article you linked to. (I have used that setup as well when configuring other things as well as its a great help and I highly recommend everyone use the info there for reference) but it did not work for me. I got as far as downloading the source file but the install of it didnt work as outlined. I chalk it up to my inexperience with windows and building from source. Maybe one day I will learn it.
However by sheer chance I took a gamble and did a search to see if someone somewhere had already compiled an .rpm for the alsa-driver-1.0.17 for the .fc9.i386.rpm or .fc9.i686.rpm.
as it is the dependency for the next file I downloaded
alsa-driver-1.0.17-68.fc9.i386.rpm
then installing that with
sudo rpm -Uvh alsa-driver-1.0.17-68.fc9.i386.rpm
once done I rebooted and it totally fixed my problem.
So I appreciate the information given. I wish I was as knowledgable as being able to do it the ways that were suggested, but hopefully in me posting this information someone else may have an easier time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.