My own reaction, running a 4850 with compositing enabled on a 1.6.5 Xorg server:
One DEFINITE improvement is found when switching workspace: I have 4, and at least 3 have many windows open in them...
Type: Posts; User: mitch074; Keyword(s):
My own reaction, running a 4850 with compositing enabled on a 1.6.5 Xorg server:
One DEFINITE improvement is found when switching workspace: I have 4, and at least 3 have many windows open in them...
It does solve the slow workspace switching problem. Yay!
Thank you for the explanation Bridgeman: I remember seeing something about that at the time, yes.
Could it also be the reason why switching workspace is so slow with fglrx? I have a 1-5s delay...
Ah. right after install, at what level are your desktop effect? If they're set to basic, try the level above, which should enable compositing (and enable some performance settings) for your card.
...
If you don't play high performance games: let it be like it's set up out of the box.
If you play high performance games: follow the hardware manager's suggestion.
Argh - currently, I mean:
- R800/Evergreen: barely any 2D support (I'm not even sure that has been ported to Lucid
- R600/R700: 3D support is still very experimental. 'Far as I know, 3D ships...
The Free driver shipped with Ubuntu doesn't support 2D acceleration (including compositing), and certainly not 3D. At least not when I tested it on my 4850.
Well, your card falls into the 'supported, but not completely' category of the free software driver: it can handle Kernel Mode Setting (KMS here), so you get a 1920x1200 splash screen, but it doesn't...
Should we understand your question as the fact that AMD is currently rewriting the 2D acceleration of fglrx? Not that I'm complaining, mind you; but, since there was little mention of it before, a...
Since I changed motherboard, RAM and PSU and tested them all (memtest, plugging stuff in it and loading the CPU), I would say... No.
...change Phoronix' Nexuiz benchmarks to 'Xonotic', then have all packages at all distributions switch Nexuiz to Xonotic the firt time there is a release.
I wonder how long it'll take Debian to...
Since version 9.8, I don't hame much to ask for driver features - WoW has no more graphical corruption :p ; since 9.12, I have no more problems with X.org initialization (admittedly, switching to a...
These quotes are direct lifts from http://wiki.jswindle.com/index.php/General_Wine_Troubleshooting - and they date back to april/may of 2009. Not exactly a year old, but getting there.
If...
@Kano: yes. A bit overkill, I'd say. I also guess that you need to provide flashrom with memory address and such, no? Or you may end up flashing your mobo's BIOS with a video card's.
That would...
Eventhough there may not be Linux versions of the tool, it should still work with FreeDOS.
Which would be preferable, as a real-mode OS, to access a system component's firmware anyway.
I don't think there is one.
Like I said in another post, I mixed up family names, so here it is in full glory:
- NV10 is the original Geforce256 model
- NV11 is the Geforce2 MX, a die shrink of Gf256
- NV15 is the...
Aaah, since we've got a Nouveau developer here... I thought the Mesa driver supported NV2x through NV1x compatibility mode, what's up with that?
And now it shows how much a TiNDC is required.
Ouch - I mixed these up one level.
NV1x: Geforce256, Geforce2
NV15+: Geforce4MX
NV2x: Geforce3
NV25+: Geforce4 Ti
NV30 are Geforce 5, indeed. They sport a NV2+ mode, which will be unused in...
NV20 covers the Geforce2 and Geforce4MX card families; Geforce3 and Geforce4 (not MX) are the NV30 families.
The Geforce3 added fixed function shaders acceleration over the Geforce2 (it's a...