ZimaOS beta 1.6.0-beta1 - Feedback

Insight & Feedback ZimaOS Open Beta
1

Hi Zima Team,

here are some feedback on my side.

  1. Icon issue for user : when I am in french, icon is not well displayed but in english it ok. ZimaOS 1.5.4 was ok

    image

    image

  2. need more search browser : Qwant, Lilo, Brave Search … it should be possible to add new ones manually

    image
    image655×236 13.4 KB

  3. IPv6 address : I have IPv6 DHCP enabled in parameters and on my unifi network, it should be nice to have all IPv6 address like for IPv4 or indication if there is none

    image
    image662×264 7.41 KB

  4. wrong ethernet speed : on my unifi switch, my zimaboard is on 2.5Gbps but only 1Gbps in UI. After rebooting the zimaboard, 2.5Gbps appears. It should update info without rebooting system.

    image
    image392×241 10.1 KB

2
  1. display manual ethernet connection : even if I have configured ethernet to manual IP address (192.168.1.95), it still shows DHCP with old IP (192.168.1.94). After rebooting zimaboard, right static IP appears. It should update info without rebooting system.
    image
    image671×117 3.71 KB
  2. icon for LAN : if LAN is connected, it should not show a wifi icon (like for WLAN)imageimage
  3. open folder links doesn’t work : we can’t click on the Open folder link (on right side)
    image
    image648×281 10.7 KB
  4. missing translations : need of some translations in french in storage
    image
    image874×637 71.5 KB
  5. SSH with HTTPS connection to ZimaOS doesn’t work : there is a SSL error connection, but if I go back to HTTP, SSH connection is available

Here is my first feedback, thanks for helping.

1 Like
3

Hi,

Since installing the beta I have been unable to transfer files from a usb connected drive. I get a message stating that I have reached the limit of 4 drives allowed for the free version and that I have to upgrade to the pro version. When using the stable version there was no problem transferring files. I have the pro version installed on a different nas so I can’t afford to buy another one. Why the change?

Regards, Peter.

4

I too lost my Plus license when I updated to 1.6.0-beta1, because it changed my DC (Device Code?).

Per a similar issue in another thread, I sent an email to community@icewhale.org to get a new license code.

I tried using the Contact Us support page, but it fails to send the message. I also sent emails to lauren @zimaspace.com, who sent the “Welcome to ZimaOS Plus” email, and to support @icewhale.org, but received nothing from them, yet. I understand this is all happening on a weekend, so we’ll see how long this takes.

Lessons Learned: In Settiings > General > Developer mode, UNCHECK “Join the Beta experience”. Duh.

Regards, Doug

5

ZimaOS beta 1.60-beta1 is much better than 1.54. I had made a ZimaPool, and I was populating it with directories. When I tried to set each as SMB shares the GUI choked. As soon as I updated to 1.60-beta1 the SMB change was easy using the GUI.

The simple visual change and main screen are better and make better sense.

LOVE IT!

1 Like
6

ZimaOS 1.6.0-beta1 – AMD VAAPI (radeonsi) broken on Kernel 6.12.25

Summary

After updating to ZimaOS 1.6.0-beta1 (Kernel 6.12.25), AMD GPU hardware acceleration via VAAPI is no longer working.

The AMD kernel driver (amdgpu) loads correctly, but the VAAPI driver (radeonsi) fails to initialize.

System Information

  • ZimaOS version: 1.6.0-beta1

  • Kernel: 6.12.25

  • GPU: AMD Barcelo (Ryzen 5000 iGPU)

  • VA-API version: 1.22.0

Problem Description

vainfo fails with the following error:

libva info: Trying to open /usr/lib/va/radeonsi_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error)

What Works

  • amdgpu kernel driver is loaded correctly:

    lspci -k | grep -A 3 VGA
→ Kernel driver in use: amdgpu

  • DRM devices are present and accessible:

    /dev/dri/card0
/dev/dri/renderD128

  • Permissions are correct (even world-readable on render node)

What Does NOT Work

  • VAAPI initialization fails completely

  • vainfo fails with both:

    • /dev/dri/card0

    • /dev/dri/renderD128

  • Forcing driver does not help:

    export LIBVA_DRIVER_NAME=radeonsi
vainfo --display drm --device /dev/dri/renderD128
→ still fails

Impact

  • Hardware video acceleration is not working

  • Plex / Jellyfin hardware transcoding is not usable

  • System falls back to CPU transcoding → higher power consumption and lower performance

Likely Cause

This appears to be a Mesa / VAAPI compatibility issue with Kernel 6.12.25:

  • radeonsi_drv_video.so is present but fails to initialize

  • Kernel is newer than userspace stack (Mesa/libva mismatch)

Expected Behavior

  • vainfo should list supported codecs (H264, HEVC, etc.)

  • VAAPI should initialize successfully

  • Hardware transcoding should work

Suggested Fix / Direction

  • Update or rebuild Mesa (mesa-va-drivers) to match Kernel 6.12

  • Ensure radeonsi VAAPI driver is compatible with current kernel

  • Verify firmware compatibility if needed

Additional Notes

  • Power (watt) monitoring improvements in this version are working correctly

  • The issue seems isolated to the video acceleration stack, not the kernel driver itself

Conclusion

This looks like a userspace (Mesa/VAAPI) incompatibility introduced with the new kernel.

Fixing this would restore AMD GPU hardware acceleration and significantly improve media server performance.

Thanks!

1 Like
7

Same her Support page only error Message and on email no nothing yet too. I have paid for lifetime not for onetime use.

8

Please contact community@icewhale.org; we usually respond within 24 hours.

9

Please add snapshots this time to the built in backup app.

1 Like