-
Notifications
You must be signed in to change notification settings - Fork 79
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
Raspberry Pi 5 Support #19
Comments
I have it running on a Pi 5, on a bookworm LITE image I flashed today. I did have to add:
to /boot/firmware/config.txt |
It installs and works fine on the lite version of bookworm using the above, but it kills the desktop even after uninstalling. |
This script ended up working well for me: https://github.com/ubopod/ubo-sdk/blob/main/system/setup/install_wm8960.sh |
Thank you @ubopod. It appears to be working for me as well. |
sorry, didn't mean to close. |
Yes, #23 fixed an issue with Bookworm, but was it still not working not Pi 5. |
@makermelissa is the desktop issue same as lxpanel problem mentioned elsewhere? I am a bit confused - @flatsiedatsie and @ubopod seems to have something that works? |
I'm not sure what the lxpanel problem is. However, installing causes the desktop environment to stop working, but I can still SSH into the Pi and play audio just fine. The solution @ubopod mentioned works in the desktop environment, but isn't working for me on the lite version. |
@makermelissa pulseaudio seems to interfere with the desktop environment - #8 . |
Thanks, I'll see if removing it first (or after) fixes the issue. |
Uninstalling PulseAudio had no effect. Still no desktop. |
@makermelissa surely there are signs why it doesn't start - e.g. if you can still ssh in, as root, have a look at sys log - for systemd based systems, it is |
I'll take a deeper look into the issue and let you know if I see something that stands out. |
Here are the relevant sections of the log that stood out. Much of it is repeated:
|
Reinstalling lightdm lets it boot to the desktop once again, but it loses any customizations and looks like the default debian desktop rather than the Raspberry Pi bookworm desktop. |
The repeatedness is meaningful - lightdm refuses to start, so systemd try to start it over and over. @makermelissa I think there is a apt.log (or as part of systemd messages) about installed packages. So it would be interesting to know what is most recently installed because of lightdm. It looks like it might depends on pulseaudio - that's a bit insane surely, the display manager needing to play sound? |
Makes sense with what I was seeing. I'll keep looking, but probably a bit later today. |
I haven't been able to get it working on my Pi5 with the Respeaker 4-Mic Array v1.2. With a fresh copy of bookworm lite I can install without issue. But I don't see any devices listed.
|
My observation on a lite installation of bookworm is that when I ran the script, rebooted the device and played some audio, I heard nothing, I had to set "Playback" and "Speaker" values to a non-zero value in alsamixer to hear things: |
I confirm the solution suggested in #19 (comment) works on lite version too |
|
@AIWintermuteAI I am not convinced about pull - for two reasons, it just loads the 2-mic device tree so doesn't apply to the other devices; the So the fact that force-loading the device tree works, seems to suggest that on p5, the
` |
It seems that i2cdetect on P5 is indeed faulty : raspberrypi/linux#6056 |
@AIWintermuteAI this upstream issue seems highly relevant: raspberrypi/linux#5743 - have a read. It seems to suggest modifying the device tree overlays. |
This sort of explains why the 2-mic card is easier to get to work - it doesn't do playbacks. |
@HinTak yes, after a look at the issue it seems that the PR I made is more a quick patch rather than actual long-term solution. I'll close it. |
@HinTak looks like recent versions of the Pi5 kernel have fixed the I2C detection issue. I'm on
(note that at this point I had the drivers loaded hence the The service also correctly identifies the 4-mic array and loads the appropriate config and state files. However,
(please ignore the The driver in question is running off the |
I tried installing the driver on a fresh bookworm image in Pi 5 and after reboot, the system does not boot anymore. On Pi 4, same OS image everything work well (v6.1).
I would like to get behind Pi 5 support and help to make it happen. This audio chip is super popular and it will be bummer not to have support for Pi 5...
The issue might be related to this:
raspberrypi/linux#5743
The text was updated successfully, but these errors were encountered: