Matthias Hopf wrote:
On Nov 24, 09 19:53:04 -0500, Dave Witbrodt wrote:
[drm:r600_cp_dispatch_texture] *ERROR* Invalid destination offset Some Googling revealed that you have fixed this in xf86-video-ati in October (commit 5f84636...). My Debian Sid version of "radeon" is 6.12.3
radeonhd shouldn't be affected from that, as we never stored more than the mapped memory in any structure. First thing I tried when I got home was to copy my working "radeonhd" config to xorg.conf, restart X, and run the apps I'm using to test OpenGL. With OpenGL enabled, 'prboom' runs perfectly with "radeon" but has *massive* screen corruption with "radeonhd" (along with spamming dmesg and kern.log with
[drm:r600_cp_dispatch_texture] *ERROR* Invalid destination offset
Ok, then we have some regression, maybe due to the ioctl rework in DRM. We haven't touched the drm code in radeonhd since then, heck, I didn't even have the time to *ever* test r6xx 3D support :-(((
But I very much believe that it is NOT the memory size issue that has been fixed in radeon in commit 5f84636, just it has the same effect.
Thanks for testing!
Let me know if there is more that I can do.
I assumed that the fix provided by Alex for #24301 (commit 5f84636...) was the commit that caused "radeon" to work correctly with OpenGL for me. However, I do not know that for a fact... and could only determine which commit, or combination of commits, fixed "radeon" for me by doing a 'git bisect' between 6.12.3 and commit 3a1a8b7 on Nov. 23.
This might help, but not necessarily. So I don't want to ask you to do this, given that I won't have time to look into this in the short term. I'll come back to you if we still need it.
OK... I offered! ....
running "radeonhd" instead of "radeon" at the moment. How would you like me to proceed? Shall I:
- file a bug report on radeonhd?
A bug report would be appreciated - so the issue is documented. Probably mostly copy-and-paste from the mails. Could be there is already a bug for this issue, but I consider your tests the best so far. Please document all driver versions (git commit ids or released versions) you tested.
http://bugs.freedesktop.org/show_bug.cgi?id=25309 My apologies on the size of the 4 attached screenshots. My screenshot app had made PNG files, which were 600KB - 4.5 MB in size. I had never used imagemagick 'convert' before, and was quite satisfied when the first 3 images became smaller than 1 MB after conversion to JPG. But Bugzilla rejected my 4th screenshot: no non-patch attachments larger than 1 MB allowed, and the JPG was 1.010 MB. After a quick reading of the documentation for 'convert', I discovered the "-quality" option. Using "-quality 60" made the 4th screenshot 1/10 the size in bytes of the original PNG. By then I had already attached the first 3 shots! (They could be made much smaller, without seriously impacting image quality.) Upon request, I can resubmit those first 3 images... now that I have read a little about 'convert'. HTH, Dave W. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org