-
Notifications
You must be signed in to change notification settings - Fork 11
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
Update for latest version of Raspbian #4
Comments
Can also confirm this issue with current firmware image. Beepy instructions indicate using the most current image:
Current Lite image is 2023-10-10 which apparently is incompatible with Beepy drivers provided in the beepy-ppa archive. |
I encountered the same issue, documented with logs in an issue raised for the Beepy Docs at sqfmi/beepy-docs#21 |
Hi all, I finally got back to this. I updated the packages to support changes in Debian 12, and they are working for me on both Debian 11 and 12 now. Please let me know if you are seeing any more problems. |
Confirmed working, thank you. |
It would be wonderful if beepy-kbd and sharp-drm could be installed on the latest version of Raspbian. Right now it isn't working:
![Screenshot_20231026-214724_1](https://private-user-images.githubusercontent.com/122766435/278515988-a94221f2-3865-47b8-8adc-f58359cbb984.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM2NjU3MDMsIm5iZiI6MTcyMzY2NTQwMywicGF0aCI6Ii8xMjI3NjY0MzUvMjc4NTE1OTg4LWE5NDIyMWYyLTM4NjUtNDdiOC04YWRjLWY1ODM1OWNiYjk4NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgxNFQxOTU2NDNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0xNDkxOTQ2YTBlY2QwM2VmZGIwNDAyZDA0ZjJlNmJmNzNkMjQ4MDhkYzYzNTEyMGVkNDNlMWQzMDM4MzE2NDkwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.ahG2yrUW-8oC-f5eu3TK5HDzGjUB-YMpsonCsAKUudA)
The text was updated successfully, but these errors were encountered: