[Mesa-dev] [Bug 104820] White screen in SDDM after upgrade to latest padoka

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=104820

Tapani Pälli <lemody at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|NOTOURBUG                   |---
             Status|RESOLVED                    |REOPENED

--- Comment #3 from Tapani Pälli <lemody at gmail.com> ---
(In reply to Robert Wahlstedt from comment #2)
> Hello, thank you for this feedback. Your computer is using software
> rendering fallback instead of hardware acceleration. This is because no path
> could be found. This appears to be a common theme across many threads.
> Padoka is labeled in Ubuntu PPA as beta software. These guys have claimed to
> find a resolution procedure.
> https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-
> source-amd-linux/913600-recommended-install-process-for-xubuntu-16-10-rx480-
> radv-vulkan 
> 
> This happens because the default xv acceleration is no longer available when
> using AIGLX (because everything is being drawn through textures on the 3D
> unit). I haven't seen this problem on NVIDIA cards using the more recent
> binary drivers (they seem to still have an accelerated xv) but the open
> source ATI drivers have a similar problem (very buggy xv when using AIGLX)
> as do the Intel drivers. AIGLX was only used in the short period of time
> when open drivers weren't capable of redirected direct rendering. DRI2 then
> made that possible, making AIGLX obsolete.
> 
> Therefore I am labeling this error as incomparable video drivers and marking
> this issue as resolved.

Robert, can you explain how did you come to that conclusion? Xorg.0.log
attachment shows that glamor is used, DRI driver loads fine and according to
glxinfo HW renderer is being used. AFAICT this bug has nothing to do with xv
acceleration or with radv vulkan. In fact I cannot see anything that would
prove that this is not our bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180129/fcc331bf/attachment-0001.html>