<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions" href="https://bugs.freedesktop.org/show_bug.cgi?id=92858#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions" href="https://bugs.freedesktop.org/show_bug.cgi?id=92858">bug 92858</a> from <a class="email" href="mailto:ysxikrhn@vomoto.com" title="Darren <ysxikrhn@vomoto.com>"> Darren</a> <pre>(In reply to Christian König from <a href="show_bug.cgi?id=92858#c1">comment #1</a>) > (In reply to Darren from <a href="show_bug.cgi?id=92858#c0">comment #0</a>) > > The section pasted above of the dmesg from kernel 4.3-rc-7 indicates the > > driver is failing on the "drm:r600_ringtest"...however, this is not a r600 > > card but a Southern Islands. > > Yeah, indeed the very basic test if the command process is up and running > didn't worked. Because of this the driver pretty much disables itself, > except for bringing up a picture to the screen. > > That r600_ringtest is used for a Verde is perfectly normal, we only got > r100_ringtest, r300_ringtest and r600_ringtest for the different hardware > generations. > > > Steps taken while attempting to resolve the issue: I'd initiallly thought it > > could be a firmware issue, with the linux-firmware package in the distro > > perhaps not having been updated to support the latest kernels, but even when > > I installed linux-firmware-git from the AUR to replace the standard > > linux-firmware package and then booted linux 4.3-rc7, mesa was still using > > llvmpipe instead of radeonsi, due to no GPU accel. I've also compiled the > > 4.3.0 kernel using the tarball directly from kernel.org, and a default > > kernel configuration file from ubuntu. When I booted into the 4.3.0 upstream > > kernel, GPU acceleration was still disabled. As neither the source nor the > > kernel config were from Manjaro, doesn't this rule out a distro bug and > > indicate the issue is upstream? > > Yes that sounds like somewhere between 4.1 and 4.2 a patch broke the support > for Verde. > > As far as I know we didn't changed anything related to Verde between 4.1 and > 4.2. > > Can you get the kernel source using git and then run "git bisect start v4.2 > v4.1" to figure out which patch exactly caused the regression?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>