Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bullseye KDE Plasma NO Sound #1000

Closed
JFLim1 opened this issue Feb 2, 2023 · 9 comments
Closed

Bullseye KDE Plasma NO Sound #1000

JFLim1 opened this issue Feb 2, 2023 · 9 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@JFLim1
Copy link

JFLim1 commented Feb 2, 2023

Hi @ophub and KDE Plasma users,

Downloaded Armbian_23.02.0_amlogic_s922x-reva_bullseye_6.1.9_server_2023.0 and installed the latest KDE Plasma from Debian Unstable repo using:

sudo apt -t unstable install tasksel
sudo apt -t unstable install task-kde-desktop

Successfully installed KDE Plasma on Bullseye but NO Sound is available. SystemSettings "Audio" shows blank like there is NO soundcard. The "Sound Volume" icon at the bottom panel indicates NO Sound available.

image

aplay -l and cat /proc/asound/cards indicates soundcard is available.

jfl@armbian:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: GTKINGPRO [GTKINGPRO], device 0: fe.dai-link-0 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: GTKINGPRO [GTKINGPRO], device 1: fe.dai-link-1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: GTKINGPRO [GTKINGPRO], device 2: fe.dai-link-2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

jfl@armbian:~$ cat /proc/asound/cards
 0 [GTKINGPRO      ]: axg-sound-card - GTKINGPRO
                      GTKINGPRO

Appreciate some guidances or tips how to enable Sound on Debian Bullseye KDE Plasma.

On your image on Bullseye-Gnome or Jammy-Gnome sound is available out of the box.

Edit: If sound is available the KDE Plasma "systemsettings" Audio should look something like this:
image

But somehow NO Playback Devices is listed on Armbian_23.02.0_amlogic_s922x-reva_bullseye_6.1.9_KDE-Plasma so NO sound output.

@langyxxl
Copy link

langyxxl commented Feb 3, 2023

Scirese/alarm#2
try this, maybe same problem

@JFLim1
Copy link
Author

JFLim1 commented Feb 3, 2023

Hi @langyxxl & @ophub

Thank you for the tips. I do know about g12_sound.sh and sound.sh and used it on Manjaro-Arm and on the old Armbin-5.9.0 image to get sound on my device.

I thought Ophub's aml-s922X images already have the sound preset and not using g12_sound.sh to set or configure the sound card.

On the earlier Ophub's aml-s922X Jammy image, I installed Gnome DE and sound is available right after installation and reboot. The option of event Multi-Channel sound option is available!

With the latest Armbian_23.02.0_amlogic_s922x-reva_bullseye_6.1.9_server I face numerous issue on first boot up. WIFI was not detected or inconsistend detection even during first boot up after flashing..

Reflash Armbian_23.02.0_amlogic_s922x-reva_bullseye_6.1.9_server on USB drive and still having the WIFI detection issue. During first boot up WIFI was NOT detected as such NOT set/configured.

Plugin Ethernet and this help in WIFI detection after boot up (no idea why). Use "armbian-config" to set up the WIFI. Install KDE Plasma again and still NO Sound.
dmesg is filled with these repeated errors.

[ 1977.024064]  fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 1977.030735]  fe.dai-link-1: ASoC: error at dpcm_fe_dai_prepare on fe.dai-link-1: -22
[ 1977.039198]  fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1

@ophub Is there a sound configuration file that I need to edit (like g12_sound.sh) to enable sound through HDMI or "Built-In Audio"?

@JFLim1
Copy link
Author

JFLim1 commented Feb 3, 2023

Hi @langyxxl and @ophub

The g12_sound.sh did the trick on Bullsleye-KDE Plasma but only "Stereo Output".

@ophub am bit confused in the sense, why on Jammy Gnome sound is available without having to run "g12_sound.sh" and also "Multi-Channel" Output is available.

Without resolving the "Sound" issue, pulseaudio daemon hog or load one CPU core to around 100%. Once run "g12_sound.sh" the CPU load reduces immediately.

