Just because I came across this. I've been told for a bug report by an ATI guy to activate debug output. This is done by changing DRM_DEBUG_CODE in the source code. The attached patch does this, if USE flag debug is activated. I also included a small info in the ebuild, that it only spits out debugging messages if the kernel module has been reloaded afterwards. Patches are against ati-drivers-8.42.3, but they should apply to older ebuild as well. Reproducible: Always
Created attachment 135962 [details, diff] ati-drivers-debug-ebuild.patch Patch for the ebuild.
Created attachment 135964 [details, diff] ati-drivers-debug.patch Activates debug output in the source code. I think this can go in ati-drivers/files and doesn't need to go in ati-drivers/files/${PV}
(In reply to comment #2) > Created an attachment (id=135964) [edit] > ati-drivers-debug.patch > > Activates debug output in the source code. > I think this can go in ati-drivers/files and doesn't need to go in > ati-drivers/files/${PV} > This can be done via sed no need for the patch.
(In reply to comment #3) > (In reply to comment #2) > > Created an attachment (id=135964) [edit] > > ati-drivers-debug.patch > > > > Activates debug output in the source code. > > I think this can go in ati-drivers/files and doesn't need to go in > > ati-drivers/files/${PV} > > > > This can be done via sed no need for the patch. > True, forgot that.
Created attachment 136684 [details, diff] ati-drivers-debug-ebuild.patch New patch for the ebuild, now using sed, which makes the patch for firegl_public.c obsolete.
Created attachment 136687 [details, diff] ati-drivers-debug-ebuild.patch Sorry, the previous patch wouldn't work, I forgot to put debug in IUSE.
Created attachment 136847 [details] ati-drivers-debug-ebuild.patch with correct path. Corrected path, sorry. ;)
8.433 is in the tree
