ZimaOS 1.6.0 Beta1: Network, UI and VAAPI Findings

Bottom Line: Most of This Thread Is Beta-State Evidence, Not a List of Current ZimaOS Defects

The useful pattern is to separate display-state bugs from real subsystem failures. In 1.6.0-beta1, one tester saw stale Ethernet speed and static-IP information that corrected after reboot, plus localization and UI-control issues. Another tester documented a separate AMD VAAPI failure where the kernel driver loaded but vainfo could not initialize the userspace video driver.

French UI screenshot showing the user icon rendering problem reported in 1.6.0-beta1.

The same area in English rendered correctly, narrowing the icon issue to localization/UI state rather than a missing global asset.

ZimaOS search engine selector listing DuckDuckGo Google Bing and StartPage — The beta search-engine selector exposed a fixed set of providers; the request was for additional or custom engines.

Network UI: Verify the Link Outside the Dashboard

If ZimaOS shows 1 Gbps but the switch shows 2.5 GbE, verify the actual interface state before blaming the cable or NIC. The current ZimaOS networking guide says the Network page should show interface link speed and the assigned IP, and static-IP changes should take effect immediately.

ZimaOS network page showing a 1 Gbps Ethernet value before refresh — The network page reported 1 Gbps even though the switch had negotiated 2.5 Gbps; a reboot later refreshed the displayed value.

UniFi client panel showing the ZimaBoard 2 wired connection at 2.5 GbE — The switch-side view showed 2.5 GbE, providing an external check against the stale 1 Gbps value in the beta UI.

ZimaOS network page showing the corrected 2.5 Gbps static IP connection after reboot — After reboot, the interface showed the expected 2.5 Gbps link and the intended static IP.

The device card used a Wi-Fi-like symbol for a wired LAN connection, one of the UI consistency issues reported in the beta.

A conventional Ethernet icon was supplied as the preferred visual for wired LAN status.

That makes the beta behavior easy to classify: if the switch and OS-level interface agree but the UI is stale, it is a presentation/state-refresh problem. Current 1.6.0 release documentation also records network-card display optimizations and later fixes. See the ZimaOS 1.6.0 feature and upgrade page.

App and Storage UI Issues Were Also Visible in the Beta

The thread captured a non-working Open folder control and incomplete French translations. These are real test artifacts, but they should not be carried forward as current defects without reproducing them on a current release.

ZimaOS app data location panel with an Open folder icon that was not clickable in beta — The app data location panel showed an Open folder control that the tester reported as non-responsive in 1.6.0-beta1.

French ZimaOS storage settings with untranslated English text in the bay customization dialog — The storage customization dialog mixed French and English, documenting missing localization in the beta build.

ZimaOS 1.6 later formalized customizable storage/device visuals and login wallpapers; the current ZimaOS customization overview shows the feature after the beta period.

The AMD VAAPI Report Needs a Different Diagnostic Standard

This was not just a UI symptom. The tester showed amdgpu loaded, /dev/dri/card0 and renderD128 present, yet vainfo failed while opening radeonsi_drv_video.so. That pattern points past basic PCI/kernel detection and toward the VAAPI userspace stack.

Use libva/vainfo to verify initialization and the Mesa documentation for userspace driver context. Do not diagnose “GPU unsupported” merely because transcoding falls back to CPU.

How to Use Old Beta Feedback Today

Reproduce the exact symptom on the current build, then compare it with the current manual. Beta screenshots are evidence of what happened on that build, not permanent product behavior. The current official ZimaOS 1.6.0 release notes provide the baseline that replaced this beta.