@JFLim1 JFLim1 closed this as completed Feb 3, 2023
@ophub ophub added the bug Something isn't working label Feb 3, 2023
@ophub
Copy link
Owner

ophub commented Feb 3, 2023

@7Ji

Scirese/alarm#2 (comment)

你在这个问题里的解决办法,JFLim1 测试有效。如果把这个压缩包解压了直接添加到所有的 Jammy和Bullsleye 默认固件里,对 Jammy 有没什么副作用?
Jammy 为什么可以工作而 Bullsleye 需要添加?你给帮忙解答下这个问题。

@7Ji
Copy link
Contributor

7Ji commented Feb 3, 2023

如果把这个压缩包解压了直接添加到所有的 Jammy和Bullsleye 默认固件里,对 Jammy 有没什么副作用?

On your image on Bullseye-Gnome or Jammy-Gnome sound is available out of the box.

The g12_sound.sh did the trick on Bullsleye-KDE Plasma but only "Stereo Output"

Without resolving the "Sound" issue, pulseaudio daemon hog or load one CPU core to around 100%.

This should not be added as a default config file as:

  1. It is not a problem with Bullseye, but Bullseye + Plasma, since Bullseye + Gnome works fine, adding it could probaly conflict with the existing working Gnome config.
  2. The script has a LOT of sutffs going on under the hood, and it expects an environment where none of the sound config was made. It is for the case of Arch, where audio daemons are just there without config after installing them, but certainly not for Armbian, where the distro already packs a lot of pre-configured stuffs before the user even use them.
  3. It does not fix the problem completely. There ARE already some auto-config sutffs going on and that's why the pulseaudio daemon went 100%, it is probably getting a LOT of config requests from the auto-config stuffs before the sound started to work, then that auto-config stuff stopped the full profile to work (hence, only stereo).

Jammy 为什么可以工作而 Bullsleye 需要添加?

Probably yet another different decision between the packagers of Ubuntu and Debian for the same package (I've seen a lot), especially on the config. If a distro decides your config, it's then not surprising that a derived distro choose something different from the parent distro. And Ubuntu loves to push more things (ah my painful experience uninstalling their pre-installed cloud-init on servers again and again)

I need to do some tests on a spare box to get exactly what different configs are there, but that'll not come soon.

@JFLim1
Copy link
Author

JFLim1 commented Feb 3, 2023

Hi @ophub and @7Ji

My memory on Ophub's aml-s922X Bullseye-Gnome has been a while ago and don't have that image anymore so my input on Sound Bullseye-Gnome works out of the box without "g12_sound.sh" is based on memory.

Still have Ophub's Jammy-Gnome which multi-channel sound is available.

aml-s922x-Jammy-Gnome:

image

@ophub
Copy link
Owner

ophub commented Feb 3, 2023

Ok, thanks for sharing your experience.

@JFLim1
Copy link
Author

JFLim1 commented Feb 3, 2023

Probably yet another different decision between the packagers of Ubuntu and Debian for the same package (I've seen a lot), especially on the config. If a distro decides your config, it's then not surprising that a derived distro choose something different from the parent distro. And Ubuntu loves to push more things (ah my painful experience uninstalling their pre-installed cloud-init on servers again and again)

In my experience in general, it is easier to install Desktop Environment on Ubuntu Jammy/Kinetic and get the expected out of the box working than installing Desktop Environment on Debian Bullseye/Sid especially KDE Plasma.

@7Ji 7Ji mentioned this issue Feb 8, 2023
@JFLim1
Copy link
Author

JFLim1 commented Feb 8, 2023

Hi @ophub & @7Ji

Just an update on aml-s922x-Bullseye-KDE sound. Earlier I had alluded that after running "g12_sound.sh" only "Stereo Output" is available. But today, i check KDE "systemsettings --> Audio" and I noticed Multi-Channel sound is also available just like in Jammy-Gnome image.

image

All is good. No idea what changes lead to this though. Great.

@ophub ophub added the documentation Improvements or additions to documentation label Feb 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants