If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Really? Yes well that's how I'd describe performance at this point I suppose, so I'm not surprised. Disappointed. Not surprised. I've already had to disable AGP and AccelDFS to get rid of graphics corruption under EXA ( and DRI1 ). It's hard to avoid the feeling that I'm going backwards.
Good luck, the OSS driver from git was working great last time I used it on my laptop. It was also able to play a 720p movie on my 26" screen and I was able to play tremulous at the resolution of 1920*1200 with an average of 35 fps.
Now, I'm using fglrx with my brand new HD4770. 3D performance is really great but user experience is not really good on kde4 and flash.
What has changed in the KMS code since it was included in the kernel as a staging driver? With this patch + drm-next applied over a 2.6.29 kernel I could get a 1680x1050 console at startup with my HD3850, but with the staging driver in the .31-rcX kernel I simply get 80x25 and no errors in dmesg when I select CONFIG_DRM_RADEON_KMS.
Is r6xx support going backwards? I know it's not supposed to work yet, but it seemed to be closer a month ago with the patch than right now :P
Thanks for that, I didn't think of using "clear Lock" there, will try that. (edit: nope, still screwy...)
This was all I had in my .xmodmap file:
remove Lock = Caps_Lock
keysym Caps_Lock = Escape
I seem to have terrible luck with keyboard things in X... this time it broke all my modifier keys, last time the keyboard stopped responding if I had xmodmap in my xinitrc, and the first time I used evdev years ago the keys were pretty much randomised...
That says it provides no hardware acceleration. Aside from testing purposes or curiosity, why would someone else want to use this patch? Without EXA and XV things would be pretty unbearable... The 1680x1050 screen on my laptop means a lot of pixels to shove around using just the CPU.
(Just trying to talk myself into/out of applying the patch to my 2.6.31-rc5 tree......)