Yes, I did install the updated version. I think this is what's causing the problem. I ran "yum -y update" and got all the updates including the newer ALSA. I want to go back from Ubuntu to Fedora. I like it better. Is there a command I can use to not update alsa 1.0.14rc1 when I run the update after the installation?
I actually got myself into this reinstall pickle by trying to remove Alsa to try to go back to the old version. When I ran the command "yum -y remove alsa", it took half my operating system with it. It removed program after program until it was totally unrepairable. I may even go back to core 5. I'm running core 5 on both of my PS's. This one was a dual boot laptop with Windows XPPRO and core 6. I haven't upgraded the two PC's because core 5 is working perfectly.

First edit /etc/asound.conf file as I mentioned earlier and see if that helps ( you have to reboot after editing ).

If you would like to erase single package and stll keep dependant packages use ( as root )
Then download directly with browser those packages what you want to your computer and use
If you have already made a reinstall then simply do following commands

Here is bugzilla link for the problem
https://bugzilla.redhat.com/bugzilla....cgi?id=233726
Those who have bugzilla account and suffer with this bug please post and describe your problem to rad-hat.
( I haven't yet created my bugzilla account )

Thanks markelo, this is good stuff. Right now I am putting Fedora back into my laptop. I shouldn't have given up on it so easily. Especially since Ubuntu had the same problem. Both your last two poists will be very useful in this installation. I'll report back as soon as I'm done.

Bob

Ok, I've put Fedora core 6 back in and I am redoing it again. I can't seem to keep alsa-lib from upgrading during the initial yum -y update. The reason is that I basically don't know how. I ran "gedit /etc/asound.conf" and it comes up empty. I believe that if I can keep my older version after the update it will work. I ran "rpm -e --nodeps alsa-lib" before the update. It didn't work. I am reinstalling once again to clean up the mess I made trying to fix the last installation.

Why don't I show an asound.conf file and when do I use rpm -e --nodeps alsa-lib command.

Here is a solution to fix this bug.

I think file
is created by
Use that first. That application should be able to play the test sound and you should be able to hear it. If that application fails then you are not suffering this bug and my writings won't help you so you can stop reading right here.

Ok. You heard the test sound.
Then you should be able to open asound.conf file with gedit.

Here is mine for example

Every defaults device with 1.0.14 alssa version should be 0. With previous alsa versions these values were different so using old asound.conf file doesn't work. With this new alsa version soundcard detector writes wrong values to this file.

After editing and saving asound.conf file it is time to reboot. Things should work now.

Man, I thought this was the one that would get it working. I ran "system-config soundcard ad it created a "/etc/asound.conf" file. It didn't work. I didn't hear any sound at the test but it created this;

This looks the same as yours except the DEV is "0". I switched to "1" like yours and still nothing. This is really too much. I had everything working perfect for months until this recent upgrade and all hell broke loose. I am not loading anything else in the installation until I can fix this problem for fear that I will only be doing it again. Anyway I hope you stay with me on this. You are helping. Thanks, Bob

I am not much of help anymore.

should get sound out. Some people have reported to get sound working under KDE using
and from it in system using reload audio drivers.

All I can think of is switching between devices. Choosing different PCM devices. Changing default devices or changing device load order. Just messing with
until you can get test sound out.

There has also been some options for acer laptops but I don't remember which file to put them ( /etc/modprobe.conf i gues ) and what those options were. Search for acer linux sound or something similar.

Markelo, in this post you stated alarm by installing this version. I've been reinstalling constantly since the yum remove fiasco at the beginning of this thread. I just spent my whole Saturday installing Core 6, Ubuntu 6.10, SuSe 10.1 and now I'm running Fedora core 5. All have sound problems. Ubuntu and both Fedora distros occur after initial updates.

Ok, now to my point. I believe the problem is in ths new version of drivers ie 1.0.14xxxx. My question is how do I not include these packages in my updates. I need also to mention that I also tried the GUI update which I was able to uncheck alsa-lib and alsa-utils. The updates still installed the new alsa drivers and left the lib and utils original. No sound. I honestly think that if I could omit the whole package from updating I could solve my problem. Maybe even remove them properly and configure them manually. I'm getting desperate.

What do you think? Bob

startcat..
Yum might have automatic update enabled. Look at
system/administration/server settings/services

After you disable automatic update yuo should be able to update kernel by just doing
Of course if alse depends on this kernel it will also get updated and then I don't know how to avoid updating.

Actually I've been disabling auto updates. I did however try once to update with automatic updates. It actually allowed me to edit out the updates I didn't want to install. I selected Alsa-lib and Alsa-utils. When the update finished It had left the two original alsa-lib and alsa-utils. The only thing is that it installed the updated Alsa drivers. I think if I could keep the original drivers it would have worked. I'm about to give this up for a while. I'm spending way too much time trying to get Linux back onto my laptop. Thanks for your help, Bob

Ok, I ended up reinstalling with Ubuntu 6.10 Edgy. I ended up with the same problem with no sound. I opened the preferences tab on my volume icon and selected "HDA Intel (Alsa Mixer" and selected the "Surround" tab. Now I have sound. I wonder if this would have worked in Fedora Core 6? If anyone tries this please let me know. As it stands now I am totally up and running with Ubuntu.

um.. can you try playing something as root?
I have had the same problem, turned out to be a permission issue with the /dev/dsp file ...
(Something to do with udev rules?)
>l /dev/dsp
crw-rw-rw- 1 root audio 14, 3 2007-04-18 10:27 /dev/dsp
if its
>l /dev/dsp
crw------- 1 root audio 14, 3 2007-04-18 10:27 /dev/dsp

then one time solution is to give write perms as root, but a long term solution
is to add the user to 'audio' and do some udev rules.. cant seem to locate a page
I saw long time back..

do post if you manage to figure out something...

I ended up here with the same problem. FC6, same kernel upgrade, same sound driver. Sound just stopped working. And soundcard detection doesn't play either. Now, I'm afraid of doing anything since stratcat had so many problems with it. Did anyone figure this out?


UPDATE: I just reloaded my old kernel (2.6.18-1.2849.fc6), and the sound works just fine. Didn't really need the new one anyway, so I can wait until the bug is fixed. My sound never worked perfectly anyway: system sounds (startup sound, etc) never played, and some web movies don't play sound, but all I really care about is jamming rhythmbox to my 100GB of ntfs mounted music at work, so...

Grant or Not, I never came up with a solution with Fedora Core 6. I even tried going back to Core 5. Both kernel upgrades produced the same alsa driver upgrade. After several tries I got pretty fed up with trying to straighten out this problem. I ended up installing Ubuntu 6.10 Edgy and I am so far very happy with it. All I had to do here was make a couple of adjustments and the sound come up. I was worried that I was going to have the same drivers problem as with FC6 but it worked out fine. Setting up the wireless also worked out nice. I may just stay with this for a while or until the sound problem in Fedora is fixed. I left this thread open so maybe others like yourself (and myself) can finally find a solution to this.

Did you by any chance try Hashash's solution? Try it it may work. I never had a chance to try it as I was already using a different distro. Good luck,

Bob