egl-wayland was not the silver bullet. WAYLAND_DEBUG=1 EGL_LOG_LEVEL=debug eglinfo -B implies that it’s a bug in the PowerVR drivers and not something we can fix, but I’ve not the motivation to do a thorough check.
With DuckStation, I assume you mean SwanStation that you listed earlier?
Yea Swanstation. Sorry. I couldn’t find a duckstation app that would work with my setup, only libretro cores. But it may work now? These things are developing rapidly
I checked your Luanti video again more closely, I guess what bothered me was the fluctuating framerate (mine is stable). For me it fluctuates around 40 unless I cap it at 30, for the K3 build you’ve shown it’s slightly above 30? In any case I’d expect it to run better, not worse or same. I guess the driver needs more work, but thankfully you’ll have Vulkan there.
I do, I suppose. Thanks. But it’ll have to wait until later this week.
Edit: again almost forgot, I tested Xash3D some more, like Counter-Strike, TF and Blue Shift and stuff. Everything is working amazingly well, possibly one of the flashiest things to showcase on VF2. Except I can’t move with keyboard input in multiplayer games. Well maybe I can. I don’t know how it works, but from what I recall you were usually able to move while waiting in lobbies?
1 Like
An update.
Gone down the rabbit hole of Firefox acceleration for a little. Looks like a layer of its graphical stack isn’t accelerated. The end output, for some reason, is, so the VF2 reports using the GPU, but the canvas, before display, is calculated by the CPU no matter what I do.
… Sonic CD doesn’t work well after all. In special stages it slows down and CTDs.
… Team Fortress and Counter Strike work fine with keyboard after all. You can find a server and just mingle with PC Master Race. I am not a fan of these games, but do recognize their significance: devs take note - CS sells the machine not only to my grumpy neighbour whom I made drool the other day, but likely to half of Eastern Europe.
(RANT: this is what sells technology. Not AI. Not surveillance tech. The ability to play Counter Strike and Super Mario.
Corporate wants you to think otherwise, but go out on the street. For every paranoid surveillance nerd out there you’ll find 20 normal people who want to have fun. AI tech is invasive and confusing. Who cares if the next machine has AI cores – the only ones who do are loud on the internet, and therein the trap lies.)
Anyhow, my kernel (6.6) lacks joypad support and something that enables box64 to work correctly. So might as well ask here – how do I recompile the same kernel with additional modules? I really want to make sure it’s actually the existing kernel I’m recompiling and the machine won’t pull stuff from the net to ‘upgrade’ and possibly break HDMI or GPU support.
6.6 for vf2 will probably be branch JH7110_VisionFive2_6.6.y_devel from here GitHub - starfive-tech/linux at JH7110_VisionFive2_6.6.y_devel · GitHub
If you don’t want to clone the whole git repo (heavy opeation), I suggest you just click Code → Download ZIP and unzip on the VF2
Then you can run
make olddefconfig
make vmlinuz -j $(nproc)
make modules -j $(nproc)
You should end up with exactly the same kernel module and images. If something doesn’t work, revert back.
Now you can try adding additional modules - instead of olddefconfig you can run menuconfig to configure the kernel features. Follow by modules and vmlinuz
1 Like
I forgot about the .config file. Take it from /boot/config-6.6.* and copy to .config in the linux folder to start with your current kernel configuration.
1 Like