XCB crash while Video Rendering in multithreded application
I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0
Following is the back trace of the multi-threaded program I am working on:
**************************************************************************************************** *******************
Please suggest the resolution.
Last edited by Don Cragun; 01-21-2015 at 05:40 PM..
Reason: Add CODE tags.
Does anyone know why Fonts and most Graphics in KDE and Gnome are rendered rather badly. There are some text editors in KDE where the font is just horrible as far as legible.
Any links or knowledge on this topic would be grealy appreciated.
A Huge Unix/Linux Fan
Gregg (2 Replies)
Hi everyone.
I made a program which renders a 3D scene into a pbuffer/pixmap (if pbuffer aren't supported) in order to export it to a postscript file.
On a RHEL4 (32/64 bits) or whatever distribution may be, it works just fine.
I'm using Exceed when I'm working under WinXP and each time I run my... (0 Replies)
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
In my mint I can't found <xcb/xcb.h> while in Ubuntu it was.
---------- Post updated at 03:11 PM ---------- Previous update was at 01:43 PM ----------
Is possibility install XCB from sources:
from linuxfromscratch.org
steps:
x7proto.html
xcb-proto.html
libXau.html
libxcb.html (3 Replies)
Hi,
This weekend there was a sudden application crash in the server.
I did not know where to start to investigate the problem, so I first looked into the /var/adm/syslog/syslog.log, and this was what I found :
Dec 17 00:38:02 L28bi01 sshd: error: accept: No buffer space available
Dec 17... (9 Replies)
Look this very good rendering on Slackware 14.2
in my opinion is near perfect.
https://i.stack.imgur.com/q5trL.png
Now look the same page on Fedora 30
https://i.stack.imgur.com/FBQv7.png
In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)
Discussion started by: Linusolaradm1
20 Replies
LEARN ABOUT CENTOS
vmware
VMWARE(4) Kernel Interfaces Manual VMWARE(4)NAME
vmware - VMware SVGA video driver
SYNOPSIS
Section "Device"
Identifier "devname"
Driver "vmware"
...
EndSection
DESCRIPTION
vmware is an Xorg driver for VMware virtual video cards.
MODESETTING, XINERAMA AND RANDR12
If the driver can connect to the "vmwgfx" kernel module on linux, it will attempt to use kernel modesetting and will then also use RandR12
for multiple output operation instead of Xinerama. The X server log or the "xrandr" application can be used to determine whether RandR12 or
Xinerama is actually used.
3D ACCELERATION
If the driver can connect to the "vmwgfx" kernel module on linux, and the Virtual Machine is set up to use 3D acceleration, the driver will
try to use Gallium3D XA to accelerate 3D operations. It will also by default enable DRI, the Direct Rendering Infrastructure, primarily for
accelerated OpenGL. If 3D acceleration is available, the driver will in addition provide an additional XVideo adaptor for textured video.
Gallium3D XA,ibxatracker.so" and the accelerated OpenGL driver, "vmwgfx_dri.so" is provided by the mesa distribution.
CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.
The driver auto-detects the version of any virtual VMware SVGA adapter.
The following driver Options are supported:
Option "HWCursor" "boolean"
Enable or disable the HW cursor. Default: off.
Option "Xinerama" "boolean"
Disable or enable Xinerama support. Default: xinerama is enabled if the hardware supports it.
Option "StaticXinerama" "string"
Provide a static xinerama geometry that will be active at server startup and will not be overridden at runtime. The format is
"Width1xHeight1+Xoffset1+Yoffset1;Width2xHeight2+Xoffset2+Yoffset2" and so on. Negative offsets are not supported. If the driver is
using RandR12, this option should be used to place and enable outputs at driver startup time or else when VMware tools is not used
for that purpose. Also please see option "GuiLayout".
Option "GuiLayout" "string"
A synonym to option "StaticXinerama", since the latter name is somewhat misleading when RandR12 is favoured before Xinerarma.
Option "AddDefaultMode" "boolean"
Provide a default mode with a resolution identical to the resolution of the guest before the X server was started. The X server will
thus try to start without changing resolution. Default: on.
Option "RenderAccel" "boolean"
Try to accelerate render operations if the operations are reading from previously accelerated contents (3D or video). This option is
needed for 3D support. Default: on if 3D acceleration is supported. Otherwise off.
Option "DRI" "boolean"
Enable the Direct Rendering Infrastructure. Default: on if 3D acceleration is supported and "RenderAccel" is enabled. Otherwise off.
Option "DirectPresents" "boolean"
Speed up OpenGL swapbuffers by skipping a copy operation. This provides some OpenGL swapbuffer speedups, but may cause performance
degradation and rendering errors when 3D contents is read back for mixing with software rendered contents. Default: off.
Option "HwPresents" "boolean"
This is a developer convenience option and should not be used by distros or normal users. When enabled, it copies software rendered
contents to a 3D surface before presenting it, so that the visible screen is always present on a 3D surface. Default: off.
Option "RenderCheck" "boolean"
This is a developer convenience option and should not be used by distros or normal users. When enabled, it tries to use 3D accelera-
tion for all XRender operations where 3D acceleration is supported, resulting in a considerable slowdown due to the increased number
of readbacks of accelerated contents from host to guest. This option is used to verify that the accelerated Xrender paths works cor-
rectly with the "rendercheck" application. Default: off.
SEE ALSO
Xorg(1), xorg.conf(5), Xserver(1), X(7), xrandr(1)AUTHORS
Copyright (c) 1999-2007 VMware, Inc.
X Version 11 xf86-video-vmware 13.0.1 VMWARE(4)