It will be released when it’s ready. Repeatedly asking won’t make it any faster.
1 Like
I understand lack of Sam’s motivation as it looks completely community-driven effort.
Thank you Sam for the effort; I have been using OSMC for 5 years now? It’s been great.
Personally, I am moving on. Just installed libreelec.tv on rpi5 (i.e. stock kodi). Works as it should; no frame drops on 1080p (where rpi3 would stutter like crazy).
There is no lack of motivation, just a lack of time.
LibreELEC is a great project. When we do have Raspberry Pi 5 support, you are welcome back any time 
1 Like
Yes, i know, I’ve been on OSMC since 2015 you know, almost 10 years. 
I have a problem with my disks that won’t mount, it’s a real problem. 
My drive is connected to a HUB with its power supply
@sam_nazarko are you really sure you are interested on Raspberry Pi5 support?
I see you and the team very focus on bug fixing for Vero devices and their sell, i don’t see any Git commit or progress on Pi5 support.
I don’t argue about development team ideas, but I think you all need to be honest and sincere in telling us whether you are interested in this or not; the first time we talked about Pi5 support was september/october 2023 and after 1 year i don’t see anythink in this direction…
Please, honeslty tell us if you are interested in Pi5 support or only on Vero devices!
Thanks,
Christian
Yes, I am interested in supporting the Raspberry Pi 5, or I would simply say that we have no intention of supporting it and not spend so much time on answering this same question repeatedly.
The problem is I am the only developer working on it, with limited time and resources. The Vero effectively sponsors OSMC development time on Raspberry Pi and keeps the project alive. Without it, there would be no Raspberry Pi support, or OSMC for that matter.
There has been work on Pi 5 support with one of the earliest commits as follows:
I am also regularly updating (for example today) other Raspberry Pi devices and they are all on the latest version of Kodi. We had the same complaints when Raspberry Pi 4 came out, and it took some time to ready that device for use.
The support will come. We have to move to a new version of Debian, move to a 64-bit userland environment and update the kernel.
I am also welcome to outside contributions and support. It is after all an open source project.
6 Likes
A list of things to do and why, would be a nice starting point for external contribution.
- Update kernel, kernel config.
- Port userland to 64-bit
- Update target installer to new kernel and Aarch64.
- Deprecate unsupported platforms such as early RBP2 models.
- Add notifications to users that a reinstall is needed to continue receiving updates for platforms that stay supported.
Updating the kernel and config will be the next step. We can then boot Pi on current userland and it will be good enough for internal testing. But when updating the kernel it’s important to get configuration right.
I have a long term plan to make kernel updates on RPi a lot quicker and maintainable in the future: take upstream defconfig and programmatically script the diff. Long term it will make supporting Pi a lot easier. The 64-bit change is a one off so once it’s done it’s done and Bookworm should be routine.
That’s it.
3 Likes
Are fine details somewhere about the difficulties involved? What are the issues precluding each achievement?
Yes, there are more specifics, but my intention was to give a general overview.
I understand, but the bare list is not actionable.
It is. The kernel is a good start.
1 Like