smarek

ok, running from "broken 5.31 upgraded to 5.38" image And running from chroot in 5.38 stable image upgraded via "apt-get dist-upgrade" So I don't think this config is an issue, both images are identical in means of CMA config

How? I already compared /boot/{armbianEnv.txt script.bin(fex) boot.cmd(scr)} and kernel cmdline (/proc/cmdline), and they show no differences.

Heads up, I've tried to completely upgrade the default 5.38 image to what repositories allow, and the video acceleration (VDPAU) did not break. Strangely there is a10disp package that on 5.31->5.38 was upgraded to now non-available version, but this is clearly not the issue, just curiosity. Also there appeared (in the upgraded image) file "/etc/X11/xorg.conf.d/80-armsoc-sun4i.conf" with some different Xorg configuration with Dri2 enabled, and "/etc/X11/Xsession.d/20vdpau-va-gl" with commented out contents (i suspect test installed, not purged xserver-xorg-video-armsoc-sun4i package). But running the upgraded and image versions side by side, I've compared Xorg outputs, and determined, there is no difference in Xorg configuration, that is responsible. There are also no additional or missing files in /etc configuration structure, that could cause the issues. Comparing /boot/armbianEnv.txt and /boot/script.bin(fex) and /boot/boot.cmd(scr) and kernel cmdline, there is no difference. So the issue must be somewhere else, and I currently don't know where to look

Not quite, stock 5.38 image works nicely (using the Armbian_5.38_Bananapi_Ubuntu_xenial_default_3.4.113_desktop.img). VDPAU works out-of-the-box (mpv from terminal automatically uses VDPAU/SUNXI correctly) Running the package comparison against stock, looks like this: We removed for production reasons a lot of "desktop" software, such as xfce, wireless tools, gtk, bluetooth, etc., which should explain, why the difference in installed packages is so extensive. But what seems curious to me is the difference in APT repositories Note the "xenial main utils xenial-desktop" vs "xenial main xenial-utils xenial-desktop" Running the "dist-upgrade" again, with repositories set to "image default" looks like this: I can clean up the "5.38 upgraded from 5.31" image and provide it to you, if you want to get hands on it for debugging. Unfortunately from what I can see there is nothing really obvious that could explain why the dist-upgrade does not work smoothly and causes such pain.

Hi, we've been running 5.31 with VDPAU support for a long time now, and I've tried to "apt-get dist-upgrade" to newer version of Armbian. With 5.31 VDPAU works well, with 5.38 all calls to vdp_imp_device_create_x11() fail with "Error when calling vdp_device_create_x11: 25" Demonstratable on "vdpauinfo" The only package, which did not get updated is mali userspace binary driver ( ii mali-sunxi-utils 1.0-1~armbian5.31+1 ) Also demonstratable with MPV Comparing the packages available in both devices goes like this (using https://github.com/lepe/scripts/blob/master/compare_ubuntu_apt.pl ) I don't really suspect added packages (debsums, iptables, socat, sshpass, etc...) of ruining the VDPAU, but I suspect the package "libdrm-common" which is linked with all the essential xserver/mali/libva-drm/libdrm/etc... packages. Removing it will want to remove all the dependencies and will essentially destroy X11 environment. There is no difference in loaded kernel modules (except for its versions), arch and the hardware is the same in testing. Debsums does not show any errors. In /var/log/Xorg.0.log there are differences, but I cannot point to anything suspicious. Armbian 5.31 Xorg.0.log http://termbin.com/sj2m Armbian 5.38 Xorg.0.log http://termbin.com/1eh5 Is there anyone experiencing the same issue? Or is this known bug for now? If I can provide more info to debug, please let me know.