Hi Joe, On Sun, May 29, 2022 at 6:58 PM Joe <joe.on.list@xxxxxxxxx> wrote: > > Hi all, I'm trying to make running hardware acceleration decoding on > my old GeForce 210 (AKA GT-218, or NVA8 / NV-50 Tesla family). > ---------------------------------- > 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 > [GeForce 210] [10de:0a65] (rev a2) > ---------------------------------- > [ ... ] > > But when I touch something, for instance "f" to enlarge to fullscreen, > or "q" to quit MPV... > Surprise! > > My system freeze, nothing work again, just the mouse cursor can still > be moved around. > > [ ... ] > > I'd like to use open drivers, but I'd like to take advantage of > hardware decoding too, so that my CPU rests as quiet and fresh as > possible. Is there some other suggest to configure some other aspect > and try to achieve my scope? > Or my tests are all I can do? > So for hwdec is better to switch back to closed source nvidia driver > legacy 340.108 ? Proprietary driver will definitely work better for hwdec than nouveau. Forgetting about any stability/performance issues, there are some reference frame ordering issues in H.264 decoding that were never addressed. This leads to occasional corruption in some videos. FWIW I've mostly tested with mplayer, and I didn't run into problems there. There should be instructions on using mplayer at https://nouveau.freedesktop.org/VideoAcceleration.html. The thing you esp want to avoid is using VDPAU + GL in the same process -- so things like "-vo vdpau" are much more likely to work than "-vo gpu" or "-vo gl". You can try enabling DRI3 -- perhaps something broke in the DRI2 paths. You can add Option "DRI" "3" into the Driver section of the xorg.conf to expose it. It's not on by default because there are some annoying corner cases that some window managers run into with it (KDE as I recall). I'm also not sure why VA-API is corrupted for you, it has worked in the past. But it gets a lot of changes only reviewed by AMD developers, so it can get broken pretty easily with AMD-specific assumptions which don't hold on NVIDIA. I suspect it should be easy to fix by someone who is interested in investigating -- probably a bisect to sort out what broke it, and then revert or get the person who wrote it to fix it. Cheers, -ilia
