| 1 |
Nikos Chantziaras <realnc@×××××.com> [16-01-16 03:36]: |
| 2 |
> On 15/01/16 21:50, Meino.Cramer@×××.de wrote: |
| 3 |
> >regardless how powerful a payable graphics card may be... |
| 4 |
> >if one uses the same graphicsscards for rendering as for the desktop |
| 5 |
> >the desktop starts heavily lagging/freezing just in the moment |
| 6 |
> >blenders rendering engine Cycles start working. |
| 7 |
> >At least, these are my experiences. |
| 8 |
> >Thats why I use an old just-fast-enough graphics card for the desktop |
| 9 |
> >and a second, more current one for rendering only. |
| 10 |
> |
| 11 |
> Yeah, makes sense. Which drivers are you using? NVidia's changelogs |
| 12 |
> almost always have a "fixed console switching issues" entry on every |
| 13 |
> driver release. It seems they're still haven't figured this out |
| 14 |
> completely, so the only suggestion I can give is to try more recent |
| 15 |
> drivers. |
| 16 |
> |
| 17 |
> Another thing is to test whether a text-only console vs a framebuffer |
| 18 |
> one makes any difference. Officially, nvidia only supports text mode |
| 19 |
> consoles. At least on my system, the nvidia driver prints this on dmesg |
| 20 |
> with my framebuffer console setup: |
| 21 |
> |
| 22 |
> NVRM: Your system is not currently configured to drive a VGA console |
| 23 |
> NVRM: on the primary VGA device. The NVIDIA Linux graphics driver |
| 24 |
> NVRM: requires the use of a text-mode VGA console. Use of other |
| 25 |
> console |
| 26 |
> NVRM: drivers including, but not limited to, vesafb, may result in |
| 27 |
> NVRM: corruption and stability problems, and is not supported. |
| 28 |
> |
| 29 |
> Although I have no choice in the matter really, since text mode is not |
| 30 |
> supported on my system. Fortunately it's been working without issues |
| 31 |
> for me. But text mode might solve your issue (if your system supports |
| 32 |
> that.) Or it might not :-P |
| 33 |
> |
| 34 |
> |
| 35 |
|
| 36 |
Hi Nikos, |
| 37 |
|
| 38 |
thanks for the informations! :) |
| 39 |
|
| 40 |
the drivers I use are: |
| 41 |
|
| 42 |
[I] x11-drivers/nvidia-drivers |
| 43 |
Available versions: [M]96.43.23-r1(0/96)^msd [M]173.14.39-r1(0/173)^msd 304.131(0/304)^msd 340.93-r1(0/340)^msd 340.96(0/340)^msd 346.96-r1(0/346)^msd 352.63(0/352)^msd (~)352.68(0/352)^msd 355.11-r2(0/355)^msd (~)358.16-r1(0/358)^msd (~)361.16(0/361)^msd (~)361.18(0/361)^msd {+X acpi custom-cflags +driver gtk gtk2 gtk3 +kms multilib pax_kernel (+)tools uvm KERNEL="FreeBSD linux"} |
| 44 |
Installed versions: 361.18^msd(20:30:57 01/15/16)(X driver gtk3 kms multilib tools uvm -acpi -gtk2 -pax_kernel KERNEL="linux -FreeBSD") |
| 45 |
Homepage: http://www.nvidia.com/ |
| 46 |
Description: NVIDIA Accelerated Graphics Driver |
| 47 |
|
| 48 |
|
| 49 |
Yesterday I experimented a little bit and I am quite sure, that the |
| 50 |
problem is created by X11/nvidia-drivers/kernel and the kind of the |
| 51 |
console is not the problem (read: I am not sure, though). |
| 52 |
|
| 53 |
The bugreport linked from another mail of this thread also reports, |
| 54 |
that using an older version of the nvidia-drivers will fix the |
| 55 |
problem. |
| 56 |
|
| 57 |
Best regards, |
| 58 |
Meino |
Archives