-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Allo Boss 2 device tree overlay or driver broken #5505
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
Comments
I don't have one of these devices, and no other sound cards appear to use the cs43130 codec, so debugging will be slow. Any thoughts, @babuenir? |
Me neither. But if someone has an idea how to debug/which output/logs to check, I will try to get everyone here from the other forums and/or forward/collect infos. |
Let's assume for now that the main codec driver is OK, since it is an unmodified upstream file. The overlay is extremely simple and hasn't changed since 5.15, so we can ignore that, which leaves the soundcard driver -
Run that test on both kernels, capturing the log to a different (and ideally suitably named) file each time. If the playback doesn't appear to work, report what you observe, and the output of |
Good day, thank you for the help on this issue. Firsts tests have been run on a vanilla Kernel version:
Output of the i2c traces as attached: After playback there was no output of Same thing but for the older kernel
This is probably also the reason i2c_log_speaker_test_kernel5_15_84.txt In general the output of tracing the speaker test command seems quite comparable. Thank you for your guidance. EDIT: maybe worthwhile to mention here: after enabling the tracing, the speaker-test command in the old kernel **this is a condensed copy of a post that i put in the dietpi forums moments ago. |
The channel count error is btw expected with audio source formats which are not natively supported by the sound driver/card. You can enforce 2 channels with However this is unrelated to the Boss 2 driver issue. |
There are differences between the traces associated with the two kernels (aside from the i2c spam from some python script), but nothing that screams error. Somebody who actually has one of these things and who cares more than the manufacturer is going to have to do some diagnosis. |
Pinging the manufacturer here, @alloboss2 in case you are not aware yet. |
I could do some tests Btw, their Katana driver also has issue but it's a driver load fail just on a Pi 4B, other Pi's are OK. Here is some ALSA info while playing something via Boss 2
|
I think the cs43130 problem is due to this commit: e14bd35 It switches from describing a fraction with two separate u16s linked only by name and usage to using a standard u16_fract structure. Unfortunately the author and reviewer failed to notice that the conversion effectively swapped the numerator and denominator. #5510 is a potential fix - I'm happy that it fixes the numerator/denominator ordering, but there might be other issues as well. Once the autobuilds have completed (in about an hour from now) you will be able to install a test kernel using |
It's good to go, if anyone wants to try:
And if you don't have rpi-update:
|
One of our users confirmed the patch works. |
Excellent. The patch was merged yesterday, so it will be in future kernel releases. At some point I'll have to notify the upstream devs... |
Super nice! Boss 2 is beloved by many Pi audio enthusiasts. |
The patch is now queued up for Linux 6.4: https://kernel.googlesource.com/pub/scm/linux/kernel/git/broonie/sound/+/a9e7c964cea4fb1541cc81a11d1b2fd135f4cf38 |
Describe the bug
We have several reports across multiple forums that the Allo Boss 2 dtb is not working (well) after one of the recent kernel upgrades: https://github.com/raspberrypi/linux/blob/rpi-6.1.y/arch/arm/boot/dts/overlays/allo-boss2-dac-audio-overlay.dts
I am not sure who is responsible, Allo, RPi kernel repo, RPi firmware repo, no one? I had a look into it but could not see any obvious error, like false node or such in the dtb. Since it affects quite a lot of users for 2 months without any other solution than downgrading the kernel, I thought it cannot hurt to report it here and hope for the best 🙂.
Steps to reproduce the behaviour
Use Allo Boss 2 HAT, enable related overlay, play audio, which either plays nothing or highly distorted, depending on audio source and format.
Device (s)
Raspberry Pi 4 Mod. B
System
It affects RPi OS, DietPi, moOde, i.e. all distros which use these kernel sources v6.1.
Logs
aplay -l
instead, just to show that the device is detected:Additional context
No response
The text was updated successfully, but these errors were encountered: