Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #239287 > unrolled thread
| Started by | James D Freels <freelsjd@gmail.com> |
|---|---|
| First post | 2021-08-24 21:10 +0200 |
| Last post | 2021-08-25 21:10 +0200 |
| Articles | 5 — 2 participants |
Back to article view | Back to linux.debian.user
problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine James D Freels <freelsjd@gmail.com> - 2021-08-24 21:10 +0200
Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine James D Freels <freelsjd@gmail.com> - 2021-08-25 19:10 +0200
Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine Georgi Naplatanov <gosho@oles.biz> - 2021-08-25 19:40 +0200
Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine James D Freels <freelsjd@gmail.com> - 2021-08-25 20:40 +0200
Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine James D Freels <freelsjd@gmail.com> - 2021-08-25 21:10 +0200
| From | James D Freels <freelsjd@gmail.com> |
|---|---|
| Date | 2021-08-24 21:10 +0200 |
| Subject | problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine |
| Message-ID | <CPJY5-8va-3@gated-at.bofh.it> |
Hello, I am a long-time debian user, and just recently upgraded my buster amd64 machine to bullseye. Essentially everything works as expected so far. However, one very nagging problem I currently have is that my sound does not work unless I am rooted. For example, if I issue the command aplay bark.au where bark.au is a snippet sound file of a dog barking, it fails. However, if I issue the command sudo aplay bark.au it works fine. Similar sound playing occurs with any sound-playing app. For example mpg123, vlc, etc., all require a sudo or be logged in as root to work. I have looked all around the WWW to try to find a solution to this problem. The most common solution is to make sure that user ids are in the audio group in the /etc/group configuration file. Of course, I have that, and have confirmed it. This is not a brand new installation after all, but an upgrade. Other common remedies I have tried are to fiddle with the pavucontrol and alsamixer settings. My sound card does not show up in the pavucontrol (pulse doesn't find my sound card), but DOES show up in the alsamixer. I have also looked at the debian sound wiki, and other sources to try to fix this problem. Then, I remembered that I often used this form to learn about debian way back in the days when I first started using debian about 1994 or so. Perhaps I can get some expert help. Maybe a source I can go down a list of troubleshoot to nail this one down. It is obviously a permissions issue (I also looked at device permissions, etc.). Just a bit puzzled and frustrated. P.S. BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and uses the oxygen HD audio driver. lspci -v output corresponding: 05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG) Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA node 0 I/O ports at e800 [size=256] Capabilities: [c0] Power Management version 2 Kernel driver in use: snd_oxygen Kernel modules: snd_oxygen Nothing has changed with the hardware, and I know the setup works. This seems to be a permissions/software issue. -- James D. Freels, Ph.D., P.E. freelsjd@gmail.com 865-457-6742 (landline) 865-919-0320 (cell)
[toc] | [next] | [standalone]
| From | James D Freels <freelsjd@gmail.com> |
|---|---|
| Date | 2021-08-25 19:10 +0200 |
| Subject | Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine |
| Message-ID | <CQ4zv-4iQ-5@gated-at.bofh.it> |
| In reply to | #239287 |
I have not received a response yet, but I am hoping. What I know: -sound works as root, not as user -snd_oxygen module (required driver for my card) is loaded, but I can't verify what is loading it. no messages in dmesg show it being loaded -since snd_oxygen is loaded, it makes sense that aplay works as root -pulse does not show the sound card, but does show the hdmi audio on my nvidia card, and the microphone on my web cam. Both are muted in pavucontrol -big question: why doesn't sound card get loaded by pulseaudio ? How can I force that -I am now going over every occurrence of a pulseaudio configuration file on my system for a clue Any help appreciated. Is there a good troubleshoot procedure for debian/11/bullseye sound problems ? On 8/24/21 3:05 PM, James D Freels wrote: > Hello, > > I am a long-time debian user, and just recently upgraded my buster > amd64 machine to bullseye. Essentially everything works as expected > so far. However, one very nagging problem I currently have is that my > sound does not work unless I am rooted. For example, if I issue the > command > > aplay bark.au > > where bark.au is a snippet sound file of a dog barking, it fails. > However, if I issue the command > > sudo aplay bark.au > > it works fine. Similar sound playing occurs with any sound-playing > app. For example mpg123, vlc, etc., all require a sudo or be logged > in as root to work. > > I have looked all around the WWW to try to find a solution to this > problem. The most common solution is to make sure that user ids are > in the audio group in the /etc/group configuration file. Of course, I > have that, and have confirmed it. This is not a brand new > installation after all, but an upgrade. > > Other common remedies I have tried are to fiddle with the pavucontrol > and alsamixer settings. My sound card does not show up in the > pavucontrol (pulse doesn't find my sound card), but DOES show up in > the alsamixer. > > I have also looked at the debian sound wiki, and other sources to try > to fix this problem. > > Then, I remembered that I often used this form to learn about debian > way back in the days when I first started using debian about 1994 or > so. Perhaps I can get some expert help. Maybe a source I can go down > a list of troubleshoot to nail this one down. It is obviously a > permissions issue (I also looked at device permissions, etc.). > > Just a bit puzzled and frustrated. > > P.S. > > BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and > uses the oxygen HD audio driver. > > lspci -v output corresponding: > > 05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 > [Oxygen HD Audio] > Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG) > Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA node 0 > I/O ports at e800 [size=256] > Capabilities: [c0] Power Management version 2 > Kernel driver in use: snd_oxygen > Kernel modules: snd_oxygen > > Nothing has changed with the hardware, and I know the setup works. > This seems to be a permissions/software issue. > > > -- Father, if you are willing, please take this cup of suffering away from me. Yet I want your will to be done, not mine. Luke 22:42 NLT James D. Freels, Ph.D., P.E. freelsjd@gmail.com 865-457-6742 (landline) 865-919-0320 (cell)
[toc] | [prev] | [next] | [standalone]
| From | Georgi Naplatanov <gosho@oles.biz> |
|---|---|
| Date | 2021-08-25 19:40 +0200 |
| Subject | Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine |
| Message-ID | <CQ52x-4sh-7@gated-at.bofh.it> |
| In reply to | #239305 |
Hi James, try to run: # alsactl init as root, reboot and adjust all channels with alsamixer or similar with your (non-root) user. Kind regards Georgi On 8/25/21 20:02, James D Freels wrote: > I have not received a response yet, but I am hoping. > > What I know: > > -sound works as root, not as user > > -snd_oxygen module (required driver for my card) is loaded, but I can't > verify what is loading it. no messages in dmesg show it being loaded > > -since snd_oxygen is loaded, it makes sense that aplay works as root > > -pulse does not show the sound card, but does show the hdmi audio on my > nvidia card, and the microphone on my web cam. Both are muted in > pavucontrol > > -big question: why doesn't sound card get loaded by pulseaudio ? How > can I force that > > -I am now going over every occurrence of a pulseaudio configuration file > on my system for a clue > > Any help appreciated. Is there a good troubleshoot procedure for > debian/11/bullseye sound problems ? > > > On 8/24/21 3:05 PM, James D Freels wrote: >> Hello, >> >> I am a long-time debian user, and just recently upgraded my buster >> amd64 machine to bullseye. Essentially everything works as expected >> so far. However, one very nagging problem I currently have is that my >> sound does not work unless I am rooted. For example, if I issue the >> command >> >> aplay bark.au >> >> where bark.au is a snippet sound file of a dog barking, it fails. >> However, if I issue the command >> >> sudo aplay bark.au >> >> it works fine. Similar sound playing occurs with any sound-playing >> app. For example mpg123, vlc, etc., all require a sudo or be logged >> in as root to work. >> >> I have looked all around the WWW to try to find a solution to this >> problem. The most common solution is to make sure that user ids are >> in the audio group in the /etc/group configuration file. Of course, I >> have that, and have confirmed it. This is not a brand new >> installation after all, but an upgrade. >> >> Other common remedies I have tried are to fiddle with the pavucontrol >> and alsamixer settings. My sound card does not show up in the >> pavucontrol (pulse doesn't find my sound card), but DOES show up in >> the alsamixer. >> >> I have also looked at the debian sound wiki, and other sources to try >> to fix this problem. >> >> Then, I remembered that I often used this form to learn about debian >> way back in the days when I first started using debian about 1994 or >> so. Perhaps I can get some expert help. Maybe a source I can go down >> a list of troubleshoot to nail this one down. It is obviously a >> permissions issue (I also looked at device permissions, etc.). >> >> Just a bit puzzled and frustrated. >> >> P.S. >> >> BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and >> uses the oxygen HD audio driver. >> >> lspci -v output corresponding: >> >> 05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 >> [Oxygen HD Audio] >> Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG) >> Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA node 0 >> I/O ports at e800 [size=256] >> Capabilities: [c0] Power Management version 2 >> Kernel driver in use: snd_oxygen >> Kernel modules: snd_oxygen >> >> Nothing has changed with the hardware, and I know the setup works. >> This seems to be a permissions/software issue. >> >> >>
[toc] | [prev] | [next] | [standalone]
| From | James D Freels <freelsjd@gmail.com> |
|---|---|
| Date | 2021-08-25 20:40 +0200 |
| Subject | Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine |
| Message-ID | <CQ5YB-51J-3@gated-at.bofh.it> |
| In reply to | #239306 |
Thanks for responding Georgi, I had already tried "alsactl init" earlier based on other advise found on the WWW. However, I did not pay close enough attention because of error messages I get as shown below: alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "CMI8786" "CMI8786" "CS4245 CMI8786" "0x1043" "0x8467" Hardware is initialized using a generic method alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2 Found hardware: "USB-Audio" "USB Mixer" "USB046d:082c" "" "" Hardware is initialized using a generic method alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA NVidia at 0xfe9fc000 irq 49) alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -6 Found hardware: "HDA-Intel" "Nvidia GPU 51 HDMI/DP" "HDA:10de0051,38422724,00100100" "0x3842" "0x2724" Hardware is initialized using a generic method I cannot find much about this message, nor how to correct it. The alsamixer seems to work fine as expected and indicates I have the sound card active and should hear sound. But, it only provides actual sound if I am root. On 8/25/21 1:28 PM, Georgi Naplatanov wrote: > Hi James, > > try to run: > > # alsactl init > > as root, reboot and adjust all channels with alsamixer or similar with > your (non-root) user. > > Kind regards > Georgi > > On 8/25/21 20:02, James D Freels wrote: >> I have not received a response yet, but I am hoping. >> >> What I know: >> >> -sound works as root, not as user >> >> -snd_oxygen module (required driver for my card) is loaded, but I can't >> verify what is loading it. no messages in dmesg show it being loaded >> >> -since snd_oxygen is loaded, it makes sense that aplay works as root >> >> -pulse does not show the sound card, but does show the hdmi audio on my >> nvidia card, and the microphone on my web cam. Both are muted in >> pavucontrol >> >> -big question: why doesn't sound card get loaded by pulseaudio ? How >> can I force that >> >> -I am now going over every occurrence of a pulseaudio configuration file >> on my system for a clue >> >> Any help appreciated. Is there a good troubleshoot procedure for >> debian/11/bullseye sound problems ? >> >> >> On 8/24/21 3:05 PM, James D Freels wrote: >>> Hello, >>> >>> I am a long-time debian user, and just recently upgraded my buster >>> amd64 machine to bullseye. Essentially everything works as expected >>> so far. However, one very nagging problem I currently have is that my >>> sound does not work unless I am rooted. For example, if I issue the >>> command >>> >>> aplay bark.au >>> >>> where bark.au is a snippet sound file of a dog barking, it fails. >>> However, if I issue the command >>> >>> sudo aplay bark.au >>> >>> it works fine. Similar sound playing occurs with any sound-playing >>> app. For example mpg123, vlc, etc., all require a sudo or be logged >>> in as root to work. >>> >>> I have looked all around the WWW to try to find a solution to this >>> problem. The most common solution is to make sure that user ids are >>> in the audio group in the /etc/group configuration file. Of course, I >>> have that, and have confirmed it. This is not a brand new >>> installation after all, but an upgrade. >>> >>> Other common remedies I have tried are to fiddle with the pavucontrol >>> and alsamixer settings. My sound card does not show up in the >>> pavucontrol (pulse doesn't find my sound card), but DOES show up in >>> the alsamixer. >>> >>> I have also looked at the debian sound wiki, and other sources to try >>> to fix this problem. >>> >>> Then, I remembered that I often used this form to learn about debian >>> way back in the days when I first started using debian about 1994 or >>> so. Perhaps I can get some expert help. Maybe a source I can go down >>> a list of troubleshoot to nail this one down. It is obviously a >>> permissions issue (I also looked at device permissions, etc.). >>> >>> Just a bit puzzled and frustrated. >>> >>> P.S. >>> >>> BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and >>> uses the oxygen HD audio driver. >>> >>> lspci -v output corresponding: >>> >>> 05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 >>> [Oxygen HD Audio] >>> Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG) >>> Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA node 0 >>> I/O ports at e800 [size=256] >>> Capabilities: [c0] Power Management version 2 >>> Kernel driver in use: snd_oxygen >>> Kernel modules: snd_oxygen >>> >>> Nothing has changed with the hardware, and I know the setup works. >>> This seems to be a permissions/software issue. >>> >>> >>> -- Father, if you are willing, please take this cup of suffering away from me. Yet I want your will to be done, not mine. Luke 22:42 NLT James D. Freels, Ph.D., P.E. freelsjd@gmail.com 865-457-6742 (landline) 865-919-0320 (cell)
[toc] | [prev] | [next] | [standalone]
| From | James D Freels <freelsjd@gmail.com> |
|---|---|
| Date | 2021-08-25 21:10 +0200 |
| Subject | Re: problem with sound for bullseye upgrade on amd64: must be root for sound to work on my machine |
| Message-ID | <CQ6rE-5r4-7@gated-at.bofh.it> |
| In reply to | #239309 |
I finally got my sound working. I followed some advice from here: https://www.linuxquestions.org/questions/slackware-14/alsa-1-2-5-upgrade-errors-4175695921/page3.html which was a similar problem to mine, and not sure what did it, but I got a flash pop up on my screen about alsa, and tested all things working now. Man, what a frustration. Otherwise, the bullseye upgrade has been flawless for me so far. On 8/25/21 2:30 PM, James D Freels wrote: > Thanks for responding Georgi, > > I had already tried "alsactl init" earlier based on other advise found > on the WWW. However, I did not pay close enough attention because of > error messages I get as shown below: > > alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import > hw:0 use case configuration -2 > Found hardware: "CMI8786" "CMI8786" "CS4245 CMI8786" "0x1043" "0x8467" > Hardware is initialized using a generic method > alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import > hw:1 use case configuration -2 > Found hardware: "USB-Audio" "USB Mixer" "USB046d:082c" "" "" > Hardware is initialized using a generic method > alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA > model (HDA NVidia at 0xfe9fc000 irq 49) > alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import > hw:2 use case configuration -6 > Found hardware: "HDA-Intel" "Nvidia GPU 51 HDMI/DP" > "HDA:10de0051,38422724,00100100" "0x3842" "0x2724" > Hardware is initialized using a generic method > > I cannot find much about this message, nor how to correct it. > > The alsamixer seems to work fine as expected and indicates I have the > sound card active and should hear sound. > > But, it only provides actual sound if I am root. > > On 8/25/21 1:28 PM, Georgi Naplatanov wrote: >> Hi James, >> >> try to run: >> >> # alsactl init >> >> as root, reboot and adjust all channels with alsamixer or similar with >> your (non-root) user. >> >> Kind regards >> Georgi >> >> On 8/25/21 20:02, James D Freels wrote: >>> I have not received a response yet, but I am hoping. >>> >>> What I know: >>> >>> -sound works as root, not as user >>> >>> -snd_oxygen module (required driver for my card) is loaded, but I can't >>> verify what is loading it. no messages in dmesg show it being loaded >>> >>> -since snd_oxygen is loaded, it makes sense that aplay works as root >>> >>> -pulse does not show the sound card, but does show the hdmi audio on my >>> nvidia card, and the microphone on my web cam. Both are muted in >>> pavucontrol >>> >>> -big question: why doesn't sound card get loaded by pulseaudio ? How >>> can I force that >>> >>> -I am now going over every occurrence of a pulseaudio configuration >>> file >>> on my system for a clue >>> >>> Any help appreciated. Is there a good troubleshoot procedure for >>> debian/11/bullseye sound problems ? >>> >>> >>> On 8/24/21 3:05 PM, James D Freels wrote: >>>> Hello, >>>> >>>> I am a long-time debian user, and just recently upgraded my buster >>>> amd64 machine to bullseye. Essentially everything works as expected >>>> so far. However, one very nagging problem I currently have is that my >>>> sound does not work unless I am rooted. For example, if I issue the >>>> command >>>> >>>> aplay bark.au >>>> >>>> where bark.au is a snippet sound file of a dog barking, it fails. >>>> However, if I issue the command >>>> >>>> sudo aplay bark.au >>>> >>>> it works fine. Similar sound playing occurs with any sound-playing >>>> app. For example mpg123, vlc, etc., all require a sudo or be logged >>>> in as root to work. >>>> >>>> I have looked all around the WWW to try to find a solution to this >>>> problem. The most common solution is to make sure that user ids are >>>> in the audio group in the /etc/group configuration file. Of course, I >>>> have that, and have confirmed it. This is not a brand new >>>> installation after all, but an upgrade. >>>> >>>> Other common remedies I have tried are to fiddle with the pavucontrol >>>> and alsamixer settings. My sound card does not show up in the >>>> pavucontrol (pulse doesn't find my sound card), but DOES show up in >>>> the alsamixer. >>>> >>>> I have also looked at the debian sound wiki, and other sources to try >>>> to fix this problem. >>>> >>>> Then, I remembered that I often used this form to learn about debian >>>> way back in the days when I first started using debian about 1994 or >>>> so. Perhaps I can get some expert help. Maybe a source I can go down >>>> a list of troubleshoot to nail this one down. It is obviously a >>>> permissions issue (I also looked at device permissions, etc.). >>>> >>>> Just a bit puzzled and frustrated. >>>> >>>> P.S. >>>> >>>> BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and >>>> uses the oxygen HD audio driver. >>>> >>>> lspci -v output corresponding: >>>> >>>> 05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 >>>> [Oxygen HD Audio] >>>> Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG) >>>> Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA >>>> node 0 >>>> I/O ports at e800 [size=256] >>>> Capabilities: [c0] Power Management version 2 >>>> Kernel driver in use: snd_oxygen >>>> Kernel modules: snd_oxygen >>>> >>>> Nothing has changed with the hardware, and I know the setup works. >>>> This seems to be a permissions/software issue. >>>> >>>> >>>> -- Father, if you are willing, please take this cup of suffering away from me. Yet I want your will to be done, not mine. Luke 22:42 NLT James D. Freels, Ph.D., P.E. freelsjd@gmail.com 865-457-6742 (landline) 865-919-0320 (cell)
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web