1 |
Alan McKinnon <alan.mckinnon@×××××.com> [14-04-14 17:23]: |
2 |
> On 14/04/2014 15:50, Walter Dnes wrote: |
3 |
> > On Mon, Apr 14, 2014 at 05:20:12AM +0200, meino.cramer@×××.de wrote |
4 |
> > |
5 |
> >> was updated and I installed Linux 3.12.17 (vanilla) and recompiled |
6 |
> >> the nvidia-drivers and finally the X11-modules, a really annoying |
7 |
> >> thing happened: |
8 |
> >> |
9 |
> >> When a program uses the screen overlay technique (right word???) to |
10 |
> >> display (mainly) videos (me-tv, flashplayer, Blender while rendering) |
11 |
> >> ANY and everything on any desktop, which has a black background (mutt, |
12 |
> >> urxvt to only name a few) displays the video even the video |
13 |
> >> application runs on a different desktop. |
14 |
> >> |
15 |
> >> Handling the desktops then becomes a masterpieces of focus and |
16 |
> >> counting.... ;) |
17 |
> >> |
18 |
> >> I am using openbox, nvidia-drivers, linux 3.12.17 vanilla, me-tv, |
19 |
> >> flashplayer, blender (daily build taken from blenders buildbot). |
20 |
> >> |
21 |
> >> What can I do to get rid of this effect? |
22 |
> > |
23 |
> > This seems to be a common problem with nvidia video cards using the |
24 |
> > nvidia binary blobs. I ran into it some time ago. If you don't want to |
25 |
> > get rid of the nvidia card, try the Nouveau open-source drivers. You |
26 |
> > won't get all the acceleration that the Nvidia binaries provide, but at |
27 |
> > least you probably won't get the problems you have now. |
28 |
> > |
29 |
> |
30 |
> +1 to this |
31 |
> |
32 |
> The nvidia blobs do work well as long as you use them the way they were |
33 |
> intended to be used. |
34 |
> |
35 |
> The way they were intended to be used is the same way Windows uses them, |
36 |
> the Linux and Windows drivers share the bulk of the internal code and |
37 |
> Linux feature set most definitely is not the driving force here :-) |
38 |
> |
39 |
> Which means some awesome things the X server can do simply do not work |
40 |
> with the blob. The blob also rips out most of the OpenGL and framebuffer |
41 |
> code and replaces it with it's own mysterious black magic, this can add |
42 |
> more wrinkles. |
43 |
> |
44 |
> And finally, the Nvidia blob is not at all integrated with the kernel in |
45 |
> any meaningful way, so your running kernel usually ends up 2-4 versions |
46 |
> behind current. |
47 |
> |
48 |
> |
49 |
> -- |
50 |
> Alan McKinnon |
51 |
> alan.mckinnon@×××××.com |
52 |
> |
53 |
> |
54 |
|
55 |
Hi, |
56 |
|
57 |
thanks for the advice. Sine Blender is heavily using CUDA and the |
58 |
nvidia card to render (cycles), I have to use nvidia-drivers, |
59 |
nvidia-settings and the nvidia-cuda-toolkit. |
60 |
|
61 |
So I want to step back one release of the drivers, because that had |
62 |
worked fine for me. |
63 |
|
64 |
Older ebuilds fo nvidia-drivers are provided...but why all older |
65 |
ebuilds except for the newest one of nvidia-settings and |
66 |
nvidia-cuda-toolkit are wiped off my harddisc as soon I have upgraded |
67 |
to a (for me) not wirking nvidia-driver-ebuild? |
68 |
|
69 |
Any chance to go back or ma I urged to live with described |
70 |
"""features""" or to quit blender and use the noveau-drivers? |
71 |
|
72 |
Best regards, |
73 |
mcc |