Nvidia 334.21 Repainting issue

jameh0 · 2014-03-24 20:21:32

I'm experiencing an incredibly annoying bug after upgrading to nvidia 334.21 where my screen will not repaint itself until I force it to, e.g. by moving a window, hovering over elements.

This happens in all of my applications and WM dialogs afaik.

I'm using a two-nvidia card setup with bumblebee allowing me to switch between them.

~ -> lspci | grep VGA
02:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9600M GT] (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400M] (rev b1)

The integrated card (9400m) is the one I run my window manager with. I can launch applications with my 9600m using `optirun`.

I want to rollback to a working driver, but here is what I've run into:

If I

pacman -U

an older version of the nvidia driver from my /var/cache, I am unable to login, and looking at my logs, it seems to be related to libEGL, that I understand moved or something in recent drivers.

If I download the nvidia driver from nvidia, installation yields the same result as above - namely slim login manager fails to log me into my session.

Does somebody know what's up? How should I proceed if I want to restore a working state nvidia driver?

Last edited by jameh0 (2014-03-24 20:22:38)

wombatz · 2014-04-13 09:34:47

Hello,

I have the same issue with the 9400M (same setup as yours).

There don't seem to be a solution to this. Here it's said that the problem does propably not apply with the 319 drivers, but they are outdated: https://devtalk.nvidia.com/default/topi … /?offset=1

Btw: How did you properly setup your bumblebee setup? when i screen with the 9400m and run glxgears via optirun the frames per second are horrible. propably a third or a quarter of what is possible when i screen with the 9600m gt directly.

EDIT:
trying lts kernel (3.10) at the moment - no repainting issue for now. i'll have a further look into this.

EDIT2:
nevermind. problem still there. even with the 9600m gt enabled

Last edited by wombatz (2014-04-13 11:17:47)

jameh0 · 2014-04-15 00:03:38

I found that this issue only happens when I use Openbox.

The current nvidia versions still cause problems for me with Openbox, however switching to KDE with KWin fixes the issue for me. So this is my workaround for now.

Bumblebee

 ~  ~> cat /etc/bumblebee/bumblebee.conf | haste

http://hastebin.com/novucikabi

 ~  ~> cat /etc/bumblebee/xorg.conf.nvidia | haste

http://hastebin.com/decebuligo

Enable bumblebeed.service. Also, I am booting via EFI Stub, and when I boot with emulated BIOS + GRUB, bumblebee does not detect my 9400m card.

Do you get the correct cards from glxinfo?:

 ~  ~> glxinfo | grep renderer                                                                                                                                                                                     
OpenGL renderer string: GeForce 9400M/integrated/SSE2
 ~  ~> optirun glxinfo | grep renderer                                                                                                                                                                             
OpenGL renderer string: GeForce 9600M GT/PCIe/SSE2

My performance with glxgears is:

 ~  ~> optirun glxgears                                                                                                                                                                                            
2346 frames in 5.0 seconds = 469.142 FPS
2347 frames in 5.0 seconds = 469.331 FPS
2387 frames in 5.0 seconds = 477.212 FPS

I don't know how this compares to when I have 9600m running the whole screen. Are these similar to your values?

Last edited by jameh0 (2014-04-15 00:04:33)

wombatz · 2014-04-15 06:40:36

yes the results are comparable to mine. i thought you found the holy grail here :-D but i think this is kind of inefficient. we have more performance with the 9400m than using optirun with the 9600m gt :-P
at the moment i switch the gpu at the bootloader (option1: 9400m screening w/ powered down 9600m gt and option2: both enabled and 9600m gt screening) - with lxdm as display manager i also can logout and in again without a corrupted screen when i use the 9400m.

about the repainting problem... as i read others also have this. it should have something to do with our window manager. are you using gnome or cinnamon? if so we should have to wait for a new version of clutter.
EDIT: just read that you use openbox - sorry

the driver shouldn't be the problem here (although nouveau users don't have this issue?) - but that's also my first thought everytime.

did you try to remove everything nvidia related with pacman -Rdds nvidia nvidia-libgl.......?

Last edited by wombatz (2014-04-15 06:47:44)

jarfbarker · 2014-04-16 16:14:30

I'm having the same issue here, from what I can tell from your description. Currently using Gnome 3.12. All Nvidia drivers after 331.49 make Gnome basically unusable. You can downgrade to 331.49, but you will need to downgrade all of the following packages.

nvidia-331.49-1-x86_64.pkg.tar.xz
nvidia-utils-331.49-1-x86_64.pkg.tar.xz
nvidia-libgl-331.49-1-x86_64.pkg.tar.xz
opencl-nvidia-331.49-1-x86_64.pkg.tar.xz
mesa-10.0.3-1-x86_64.pkg.tar.xz
linux-3.13.8-1-x86_64.pkg.tar.xz
linux-headers-3.13.8-1-x86_64.pkg.tar.xz

Unfortunately, sticking with 331.49 also means sticking with 3.13 kernel.

See also:
https://bbs.archlinux.org/viewtopic.php?pid=1403666

Arch Linux

#1 2014-03-24 20:21:32

Nvidia 334.21 Repainting issue

#2 2014-04-13 09:34:47

Re: Nvidia 334.21 Repainting issue

#3 2014-04-15 00:03:38

Re: Nvidia 334.21 Repainting issue

Bumblebee

#4 2014-04-15 06:40:36

Re: Nvidia 334.21 Repainting issue

#5 2014-04-16 16:14:30

Re: Nvidia 334.21 Repainting issue

Board footer