-
Radxa Cubie A7A/A7Z - Allwinner a733
I found this Github repo with a driver for the GPU: https://github.com/TumRedSun/apercel I tried building it, but I have no experience building out-of-tree modules. It's not clear for me how I get the kernelbuild directory. I assume this has to match the kernel in use. https://github.com/TumRedSun/apercel#1-kernel-and-helpers Can the GPU driver be added to the images? Or can someone explain a dummy how to get the kernelbuild directory?
- NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
-
NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
Installation with Pi OS on a Pi 5 works like a charm. Performance is a bit underwhelming, but I guess that's more of an issue with the GPU driver and Proton. So far I was only able to get some games working with OpenGL. Perhaps we need someone to do some magic for the Raspberry Pi 5. Here you can see Half-Life and Steamworld Dig with Mangohud. (MANGOHUD_CONFIG=gpu_name,engine_version,fps,frametime,cpu_stats,core_load mangohud %command%) I'll try it on a Pi 4 next.
- NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
-
NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
I tried 2.2 on RPi OS. Installation goes fine, but starting steam-arm doesn't work. I also tried like this: steam-arm -no-cef-sandbox I also tried the restart options. Output of terminal attached. Anything else you need for analysis? The dmp file doesn't look human readable, but I can add it. Steam.txt
- NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
- NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
- NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
- NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
-
NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
Thanks for the quick response. I was not the GAMEUSER, so I installed as you suggested: sudo env GAMEUSER=livinglinux bash steam-arm-install.sh --keep My id number is 1002, perhaps that's causing issues? Ubuntu uses the 4k page size kernel, so I haven't tested switching kernels. Performance is underwhelming, especially compared to the RK3588. I guess we run into the limitations of the RPi5 hardware. There was one weird thing when I started using my controller in the game Half-Life. I got a popup about allowing remote interaction. On the RK3588 I got a popup about allowing access to the controller, but this seems to be the wrong popup. You can see it at around 6:50 in the video. I'm not really motivated to continue testing with the RPi5, unless we get some better performance.
-
NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
@Scrumpper I tried the new installer on a Raspberry Pi 5 running Ubuntu. The script gets busy installing a lot of things. But when I start steam-arm, I get errors. livinglinux@Pi5:~$ steam-arm /usr/local/bin/steam-arm: 43: cannot create /home/livinglinux/.local/share/steam-arm/.local/share/Steam/steamrtarm64/steam-launch-wrapper: Directory nonexistent chmod: cannot access '/home/livinglinux/.local/share/steam-arm/.local/share/Steam/steamrtarm64/steam-launch-wrapper': No such file or directory /usr/local/bin/steam-arm: 59: cannot create /home/livinglinux/.local/share/steam-arm/.local/share/Steam/steamrtarm64/streaming_client: Directory nonexistent chmod: cannot access '/home/livinglinux/.local/share/steam-arm/.local/share/Steam/steamrtarm64/streaming_client': No such file or directory /usr/local/bin/steam-arm: 215: cd: can't cd to /home/livinglinux/.local/share/steam-arm/.local/share/Steam/steamrtarm64
-
NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
Did a test on the Radxa Rock 5B RK3588. Armbian 26.8 has Mesa 26.0 and I had issues to get games working with Vulkan. Upgraded to 26.2.3 with the Persson PPA, and Tomb Raider GOTY is also working on the RK3588! https://launchpad.net/~ernstp/+archive/ubuntu/mesarc Half-Life needs OpenGL 3.2, so I started the Steam client like this: PAN_MESA_DEBUG=gl3 steam-arm Mangohud wasn't working for me, but you can use Gallium HUD for OpenGL and Vulkan Overlay. You can start games in Steam like this: GALLIUM_HUD=simple,fps %COMMAND% VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay %COMMAND% Tomb Raider GOTY Benchmark Min FPS: 15.6 Max FPS: 22.9 Average FPS: 19.7 You can see my video here:
- Gaming experience Radxa Dragon Q6A Snapdragon QCS6490
-
NATIVE ARM64 Steam Client Installer built on RK3588 board (Using the ARM64 Steam Frame's Client)
Thanks for releasing this. It's works fine on the Radxa Dragon Q6A Snapdragon QCS6490 SBC. I assume it won't work on ARM Mac, unless you added something like a micro VM, to enable running 4k page size apps in a 16k page size environment. My PS4 controller works. I skipped installing glx-lax and vk-spoof. I assume vk-spoof is for the RK3588 (and perhaps other SoCs that don't support everything needed for Vulkan). Steam overlay doesn't seem to work, and running with Mangohud doesn't seem to work either. Mangohud did work when I tested a different setup of Steam ARM Linux. Here is the result of the benchmark of Tomb Raider GOTY (1080p Normal quality). Min FPS: 18.9 Max FPS: 31.9 Average FPS: 26.7
-
waydroid
Installing Waydroid should be no problem, but you might have to activate psi. Waydroid installation. https://docs.waydro.id/usage/install-on-desktops sudo apt install curl ca-certificates -y curl -s https://repo.waydro.id | sudo bash sudo apt update sudo apt install waydroid -y Reboot and start Waydroid. Preferably from the command line, as you will see the output directly. After downloading the image, it tries to start. If you get the error "Service manager /dev/binder has died", it probably means you have to activate psi. See more details here: https://github.com/waydroid/waydroid/issues/136 TL;DR Activate psi. sudo nano /etc/default/grub Add psi=1, so the line will look like this: GRUB_CMDLINE_LINUX="psi=1" Update grub. sudo update-grub Reboot. This is a quick test to see if psi is active. It should show some numbers. cat /proc/pressure/cpu Waydroid should work now. Unless you run into a different issue than I did.
LivingLinux
Members
-
Joined
-
Last visited