Hi,
This is in a way a continuation of the problem from this thread http://forums.fedoraforum.org/showthread.php?t=284414 but there's some new info.
After uninstalling PulseAudio it would appear that ALSA does very bad job at identifying devices. In particular, it identifies a microphone of the webcam as an output device. Or at least this is what I could infer from running alsamixer (it lists the webcam as a device it is outputting to, hance no playback device).
Beside the obvious stupidity of the situation, is there anything that I can do to:
1. Cofigure and prevent ALSA from further re-configuration?
2. Deliberately restart ALSA without restarting the OS?
Some more info:
kmix and system sound settings appear as in no relevance to what and how ALSa functions. It took me very long time to understand that the pictures they show are absolutely disconnected from what really happens... fun stuff here...
I was looking online for where would ALSA save its configuration files or how would it name its service - I could not find any up to date information on the subject. Most info out there on the internet dates back to 2007-ish, and there's nothing even somewhat similar on my system.
All help is welcome!
EDIT
Here's the output form alsa-info.sh http://pastebin.com/LeE0RWRe it is too large to post it here.
And some more info, just in case:
EDIT2:
http://www.redhat.com/archives/rhl-l.../msg03054.html is this seriously true? Is there really no other way to restart this piece of junk, only log in/out?
This is in a way a continuation of the problem from this thread http://forums.fedoraforum.org/showthread.php?t=284414 but there's some new info.
After uninstalling PulseAudio it would appear that ALSA does very bad job at identifying devices. In particular, it identifies a microphone of the webcam as an output device. Or at least this is what I could infer from running alsamixer (it lists the webcam as a device it is outputting to, hance no playback device).
Beside the obvious stupidity of the situation, is there anything that I can do to:
1. Cofigure and prevent ALSA from further re-configuration?
2. Deliberately restart ALSA without restarting the OS?
Some more info:
kmix and system sound settings appear as in no relevance to what and how ALSa functions. It took me very long time to understand that the pictures they show are absolutely disconnected from what really happens... fun stuff here...
I was looking online for where would ALSA save its configuration files or how would it name its service - I could not find any up to date information on the subject. Most info out there on the internet dates back to 2007-ish, and there's nothing even somewhat similar on my system.
All help is welcome!
EDIT
Here's the output form alsa-info.sh http://pastebin.com/LeE0RWRe it is too large to post it here.
And some more info, just in case:
Code:
[wvxvw@wvxvw-desktop ~]$ cat /proc/asound/cards
0 [Q9000 ]: USB-Audio - QuickCam Pro 9000
Logitech, Inc. QuickCam Pro 9000 at usb-0000:02:00.0-2.2, high speed
1 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfbff4000 irq 56
2 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfb7fc000 irq 57
[wvxvw@wvxvw-desktop ~]$ cat /proc/asound/devices
1: : sequencer
2: [ 0- 0]: digital audio capture
3: [ 0] : control
4: [ 1- 2]: digital audio capture
5: [ 1- 1]: digital audio playback
6: [ 1- 1]: digital audio capture
7: [ 1- 0]: digital audio playback
8: [ 1- 0]: digital audio capture
9: [ 1- 2]: hardware dependent
10: [ 1] : control
11: [ 2-11]: digital audio playback
12: [ 2-10]: digital audio playback
13: [ 2- 9]: digital audio playback
14: [ 2- 8]: digital audio playback
15: [ 2- 7]: digital audio playback
16: [ 2- 3]: digital audio playback
17: [ 2- 0]: hardware dependent
18: [ 2] : control
33: : timer
[wvxvw@wvxvw-desktop ~]$http://www.redhat.com/archives/rhl-l.../msg03054.html is this seriously true? Is there really no other way to restart this piece of junk, only log in/out?