[kde-freebsd] kwin and GL_OUT_OF_MEMORY

[Schaich Alonso]

On Sun, 24 Jan 2016 20:13:46 -0500
"Mikhail T." <mi+thun at aldan.algebra.com> wrote:

> On 24.01.2016 17:16, Schaich Alonso wrote:
> >> cc $(pkg-config --cflags --libs gl glu x11) NVX_gpu_memory_info.c
> > on a box with kde and it's dependencies installed.
> Ok, here it is:
> 
>     NVIDIA: API mismatch: this NVIDIA driver component has version
>     304.128, but the NVIDIA kernel module's version does not match.
>     Please make sure that the kernel module and all NVIDIA driver
>     components have the same version.
>     GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX=0
>     GPU_MEMORY_INFO_CURRENT_AVAILABLE_VIDMEM_NVX=0
>     GPU_MEMORY_INFO_EVICTION_COUNT_NVX=0
>     GPU_MEMORY_INFO_EVICTED_MEMORY_NVX=895
> 
> This is an older video card (Quadro FX 1400), so the kernel-part has to
> be older... Everything worked, though -- and even OpenGL screensavers
> are /fast/ -- except for this problem...
> > Do you have any custom xorg.conf tuning?
> The above qualifies, does not it?.. Thank you very much. Yours,
> 
>     -mi
> 
> 

All those numbers are supposed to be kilobytes, to
GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX=0 should hint your video card
has no video memory at all, or at least applications using
GL_NVX_gpu_memory_info would get the impression thereof, however a
quadro fx1400 card should have 128MB of dedicated memory.

I'm having the x11/nvidia-driver-340 on one of my boxes, and it
doesn't cause that version mismatch warning to be emited.

Are you sure the driver is properly installed? The kernel module's
version is printed when the module is loaded which can later be queried
by reviewed using dmesg, while the userspace version can be seen using
kinfocenter at Graphical Information->OpenGL->[right side]->Direct
Rendering->Driver->OpenGL/ES Version.

Poor installations of the driver can occur when /boot is a dedicated
partition and it's not mounted while the port is being installed, or
it's mounted during installation but the driver is manually loaded
(instead of a nvidia_load at loader.conf) after booting without /boot
being mounted (so the module is loaded from the rootfs' /boot copy
where there is still the previous nvidia driver). I.e. when the mount
state of /boot is different during driver installation and module load
time.

Alonso
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-freebsd/attachments/20160125/d3214df3/attachment.sig>