Alex Deucher wrote:
On Tue, Nov 17, 2009 at 12:55 AM, Dave Witbrodt
wrote: Apart from corruption on the XDM login window (which occurs with and without acceleration), I have had no bugs or negative issues yet. I haven't tested it much -- windows can be slid with the mouse very rapidly without leaving long trails; DOSBox plays my favorite old game without sound glitches (graphics seem quicker, but haven't played with settings yet); prboom doesn't bog down so much -- but I'm already liking it. The visual aspects of my desktop machine haven't been this responsive since the proprietary NVidia driver went away (with the dead card this past summer). I need to make a slight correction here. Before my GeForce 7950GT died, I was running the 'nvidia' proprietary driver. Two of the applications I mentioned above, 'prboom' and 'dosbox', could be configured to use OpenGL -- and with 'nvidia' that produced the most satisfying visual results and peformance.
When the GeForce died, I replaced it with a Radeon X1650Pro I had lying around. After about a month, replaced that with my current card, a Radeon HD 4850.
With the X1650Pro, I had switched to 'radeonhd'. Both of those apps would not run while configured to use OpenGL, so I reconfigured them to default output options. I forgot that I had disabled OpenGL with those programs.
Just now, as an experiment, I reconfigured both apps to use OpenGL. What a trip! They are both totally unusable: 'prboom' looks like it was designed by someone tripping on acid, with the walls (and enemies) a colorful mess and random-colored dots; 'dosbox' just gives me a motionless field of randomly-colored dots. Nothing can really be done with 'dosbox' under the circumstances, but you can sort of "play" 'prboom': the enemies appear as moving rectangles of colored dots, as do their shots. It's sort of like the third Matrix movie, when Neo had his eyes burned out but could still "see" -- just less orangish, and more greens, blues, and reds! ;)
I take it OpenGL support is not there yet?
GL works fine for most apps. You might try a newer version of mesa as the 3d drivers are part of mesa. If that doesn't help, file a bug: https://bugs.freedesktop.org
Well, I had just finished building DEBs of Mesa from git, up to date as of Nov. 15, so that I could get r600 DRI and 2D/3D support with radeonhd! ;) I even had a problem with RV770 registers not being supported, and you pointed me to a fix you had just committed to the git repo:
Hmm, thanks for the info. Looks like commit #37676b39... is the fix?
Yes.
Alex
Anyway, I would like to report a bug on Mesa about OpenGL support not quite working on my Radeon HD 4850. I have read the "FreeDesktop Bugzilla User's Guide" and have created an account there. Before I report a bug, can you give me some advice? 1. The OpenGL corruption looks different on "radeon" versus "radeonhd". Should I provide screenshots of applications with OpenGL disabled (no corruption) and OpenGL enabled (with corruption)? If so, should I provide screenshots of corruption with both "radeon" and "radeonhd" (since it appears somewhat different)? 2. I have made some fullscreen screenshots already, but my desktop is 1920x1200 and the resulting files were rather large: between 600KB and 3.5MB. Is there a rule about not posting attachments that are too large, or a limit on the size of attachments? 3. Should I make an effort to identify bugs that might be related, or should I leave that to the developers? (I have already looked around, and haven't seen anything particularly similar to my problems, but my search was far from exhaustive.) Thanks for your help, Dave W. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org