Hello,
On Sat, 04 Apr 2020, Andrew Udvare wrote:
>> On Apr 4, 2020, at 00:59, Dale <rdalek1...@gmail.com> wrote:
>> tu...@posteo.de wrote:
>>> I have discussed this on www.blenderartists.org and they asked
>>> me to ask here to sort out, whether the problem is a Blender-thing,
>>> a Linux-thing or a GENTOO-thing.
>>>
>>> My setup is as follows:
>>> NVidia RTX 2060 SUPER
>>>
>>> NVidia-drivers:
>>> [I] x11-drivers/nvidia-drivers
>>> Available versions: (~)304.137-r1(0/304)^md[1]
>>> (~)340.107-r2(0/340)^md[1] 340.108(0/340)^mtd (~)375.82-r2(0/375)^md[1]
>>> (~)378.13-r5(0/378)^md[1] (~)381.22-r3(0/381)^md[1]
>>> (~)384.130-r1(0/384)^md[1] (~)387.34-r1(0/387)^md[1]
>>> (~)390.77-r1(0/390)^md[1] (~)390.87(0/390)^md[1] 390.132-r1(0/390)^mtd
>>> (~)390.132-r2(0/390)^mtd (~)396.24-r2(0/396)^md[1]
>>> (~)396.24.10-r1(0/396.24)^md[1] (~)396.45-r1(0/396)^md[1]
>>> (~)396.51-r1(0/396)^md[1] (~)396.51.02(0/396.51)^md[1]
>>> (~)396.54(0/396)^md[1] 430.64-r1(0/430)^mtd 435.21-r1(0/435)^mtd
>>> 440.64(0/440)^mtd {+X acpi compat +driver gtk3 +kms +libglvnd multilib
>>> pax_kernel static-libs +tools uvm wayland ABI_MIPS="n32 n64 o32"
>>> ABI_RISCV="lp64 lp64d" ABI_S390="32 64" ABI_X86="32 64 x32" KERNEL="FreeBSD
>>> linux"}
>>> Installed versions: 440.64(0/440)^mtd(03:03:25 AM 04/03/2020)(X driver
>>> kms libglvnd static-libs tools uvm -acpi -compat -gtk3 -multilib -wayland
>>> ABI_MIPS="-n32 -n64 -o32" ABI_RISCV="-lp64 -lp64d" ABI_S390="-32 -64"
>>> ABI_X86="64 -32 -x32" KERNEL="linux -FreeBSD")
>>> Homepage: https://www.nvidia.com/
>>> Description: NVIDIA Accelerated Graphics Driver
>>>
>>> Blender 2.82a (stable) and
>>> Blender 2.83 (deveoper build)
>>>
>>> The NVidia RTX-cards offer a new feature called "Optix" which blender
>>> can use to speed up rendering and denoising.
>>>
>>> When Blender is started one choose "Optix" from the user
>>> Preferences->System tab and then the Optix-enabled devices of the
>>> system in question are shown.
>>> There is a similiar tab, if you want to use CUDA instead.
>>>
>>> The CUDA tab shows my graphics card and everything behaves as
>>> exsoected. Choosing "Optix" instead says "No Optix enabled
>>> device".
>>>
>>> Which is not quite right, since the RTX-cards are Optix enabled.
>
>I suggest filing a bug about this regarding the nvidia-drivers
>package. It's possible it's not installing the necessary files.
Looking at the ebuild, it seems that it only installs libnvoptix when
multilib enabled is *and* if it's on amd64:
==== x11-drivers/nvidia-drivers/nvidia-drivers-440.64.ebuild ====
if use kernel_linux && has_multilib_profile && [[ ${ABI} ==
"amd64" ]];
then
NV_GLX_LIBRARIES+=(
"libnvidia-cbl.so.${NV_SOVER}"
"libnvidia-rtcore.so.${NV_SOVER}"
"libnvoptix.so.${NV_SOVER}"
)
fi
====
And that's the only occurrence of optix in the ebuild. In driver,
there's only a 64-bit libnvoptix.so.440.64 included, it's missing from
the ./32 subfolder, so I guess that optix stuff it's 64bit only.
But that dep on has_multilib_profile seems buggish to me. Test /
workaround: Just add 'multilib' to your package.use flags of
x11-drivers/nvidia-drivers (and _do not set_ e.g. abi_x86_32), just
switch on the 'multilib'. If that works and libnvoptix.so is then
installed and Blender works with it, I'd say it's a bug that those
libs should only be installed with multilib on. My guess is, that the
intent and/or right way would be to just omit that multilib dep. Apart
from other useflags that could be used. I.e. it should be:
====
if use kernel_linux && [[ ${ABI} == "amd64" ]];
then
NV_GLX_LIBRARIES+=(
"libnvidia-cbl.so.${NV_SOVER}"
"libnvidia-rtcore.so.${NV_SOVER}"
"libnvoptix.so.${NV_SOVER}"
)
fi
====
HTH,
-dnh
--
printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?\n");
linux-2.2.16/drivers/char/msp3400.c
