intermittent no sound and programs somtimes crashing at boot in F10

[terry_g]

I'm running fedora 10 i386 fully updated with the latest kernel on an Intel E2180 dual processor with 2 Gigs of ram on an ASRock SATA2 Dual mobo with two 320 Gig SATA drives. Fedora 7,8 and 9 ran perfectly on this system, 8, 9 and 10 are multi booted on this system .

After installing Fedora 10 from a live CD everything just worked! I had to do a few tweaks to get my webcam working with Skype and to get Google Earth running with SELinux set to enforcing mode and I got rid of NetworkManager.

About 10% of the time when I boot up my computer something will not work.
Usually it's the sound but not always sometimes a notification will pop up right after boot saying that sealert has crashed or nautilus has crashed or gnome-something has crashed or bugbuddy has crashed or something else has crashed there have been a lot of different ones, sometimes the bugbuddy reporting tool pops up, very seldom it's the same notification. Some times my desktop theme is not loaded at startup, I'm running Enigma.
I never get a notification when the sound doesn't work.

When the sound doesn't work I right click on the volume control on the panel and select "open volume control" Alsa is missing from the list.

If I run the lsmod command the same modules are always loaded although in a different order, I believe that is normal.

If I reboot whatever the problem was it is almost always gone until a few reboots later. This problem existed with all the previous kernels.

Iwas hoping this problem would be cured by an update but that has not happened.
Is anyone else experiencing this?

Thanks Terry

[hephasteus]

Originally Posted by terry_g

I'm running fedora 10 i386 fully updated with the latest kernel on an Intel E2180 dual processor with 2 Gigs of ram on an ASRock SATA2 Dual mobo with two 320 Gig SATA drives. Fedora 7,8 and 9 ran perfectly on this system, 8, 9 and 10 are multi booted on this system .

After installing Fedora 10 from a live CD everything just worked! I had to do a few tweaks to get my webcam working with Skype and to get Google Earth running with SELinux set to enforcing mode and I got rid of NetworkManager.

About 10% of the time when I boot up my computer something will not work.
Usually it's the sound but not always sometimes a notification will pop up right after boot saying that sealert has crashed or nautilus has crashed or gnome-something has crashed or bugbuddy has crashed or something else has crashed there have been a lot of different ones, sometimes the bugbuddy reporting tool pops up, very seldom it's the same notification. Some times my desktop theme is not loaded at startup, I'm running Enigma.
I never get a notification when the sound doesn't work.

When the sound doesn't work I right click on the volume control on the panel and select "open volume control" Alsa is missing from the list.

If I run the lsmod command the same modules are always loaded although in a different order, I believe that is normal.

If I reboot whatever the problem was it is almost always gone until a few reboots later. This problem existed with all the previous kernels.

Iwas hoping this problem would be cured by an update but that has not happened.
Is anyone else experiencing this?

Thanks Terry

No I'm using x64 and I did the how to get sound working sticky thread and it's worked fairly well. Very rarely sound chops and sometimes the pulse audio sound server will refuse to work on one app but works on another app. VLC is messing with it some and i have to go to pulse audio applet and reset the bullets to default sound server to fix it.

Try the sound fix sticky thread. It seems to me that it's crashing and bug buddy is trying to come up and that is crashing right after. Are you loading a lot of sound enabled programs at boot up and they aren't getting along because the bootup is sending them to sound server in parallel instead of serially?

[terry_g]

I followed the instructions in the thread "How to: Fix PulseAudio and primary audio issues with Fedora 10 (F10)"
I was not having the problems mentioned in the thread.
When my sound works it works properly. After making the changes I rebooted a couple times and the second time the sound did not work. I rebooted again and it worked.
I do not have any sound enabled programs loading at startup.

Terry

[terry_g]

After the last few updates I have had no problems with programs crashing at startup. However I had no sound with the latest kernel 2.6.27.9-159.fc10.i686. So I edited grub to boot to the previous kernel 2.6.27.7-134.fc10.i686 and the sound was back.
I am still having intermittent no sound at bootup however I discovered that if I log out and back in the sound usually will work again. This would eliminate a driver issue and I suspect it's probably a config file in my home directory.