-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Allo Piano DAC 2.1 missing alsa controls #6548
Comments
It would be helpful if you could resurrect an old image and make a list of the controls which used to be available ( @foonerd Does this chime with your experience? |
I had to step into the Wayback Machine but here's some information from my notes on the vintage Piano 2.1. Piano 2.1 DSP firmware files
Amixer output
|
Unfortunately I'm away till weekend. If you can outline what details are needed, or tests - happy to oblige. |
FYI
I have an older version running.
RPiOS: 11.9 Bullseye 64-bit | Linux: 6.1.21 64-bit
Output of amixer scontrols
Simple mixer control 'Master',0
Simple mixer control 'Dual Mode',0
Simple mixer control 'Lowpass',0
Simple mixer control 'Main Analogue',0
Simple mixer control 'Main Analogue Playback Boost',0
Simple mixer control 'Main DSP Program',0
Simple mixer control 'Main Deemphasis',0
Simple mixer control 'Sub Analogue',0
Simple mixer control 'Sub Analogue Playback Boost',0
Simple mixer control 'Sub DSP Program',0
Simple mixer control 'Sub Deemphasis',0
Simple mixer control 'Subwoofer',0
Simple mixer control 'Subwoofer mode',0
Note that the control 'Master' in the early days of the Piano 2.1 driver
was called 'Digital'.
Op 19-12-2024 om 05:58 schreef Just a nerd:
…
It would be helpful if you could resurrect an old image and make a
list of the controls which used to be available (|amixer scontrols|?).
@foonerd <https://github.com/foonerd> Does this chime with your
experience?
Unfortunately I'm away till weekend. If you can outline what details
are needed, or tests - happy to oblige.
The kernel path I was on was 5.5.y -> 6.1.y -> 6.6.y and can get the
details from these if it helps.
—
Reply to this email directly, view it on GitHub
<#6548 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNZXAXKJ22VCPTSV64MSBK32GJG7PAVCNFSM6AAAAABT24NBL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSG44DOOBXG4>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--------------SN3PcCOOlDFO8fsRWNm0vbVp
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<font face="Tahoma">FYI<br>
I have an older version running.<br>
RPiOS: 11.9 Bullseye 64-bit | Linux: 6.1.21 64-bit<br>
<br>
<br>
Output of amixer scontrols<br>
Simple mixer control 'Master',0<br>
Simple mixer control 'Dual Mode',0<br>
Simple mixer control 'Lowpass',0<br>
Simple mixer control 'Main Analogue',0<br>
Simple mixer control 'Main Analogue Playback Boost',0<br>
Simple mixer control 'Main DSP Program',0<br>
Simple mixer control 'Main Deemphasis',0<br>
Simple mixer control 'Sub Analogue',0<br>
Simple mixer control 'Sub Analogue Playback Boost',0<br>
Simple mixer control 'Sub DSP Program',0<br>
Simple mixer control 'Sub Deemphasis',0<br>
Simple mixer control 'Subwoofer',0<br>
Simple mixer control 'Subwoofer mode',0<br>
<br>
Note that the control 'Master' in the early days of the Piano 2.1
driver was called 'Digital'.<br>
</font><br>
<br>
<br>
<div class="moz-cite-prefix">Op 19-12-2024 om 05:58 schreef Just a
nerd:<br>
</div>
<blockquote type="cite" ***@***.***">
<blockquote>
<p dir="auto">It would be helpful if you could resurrect an old
image and make a list of the controls which used to be
available (<code class="notranslate">amixer scontrols</code>?).</p>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/foonerd/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/foonerd" ***@***.***</a>
Does this chime with your experience?</p>
</blockquote>
<p dir="auto">Unfortunately I'm away till weekend. If you can
outline what details are needed, or tests - happy to oblige.<br>
The kernel path I was on was 5.5.y -> 6.1.y -> 6.6.y and
can get the details from these if it helps.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="#6548 (comment)" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/BNZXAXKJ22VCPTSV64MSBK32GJG7PAVCNFSM6AAAAABT24NBL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSG44DOOBXG4" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you authored the thread.<img src="https://github.com/notifications/beacon/BNZXAXKH4JZNTCG6FVFWQCD2GJG7PA5CNFSM6AAAAABT24NBL6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUYFBZ2K.gif" height="1" width="1" alt="" moz-do-not-send="true"><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><raspberrypi/linux/issues/6548/2552787877</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#6548 (comment)",
"url": "#6548 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
<br>
</body>
</html>
--------------SN3PcCOOlDFO8fsRWNm0vbVp--
|
I hope to get a chance to look at this tomorrow. |
With a one-line change to allo-piano-dac-plus.c: diff --git a/sound/soc/bcm/allo-piano-dac-plus.c b/sound/soc/bcm/allo-piano-dac-plus.c
index f999133dddb20..aa6f01069cdd2 100644
--- a/sound/soc/bcm/allo-piano-dac-plus.c
+++ b/sound/soc/bcm/allo-piano-dac-plus.c
@@ -916,7 +916,7 @@ static struct snd_soc_dai_link_component allo_piano_2_1_codecs[] = {
SND_SOC_DAILINK_DEFS(allo_piano_dai_plus,
DAILINK_COMP_ARRAY(COMP_EMPTY()),
DAILINK_COMP_ARRAY(COMP_CODEC("pcm512x.1-004c", "pcm512x-hifi"),
- COMP_CODEC("pcm512x.1-004d", "pcm512x-hifi")),
+ COMP_CODEC("pcm512x.1-004c", "pcm512x-hifi")),
DAILINK_COMP_ARRAY(COMP_EMPTY()));
static struct snd_soc_dai_link snd_allo_piano_dac_dai[] = { I am able to use the
which is the same as your list on 6.1. In the kernel (
However, these messages come from the code that removes the codec's controls, and only for the Sub codec (which doesn't exist on an IQaudIO Pi-DAC+). I also get a working volume control etc. using alsamixer. Running the current 6.6 kernel ( |
Kernel (uname): Linux raspberrypi 6.6.67-v8+ #1833 SMP PREEMPT Fri Dec 20 14:14:15 GMT 2024 aarch64 GNU/Linux |
amixer and alsamixer default to card 0 unless -c N is specified Might be worth checking |
Output of aplay -l: |
Then add -c2
|
Alternatively, if you don't want to use the HDMI audio, add the
|
output of amixer -c2 scontrols: alsamixer -c2 command gives the graphical interface of the controls Nice. |
Tried to add the noaudio option and rebooted the system now the result of aplay -l is: The Piana 2.1 dac card number now is 1. |
Good catch, @moodeaudio. |
Describe the bug
Running a rpi4 with Allo Piano 2.1 dac and Allo Kali reclocker.
Streamer is MoOde audio version 9.x.x. kernel 6.6.5 With this kernel the Rpi is locking, no response what so ever.
I bumped the kernel to include the "Fix volume limit locking" patch (RPiOS: 12.8 Bookworm 64-bit | Linux: 40 64-bit)
https://github.com/raspberrypi/linux/com...7156a1a4b4
Now the RPi is responding and producing sound.
Alsamixer command reports : "This sound device does not have any controls."
Steps to reproduce the behaviour
Running a rpi4 with Allo Piano 2.1 dac and Allo Kali reclocker.
Streamer is MoOde audio version 9.x.x. kernel 6.6.5
Bump the kernel to include the "Fix volume limit locking" patch (RPiOS: 12.8 Bookworm 64-bit | Linux: 40 64-bit)
https://github.com/raspberrypi/linux/com...7156a1a4b4
Alsamixer command fails
Device (s)
Raspberry Pi 4 Mod. B
System
cat /etc/rpi-issue:
Raspberry Pi reference 2024-11-26
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 6fb311e7fb57b4e7980ae3270c25b569b19dfe8f, stage3
vcgencmd version:
Dec 5 2024 11:45:37
Copyright (c) 2012 Broadcom
version 03554ca336a03ace164f36755144e0d8c060062d (clean) (release) (start)
uname -a:
Linux raspberrypi 6.6.66-v8+ #1830 SMP PREEMPT Mon Dec 16 14:40:26 GMT 2024 aarch64 GNU/Linux
Logs
No response
Additional context
With kernel 6.6.5 after selecting dtoverlay=allo-piano-dac-plus-pcm512x-audio for Allo Piano 2.1 the system comes in a locked status during boot. (Deadlock)
After bumping the kernel the boot process completes leaving a working system
The text was updated successfully, but these errors were encountered: