Hi, my sister has MS-1221 (PR200) laptop that I need to fix for her so that Skype works.
The issues were - webcam didn't work - audio didn't work on skype
I installed 2.6.31 kernel - that fixed webcam issue now cheese and skype, cheese and other apps worked ok with webcam.
After installing new Skype 2.1 beta sound didn't work until I disabled in skype "Allow Skype to automatically adjust my mixer levels", after that it worked without problems.
Then I tried using skype (and other audio recording applications on Fedora) but couldn't record audio from internal microphone, but when I connected external microphone audio recording (and skype) worked.
So I had everything working ok, except that I couldn't record from internal microphone, which wasn't such a big issue, but I still wanted to try and fix it.
I googled around and tried a few parameters for snd-hda-intel module, by issuing "rmmod snd-hda-intel -f" and then loading module with different options. Whatever I tried internal microphone still didn't work, but that was acceptable.
I was doing all configuration while in Gnome, and now I had working audio and video for skype, and also working audio recording (via external mic) and working webcam for cheese, skype and other applications that use webcam.
Then I switched into KDE, without restart, just log off and login to KDE. KDE immediately popped up a window saying: KDE detected that one or more internal sound devices were removed: * Output: HDA Intel, INTEL HDMI (HDMI Audio Output)
And now sound was gone!
I tried reloading snd-hda-intel module, logging back to gnome, restarting... nothing!
There is absolutely no sound output!
Now can I troubleshoot and fix this?
Why and how can KDE interfere with PulseAudio so much that it also messes up sound in Gnome?!?
This has really pissed me off! And I returned laptop to my sister in worst state than she game it to me :(
Any suggestions are more than welcome, so please give any suggestions you have.
Also if you need more info just tell me what do you need.
Cheers!
Here is some extra info:
Smolt profile for laptop: http://www.smolts.org/client/show/pub_2eb97796-1ebc-46e9-933a-6d53dfb00749
lspci: http://www.fpaste.org/M7Og
/etc/modprobe.d/dist.conf (modprobe.conf is depracated) http://www.fpaste.org/EG6U/
by default the options file isn't commented, but I tried both ways, and it is the same: alias char-major-116-* snd alias sound-service-*-0 snd-mixer-oss #options snd-hda-intel model=laptop-eapd probe_mask=1
Valent Turkovic wrote:
Then I switched into KDE, without restart, just log off and login to KDE. KDE immediately popped up a window saying: KDE detected that one or more internal sound devices were removed:
- Output: HDA Intel, INTEL HDMI (HDMI Audio Output)
And now sound was gone!
KDE didn't eat anything, it just detected that the device is no longer available at the ALSA level. You're shooting the messenger. I have no idea why the device vanished from ALSA.
Kevin Kofler
On Sat, 05 Sep 2009 20:40:53 +0200, Kevin Kofler wrote:
KDE didn't eat anything, it just detected that the device is no longer available at the ALSA level. You're shooting the messenger. I have no idea why the device vanished from ALSA.
Thank you for the info. But there is some connection between ALSA and KDE because sound worked fine UNTIL I logged to KDE.
Any ideas why ALSA went crazy when I logged into KDE?
2009/9/6 Valent Turkovic valent.turkovic@gmail.com:
On Sat, 05 Sep 2009 20:40:53 +0200, Kevin Kofler wrote:
KDE didn't eat anything, it just detected that the device is no longer available at the ALSA level. You're shooting the messenger. I have no idea why the device vanished from ALSA.
Thank you for the info. But there is some connection between ALSA and KDE because sound worked fine UNTIL I logged to KDE.
Any ideas why ALSA went crazy when I logged into KDE?
What i see here since my last reboot (today after 5 days uptime) is:
http://img137.imageshack.us/i/soundremove.png/
On Mon, 07 Sep 2009 11:28:25 +0200, Thomas Janssen wrote:
What i see here since my last reboot (today after 5 days uptime) is:
And have you been tampering with sound system like I did or did ALSA/KDE just went bonkers by them selves?
2009/9/7 Valent Turkovic valent.turkovic@gmail.com:
On Mon, 07 Sep 2009 11:28:25 +0200, Thomas Janssen wrote:
What i see here since my last reboot (today after 5 days uptime) is:
And have you been tampering with sound system like I did or did ALSA/KDE just went bonkers by them selves?
It did it on its own. Only rebooting the box.
On Mon, 07 Sep 2009 15:53:32 +0200, Thomas Janssen wrote:
It did it on its own. Only rebooting the box.
And will now others say again that this has nothing to do with KDE?!?
Come on guys, help su troubleshoot and find why is this issue happening.
On Mon, Sep 7, 2009 at 22:29, Valent Turkovicvalent.turkovic@gmail.com wrote:
On Mon, 07 Sep 2009 15:53:32 +0200, Thomas Janssen wrote:
It did it on its own. Only rebooting the box.
And will now others say again that this has nothing to do with KDE?!?
Come on guys, help su troubleshoot and find why is this issue happening.
I am not saying that it is not KDE since i don't know enough about the underlying system but from my limited knowledge it seems pretty unlikely. Also from experience i can say that the KDE guys as a whole are pretty good at knowing these things. Before you start insisting the blame lies completely with KDE have you considered other possibilities that are just as likely such as other updates that may have been run along with KDE and bugs in them were triggered by rebooting or similar. Kernel updates for instance have often caused this kind of issue with me where the kernel doesn't detect the sound card properly, therefore neither can pulseaudio and then KDE throws up the message. Unless you understand the issue properly don't throw wild accusations around.
On Mon, 07 Sep 2009 22:38:25 +0100, John5342 wrote:
Before you start insisting the blame lies completely with KDE have you considered other possibilities that are just as likely such as other updates that may have been run along with KDE and bugs in them were triggered by rebooting or similar. Kernel updates for instance have often caused this kind of issue with me where the kernel doesn't detect the sound card properly, therefore neither can pulseaudio and then KDE throws up the message. Unless you understand the issue properly don't throw wild accusations around.
Agreed, I'm not 100% sure that KDE is to blame, but I updated everything, rebooted, logged int gnome, sound worked, I player with removing and reloading audio module. Sound worked fine in Gnome. I logged to KDE, got the message and sound stopped working both in KDE and in Gnome.
That is why I made slightly comical title "KDE ate my sound card" and not "F*CK KDE, it killed my sound" or something similar.
I'm just interested how to get sound back working again, any tips/tricks or suggestion are more than welcome, and I'll share back what I found out about this issue. So hopefully other users don't get bitten with by same situation.
On 09/08/2009 09:19 AM, Valent Turkovic wrote:
On Mon, 07 Sep 2009 22:38:25 +0100, John5342 wrote:
Before you start insisting the blame lies completely with KDE have you considered other possibilities that are just as likely such as other updates that may have been run along with KDE and bugs in them were triggered by rebooting or similar. Kernel updates for instance have often caused this kind of issue with me where the kernel doesn't detect the sound card properly, therefore neither can pulseaudio and then KDE throws up the message. Unless you understand the issue properly don't throw wild accusations around.
Agreed, I'm not 100% sure that KDE is to blame, but I updated everything, rebooted, logged int gnome, sound worked, I player with removing and reloading audio module. Sound worked fine in Gnome. I logged to KDE, got the message and sound stopped working both in KDE and in Gnome.
That is why I made slightly comical title "KDE ate my sound card" and not "F*CK KDE, it killed my sound" or something similar.
I'm just interested how to get sound back working again, any tips/tricks or suggestion are more than welcome, and I'll share back what I found out about this issue. So hopefully other users don't get bitten with by same situation.
What sound devices are listed in KDE?
On Tue, Sep 8, 2009 at 14:55, Timothy Murphygayleard@eircom.net wrote:
Patrick Boutilier wrote:
What sound devices are listed in KDE?
How do you "list sound devices in KDE" ?
System Settings -> Multimedia
On Tue, 08 Sep 2009 09:31:19 -0300, Patrick Boutilier wrote:
What sound devices are listed in KDE?begin:vcard
Here they are: http://bayimg.com/image/dadcmaacn.jpg
My sister was away so sorry for the delay.
On 09/09/2009 06:01 PM, Valent Turkovic wrote:
On Tue, 08 Sep 2009 09:31:19 -0300, Patrick Boutilier wrote:
What sound devices are listed in KDE?begin:vcard
Here they are: http://bayimg.com/image/dadcmaacn.jpg
My sister was away so sorry for the delay.
Do any of the listed devices work when you try the test button?
On Wed, 09 Sep 2009 18:56:15 -0300, Patrick Boutilier wrote:
Do any of the listed devices work when you try the test button?
Only one working is "HDA Intel (ALC880 Analog)"
Other ones aren't working :(
Valent Turkovic wrote:
On Mon, 07 Sep 2009 15:53:32 +0200, Thomas Janssen wrote:
It did it on its own. Only rebooting the box.
And will now others say again that this has nothing to do with KDE?!?
Come on guys, help su troubleshoot and find why is this issue happening.
What sound devices are listed in KDE?
On Mon, Sep 07, 2009 at 03:53:32PM +0200, Thomas Janssen wrote:
What i see here since my last reboot (today after 5 days uptime) is: http://img137.imageshack.us/i/soundremove.png/
And have you been tampering with sound system like I did or did ALSA/KDE just went bonkers by them selves?
It did it on its own. Only rebooting the box.
No kernel/alsa-update between that reboot and the previous one?
Do you actually use hdmi audio?
2009/9/7 Sven Lankes sven@lank.es:
On Mon, Sep 07, 2009 at 03:53:32PM +0200, Thomas Janssen wrote:
What i see here since my last reboot (today after 5 days uptime) is: http://img137.imageshack.us/i/soundremove.png/
And have you been tampering with sound system like I did or did ALSA/KDE just went bonkers by them selves?
It did it on its own. Only rebooting the box.
No kernel/alsa-update between that reboot and the previous one?
Yep, there were updates: Sep 06 23:38:49 Updated: alsa-lib-1.0.21-1.fc10.x86_64
Kernel in use since a long time (due to broken sound and flaky wifi in kernel-2.6.29.6-99.fc10.x86_64) kernel-2.6.27.30-170.2.82.fc10.x86_64
Do you actually use hdmi audio?
I have two soundcards. Intel HDA and the ATI one. I use the Intel. 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 01:00.1 Audio device: ATI Technologies Inc RV635 Audio device [Radeon HD 3600 Series]
On Tue, Sep 08, 2009 at 10:15:07AM +0200, Thomas Janssen wrote:
It did it on its own. Only rebooting the box.
No kernel/alsa-update between that reboot and the previous one?
Yep, there were updates: Sep 06 23:38:49 Updated: alsa-lib-1.0.21-1.fc10.x86_64 Kernel in use since a long time (due to broken sound and flaky wifi in kernel-2.6.29.6-99.fc10.x86_64) kernel-2.6.27.30-170.2.82.fc10.x86_64
Ok - so this doesn't look like a kde issue at all then and as Kevin said earlier KDE is only the messenger here.
Running diverging alsa-kernel and alsa-utils/lib-parts is probably not tested at all so it might be broken in many ways.
2009/9/8 Sven Lankes sven@lank.es:
On Tue, Sep 08, 2009 at 10:15:07AM +0200, Thomas Janssen wrote:
It did it on its own. Only rebooting the box.
No kernel/alsa-update between that reboot and the previous one?
Yep, there were updates: Sep 06 23:38:49 Updated: alsa-lib-1.0.21-1.fc10.x86_64 Kernel in use since a long time (due to broken sound and flaky wifi in kernel-2.6.29.6-99.fc10.x86_64) kernel-2.6.27.30-170.2.82.fc10.x86_64
Ok - so this doesn't look like a kde issue at all then and as Kevin said earlier KDE is only the messenger here.
Running diverging alsa-kernel and alsa-utils/lib-parts is probably not tested at all so it might be broken in many ways.
Well, that alsa-lib update should be tested with the 2.6.27 kernel, since the 2.6.29 one is from updates-testing. I have that kernel for catalyst testing and of course for general testing purposes.
But of course it might be. The alsa-lib was pushed to updates, so maybe we will see some more with interesting sound behavior. Or KDE suggestions as in my case.
2009/9/8 Thomas Janssen thomasj@fedoraproject.org:
2009/9/8 Sven Lankes sven@lank.es:
On Tue, Sep 08, 2009 at 10:15:07AM +0200, Thomas Janssen wrote:
It did it on its own. Only rebooting the box.
No kernel/alsa-update between that reboot and the previous one?
Yep, there were updates: Sep 06 23:38:49 Updated: alsa-lib-1.0.21-1.fc10.x86_64 Kernel in use since a long time (due to broken sound and flaky wifi in kernel-2.6.29.6-99.fc10.x86_64) kernel-2.6.27.30-170.2.82.fc10.x86_64
Ok - so this doesn't look like a kde issue at all then and as Kevin said earlier KDE is only the messenger here.
Running diverging alsa-kernel and alsa-utils/lib-parts is probably not tested at all so it might be broken in many ways.
Well, that alsa-lib update should be tested with the 2.6.27 kernel, since the 2.6.29 one is from updates-testing. I have that kernel for catalyst testing and of course for general testing purposes.
But of course it might be. The alsa-lib was pushed to updates, so maybe we will see some more with interesting sound behavior. Or KDE suggestions as in my case.
Right now updated from updates-testing again. Alsa-lib was updated (and complete KDE to 4.3.1). And right after alsa-lib update was done i got the same popup as posted earlier.
Valent Turkovic wrote:
Then I switched into KDE, without restart, just log off and login to KDE. KDE immediately popped up a window saying: KDE detected that one or more internal sound devices were removed:
- Output: HDA Intel, INTEL HDMI (HDMI Audio Output)
And now sound was gone!
Your problem is probably: https://bugzilla.redhat.com/show_bug.cgi?id=521988
It should be fixed in alsa-lib-1.0.21-2.fc10/3.fc11/3.fc12 which just got pushed to the F10/F11 stable updates 2 days ago.
Kevin Kofler