Hello, A few months ago I installed a graphic card GeForce GTX 1050 Ti/PCIe/SSE2 : dkms status nvidia-current, 460.80-1.mga8.nonfree, 5.10.37-desktop-2.mga8, x86_64: installed nvidia-current, 460.80-1.mga8.nonfree, 5.10.33-desktop-1.mga8, x86_64: installed all seems OK, but when I tried to record audio, that didn't work. I had no problems with recording audio before. draksound said my sound card is "NVIDIA Corporation GP107 High Definition Audio Controller" : that's false, my usual sound card is the built-in "8 Series/C220 Series Chipset High Definition Audio Controller". The NVidia sound capabilities are only numerical outputs while my computer uses analog inputs/outputs. I can't change for the good one. Both "NVidia GP107" and "8 series/C220" using snd_hda_intel as pilot A post about this problme on MLO forum (in french) https://www.mageialinux-online.org/forum/topic-28789+diagnostiquer-le-systeme-audio-e.php but we haven't found the solution.
Thank you for the report, and sorry for your angst. That post is very long, but informative. From it, the essential seems to be that the unwanted video card sound (!) "NVIDIA Corporation GP107 High Definition Audio Controller" takes precedence over the desired one "8 Series/C220 Series Chipset High Definition Audio Controller", and is always *the* visible & active card. It cannot be disactivated, and the wanted one cannot be selected. The problem seems to be the order in which the two are taken on board by the system ; and changing this order. To summarise the audio hardware, please post the O/P of: $ inxi -A++ One comment notes that this problem is 'since kernel 5.10'. I was unclear about the post 16/04/2021 à 12h46 and the exact file modified /etc/modprobe.d/modprobe.conf ? 01_mga-config.conf adding "options snd-hda-intel index=1,0" to the relevant line ; and whether that changed anything. And did you try 'index=0,1' ? And whether using 'audio-recorder' worked when (for sound) 'kazam' does not.
Status: NEW => NEEDINFOCC: (none) => lewyssmith
Thank you for this long reading ;) We agree about the problem. I'm not using this computer now so I'll do the tests on monday ( $ inxi -A, try 'index=0,1', testing audio-recorder and kazam) > I was unclear about the post 16/04/2021 à 12h46 There is a mistake in this post. The post 17/04/2021 à 19h49 @nic80 shows the correct handling : as the result, the NVidia card disappeared in pavucontrol, alsamixer and "$ cat /proc/asound/cards", but draksound still display it.
Just to note that there is another bug 29032 about Kazam re microphone, with a correction to /usr/lib/python3.8/dist-packages/kazam/pulseaudio/pulseaudio.py I do not think it is relevant, but two bugs stemming from Kazam...
Oki. > To summarise the audio hardware, please post the O/P of: > $ inxi -A++ -A++ doesn't work, I used -A $ inxi -A Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel Device-3: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder driver: saa7134 Sound Server: ALSA v: k5.10.37-desktop-2.mga8 > And whether using 'audio-recorder' worked when (for sound) 'kazam' does not. audio-recorder 2.2.3 works. After a few seconds its windows appears. When I click on "Débuter l'enregistrement" (start recording) the shell shows : "(audio-recorder:303957): GLib-GObject-CRITICAL **: 22:06:18.658: g_object_unref: assertion 'G_IS_OBJECT (object)' failed" but audio file is created whith correct sound datas in it. kazam searches an audio devices : $ kazam /usr/lib/python3.8/site-packages/kazam/frontend/indicator.py:150: PyGIWarning: AyatanaAppIndicator3 was imported without specifying a version first. Use gi.require_version('AyatanaAppIndicator3', '0.1') before import to ensure that the right version gets loaded. from gi.repository import AyatanaAppIndicator3 as AppIndicator3 /usr/lib/python3.8/site-packages/kazam/app.py:145: Warning: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize' self.builder.add_from_file(os.path.join(prefs.datadir, "ui", "kazam.ui")) (kazam:313806): Gtk-WARNING **: 22:31:13.121: Can't set a parent on widget which has a parent (kazam:313806): Gtk-WARNING **: 22:31:13.124: Can't set a parent on widget which has a parent WARNING Prefs - Unable to find any audio devices. WARNING Main - It appears that speakers audio source isn't set up correctly. No Audio but Video capture is OK. When I go to Fichier/Preferences (Files/Prefs) the shell says : Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/kazam/frontend/preferences.py", line 256, in cb_audio2_changed pa_audio2_idx = prefs.mic_sources[prefs.audio2_source][0] IndexError: list index out of range > did you try 'index=0,1' ? alsamixer shows NVidia's audio channels using procedure in the post 17/04/2021 à 19h49 @nic80, adding 'options snd-hda-intel enable' in 00_modprobe.conf : 'index=0,1' $ cat /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17 1 [SAA7134 ]: SAA7134 - SAA7134 saa7133[0] at 0xf7100000 irq 16 'index=1,0' $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7310000 irq 33 1 [SAA7134 ]: SAA7134 - SAA7134 saa7133[0] at 0xf7100000 irq 16
Thank you for the extra information & tests. > -A++ doesn't work, I used -A My fault! It should have been -Axx Interesting that inxi shows the '8 Series/C220 Series' before the 'NVIDIA GP107GL'. Was this before or after the 'correct' index parameter (below) ? > 'index=1,0' > $ cat /proc/asound/cards > 0 [PCH ]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xf7310000 irq 33 > 1 [SAA7134 ]: SAA7134 - SAA7134 > saa7133[0] at 0xf7100000 irq 16 Is this not what you hope for - the 'PCH' card ? (The different ways of identifying which audio device is which certainly complicates explanations). See final questions. > The post 17/04/2021 à 19h49 @nic80 shows the correct handling > après modification du fichier /etc/modprobe.d/00_modprobe.conf > par ajout de "options snd-hda-intel enable=1,0" Some things say "index=1,0", others "enable=1,0". ------------------------------------------------- It seems that when you got it right, most things work. In this situation, can you please summarise (because different info is now scattered all over the place) : * BEFORE the magic modification, what applications found & used or showed the correct (PCH) or incorrect (NVidia) sound card : cat /proc/asound/cards, gnome-sound-recorder, kazam, draksound, other sound utilities you use, like pavucontrol. * exactly what modification, and where, did the trick * AFTER the mod, what applications find & use or show the correct (PCH) sound card : cat /proc/asound/cards, gnome-sound-recorder, kazam, draksound, other sound utilities you use, like pavucontrol. Sorry for asking for this recapitulation, but it is to help pin down where the original problem lay. It has become difficult to see the essential among the diverse bits of evidence.
> Sorry for asking for this recapitulation Don't worry that's not a problem, I work about this recapitulation but it is too early for writing results in this comment. > It should have been -Axx That works ! Many inxi -Axx below. >> 'index=1,0' >> $ cat /proc/asound/cards >> 0 [PCH ]: HDA-Intel - HDA Intel PCH >> HDA Intel PCH at 0xf7310000 irq 33 >> 1 [SAA7134 ]: SAA7134 - SAA7134 >> saa7133[0] at 0xf7100000 irq 16 >Is this not what you hope for - the 'PCH' card ? Yes, this is the 'PCH' card I want to use. > The post 17/04/2021 à 19h49 @nic80 shows the correct handling > après modification du fichier /etc/modprobe.d/00_modprobe.conf > par ajout de "options snd-hda-intel enable=1,0" > Some things say "index=1,0", others "enable=1,0". > ------------------------------------------------- Yes, "index" is not in "options snd-hda-intel enable=1,0", I don't know why I wanted to use it. Maybe I didn't understand what you mean about 'did you try 'index=0,1' ?' However I redo the tests and I found the same results as at the end of Comment 4, so I used the correct syntax in the 00_modprobe.conf. Here is a better presentation with more datas : ** 00_modprobe.conf without any line 'options snd-hda-intel enable=': $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7310000 irq 33 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17 2 [SAA7134 ]: SAA7134 - SAA7134 saa7133[0] at 0xf7100000 irq 16 $ inxi -Axx Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 Device-3: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Hauppauge works WinTV HVR-1110 driver: saa7134 v: 0, 2, 17 bus ID: 05:01.0 chip ID: 1131:7133 Sound Server: ALSA v: k5.10.41-desktop-1.mga8 ** 00_modprobe.conf with 'options snd-hda-intel enable=0,1' $ cat /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17 1 [SAA7134 ]: SAA7134 - SAA7134 saa7133[0] at 0xf7100000 irq 16 $ inxi -Axx Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte driver: N/A bus ID: 00:1b.0 chip ID: 8086:8c20 Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 Device-3: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Hauppauge works WinTV HVR-1110 driver: saa7134 v: 0, 2, 17 bus ID: 05:01.0 chip ID: 1131:7133 Sound Server: ALSA v: k5.10.41-desktop-1.mga8 ** 00_modprobe.conf with 'options snd-hda-intel enable=1,0' $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7310000 irq 33 1 [SAA7134 ]: SAA7134 - SAA7134 saa7133[0] at 0xf7100000 irq 16 $ inxi -Axx Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: N/A bus ID: 01:00.1 chip ID: 10de:0fb9 Device-3: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Hauppauge works WinTV HVR-1110 driver: saa7134 v: 0, 2, 17 bus ID: 05:01.0 chip ID: 1131:7133 Sound Server: ALSA v: k5.10.41-desktop-1.mga8
Thank you for repeating all that; which I summarise further (ignoring the Philips SAA7134 device): * inxi always shows Device-1: Intel 8 Series/C220, Device-2: NVIDIA GP107GL 1] With no 'options snd-hda-intel enable=' (normal situation): - /proc/asound/cards shows BOTH cards: 0 PCH, 1 NVidia - inxi shows 'driver: snd_hda_intel' for BOTH cards 2] With 'options snd-hda-intel enable=0,1' : - /proc/asound/cards shows ONLY 0 NVidia card, not the PCH - inxi shows 'driver: N/A' for the Intel/PHC, but 'driver: snd_hda_intel' for the NVidia GP107GL 3] With 'options snd-hda-intel enable=1,0' : - /proc/asound/cards shows ONLY 0 PCH/Intel, not the NVidia - inxi shows 'driver: snd_hda_intel' for the Intel/PCH, but 'driver: N/A' for the NVidia GP107GL Although you referred back to the end of comment 4 for what works or does not: - BEFORE the sucessful modification (case 1 above) - AFTER the sucessful modification (case 3 above) this remains unclear. We can ignore case 2 above (which specifically favours the NVidia card, which you do *not* want!); and gnome-sound-recorder, because that always worked/works. Please clarify the following points from what you already know, rather than re-testing them. The problem areas seem to be: - draksound : does/did not show, or at least enable selection of, the PCH/Intel card; just the NVidia one. Is this still true with the configuration 3. - kazam, recording video but no sound. Is this related to which card it uses ? Does it allow sound card selection? If so, does it offer both? Is its behaviour the same before & after the configuration 3 ? - alsamixer[gui] "shows NVidia's audio channels". Where it should be the PCH/Intel's ? Even after the configuration 3 ? It remains to say definitely whether the problem is just kernel related (goes away with the configuration 3); or application related (remains after the configuration tweak). What exactly does the configuration 3 make work that was wrong previously ? It might help to attach screenshots (which can include a full comment) of, say, draksound and alsamixer[gui] when they are displaying wrong or incomplete information. And say whether it is before and/or after the change 3. A long post - but soliciting a shorter reply.
Note that draksound does not select which sound device is active - that is the job of the sound settings tool that comes with your DE (or alternatively, the DE-agnostic 'pavucontrol' tool). draksound just allows you to set the driver options for each sound device. It does this for each device in turn. On my laptop with both Intel and Nvidia sound devices, it first presents a screen allowing the driver for the Nvidia device to be configured, then, when you click on OK, it presents a screen allowing the driver for the Intel device to be configured. Because both devices use the snd-hda-intel driver, the two screens look very similar, so unless you look closely, you might miss that it has changed to a different device.
CC: (none) => mageia
Created attachment 12753 [details] drakconf - Hardware - Browse and configure hardware - situation 1 Comment 7 drakconf - Hardware - Browse and configure hardware situations 1 : both PCH/intel and NVidia GP107
Created attachment 12754 [details] drakconf - Hardware - Browse and configure hardware - situation 3 Comment 7 drakconf - Hardware - Browse and configure hardware only PCH/Intel
Created attachment 12755 [details] drakconf - Hardware - Sound Configuration Comment 7 drakconf shows always the NVidia Corporation GP107: the card in use is 'Built-in Audio' HDA/Intel
Created attachment 12756 [details] kazam - Preferences - General - Situation 1 and 3 Comment 7 kazam - Preferences - General - Situation 1 and 3 We can adjust the volume but this setting in inoperative, and the combobox is still grey. Loudspeakers work as expected but kazam don't capture their stream
Created attachment 12757 [details] kazam - Preferences - Screencast - Situation 1 and 3 Comment 7 The second kazam setting window Situation 1 et 3
Created attachment 12758 [details] kazam - audio stream exists on the system Comment 7 There is an audio stream generated by Sayonara and transmitted to the speakers
Created attachment 12759 [details] kazam - no audio stream is recorded Comment 7 kazam records video but ignore the audio stream. In pavucontrol, tab 'Recording' says 'No application is currently recording audio'
Created attachment 12760 [details] kazam - pavucontrol configuration Comment 7 Situation 1 : NVidia GP107 and HDA/Intel NVidia is off because the computer doesn't have hdmi devices
Created attachment 12761 [details] kazam - profiles built-in audio Comment 7 The list of Built-in Audio profiles : only outputs are available, duplex and inputs aren't. Before the NVidia graphic card installation, duplex et inputs worked well.
Created attachment 12762 [details] kazam - pavucontrol configuration situation 3 Comment 7 Situation 3 : NVidia doesn't appear, that expected. Nothing changed since situation 1, the audio stream goes to the loudspeakers
Created attachment 12763 [details] drakconf - Hardware - Browse and configure hardware - list of items Comment 8 Each item of the list, when we click on 'run config tool', give access to two windows
Created attachment 12764 [details] drakconf - Hardware - Browse and configure hardware - NVidia window Comment 8 One of the two windows open by 'Run config tool', with limited options...
Created attachment 12765 [details] drakconf - Hardware - Browse and configure hardware - Intel 8 series/C220 window Comment 8 The second window. The only change is the name of audio card : Intel 8series/C220
The attachments didn't work as I expected, I only see it now. I thought they were links like in forums, not comments. Sorry... Let us return to the initial problem. > The problem areas seem to be: > - draksound : does/did not show, or at least enable selection of, > the PCH/Intel card; just the NVidia one. Is this still true with the > configuration 3. In the usual situation (#1) there are both PCH/Intel and NVidia lines when we're looking on 'Hardware - Manage your hardware - Browse and configure your hardware' In situation 3 at the same location, only the lines referring to PCH/Intel are displayed. But in both cases, in 'Hardware - Manage your hardware - Sound Configuration', only the NVidia card is displayed. > - kazam, recording video but no sound. > Is this related to which card it uses ? No. In pavucontrol, only Built-in audio (PCH/Intel) works. NVidia GP107 is off (this is the only choice : all other profiles of this card are 'unplugged', and no equipments use hdmi on my computer) > Does it allow sound card selection? If so, does it offer both? No option in Kazam to select the card in use. > Is its behaviour the same before & after the configuration 3 ? Yes. Both situation 1 and 3 : * options in kazam's preferences are the same and kazam doesn't record audio stream * In pavucontrol, the 'recording' tab says 'No application is currently record audio', even when Kazam records * In drakconf, in 'Hardware - Manage your hardware - Sound Configuration', only the NVidia card is displayed (this is a fact, not a repeat about this point that disturb me a little bit). > - alsamixer[gui] "shows NVidia's audio channels". Where it should be the > PCH/Intel's ? Even after the configuration 3 ? It is only on situation : 2] With 'options snd-hda-intel enable=0,1'. PCH/Intel is disabled, alsamixer shows only NVidia audio channels (and SAA7134), that's normal and expected. Comment 8 : > draksound just allows you to set the driver options for each sound device... > ...Because both devices use the snd-hda-intel driver, the two screens look > very similar, so unless you look closely, you might miss that it has changed > to a different device. I didn't see a difference on my PC. Please look at the screenshots attachments 12763 to 12765. Is it the same on your PC ?
(In reply to Christophe Parigot from comment #22) > Comment 8 : > > draksound just allows you to set the driver options for each sound device... > > ...Because both devices use the snd-hda-intel driver, the two screens look > > very similar, so unless you look closely, you might miss that it has changed > > to a different device. > I didn't see a difference on my PC. Please look at the screenshots > attachments 12763 to 12765. Is it the same on your PC ? As you show, selecting the config tool runs draksound, which allows you to configure all sound cards (one after another), not just the one currently selected in the hardware browser. Yes, that's exactly the behaviour I described in comment 8. It would be nicer if draksound first showed a list of sound cards and allowed you to choose which one(s) you wanted to configure (like drakconnect does for ethernet and WiFi cards), but it doesn't :-(
Thank you very much for commenting, Martin. @Christophe Thank you for all those screenshots! [Did you annotated them with a graphics program like Gimp? Flameshot is a screenshot program that enables on-the-spot annotations, geometric & text, before they are saved. Very handy once you know how to drive it]. The configuration situations 1 (normal, both cards) and 3 (Nvidia card disabled) are reflected in what gets shown. The MCC Hardware list always shows both cards under "Soundcard", but only the finer details of enabled cards. Your comments 19 & 21 and related attachments confirm what Martin describes: draksound "Sound configuration" *does* show the Intel card in turn. Does this not answer your title complaint? Apart from this confusion: > As you show, selecting the config tool runs draksound, which allows you > to configure all sound cards (one after another), not just the one > currently selected in the hardware browser. I think we should close this aspect as being 'understood how it functions'. That could be an enhancement bug. --------------------------------- I think this bug - what really troubles you - is about Kazam not recording sound when you have more than one sound card. > Yes. Both situation 1 and 3 : > * options in kazam's preferences are the same and kazam doesn't record > audio stream > * In pavucontrol, the 'recording' tab says 'No application is currently > record audio', even when Kazam records Do you agree about this? Or am I still missing something else?
@Lewis > [Flameshot is a screenshot program that enables on-the-spot > annotations, geometric & text, before they are saved. Thank's a lot ! I'll try Flameshot. Usually I use Spectacle for screenshots and KolourPaint for annotations] > Your comments 19 & 21 and related attachments confirm what Martin describes: > draksound "Sound configuration" *does* show the Intel card in > turn. Does this not answer your title complaint? I don't think we are speaking about the same window. The window 'Sound configuration' wich shows the Intel card in turn, is reachies by going through 'MCC/drakconf - Hardware - Manage your hardware - Browse and configure hardware', but I spoke about the 'MCC/drakconf - Hardware - Manage your hardware - Sound Configuration' tab, which always shows the NVidia card (Comment 11) > Apart from this confusion: > > As you show, selecting the config tool runs draksound, which allows you > > to configure all sound cards (one after another), not just the one > > currently selected in the hardware browser. > I think we should close this aspect as being 'understood how > it functions'. That could be an enhancement bug. If we are talking about 'MCC - Hardware - Browse and configure hardware' I agree. The light is coming but I'm not very sure I really understand how does this section works with audio cards. I suppose that it is only a not very good presentation that makes understanding difficult, for those who are not initiated (as me ;) Thanks @Martin and @Lewis for your explanations. @Lewis > I think this bug - what really troubles you - is about Kazam not recording > sound when you have more than one sound card. > > Yes. Both situation 1 and 3 : > > * options in kazam's preferences are the same and kazam doesn't record > > audio stream > > * In pavucontrol, the 'recording' tab says 'No application is currently > > record audio', even when Kazam records > Do you agree about this? Or am I still missing something else? * Not only kazam, but also audacity and kdenlive. * Ssometimes I could recording an audio stream, but that doesn't work very well, see the two last posts of https://www.mageialinux-online.org/forum/topic-28789-2+diagnostiquer-le-systeme-audio-e.php#m287021. I haven’t done any more tests since. * And I can't choose 'Input' or 'Duplex' anymore in the sound profiles of pavucontrol (Comment 17)
I do not think we can ask more questions! Most of this bug is to do with disabling the nVidia sound device, which seems an academic diversion because the problem applications still record no sound with the config modification described: ** 00_modprobe.conf with 'options snd-hda-intel enable=1,0' See the end of the previous comment for the real problem. I do not think it is an application problem, given the diversity of those cited. One comment [in the long French forum topic whose URL is given] notes that this problem is 'since kernel 5.10' Assigning to kernel/drivers for their view.
Source RPM: draksound drakxtools-curses-18.45-1.mga8 => (none)Summary: draksound shows the wrong audio card. I can't choose the good one => Some applications do not record sound after adding an nVidia GeForce GTX 1050 card (which also does sound)CC: lewyssmith => (none)Assignee: bugsquad => kernelURL: (none) => https://www.mageialinux-online.org/forum/topic-28789+diagnostiquer-le-systeme-audio-e.php