Solved AMD VAAPI regression for Leia 18.5
#61
I switch off my desktop PC every night. The problem occurs 2 days long until i revert back linux-fimware, so I a sure update was applied.
And yes, after go back with synaptic, you have to warm - reset your linux to load original (linux-firmware is loaded by kernel at start).

Look at here : https://launchpad.net/ubuntu/+source/linux-firmware
My Mint is based on Ubuntu bionic beaver. The update 1.173.15 came at Ubuntu repo at february the 27th.
I think boths update (linux-firmware and Leia 18.6) came on my Mint update system the same day (march the 1rst). That why i had first thinking a Leia 18.6 problem.

Amd stuff upgrades are so neglected at my eyes that now i look for each comma of upgrade from there side, it's becoming CATASTROPHIC !! ( no more regression tests). They pushes the updates and voila !!!
I think we can change the tittle of tread to "Tips an tricks for Amd Graphics Bugs"  Blush
Reply
#62
I've tested today on my Ubuntu test disk. Linux firmware 1.173.15 breaks VAAPI too. 
I have revert to 1.173.12 and all is fine. So problem is located between 1.173.12 and 1.173.15.
Reply
#63
I've just tested linux-firmware fresh new 1.173.16 , it breaks VAAPI too...
Revert to 1.173.12 again.
It's starting complicated using AMD GPU, 2 bugs remaining (mesa  and  linux-frmware)
This WE i'll try to post boths bugs at Ubuntu's launchpad.
Reply
#64
A ticket was opened here for linux-firmware bug:  https://bugs.launchpad.net/ubuntu/+sourc...ug/1865130 (not by me) on 2020-02-28.
Still not solved...
I have post my identical case, wait and see ... pipeline is longggggggggg
Reply
#65
mesa problem reported at :
https://bugs.launchpad.net/ubuntu/+sourc...ug/1867188
Wait and see
Reply
#66
Linux-firmware just corrected today , status  proposed:

https://launchpad.net/ubuntu/+source/linux-firmware

But Mesa - bob bug still remaining, no progress there Confused
Reply
#67
Still nothing ATM. Work in progress.... pipeline .....
Reply
#68
This comment is for Mesa - bob problem. Linux-firmware correction was finally going out to release
Reply
#69
(2020-04-10, 17:35)enigma7 Wrote: This comment is for Mesa - bob problem. Linux-firmware correction was finally going out to release

The bob fix is in the queue for Mesa 20.0.5. Mesa is on a 2 week release cycle for bug fix releases. 20.0.5 is scheduled for next Wednesday. At this point, it's up to Ubuntu to bump to 20.0.5 when it's released or pull in the fix to their package.
Reply
#70
A proposed fix 20.0.4-2ubuntu1 is going out for Fossa and is working. But fix for Bionic is planned for .. june now  ..... pipeline, what a mess at Mesa!!!!
Reply
#71
(2020-04-17, 17:21)enigma7 Wrote: A proposed fix 20.0.4-2ubuntu1 is going out for Fossa and is working. But fix for Bionic is planned for .. june now  ..... pipeline, what a mess at Mesa!!!!

Mesa doesn't do the packaging for Ubuntu. They've fixed the problem, and backported to their stable 20.0.x branch. No need to bother upstream mesa anymore. They've done their fix and are not responsible for Ubuntu. Ubuntu does the packaging of the drivers for Ubuntu.
Reply
#72
Mesa 20.0.4-2 proposed here https://launchpad.net/ubuntu/+source/mesa for Ubuntu bionic ... seems to work.
Reply
#73
I've got mesa 20.0.8 update for bionic LTS today that solve the bob interlacing problem. 5.5 months of waiting time to solve the issue, impressive log time.. Mesa and Ubuntu haven't react in time Sleepy
Reply

Logout Mark Read Team Forum Stats Members Help
AMD VAAPI regression for Leia 18.50