|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Hardware Questions about drivers, peripheral cabling, configuration |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
||||
|
__________________
Box: Fedora 11 | (KDE4.3.2) | M2N4-SLI | AMD 64 X2 5200+ | nVidia 8500GT | 4GB RAM Lap: openSUSE 11.2 | Celeron 550 | (KDE4.3.3)"3" | Intel 965 GM | Lenovo R61e | 3GB RAM |
|
||||
|
Quote:
I note KDE-4.1, ... pardon the silly question, but have you discovered yet on KDE-4.1 that you can add extra controls/channels on your mixer via menu controls in kmix ? Aside from that, to progress further I would need a lot of detail, and its possible I still can't help. Still, if you are confident you have added the necessary controls to your mixer, can you then run a diagnostic script and some other command commands? Specifically, with your PC connected to the internet, run twice in a terminal: /usr/sbin/alsa-info.shthe first time run that with root permissions and select YES to the question do you wish to update? You need root permissions so the update to /usr/sbin directory can take place. The second time run it as a regular user, and select the SHARE/UPLOAD option. When the diagnostic script is complete, it will upload diagnostic information to the alsa web site and it will give you a URL. Please post that URL here. Just the URL. Then please also run the following in a terminal (and post here the output): rpm -qa '*alsa*' |
|
||||
|
OK. first, I have all the channels available open. all of them!
second. here is teh link for the alsa script. http://www.alsa-project.org/db/?f=d2...40fbc9e355ce60 here is are the outputs for the commands requested. Code:
cj:/home/fcj # rpm -qa '*alsa*' alsa-1.0.18-8.12.1 kalsatools-1.5.0-499.130 alsa-oss-1.0.17-1.37 alsa-utils-1.0.18-6.4 alsa-plugins-pulse-1.0.18-6.12 alsa-devel-1.0.18-8.12.1 gmerlin-alsamixer-0.4.1-0.pm.5.1 alsa-firmware-1.0.17-1.42 alsa-tools-1.0.18-1.13 alsa-plugins-1.0.18-6.12 alsa-tools-gui-1.0.18-1.13 Code:
fcj:/home/fcj # rpm -qa '*pulse*' pulseaudio-module-zeroconf-0.9.14-2.2.1 pulseaudio-lang-0.9.14-2.2.1 libxine1-pulse-1.1.16.3-2.pm.6.10 pulseaudio-0.9.14-2.2.1 alsa-plugins-pulse-1.0.18-6.12 pulseaudio-module-jack-0.9.14-2.2.1 libpulse0-0.9.14-2.2.1 pulseaudio-module-lirc-0.9.14-2.2.1 libpulse-browse0-0.9.14-2.2.1 libpulse-mainloop-glib0-0.9.14-2.2.1 pulseaudio-utils-0.9.14-2.2.1 pulseaudio-module-bluetooth-0.9.14-2.2.1 pulseaudio-esound-compat-0.9.14-2.2.1 vlc-aout-pulse-1.0.2-2.6 pulseaudio-module-x11-0.9.14-2.2.1 pulseaudio-module-gconf-0.9.14-2.2.1 Code:
fcj:/home/fcj # rpm -q libasound2 libasound2-1.0.18-8.12.1 Code:
fcj:/home/fcj # uname -a Linux fcj 2.6.27.29-0.1-pae #1 SMP 2009-08-15 17:53:59 +0200 i686 i686 i386 GNU/Linux Code:
fcj:/home/fcj # cat /etc/modprobe.d/sound options snd slots=snd-hda-intel,snd-hda-intel # u1Nb.PA+KAPLQWwF:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel # NXNs.UiE7Hare5X3:RV730XT Audio device [Radeon HD 4670] alias snd-card-1 snd-hda-intel
|
|
||||
|
OK, thanks, I note from the script output your PC has a 32-bit openSUSE-11.1 with 1.0.17/1.0.18 of alsa.
The output of the various rpm commands indicated that setup is an ok "stock" setup and has not been mistakenly altered. I see that 4 sound devices are detected, two of which are USB devices. I assume the HDMI deivces is part of the hardware associated with the HDA-Intel (a STAC9271D). Code:
!!Soundcards recognised by ALSA
!!-----------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xe0420000 irq 22
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe0310000 irq 17
2 [USX2Y ]: USB US-X2Y - TASCAM US-X2Y
TASCAM US-X2Y (1604:8007 if 0 at 002/002)
3 [camera ]: USB-Audio - USB camera
USB camera at usb-0000:00:1a.1-1, full speed
Code:
**** List of CAPTURE Hardware Devices **** card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] card 2: USX2Y [TASCAM US-X2Y], device 0: US-X2Y Audio [US-X2Y Audio #0] card 3: camera [USB camera], device 0: USB Audio [USB Audio] If you are trying to capture via a "line in" input, as caf4926 suggested you need to setup the mixer to open the necessary channgels (although his image did not show it). I also believe you need to setup your mixer better. The diagnostic script output suggests it is set to NOT allow any line in, which is not what you want I believe. Please note the following from the script output: !!Amixer outputI do not have your PC's hardware, nor any experience with it, but the above does suggest a misconfiguration to me. I highlighted in RED what could be mistakes, where anyone in the wrong configuration might cause a problem. In all cases but one, capture is set to zero to ensure NO capture. In all cases the switches are set to "Mic" and not one to "Line". Hence Line will not function. I believe you need to set "Line" in an appropriate control and also set "capture" in the corresponding control up to a reasonably high % for capture. And you need to identify on your hardware which mixer control corresponds to what physical input. Now mixer controls for other two are slim and I assume they are not relevant to this problem: !!-------Mixer controls for card 2 [USX2Y] !!-------Mixer controls for card 3 [camera]I also searched the alsa web site for the stac9271d to see if there were any pressing updates in alsa for it, but obtained no indications of updates for the stac9271d nor stac9271. I did get a general "hit" for the stac92xx, with a couple of recent updates, but the descriptions suggest to me this may not be relevant to your PC's stac9271D: Search results - AlsaProject Hence for now I recommend you stick with alsa-1.0.17/1.0.18. |
|
||||
|
I have played with all the channels in order to capture the sound coming to "line in" and I have been able to do it. I know it is not a hardware problem because when I set the right configuration in the mixer I'm able to capture the sound and record it.
The problem is that the channel that loops the sound from the "line in" to the "line out" is no longer in the mixer. so even though the pc receives the sound in the "line in" I'm unable to hear it through the speakers. Is there a way to manually add another channel to the mixer?
|
|
||||
|
Quote:
All that I was able to see in your previous setup was you had one input set to microphone with a 64% capture (but its mixer mux setting set to zero- which may be what gives NO audio at the same time as record - I'm guessing here), and the remainder set to microphone with no capture, nor any mixer mux setting. Did you try to adjust those mux capture settings? Were you trying to treat the line-in as a mic to get audio at the same time as record that way? If playing with your mixer settings does not solve this, then its not likely I can solve it. You could try updating to 1.0.21 of alsa (guidance here: Alsa-update - openSUSE ) being certain to fully read that guide and to send all 6 zypper commands, and modify the 2nd zypper command to update all your alsa and not just alsa, alsa-docs and libasound2. And ensure your CD as a repository is disabled in your software package manager and ensure that OSS repos do not have a higher priority. My view is that will not help, but I do not know this (only speculate). In KDE4, in kmix, there is a menu item in which more mixers can be added. But only those mixers that are within that menu (and not yet selected) can be added. Failing the above, you could try the bug report route, noting you lost a feature of this in the recent 1.0.17/1.0.18 alsa updates in 11.1. Guidance for wrtting bug reports is here: Submitting Bug Reports - openSUSE Be certain to raise this bug report against component "sound". |
|
||||
|
Ok, first of all, thanks for the effort to help. I updated the alsa driver and still did not work, so since I remember it worked when OPENsuse was freshly installed, I decided to look what changes were made after the fresh install. I ran the OPENsuse KDE 4.1 live cd and checked the mixer, and there it was. In the channels that could be added to the mixer, there was one called "analog loopback" which has the setting to just turn it on and of. As soon as I turned it on, there it was the sound from my satellite receiver, connected to the "line in".
So I went back to my regular kde and tried to downgrade the alsa driver to the original in the cd. I was able to do it, and the sound still works fine, but that channel "analog loopback" is not available anymore. do you think it was something that was changed in a kernel update? that's the only thing I can think of! any help would be greatly appreciated!
|
|
||||
|
Quote:
More likely the alsa version. Write a bug report on this, and explain what you just did. |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|