Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything. I get no error messages from the audio applications like xmms or mplayer when I try to play audio. They show the normal behaviour, I just don't hear anything.
The soundcard is OK, when I boot Knoppix from DVD, sound is working
The mixer is not muted, system-config-soundcard won't help, the modules are loaded.
Is there any configuration I can reset? Or should I just wait for FC7 and reinstall the whole stuff? I'm desperate...
Chris
On Fri, 2007-05-18 at 17:11 +0200, Christian Menzel wrote:
Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything. I get no error messages from the audio applications like xmms or mplayer when I try to play audio. They show the normal behaviour, I just don't hear anything.
The soundcard is OK, when I boot Knoppix from DVD, sound is working
The mixer is not muted, system-config-soundcard won't help, the modules are loaded.
Is there any configuration I can reset? Or should I just wait for FC7 and reinstall the whole stuff? I'm desperate...
When I got REALLY desperate, I'd powerdown, unplug the card, reboot, let the system deal with no sound card for a bit, making sure that /etc/modprobe.conf was empty of sound card module info (or better yet comment them out) then shutdown and carefully re-insert it, reboot and Voila`! Woot! ...der it is! The hardware dingus would automatically detect and install it brand new. It's a bit *ExTrEmE* but worked for me in a royal pinch when I was at wit's end. Ric
On Friday 18 May 2007 18:37, Ric Moore wrote:
On Fri, 2007-05-18 at 17:11 +0200, Christian Menzel wrote:
Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything. I get no error messages from the audio applications like xmms or mplayer when I try to play audio. They show the normal behaviour, I just don't hear anything.
The soundcard is OK, when I boot Knoppix from DVD, sound is working
The mixer is not muted, system-config-soundcard won't help, the modules are loaded.
Is there any configuration I can reset? Or should I just wait for FC7 and reinstall the whole stuff? I'm desperate...
When I got REALLY desperate, I'd powerdown, unplug the card, reboot, let the system deal with no sound card for a bit, making sure that /etc/modprobe.conf was empty of sound card module info (or better yet comment them out) then shutdown and carefully re-insert it, reboot and Voila`! Woot! ...der it is! The hardware dingus would automatically detect and install it brand new. It's a bit *ExTrEmE* but worked for me in a royal pinch when I was at wit's end. Ric --
Now just where did you find that word "dingus"? The last time I heard that was from a Belgian friend, who used it when he couldn't find the correct english word for something.
Nigel.
On Fri, 2007-05-18 at 19:03 +0200, Nigel Henry wrote:
On Friday 18 May 2007 18:37, Ric Moore wrote:
On Fri, 2007-05-18 at 17:11 +0200, Christian Menzel wrote:
Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything. I get no error messages from the audio applications like xmms or mplayer when I try to play audio. They show the normal behaviour, I just don't hear anything.
The soundcard is OK, when I boot Knoppix from DVD, sound is working
The mixer is not muted, system-config-soundcard won't help, the modules are loaded.
Is there any configuration I can reset? Or should I just wait for FC7 and reinstall the whole stuff? I'm desperate...
When I got REALLY desperate, I'd powerdown, unplug the card, reboot, let the system deal with no sound card for a bit, making sure that /etc/modprobe.conf was empty of sound card module info (or better yet comment them out) then shutdown and carefully re-insert it, reboot and Voila`! Woot! ...der it is! The hardware dingus would automatically detect and install it brand new. It's a bit *ExTrEmE* but worked for me in a royal pinch when I was at wit's end. Ric --
Now just where did you find that word "dingus"? The last time I heard that was from a Belgian friend, who used it when he couldn't find the correct english word for something.
I think that is a word that Robert Heinlein used. It was always a "dingus" that enabled a red-haired and freckled 13 year old Lazarus Long to journey to Mars or the Asteroids, after cobbling together an improbable craft made from various assorted bits and pieces found conveniently in an Uncle's barn. Of course the Uncle worked undercover for the AEC and had some really mysterious yet useful dingus's lying about, just waiting to be put together by an inquisitive mind. Isn't that how Linux got started? Same mindset. Every male geek on this list over 40 has read Heinlein, dreamed of finding the Uncle's barn and blasting off and away from this festering cheese-ball called Earth to reach adulthood "out there" instead of back home in some Dog Patch.
The female brain remains just as mysterious today as it was back when, in a Heinlein novelette. They were always too smart! Read Starship Troopers, where the she became high IQ starship pilot and he drug knuckles as a ground pounding grunt, and was proud of it. Nothing has changed. He finally solved the problem for his character in his last works by cloning Lazarus Long's feminine self and marrying "her". That made me cringe a bit, but it made sense after awhile of digestion. But, even that "she" was still smarter and meaner. I miss ole Robert. This may be way off topic, but I'll bet there is a collective "ahhhhh..." of recollection among the older geek males on this list, and possibly some of the Ladies as well.
<drags hairy knuckles, toothy grins and eyebrow waggles> Ric
On Friday 18 May 2007, Ric Moore wrote:
On Fri, 2007-05-18 at 19:03 +0200, Nigel Henry wrote:
On Friday 18 May 2007 18:37, Ric Moore wrote:
When I got REALLY desperate, I'd powerdown, unplug the card, reboot, let the system deal with no sound card for a bit, making sure that /etc/modprobe.conf was empty of sound card module info (or better yet comment them out) then shutdown and carefully re-insert it, reboot and Voila`! Woot! ...der it is! The hardware dingus would automatically detect and install it brand new. It's a bit *ExTrEmE* but worked for me in a royal pinch when I was at wit's end. Ric --
Now just where did you find that word "dingus"? The last time I heard that was from a Belgian friend, who used it when he couldn't find the correct english word for something.
I think that is a word that Robert Heinlein used. It was always a "dingus" that enabled a red-haired and freckled 13 year old Lazarus Long to journey to Mars or the Asteroids, after cobbling together an improbable craft made from various assorted bits and pieces found conveniently in an Uncle's barn. Of course the Uncle worked undercover for the AEC and had some really mysterious yet useful dingus's lying about, just waiting to be put together by an inquisitive mind. Isn't that how Linux got started? Same mindset. Every male geek on this list over 40 has read Heinlein, dreamed of finding the Uncle's barn and blasting off and away from this festering cheese-ball called Earth to reach adulthood "out there" instead of back home in some Dog Patch.
Yup, and some of us started with Doc Smiths output.
The female brain remains just as mysterious today as it was back when, in a Heinlein novelette. They were always too smart! Read Starship Troopers, where the she became high IQ starship pilot and he drug knuckles as a ground pounding grunt, and was proud of it. Nothing has changed. He finally solved the problem for his character in his last works by cloning Lazarus Long's feminine self and marrying "her". That made me cringe a bit, but it made sense after awhile of digestion. But, even that "she" was still smarter and meaner. I miss ole Robert. This may be way off topic, but I'll bet there is a collective "ahhhhh..." of recollection among the older geek males on this list, and possibly some of the Ladies as well.
Yes, in particular I enjoyed his bit of congressional testimony and reparte in the exchanges that took place as he was testifying in favor of continued funding for NASA at the time. His testimony involved replaying for the senators present the goings on during his recent brain surgery. He was at the time before the surgery slowly dying of an occluded carotid artery, and was getting dumber by the week.
So they located an artery in his scalp that had good flow, drilled a hole in his skull and tied that artery into the top of the carotid, and when the flow was released he could tell instantly that he was pretty close to the old Robert we all read and thought we knew.
That bit of surgery, using micro-miniature tools NASA had paid to develop, gave him another 5 years of productive life behind the keyboard. But nothing particularly memorable came out of it, just as nothing memorable has come out of A.C. Clarks computer recently. His 'creative' juices were on the wane 20 years ago & now all he does is co-sign some other budding writers work, not much of which is terribly memorable, but which sells reasonably well because it has his imprimature on it. We have some decent writers today, but none of the caliber they were in their heyday. I miss them both although I believe ACC lives yet.
<drags hairy knuckles, toothy grins and eyebrow waggles> Ric
Don't you believe that for a second, Ric sent me a pix once, and he is a right good looking man in excellent shape with just a trace of grey. Girls, the line forms over there ---------------->
On 5/18/07, Ric Moore wayward4now@gmail.com wrote:
When I got REALLY desperate, I'd powerdown, unplug the card, reboot, let the system deal with no sound card for a bit, making sure that /etc/modprobe.conf was empty of sound card module info (or better yet comment them out) then shutdown and carefully re-insert it, reboot and Voila`! Woot! ...der it is! The hardware dingus would automatically detect and install it brand new. It's a bit *ExTrEmE* but worked for me in a royal pinch when I was at wit's end. Ric --
Well, this weekend I was THAT desperate removed the soundcard and cleaned modprobe.conf. After reinserting the card it was detected and the entries in modprobe.conf where made automatically. But - still no sound! Everything is like it was before. Now I really wait for the FC7 re installation. I'm afraid I will never solve this mystery.
Regards Chris
Christian Menzel wrote:
On 5/18/07, Ric Moore wayward4now@gmail.com wrote:
When I got REALLY desperate, I'd powerdown, unplug the card, reboot, let the system deal with no sound card for a bit, making sure that /etc/modprobe.conf was empty of sound card module info (or better yet comment them out) then shutdown and carefully re-insert it, reboot and Voila`! Woot! ...der it is! The hardware dingus would automatically detect and install it brand new. It's a bit *ExTrEmE* but worked for me in a royal pinch when I was at wit's end. Ric --
Well, this weekend I was THAT desperate removed the soundcard and cleaned modprobe.conf. After reinserting the card it was detected and the entries in modprobe.conf where made automatically. But - still no sound! Everything is like it was before. Now I really wait for the FC7 re installation. I'm afraid I will never solve this mystery.
Jeez, what kind of soundcard is it? IRQ conflict might not be out of the question. If you're still desperate, jerk more cards out to see if that resolves a possible conflict. What kind of mo-board and processor, how much ram? I assume you have checked the mixer, got the speakers plugged in,? Plugged into the "speaker out" and not the "mike"? (I've done that!) They are turned on and the volume about halfway up.
If it's a good ole ISA SoundBlaster AWE64, they have mentioned that support has been dropped and it takes a bit of wrangling to get one to work. Ric
On 5/21/07, Ric Moore wayward4now@gmail.com wrote:
Jeez, what kind of soundcard is it? IRQ conflict might not be out of the question. If you're still desperate, jerk more cards out to see if that resolves a possible conflict. What kind of mo-board and processor, how much ram? I assume you have checked the mixer, got the speakers plugged in,? Plugged into the "speaker out" and not the "mike"? (I've done that!) They are turned on and the volume about halfway up.
If it's a good ole ISA SoundBlaster AWE64, they have mentioned that support has been dropped and it takes a bit of wrangling to get one to work. Ric
It's a PCI soundblaster which was working for month without any problems. When I boot a live system from DVD sound is working. I think it stopped working when I tried to use Audacity to capture from lineIn.
There must be a master mixer or something that thinks the card is muted. Even if I boot into runlevel 3 and try auplay as root, I hear nothing.
Waiting for FC7... Chris
On Mon, 21 May 2007 18:25:46 +0200 "Christian Menzel" christian.menzel@gmail.com wrote:
On 5/21/07, Ric Moore wayward4now@gmail.com wrote:
Jeez, what kind of soundcard is it? IRQ conflict might not be out of the question. If you're still desperate, jerk more cards out to see if that resolves a possible conflict. What kind of mo-board and processor, how much ram? I assume you have checked the mixer, got the speakers plugged in,? Plugged into the "speaker out" and not the "mike"? (I've done that!) They are turned on and the volume about halfway up.
If it's a good ole ISA SoundBlaster AWE64, they have mentioned that support has been dropped and it takes a bit of wrangling to get one to work. Ric
It's a PCI soundblaster which was working for month without any problems. When I boot a live system from DVD sound is working. I think it stopped working when I tried to use Audacity to capture from lineIn.
There must be a master mixer or something that thinks the card is muted. Even if I boot into runlevel 3 and try auplay as root, I hear nothing.
Waiting for FC7... Chris
You can check what audacity thinks is the card it is using by going into edit:preferences. There is a selection drop down for play and record separately. Then from a console or terminal type aplay -lLv to see what devices alsa has defined as aliases. Once you know that try aplay -D one of the devices some.wav. Make sure that the speaker out is plugged into the correct jack. The aplay -lLv should also give you the hardware devices. if aplay -D some device alias doesn't work, try aplay -D hwplug:0,0 some.wav, or whichever devices alsa has assigned.
My past experience indicates that alsa keeps some internal state information that can wreak havoc while having problems. And did you remove any .asoundrc in ~/home or asound.state or asound.conf in /etc before you removed the card and plugged it back in? That could cause problems also.
If none of this works, ask on the alsa-devel list. They will want a lot of information before they can help you, but they are very knowledgeable about sound issues.
On 5/21/07, stan stanl@cox.net wrote:
You can check what audacity thinks is the card it is using by going into edit:preferences. There is a selection drop down for play and record separately. Then from a console or terminal type aplay -lLv to see what devices alsa has defined as aliases. Once you know that try aplay -D one of the devices some.wav. Make sure that the speaker out is plugged into the correct jack. The aplay -lLv should also give you the hardware devices. if aplay -D some device alias doesn't work, try aplay -D hwplug:0,0 some.wav, or whichever devices alsa has assigned.
aplay -D <device> seems to think everything is OK and plays the file, but I hear nothing :-(
aplay -D hwplug:0,0 returns an audio open error: No such file or directory, allthough aplay -lLv tells me there is a device 0,0: card 0: Audigy [Audigy 1 [Unknown]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Maybe I have to mknod a device?
My past experience indicates that alsa keeps some internal state information that can wreak havoc while having problems. And did you remove any .asoundrc in ~/home or asound.state or asound.conf in /etc before you removed the card and plugged it back in? That could cause problems also.
I don't have a local .asoundrc. The files in /etc were deleted.
Regards Chris
On Tue, 22 May 2007 10:38:58 +0200 "Christian Menzel" christian.menzel@gmail.com wrote:
On 5/21/07, stan stanl@cox.net wrote:
You can check what audacity thinks is the card it is using by going into edit:preferences. There is a selection drop down for play and record separately. Then from a console or terminal type aplay -lLv to see what devices alsa has defined as aliases. Once you know that try aplay -D one of the devices some.wav. Make sure that the speaker out is plugged into the correct jack. The aplay -lLv should also give you the hardware devices. if aplay -D some device alias doesn't work, try aplay -D hwplug:0,0 some.wav, or whichever devices alsa has assigned.
aplay -D <device> seems to think everything is OK and plays the file, but I hear nothing :-(
aplay -D hwplug:0,0 returns an audio open error: No such file or directory, allthough aplay -lLv tells me there is a device 0,0: card 0: Audigy [Audigy 1 [Unknown]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Maybe I have to mknod a device?
The device should have been taken care of by the initial setup of the card. And the two aplay results are contradictory. The device aliases are on top of the hardware plug. So alsa is recognizing the hardware before it creates the device aliases, then not recognizing the hardware. You can try aplay -D hw:0,0 as a long shot, but it sounds to me like there is something very wrong. I'm not an expert in this by any stretch of the imagination; at this point I would ask on the alsa-devel list at http://www.alsa-project.org. Technically, you should ask on the alsa-user list, but that seems to have low traffic and sound is so complicated the devel list is better.
Good luck.
My past experience indicates that alsa keeps some internal state information that can wreak havoc while having problems. And did you remove any .asoundrc in ~/home or asound.state or asound.conf in /etc before you removed the card and plugged it back in? That could cause problems also.
I don't have a local .asoundrc. The files in /etc were deleted.
Regards Chris
"Christian Menzel" christian.menzel@gmail.com wrote:
On 5/21/07, stan stanl@cox.net wrote:
You can check what audacity thinks is the card it is using by going into edit:preferences. There is a selection drop down for play and record separately. Then from a console or terminal type aplay -lLv to see what devices alsa has defined as aliases. Once you know that try aplay -D one of the devices some.wav. Make sure that the speaker out is plugged into the correct jack. The aplay -lLv should also give you the hardware devices. if aplay -D some device alias doesn't work, try aplay -D hwplug:0,0 some.wav, or whichever devices alsa has assigned.
aplay -D <device> seems to think everything is OK and plays the file, but I hear nothing :-(
aplay -D hwplug:0,0 returns an audio open error: No such file or directory, allthough aplay -lLv tells me there is a device 0,0: card 0: Audigy [Audigy 1 [Unknown]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Maybe I have to mknod a device?
With udev, you should never have to manually make a device node. If you do create one, it will not survive a reboot.
Now, as far as the the aplay error message, for some reason the rc1 release of ALSA is missing some files, or has them in the wrong place. It works fine on my desktop, but I had to build my own copy of rc3 for my laptop because I was getting the same type of error message. I was going to file a bug report, but because it was fixed in the later version, I figured it would show up as another update. I guess it didn't...
Mikkel
On 5/18/07, Christian Menzel christian.menzel@gmail.com wrote:
Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything. I get no error messages from the audio applications like xmms or mplayer when I try to play audio. They show the normal behaviour, I just don't hear anything.
The soundcard is OK, when I boot Knoppix from DVD, sound is working
The mixer is not muted, system-config-soundcard won't help, the modules are loaded.
Is there any configuration I can reset? Or should I just wait for FC7 and reinstall the whole stuff? I'm desperate...
Chris
In this month's mailing list archive look up "FYI: ISA Soundcards no longer supported". You may not have an ISA soundcard but the fix offered might work for you.
On Fri, 2007-05-18 at 10:31 -0700, Kam Leo wrote:
In this month's mailing list archive look up "FYI: ISA Soundcards no longer supported". You may not have an ISA soundcard but
Some on-board chipsets are done as if they were an ISA card. Granted that tends to be older motherboards, but it's still something to watch for.
Christian Menzel wrote, On 05/18/2007 11:11 AM:
Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything.
<snip>
Just for record, my AC97 onboard sound just stopped while listening to a Real Player stream. Had been working previously with no problems. Did nothing to stop sound such as playing with mixer, updating stuff, etc. Reboot did not help. Finally this "fixed" it:
In kde ctrl panel, set hardware from autodetect to oss get error about /dev/dvd not present. Test sound fails. Set to hardware to alsa. Test sound works again! Set back to autodetect. Test sounds still works.
Must be a bug somewhere, but who knows.
-gene
I always set that setting to ALSA and keep it there - haven't had many problems with that config. All programs that have a setting for it, I also set to ALSA.
Gene Smith wrote:
Christian Menzel wrote, On 05/18/2007 11:11 AM:
Hi,
The sound in my FC6 installation was workings since I installed it in Oct 2006. Now it suddenly stopped working and I'm not aware of changing anything.
<snip>
Just for record, my AC97 onboard sound just stopped while listening to a Real Player stream. Had been working previously with no problems. Did nothing to stop sound such as playing with mixer, updating stuff, etc. Reboot did not help. Finally this "fixed" it:
In kde ctrl panel, set hardware from autodetect to oss get error about /dev/dvd not present. Test sound fails. Set to hardware to alsa. Test sound works again! Set back to autodetect. Test sounds still works.
Must be a bug somewhere, but who knows.
-gene
-
Christian Menzel -
Gene Heskett -
Gene Smith -
Kam Leo -
Konstantin Svist -
Mikkel -
Nigel Henry -
Ric Moore -
stan -
Tim