-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Last night, I was fumbling around trying to play a DVD that was just a bit too encrypted. I installed libdvdcss and then lindvd. They have since been uninstalled. Now, I have no sound. I'm not sure that those packages caused the problem, but ...
In any case, system-config-soundcard sees the SB Audigy card, but nothing comes out. When I boot into Windows, it's happy.
On the same day, a bunch of packages were installed, including hal.
My suspicion is that it has more to do with HAL than the dvd fumbling. Has anyone else lost sound since hal - 0.5.10-1.fc8.2.i386
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?
- --
~ Steve
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.
-----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.
Since last time it worked (for sure):
Mar 13 07:23:29 Installed: perl-Date-Manip - 5.48-1.fc8.noarch Mar 13 07:23:34 Installed: python-paste - 1.4.2-1.fc8.noarch Mar 13 07:23:37 Installed: python-genshi - 0.4.4-2.fc8.noarch Mar 13 07:23:40 Updated: smolt - 1.1.1.1-1.fc8.noarch Mar 13 07:23:41 Updated: smolt-firstboot - 1.1.1.1-1.fc8.noarch Mar 13 07:23:41 Updated: hal-libs - 0.5.10-1.fc8.2.i386 Mar 13 07:23:46 Updated: e2fsprogs-libs - 1.40.4-2.fc8.i386 Mar 13 07:23:52 Updated: coreutils - 6.9-16.fc8.i386 Mar 13 07:23:54 Updated: boost - 1.34.1-7.fc8.i386 Mar 13 07:23:54 Updated: net-snmp-libs - 1:5.4.1-6.fc8.i386 Mar 13 07:23:55 Updated: nautilus-extensions - 2.20.0-9.fc8.i386 Mar 13 07:24:07 Updated: ruby-libs - 1.8.6.114-1.fc8.i386 Mar 13 07:24:14 Updated: eject - 2.1.5-6.fc8.i386 Mar 13 07:24:20 Updated: ruby - 1.8.6.114-1.fc8.i386 Mar 13 07:24:58 Updated: kdelibs - 6:3.5.9-5.fc8.i386 Mar 13 07:24:59 Updated: hal - 0.5.10-1.fc8.2.i386 Mar 13 07:25:39 Updated: gnucash - 2.2.4-1.fc8.i386 Mar 13 07:25:40 Updated: imlib2 - 1.4.0-6.fc8.i386 Mar 13 07:25:40 Updated: fuse-libs - 2.7.3-2.fc8.i386 Mar 13 07:25:41 Updated: cpio - 2.9-7.fc8.i386 Mar 13 07:25:44 Updated: doxygen - 1:1.5.5-1.fc8.i386 Mar 13 07:25:46 Updated: net-snmp - 1:5.4.1-6.fc8.i386 Mar 13 07:25:46 Updated: hal-devel - 0.5.10-1.fc8.2.i386 Mar 13 07:25:47 Updated: xterm - 234-1.fc8.i386 Mar 13 07:26:12 Updated: nautilus - 2.20.0-9.fc8.i386 Mar 13 07:26:33 Updated: fuse - 2.7.3-2.fc8.i386 Mar 13 07:26:33 Updated: rsyslog - 2.0.2-3.fc8.i386 Mar 13 07:26:42 Updated: boost-devel - 1.34.1-7.fc8.i386 Mar 13 07:26:44 Updated: e2fsprogs-devel - 1.40.4-2.fc8.i386 Mar 13 07:26:45 Updated: e2fsprogs - 1.40.4-2.fc8.i386 Mar 13 07:26:45 Erased: perl-DateManip Mar 13 21:32:49 Installed: libdvdcss - 1.2.9-4.lvn6.i386 Mar 13 21:45:27 Installed: compat-libstdc++-33 - 3.2.3-62.i386 Mar 14 07:52:59 Erased: compat-libstdc++-33 Mar 14 19:39:00 Erased: libdvdcss
It appears that the drivers are loaded:
# lsmod |grep sn snd_ca0106 32993 3 snd_rawmidi 22465 1 snd_ca0106 snd_ac97_codec 93413 1 snd_ca0106 snd_seq_dummy 6725 0 snd_seq_oss 31553 0 snd_seq_midi_event 9665 1 snd_seq_oss snd_seq 48945 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 10317 4 snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 44353 0 snd_mixer_oss 17217 2 snd_pcm_oss snd_pcm 70981 3 snd_ca0106,snd_ac97_codec,snd_pcm_oss snd_timer 21317 2 snd_seq,snd_pcm snd 48453 15 snd_ca0106,snd_rawmidi,snd_ac97_codec,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 9505 2 snd ac97_bus 5825 1 snd_ac97_codec snd_page_alloc 11593 2 snd_ca0106,snd_pcm dm_snapshot 17765 0 dm_mod 48773 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
- --
~ Steve
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?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/15/2008 04:52 PM, 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? | $ cat /proc/asound/cards ~ 0 [CA0106 ]: CA0106 - CA0106 ~ Live! 7.1 24bit [SB0413] at 0xc8e0 irq 17
Alsamixer says "card - pulseaudio" and "chip - pulseaudio".
- --
~ Steve
Steven Stern wrote:
|> 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? | $ cat /proc/asound/cards ~ 0 [CA0106 ]: CA0106 - CA0106 ~ Live! 7.1 24bit [SB0413] at 0xc8e0 irq 17
Alsamixer says "card - pulseaudio" and "chip - pulseaudio".
I heard mention that there should be no sound based items in /etc/modprobe.conf. Perhaps you could post it / try commenting {#} any such items out ?
DaveT.
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?
Make sure the cat didn't rub itself against the power plug and yank it out. <grins hugely> I've had that happen to me and only found it after cursing and swearing for several days. Ric
On Saturday 15 March 2008, David Timms wrote:
Steven Stern wrote:
|> 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?
$ cat /proc/asound/cards ~ 0 [CA0106 ]: CA0106 - CA0106 ~ Live! 7.1 24bit [SB0413] at 0xc8e0 irq 17
Alsamixer says "card - pulseaudio" and "chip - pulseaudio".
I heard mention that there should be no sound based items in /etc/modprobe.conf. Perhaps you could post it / try commenting {#} any such items out ?
DaveT.
'scuse me? Whoever said that probably needs help tieing his shoes too. Mine doesn't work without this stuff:
alias snd-card-0 snd-emu10k1 options snd-card-0 index=0 options snd-emu10k1 index=0 alias snd-card-1 snd-intel8x0 options snd-card-1 index=1 options snd-intel8x0 index=1 alias snd-card-2 snd-mpu401 options snd-card-2 index=2 options snd-mpu401 index=2
I have effectively 2 cards, the builtin one on the mobo I use about .1% of a blue moon for skype, and an audigy2 for everything else.
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@sbcglobal.net
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@sbcglobal.net
Check that all the services that should be running are in fact running.
Max
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@sbcglobal.net
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.
-----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@sbcglobal.net |> 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
On Sun, 2008-03-16 at 14:04 -0500, Steven Stern wrote:
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?
Can you disable madwifi, reboot, check for sound? If you have it, check and note the contents of /proc/interrupts. Then re-enable madwifi, reboot and check /proc/interrupts again to see if anything changed. I'd like to know how it works out for you. Ric
On Sun, 2008-03-16 at 19:10 +0100, 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@sbcglobal.net
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.
Amen to that. I've been banging my head againt the wall for several weeks because sound worked in stuff like mplayer, vlc, flash videos etc., but not in Amarok. Removing alsa-plugins-pulseaudio magically fixed everything.
poc
On Monday 17 March 2008 15:59, Patrick O'Callaghan wrote:
On Sun, 2008-03-16 at 19:10 +0100, 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@sbcglobal.net
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.
Amen to that. I've been banging my head againt the wall for several weeks because sound worked in stuff like mplayer, vlc, flash videos etc., but not in Amarok. Removing alsa-plugins-pulseaudio magically fixed everything.
poc
Hi Patrick. Nice to hear your sounds are fixed. Something else you could do if you have any audio apps that use SDL, is to add the following line to ~/.bashrc, which will remove the hack that SDL programs need to use pulseaudio.
unset SDL_AUDIODRIVER
All the best.
Nigel.
On Mon, 2008-03-17 at 16:33 +0100, Nigel Henry wrote:
On Monday 17 March 2008 15:59, Patrick O'Callaghan wrote:
On Sun, 2008-03-16 at 19:10 +0100, 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@sbcglobal.net
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.
Amen to that. I've been banging my head againt the wall for several weeks because sound worked in stuff like mplayer, vlc, flash videos etc., but not in Amarok. Removing alsa-plugins-pulseaudio magically fixed everything.
poc
Hi Patrick. Nice to hear your sounds are fixed. Something else you could do if you have any audio apps that use SDL, is to add the following line to ~/.bashrc, which will remove the hack that SDL programs need to use pulseaudio.
unset SDL_AUDIODRIVER
I have no idea whether any of my stuff uses SDL and am too lazy to check, but I guess it doesn't do any harm to unset the variable anyway :-)
poc
On Tue, Mar 18, 2008 at 10:29 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sun, 2008-03-16 at 19:10 +0100, 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@sbcglobal.net
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.
Amen to that. I've been banging my head againt the wall for several weeks because sound worked in stuff like mplayer, vlc, flash videos etc., but not in Amarok. Removing alsa-plugins-pulseaudio magically fixed everything.
Just a note to the effect that I now have sound working with pulseaudio. The trick was to RTFM :-). Specifically, the instructions in http://fedoraproject.org/wiki/YumUpgradeFaq (in the section entitled Fedora 7 -> Fedora 8) where it says:
yum groupinstall sound-and-video gnome-desktop (if you are using Gnome) yum groupinstall sound-and-video kde-desktop (if you are using KDE) yum install libflashsupport paman padevchooser
After exiting and restarting the session, this worked.
poc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
OK, take away my license to operate linux...
While digging through the pile of cables today looking for the volume control for my Monsoon speaker system, I found that the mute button was pressed. Yet another misdiagnosed hardware problem!
On 03/14/2008 07:42 PM, Steven Stern wrote: | Last night, I was fumbling around trying to play a DVD that was just a | bit too encrypted. I installed libdvdcss and then lindvd. They have | since been uninstalled. Now, I have no sound. I'm not sure that those | packages caused the problem, but ... | | In any case, system-config-soundcard sees the SB Audigy card, but | nothing comes out. When I boot into Windows, it's happy. | | On the same day, a bunch of packages were installed, including hal. | | My suspicion is that it has more to do with HAL than the dvd fumbling. | Has anyone else lost sound since hal - 0.5.10-1.fc8.2.i386 | | 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? |
- --
~ Steve
On Fri, 2008-03-21 at 11:24 -0500, Steven Stern wrote:
OK, take away my license to operate linux...
While digging through the pile of cables today looking for the volume control for my Monsoon speaker system, I found that the mute button was pressed. Yet another misdiagnosed hardware problem!
Even the manuals for $60,000 BetaCAMs have a diagnosis section with "is it plugged in?" and "it it turned on?" types of steps. It seems that nobody's immune from making those sort of mistakes.
I wonder what the flight manuals are like for jumbo jets? "Thank you for purchasing your new Boeing 707, before flying ensure that you have closed the doors and fastened your safety belt..."
Tim wrote:
On Fri, 2008-03-21 at 11:24 -0500, Steven Stern wrote:
OK, take away my license to operate linux...
While digging through the pile of cables today looking for the volume control for my Monsoon speaker system, I found that the mute button was pressed. Yet another misdiagnosed hardware problem!
Even the manuals for $60,000 BetaCAMs have a diagnosis section with "is it plugged in?" and "it it turned on?" types of steps. It seems that nobody's immune from making those sort of mistakes.
I wonder what the flight manuals are like for jumbo jets? "Thank you for purchasing your new Boeing 707, before flying ensure that you have closed the doors and fastened your safety belt..."
Not to pick nits, but a 707 isn't considered a jumbo jet and they've been out of production for over 30 years so you can't get a new one anyway. :-)
However, the 747, 757 and 767 manuals all have preflight inspection steps including "remove all covering material from the pitot tubes" and "remove wheel chocks before attempting to taxi".
Chuck Yeager had two great lines:
"You know you've landed gear-up when it takes full power to taxi." "The only time you can have too much gas is when you're on fire."
And yes, I'm a pilot. Only little planes, though, with big, spinny things on the nose called, uhm, "propellers". ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer rps2@nerd.com - - Hosting Consulting, Inc. - - - - Polygon: A dead parrot (With apologies to John Cleese) - ----------------------------------------------------------------------
On Fri, 2008-03-21 at 10:23 -0700, Rick Stevens wrote:
However, the 747, 757 and 767 manuals all have preflight inspection steps including "remove all covering material from the pitot tubes" and "remove wheel chocks before attempting to taxi".
While we're digressing about manuals, I was somewhat amused by something I was told by a colleague, years ago: The service manuals for one of the broadcast television cameras (I think it was a Marconi) all had CPR instructions in the front, just in case someone working on them got bitten by the electricity.
One of my favourite personal discoveries while doing some servicing work at a local studio was finding an aspirin taped inside the chassis of a computer. It caused some mirth while we debated whether it was supposed to help the crappy PC, or was there to help the next poor sod who had to work on it. ;-)
On Fri, 2008-03-21 at 10:23 -0700, Rick Stevens wrote:
Tim wrote:
On Fri, 2008-03-21 at 11:24 -0500, Steven Stern wrote:
OK, take away my license to operate linux...
While digging through the pile of cables today looking for the volume control for my Monsoon speaker system, I found that the mute button was pressed. Yet another misdiagnosed hardware problem!
Even the manuals for $60,000 BetaCAMs have a diagnosis section with "is it plugged in?" and "it it turned on?" types of steps. It seems that nobody's immune from making those sort of mistakes.
I wonder what the flight manuals are like for jumbo jets? "Thank you for purchasing your new Boeing 707, before flying ensure that you have closed the doors and fastened your safety belt..."
Not to pick nits, but a 707 isn't considered a jumbo jet and they've been out of production for over 30 years so you can't get a new one anyway. :-)
However, the 747, 757 and 767 manuals all have preflight inspection steps including "remove all covering material from the pitot tubes" and "remove wheel chocks before attempting to taxi".
Chuck Yeager had two great lines:
"You know you've landed gear-up when it takes full power to taxi." "The only time you can have too much gas is when you're on fire."
And yes, I'm a pilot. Only little planes, though, with big, spinny things on the nose called, uhm, "propellers".
And Story Musgrave said "Control-alt-delete is not an option when you are on final approach in the shuttle!"
Regards, Les H
On Fri, Mar 21, 2008 at 12:24 PM, Steven Stern < subscribed-lists@sterndata.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
OK, take away my license to operate linux...
While digging through the pile of cables today looking for the volume control for my Monsoon speaker system, I found that the mute button was pressed. Yet another misdiagnosed hardware problem!
SO it goes...i have done it to. At least your willing to admit your
mistake.
Max
http://fedoraproject.org/wiki/YumUpgradeFaq (in the section entitled Fedora 7 -> Fedora 8) where it says:
yum groupinstall sound-and-video gnome-desktop (if you are using Gnome) yum groupinstall sound-and-video kde-desktop (if you are using KDE) yum install libflashsupport paman padevchooser
So what are those of us not using Gnome or KDE supposed to do?
If I try running any Gnome sound apps I get my desktop background reset, followed by a hang in a few minutes when gnome-screensaver takes on my xscreensaver and locks up X. Kaffeine worked for a while when run as root, but now it just crashes.
If sound doesn't work in Fedora 9 I'll be switching to some distribution where it does work. I don't have time to waste trying apparently random suggestions involving half a dozen daemons, security and module configuration files, and package installs and uninstalls -- some of which swap functionality between Flash and music players, some of which work for a while and then stop working.
Danny. --------------------------------------------------------- http://dannyreviews.com/ - over one thousand book reviews http://danny.oz.au/ - civil liberties, travel tales, blog ---------------------------------------------------------
On Fri, 2008-03-21 at 11:24 -0500, Steven Stern wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
OK, take away my license to operate linux...
While digging through the pile of cables today looking for the volume control for my Monsoon speaker system, I found that the mute button was pressed.
<huge cackles> You won't be the first nor the last!! Done it myself. More than once. Ric
On Friday 21 March 2008, Tim wrote:
On Fri, 2008-03-21 at 10:23 -0700, Rick Stevens wrote:
However, the 747, 757 and 767 manuals all have preflight inspection steps including "remove all covering material from the pitot tubes" and "remove wheel chocks before attempting to taxi".
While we're digressing about manuals, I was somewhat amused by something I was told by a colleague, years ago: The service manuals for one of the broadcast television cameras (I think it was a Marconi) all had CPR instructions in the front, just in case someone working on them got bitten by the electricity.
One of my favourite personal discoveries while doing some servicing work at a local studio was finding an aspirin taped inside the chassis of a computer. It caused some mirth while we debated whether it was supposed to help the crappy PC, or was there to help the next poor sod who had to work on it. ;-)
And then there was the manual that came with the Bell TR-7 1/4" audio tape recorder, circa 1956 or so. It said in rather large type,
Please try our way first!
Loved it, never forgot it.
On Fri, 2008-03-21 at 22:16 -0400, Gene Heskett wrote:
On Friday 21 March 2008, Tim wrote:
On Fri, 2008-03-21 at 10:23 -0700, Rick Stevens wrote:
However, the 747, 757 and 767 manuals all have preflight inspection steps including "remove all covering material from the pitot tubes" and "remove wheel chocks before attempting to taxi".
While we're digressing about manuals, I was somewhat amused by something I was told by a colleague, years ago: The service manuals for one of the broadcast television cameras (I think it was a Marconi) all had CPR instructions in the front, just in case someone working on them got bitten by the electricity.
One of my favourite personal discoveries while doing some servicing work at a local studio was finding an aspirin taped inside the chassis of a computer. It caused some mirth while we debated whether it was supposed to help the crappy PC, or was there to help the next poor sod who had to work on it. ;-)
And then there was the manual that came with the Bell TR-7 1/4" audio tape recorder, circa 1956 or so. It said in rather large type,
Please try our way first!
Loved it, never forgot it.
"When all else fails, read the manual" -- Hacker folklore from prehistory
poc
On Sat, 2008-03-22 at 08:10 -0430, Patrick O'Callaghan wrote:
"When all else fails, read the manual" -- Hacker folklore from prehistory
;-) I've said that to many a person...
Only about a week ago I was doing some work for a client who wanted to install some software, which kept on failing during registration. So while he floundered around, trying things without really thinking, nor even reading what was on the screen in front of him, I had a quick read of the manual, and worked out what he was doing wrong.
The time I spent reading it was far less time than he spent flailing about, and what I did (by the book) worked. ;-)