You are not logged in.
Just thought I'd share in-case anyone else has this issue.
PROBLEM:
After upgrading to xorg-server 1.9.0 I noticed text rendering was painfully sluggish,
this effect was most noticeable in my terminals (urxvt), when drawing text from
IRC or scrolling other text output.
I found the issue discussed here:
http://www.nvnews.net/vbulletin/showthr … 563&page=4
and at the end the helpful Nvidia developer provided a fix
in Nvidia 260.19.06.
SOLUTION:
install aur/nvidia-beta (260.19.06)
which clears up the issue with nvidia slow text-rendering with xorg 1.9.0
thank the lord nvidia cares about linux users! (a little bit anyways)
Offline
If one of the Arch mods would be kind enough to sticky this and/or reference it in the IRC topic like they did AwesomeWM and Cairo-XCB, it'd be appreciated.
Last edited by ZekeSulastin (2010-10-01 02:49:16)
Offline
Beta driver is probably 1000x better. Here I was thinking that I had to find some sort of WM instead of KDE. Everything is snappy again.
Offline
https://bbs.archlinux.org/viewtopic.php?id=103716
https://bbs.archlinux.org/viewtopic.php … 51#p832851
Last edited by karol (2010-10-01 11:41:59)
Offline
Which is why THIS SHOULD BE STICKIED. It has even been said IN THAT THREAD "hmm, this might be a common enough problem to take extra steps to warn people." If we can put in the IRC topic "Hay AwesomeWM users, you're in the AUR and use Cairo-XCB" and "Qt 4.7 is coming!", we can sure as heck give a heads up that regressions can occur if you use the nvidia drivers that are fixed in the beta.
Last edited by ZekeSulastin (2010-10-01 16:24:57)
Offline
There were many things that I though should be stickied and were not. That taught me not to rely on the "managers" too much :-)
Offline
This issue was brought up in the Arch dev mailing list when discussing the Xorg 1.9 move from testing to extra. I'm not a dev and half the time I don't fully understand what's being discussed in the mailing list but over the last month I have noticed a couple of benefits to subscribing. One is that I'm beginning to catch on to some of the more technical information through osmosis. And the other is that you can get a heads up on topics like this before they actually hit.
Offline
I can't even start x with xf86-video-nv driver,I assumed that there will be no problems,because it is open source driver,but apparently I was wrong.
Offline
In order to get the nvidia-beta driver to load (and hence to start X), I had to blacklist the ahci module in rc.conf.
Offline
In order to get the nvidia-beta driver to load (and hence to start X), I had to blacklist the ahci module in rc.conf.
Why ?
Offline
+1 for a sticky
This problem affected me too albiet in a round-about way: https://bbs.archlinux.org/viewtopic.php?id=105972
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I am having frequent Xorg crashes with the Nvidia beta driver. For instance, if I run Unetbootin or Skype is crashes as soon as I launch them. I figure this may be a combination of Xorg 1.9, Nvidia-beta, and qt 4.7.0-2.
I am beginning to think that this is because I have three monitors and dual cards.
╔═ comhack@Venus 11:13 AM
╚═══ ~-> lspci | grep VGA
03:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9500 GT] (rev a1)
04:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9500 GT] (rev a1)
Also, I am running XMonad 0.9.1-8 and 64bit Arch if it helps.
Does anyone know when an update is coming to fix these issues?
Last edited by securitybreach (2010-10-06 15:22:43)
"Every normal man must be tempted at times to spit upon his hands, hoist the black flag, and begin slitting throats." -- H.L. Mencken
Website Configs
Forum Admin: Bruno's All Things Linux
securitybreach<a>archlinux.us
Offline
i'm using also the nvidia beta driver, and appears some little white dots while mplayer is running a movie (even if it paused) in the background.
Arch64/DWM || My Dropbox referral link
Offline
Also, after rebooting the nvidia module is not found and I have to reinstall version 256. Then reinstall Nvidia-beta in order for the module to be recognized.
Last edited by securitybreach (2010-10-07 00:24:06)
"Every normal man must be tempted at times to spit upon his hands, hoist the black flag, and begin slitting throats." -- H.L. Mencken
Website Configs
Forum Admin: Bruno's All Things Linux
securitybreach<a>archlinux.us
Offline
Am I the only one who do not notice any kind of "regression" ?
Offline
While the severity of the problem is alleviated with the nvidia 260.19.12 driver, I found it to be not solved.
X still uses almost a full core some time into the session.
Does anyone else still experience problems?
(and I had to blacklist nouveau in order to get it running)
Last edited by mschu (2010-10-19 23:11:18)
Offline
While the severety of the problem is alleviated with the nvidia 260.19.12 driver, I found it to be not solved.
X still uses almost a full core some time into the session.Does anyone else still experience problems?
(and I had to blacklist nouveau in order to get it running)
I think you always need to have nouveau blacklisted to run nvidia drivers.
Offline
Well I removed the beta driver and installed 260.19.12-1 and everything seems back to normal so far.
"Every normal man must be tempted at times to spit upon his hands, hoist the black flag, and begin slitting throats." -- H.L. Mencken
Website Configs
Forum Admin: Bruno's All Things Linux
securitybreach<a>archlinux.us
Offline
I've never tried the beta release but 260.19.12 seems to be working fine.
oz
Offline
260.19.12 *WAS* the beta release until yesterday
Offline
Everything was fine with the beta. Changed over to the *stable* and now my GPU clock seems stuck at its lowest possible setting. GTS 360M. Not a huge deal really as I don't game or anything, but I guess it's time to once again dial back compositing.
Offline