-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
PINE A64 | No sound with mainline kernel #4805
Comments
Many thanks for your report. Is the sound card listed by ALSA? aplay -l |
Nope:
|
So there is simply no sound device found. I checked the current A64 kernel and device tree overlays and there is at least no overlay to enable onboard sound, means that it "should" be enabled by default. I checked the Armbian forum but couldn't find something related so far: https://forum.armbian.com/forum/27-allwinner-a64-h5-h6-and-h616/ Does the kernel report any errors that may be related? dmesg -l emerg,alert,crit,err
dmesg | grep -E 'audio|sound|snd' |
These are the errors I found (there are many others but they are CIFS-related):
and
|
Was this on a fresh DietPi system or did it work before? |
Sorry, did not receive the notification for your reply. |
You tried a reboot, didn't you? To me it looks like a related kernel module isn't loaded. Does this one load? modprobe sunxi_codec or this one: modprobe snd-soc-simple-card Interesting is that |
Yes, I've rebooted many times already.
(No output on the last one) |
Ok, I don't know what I did, but now the soundcards show up (but still no sound):
I have also tried editing the squeezelite service to specify the output card ("-o hw:CARD=sun50ia64audio,DEV=0") but still can't hear any sounds :( |
Good so far. Can you please try to re-select the right card via |
I've re-selected |
Can you show the available controls with values:
|
Sure: Logfile attached. Click to expand!
|
Okay, I also cannot see something that is missing or muted. Try to move all sliders to max in Some controls are muted, especially try to raise those, although it doesn't look like it were related to regular 3.5mm output, mostly ADC/DAC devices:
|
I've followed your advice and unmuted everything, then raised everything to 100%. Rebooted. |
Let me create a Bullseye image, probably the userland updates solve it, so we don't waste time in debugging an old Debian version. |
Should I try to update my installation to Bullseye? |
Good idea, as my server is in the middle of builds already: https://dietpi.com/blog/?p=811#2.2-manual-upgrade |
Ok, I don't have the time to do that now either but will try ASAP. Thank you |
Okay, a new image will be ready then as well, so you have the choice. |
Perfect, I can even try both solutions, so we can see what works and what does not. |
Image ready: https://dietpi.com/downloads/images/ |
Trying the new image:
this command hangs. And after installing LMS+Squeezelite, still no audio output :-( But if I launch a song on Squeezelite, this happens:
I'm starting to suspect my line-out output is defective... |
As long as ALSA ( Can you check again: dmesg | grep -E 'audio|sound|snd' Probably the legacy kernel is then required. If you find time, could you try to replicate the same issue with Armbian's Bullseye image: https://www.armbian.com/pine64/ |
My latest post was related to the Bullseye image. Sorry for not being clear about that. |
Same kind of trouble trying bookworms version : fresh install for minimal pure image on Pine A64 SBC, no sound out of earphone jack whatever I try with JustBoom and alsamixer. aplay -l =>
aconnect -l =>
aconnect -o gives nothing ! Then I tried to follow https://debian-facile.org/doc:materiel:cartes-son:depannage
Same SBC is still working with buster version, so I can compare both cases, but I do not know what to compare... I would like to use bookworms because buster gives problem with perl scripts (can not install libwww-perl) and to be frank, I had very hard time with buster before to get sound on jack, even do not know how it came ok ! I am lost ! What could I do ? |
You are aware that the guide you tried to use is from 2011? 😄
Do you know what However, we already know that it is an issue with the device tree. @PanderMusubi opened an issue at the Armbian repo, but it was closed by someone else who seem to have not understood that it is an issue with the device tree, and not one with "running" Armbian, even that Pander is the official maintainer for this SBC 🤔. Or @PanderMusubi were you able to fix it, and it is just some |
Thank to your reply and explanations, even if I am not smart enough to fully understand... About aconnect, I already made wild tries like
instead of nothing with bookworm, other tests done today :
I tried to blacklist hdmi sound card into alsa-base-blacklist.conf but it did not help Then I compare with the working buster version where
Well, it is true that I made a lot of tries with buster 2 years ago before to get sound Other details : When I plug or unplug the jack, it is reported on the display, but in reverse way : display "plug removed" when I plug in ! So I tred to install with and without plug inserted : no difference. Thank a lot for all your time helping people like me, just tell me if I should stop to post helpless stuff ! |
use |
I just tried : Thank anyway for your reply. |
I am one of the two maintainers and mainly test. Device trees are above my pay grade and we need help from others. Perhaps you can find somebody on the forum of Armbian who has fixed it in the past and/or can help out. |
Creating a bug report/issue
Required Information
DietPi version |
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=6
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='not applicable'
G_LIVE_PATCH_STATUS[1]='applied'
G_LIVE_PATCH_STATUS[2]='applied'
G_LIVE_PATCH_STATUS[3]='applied'
G_LIVE_PATCH_STATUS[4]='not applicable'
Distro version | buster
Kernel version |
Linux DietPineA64 5.10.60-sunxi64 #21.08.1 SMP Wed Aug 25 18:29:57 UTC 2021 aarch64 GNU/Linux
SBC model | PINE A64 (aarch64)
Power supply used | 5V 2A UGreen
SDcard used | SanDisk ultra 32Gb
Additional Information (if applicable)
echo $G_HW_UUID
Steps to reproduce
Expected behaviour
The text was updated successfully, but these errors were encountered: