-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/16/2008 01:10 PM, Nigel Henry wrote: | On Sunday 16 March 2008 18:10, max wrote: |> Aaron Konstam wrote: |>> On Sat, 2008-03-15 at 17:52 -0400, Bill Davidsen wrote: |>>> Steven Stern wrote: |>>>> -----BEGIN PGP SIGNED MESSAGE----- |>>>> Hash: SHA1 |>>>> |>>>> On 03/14/2008 09:23 PM, David Timms wrote: |>>>> | Steven Stern wrote: |>>>> |> In any case, system-config-soundcard sees the SB Audigy card, but |>>>> |> nothing comes out. When I boot into Windows, it's happy. |>>>> | |>>>> | = hardware OK,, software problem. |>>>> | Maybe you could post the |>>>> | /root/scsconfig.log |>>>> | |>>>> | Are modules getting loaded: lsmod|grep sn |>>>> | |>>>> | Did you see the s-c-soundcard System tab it has some functions to |>>>> | redetect and so-on... |>>>> | |>>>> |> On the same day, a bunch of packages were installed, including hal. |>>>> |> Is there some way I can "clean" the system of what it knows about |>>>> |> the current sound card and let it rediscover it from scratch? |>>>> | |>>>> | Post the yum changes since the last time that sound was working from |>>>> | /var/log/yum?.log |>>>> | |>>>> | That might indicate what has changed. |>>>> | |>>>> | DaveT. |>>>> |>>>> I get sound when booting from the F8 Live CD, so *something's* changed. |>>>> ~ The scsconfig.log file is attached. |>>> cat /proc/asound/cards and see if somehow it's still finding another |>>> card. What does alsamixer show for output devices? |>> Omce again. alsamixer does not work if pulseaudio is active. |>> -- |>> ======================================================================= |>> No matter who you are, some scholar can show you the great idea you had |>> was had by someone before you. |>> ======================================================================= |>> Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx |> Check that all the services that should be running are in fact running. |> |> |> Max | | Personally, and not wishing to knock Lennart's Pulseaudio, which I'm sure | quite a lot of folks have found usefull. All the same though, I think I'd | temporarily remove the alsa-plugins-pulseaudio package, then see if sounds | work as expected. | | Pulseaudio, installed as default on F8 appears to have caused problems for | some folks, including myself, and removing alsa-plugins-pulseaudio got my | sounds back as they were before on previous Fedora versions. | | 2¢ worth of nothing perhaps. | | Nigel. | If we can get back to my problem instead of arguing about pulseaudio.... Today, I reinstalled F8 from scratch. Got sounds. Ran YUM UPDATE. Got sounds. Rebooted. Got sounds. Deactivated eth0, wlan0. Installed and activated madwifi drivers. Rebooted. No sounds. Could this be an interrupt conflict? - -- ~ Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFH3W87eERILVgMyvARAp4GAJsFkIvD8JR4kQDOAfKNpAnMOXjILgCeLq65 C73H4vKqhOCT/6yIu9ZXEbM= =Bt3C -----END PGP SIGNATURE----- -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
