XC-MISC
default screen number:0
When running xdpyinfo local (DISPLAY=:0) it's complete:
[...]
number of extensions:29
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
DRI3
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
On Thu, Jun 14, 2018 at 06:02:07AM +0100, Steve Dodd wrote:
>On 12 June 2018 at 10:45, Ilya Anfimov wrote:
>
> The GLX pathway had too many data copy-ing, that process wass
>
> too CPU-based and sycnhronous, also it had some optimisations
>
>of pa
On 12 June 2018 at 10:45, Ilya Anfimov wrote:
> The GLX pathway had too many data copy-ing, that process wass
too CPU-based and sycnhronous, also it had some optimisations
of packing and pipelining drawcalls in one write() syscall, [..]
I was thinking about this .. what happened to
med synchronizations. It
was barely compatible with 20-year old code of sockets-based in-
terprocess comuncation. The GLX pathway had too many data copy-
ing, that process wass too CPU-based and sycnhronous, also it had
some optimisations of packing and pipelining drawcalls in one
write() syscall,
On 12 June 2018 at 10:08, Ilya Anfimov wrote:
>
> No, currently there is no developers willing to improve this.
> However, you can try some proxies like virtualgl.
>
Is there any understanding of the root of the problem? In theory I could
start looking into it, but I'm old and ill and very out
d I would at least like to test/benchmark
>performance with indirect GLX (I have turned it on in xorg.conf)
>I am using the modesetting driver, but think I have also seen this on the
>old intel driver too (I can retest that if useful, but obviously
>modesetting is now
ashioned X Terminal - but it does have a
3D-accelerated chipset and I would at least like to test/benchmark
performance with indirect GLX (I have turned it on in xorg.conf)
I am using the modesetting driver, but think I have also seen this on the
old intel driver too (I can retest that if useful, but
Hi.
TL;DR
I started playing with Xdmx, but it crashes on any OpenGL application
(even glxinfo). So I want to ask what is Xdmx GLX proxy status? Is it
badly broken or I have hope?
Long version:
Xdmx crashes on any OpenGL application.
Tested versions: 1.19.5 and GIT
Cause: variable
if this will help, but previously adam had said:
>> >
>> > > How are you launching Xvfb? I believe it defaults to 8bpp, but
>> > > GLX
>> > only
>> > > works at 16 or 32bpp.
>> >
>> > which I think you hadn't tried yet.
>> &
you launching Xvfb? I believe it defaults to 8bpp, but
> > > GLX
> > only
> > > works at 16 or 32bpp.
> >
> > which I think you hadn't tried yet.
> >
>
> Well I did with
>
> xvfb-run -s '-screen 0 1024x768x24 +extension GLX +iglx&#x
t;>> "-nolisten tcp") to pass to the Xvfb
>>>>>> server
>>>>>> (default: "-screen 0 640x480x8")
>>>>>>
>>>>>> I am not familiar wi
On Mon, Dec 12, 2016 at 2:34 PM, Eric Gunther wrote:
> On Mon, 2016-12-12 at 13:51 -0500, Long Vu wrote:
>
> I don't know if this will help, but previously adam had said:
>
>> How are you launching Xvfb? I believe it defaults to 8bpp, but GLX
> only
>> works at 16
the Xvfb
>>>>> server
>>>>> (default: "-screen 0 640x480x8")
>>>>>
>>>>> I am not familiar with X server options, what server args I would need
>>>>> to get rid of this "ES2 P
; > > (default: "-screen 0
> > > > 640x480x8")
> > > >
> > > > I am not familiar with X server options, what server args I
> > > > would need
> > > > to get rid of this "ES2 Prism: E
0x480x8")
>>>>
>>>> I am not familiar with X server options, what server args I would need
>>>> to get rid of this "ES2 Prism: Error - GLX extension is not supported"
>>>> error?
>>>
>>> Yes, I think it would be:
>>
arguments (other than server number and
>>> "-nolisten tcp") to pass to the Xvfb
>>> server
>>> (default: "-screen 0 640x480x8")
>>>
>>> I am not familiar with X se
"-nolisten tcp") to pass to the Xvfb
>> server
>> (default: "-screen 0 640x480x8")
>>
>> I am not familiar with X server options, what server args I would need
>> to get rid of this "ES2 Prism: Error - GL
to the Xvfb
> server
> (default: "-screen 0 640x480x8")
>
> I am not familiar with X server options, what server args I would need
> to get rid of this "ES2 Prism: Error - GLX extension is not supported"
> error?
Yes, I think it would be:
xvfb-run -
gt;>> We got this error with Xvfb that we do not have when we were running a
>>> real VNC server just to provide X.
>>>
>>> ES2 Prism: Error - GLX extension is not supported
>>>GLX version 1.3 or higher is required
>>> Xlib: extension "RAND
ning a
>> real VNC server just to provide X.
>>
>> ES2 Prism: Error - GLX extension is not supported
>>GLX version 1.3 or higher is required
>> Xlib: extension "RANDR" missing on display ":99".
>>
>> Is there something we can do to avoid
On Fri, 2016-12-09 at 14:09 -0500, Long Vu wrote:
> Hi,
>
> We use Xvfb to avoid having to run an X server on our build machine.
>
> We got this error with Xvfb that we do not have when we were running a
> real VNC server just to provide X.
>
> ES2 Prism: Error - GLX ex
Hi,
We use Xvfb to avoid having to run an X server on our build machine.
We got this error with Xvfb that we do not have when we were running a
real VNC server just to provide X.
ES2 Prism: Error - GLX extension is not supported
GLX version 1.3 or higher is required
Xlib: extension "
Hi,
We use Xvfb to avoid having to run an X server on our build machine.
We got this error with Xvfb that we do not have when we were running a
real VNC server just to provide X.
ES2 Prism: Error - GLX extension is not supported
GLX version 1.3 or higher is required
Xlib: extension "
Hi
I need GLX in my work - radiation modelling in particle physics, nuclear
physics, medicine (radiation therapy) and spacecraft design. Radiation
modelling takes lots of remote CPU and we display results locally via X11 with
GLX using relatively low bandwidth. Using Quartz on Mac.
John
Hi,
After installing some pacakges, like:
libdrm* mesa* libgl* libdricore* libglapi* xserver-xorg-extension-glx*
Celestia Test Pass.
Thanks
On Fri, May 9, 2014 at 9:30 PM, Thomas Lübking wrote:
> On Freitag, 9. Mai 2014 07:18:36 CEST, ashish yadav wrote:
>
>> Hi,
>>
>
On Freitag, 9. Mai 2014 07:18:36 CEST, ashish yadav wrote:
Hi,
Please let me know if you need more info.
"The Silicon Motion SM712 is a PCI-based 2D graphics engine with 4MB of embedded
video memory and a maximum output resolution of 1280x1024"
-> plug a reasonable GPU card into the box and
:
>
> sh-4.2# /opt/lsb/appbat/bin/celestia
> freeglut (/opt/lsb/appbat/bin/celestia): OpenGL GLX extension not supported by
> display ':0'
> sh-4.2#
>
> sh-4.2# glxinfo
> name of display: :0
> Error: couldn't find RGB GLX visual or fbconfig
> sh-4.2#
Hi ,
I am doing LSB Certification Test on My System (x86_64 system Sandy Bridge).
While Doing Manual Test Celestia, I got following error:
sh-4.2# /opt/lsb/appbat/bin/celestia
freeglut (/opt/lsb/appbat/bin/celestia): OpenGL GLX extension not supported by
display ':0'
sh-4.2#
sh-4.
28 matches
Mail list logo
