Hi @MagnificentPako,
I assumed it was going to be really easy to point out the missing device tree overlay or kernel module. That’s not the issue, though. You actually found it. I’ll repeat what I saw when looking through Mesa 3D
The problem is that the version of Mesa 3D, 24.0.9, supplied by Buildroot isn’t new enough.
The technical issue is described pretty well in this Mesa 3D commit message. It looks like you found this and started down this path.
These updates are in the Mesa 3D 24.3.0 release.
The good news is that there’s a patch to update Mesa 3D to 24.3.3 that was posted on Jan 18. It’s part of a patch series that is more complicated than I was expecting.
Waiting for the Buildroot maintainers to accept the patch is by far the easiest option, but it takes time. Luckily, the submitter is a maintainer so it may take less time, but I’d still allow for it to take a few more weeks.
The alternative is to fork kiosk_system_rpi5, copy/paste in the Buildroot patch I linked above, rename the package to MESA3D_RPI (or anything that’s not MESA3D so that it doesn’t conflict), and update the nerves_defconfig to use it instead. This is more time consuming than I’m making it sound, and my strategy at this would be to get the update patch working in Buildroot first before trying it out with Nerves. The reason being that the patch looked more involved than I expected and I didn’t understand why on my brief skim of it.
If I get time this week, I’ll take a harder look at that patch. I have a 7" touchscreen, but not the right cable for the RPi 5. I’ll see if I can find one.
Anyway, the summary is that if you can wait, I’m pretty sure this will be fixed in the coming weeks. Thanks for posting that it didn’t work, since until I saw your post, I didn’t know that the situation had changed on the RPi5.
