mesa3d-users

Re: [Mesa3d-users] Mesa-7.5 in Fedora 11 is very awful.

[tom f. <tf...@al...>]

tornadory <tor...@16...> writes:
>  I use Fedora 11 and find that it is only less than 200 FPS when I run the 'g
> lxgears'. I ever used Fedora 8 and it is more than 600 FPS.
> 
> The attachment is the glxinfo information in the system.

The attachment is not present.  I don't think it's needed though.

> I want to know why it is so slow.

SwapBuffers is apparently slower these days.

  http://bugs.freedesktop.org/show_bug.cgi?id=4704#c3

-tom

Re: [Mesa3d-users] Mesa-7.5 in Fedora 11 is very awful.

[François C. <fc...@fe...>]

On Fri, 3 Jul 2009 14:33:22 +0800 (CST)
tornadory <tor...@16...> wrote:

>  I use Fedora 11 and find that it is only less than 200 FPS when I run the 'glxgears'. I ever used Fedora 8 and it is more than 600 FPS.

Hi tornadory,

First of all, glxgears cannot be used as a benchmark. What it
measures is of no use in real world situations.

However, should you find that real applications behave slower,
please file a bug report at https://bugzilla.redhat.com against the
"mesa" component, providing  the information listed there :
https://fedoraproject.org/wiki/Xorg/Debugging

Best wishes,

François

[Mesa3d-users] Mesa-7.5 in Fedora 11 is very awful.

[tornadory <tor...@16...>]

Dear all,

 I use Fedora 11 and find that it is only less than 200 FPS when I run the 'glxgears'. I ever used Fedora 8 and it is more than 600 FPS.

The attachment is the glxinfo information in the system.

I want to know why it is so slow.

Thanks in advance and hope your reply.

Re: [Mesa3d-users] Hello

[Debiminho <deb...@gm...>]

On Thu, Jul 2, 2009 at 5:50 PM, tom fogal<tf...@al...> wrote:
> Debiminho <deb...@gm...> writes:
>> Im just a user looking for "free" support driver to my nvidia GeForce
>> 7300 GS
>
> There's the `nv' one in Xorg.  Mesa includes a `nouveau' driver, but it
> is not for users ATM, unless I've missed something.
>
> Cheers,
>
> -tom
>

Hello Tom,

I'm using nv at the moment, but i forget to say that i would like to
have 3D acceleration.
I know that i can install Nvidia one, but im trying to have a system
clean, only Free Software.

Cheers,
Silvino
-- 
debiminho.com

Re: [Mesa3d-users] Hello

[tom f. <tf...@al...>]

Debiminho <deb...@gm...> writes:
> Im just a user looking for "free" support driver to my nvidia GeForce
> 7300 GS

There's the `nv' one in Xorg.  Mesa includes a `nouveau' driver, but it
is not for users ATM, unless I've missed something.

Cheers,

-tom

[Mesa3d-users] Hello

[Debiminho <deb...@gm...>]

Hello,

My first time here, i have lot of questions, but before i post i will
read more :)
Im just a user looking for "free" support driver to my nvidia GeForce 7300 GS...

See you
Silvino
-- 
debiminho.com

[Mesa3d-users] Mesa 7.5 release candidate 4

[Brian P. <br...@vm...>]

Available at http://www.mesa3d.org/beta/

MD5 checksums:

68d4994087863a88ef46b0f19ee35a23  MesaLib-7.5-rc4.tar.gz
38ade09207802576f2716b85fe01e4ca  MesaLib-7.5-rc4.zip
5adaaa884026e89c9ed7494c35835843  MesaDemos-7.5-rc4.tar.gz
984b4ca8666bcd5ae6edde86b4d41815  MesaDemos-7.5-rc4.zip
28c5725dad1e4fd497a72a3599275837  MesaGLUT-7.5-rc4.tar.gz
5f8c28d789d2200cf9143a24fb1041c0  MesaGLUT-7.5-rc4.zip

[Mesa3d-users] Problem with de xdemo glsync

[Nicolas C. <nic...@ym...>]

Hello

I want to test the demo glsync (...\progs\xdemos\glsync.c) with the option -s b to use the verticale sync. 
The problem is when the function glXSwapBuffer calls the function GetGLXDRIDrawable(dpy, drawable, NULL), GetGLXDRIDrawable returns a pointer(pdraw) which is NULL.

pdraw is NULL because psc->drawHash is NULL.

The function __glXInitialize(dpy) called from GetGLXDRIDrawable returns a display private wich already exists

I want to know why the drawHash structure is NULL and how to do to have a drawHash which is not NULL ?

Thanks
Nicolas Cadio



      

[Mesa3d-users] Problem with de xdemo glsync

[Nicolas C. <nic...@ym...>]

Hello

I want to test the demo glsync (...\progs\xdemos\glsync.c) with the option -s b to use the verticale sync. 
The
problem is when the function glXSwapBuffer calls the function
GetGLXDRIDrawable(dpy, drawable, NULL), GetGLXDRIDrawable returns a
pointer(pdraw) which is NULL.

pdraw is NULL because psc->drawHash is NULL.

The function __glXInitialize(dpy) called from GetGLXDRIDrawable returns a display private wich already exists

I want to know why the drawHash structure is NULL and how to do to have a drawHash which is not NULL ?

Thanks
Nicolas Cadio


      

Re: [Mesa3d-users] Visual Studio project files broken?

[Brian P. <br...@vm...>]

Jianrong Shu wrote:
> Hi there,
> 
> I tried to build Mesa 7.5 branch on Windows using Visual Studio 2008
> and the VC8 solution file and got several errors.
> 
> First, the "mesa" project included a file "prog_debug.c", which
> doesn't exist. After deleting it from the project, I was able to
> compile it successfully. Then, when building the "gdi" project, I got
> the following error messages:
> 
> 1>Linking...
> 1>mesa.def : error LNK2001: unresolved external symbol
> _mesa_get_compressed_teximage
> 1>mesa.def : error LNK2001: unresolved external symbol
> _mesa_get_program_register
> 1>mesa.def : error LNK2001: unresolved external symbol _mesa_get_teximage
> 1>mesa.def : error LNK2001: unresolved external symbol _mglapi_check_multithread
> 1>mesa.def : error LNK2001: unresolved external symbol _mglapi_get_proc_address
> 
> I also tried the master branch and the same problem exists. Any fix to this?

The Visual Studio project files haven't been actively maintained 
lately (we've been using scons on Windows).

If you can provide updated project files, that'd be great.  It's just 
a matter of removing references to old/removed files and adding the 
new ones.

-Brian

[Mesa3d-users] Visual Studio project files broken?

[Jianrong S. <jia...@gm...>]

Hi there,

I tried to build Mesa 7.5 branch on Windows using Visual Studio 2008
and the VC8 solution file and got several errors.

First, the "mesa" project included a file "prog_debug.c", which
doesn't exist. After deleting it from the project, I was able to
compile it successfully. Then, when building the "gdi" project, I got
the following error messages:

1>Linking...
1>mesa.def : error LNK2001: unresolved external symbol
_mesa_get_compressed_teximage
1>mesa.def : error LNK2001: unresolved external symbol
_mesa_get_program_register
1>mesa.def : error LNK2001: unresolved external symbol _mesa_get_teximage
1>mesa.def : error LNK2001: unresolved external symbol _mglapi_check_multithread
1>mesa.def : error LNK2001: unresolved external symbol _mglapi_get_proc_address

I also tried the master branch and the same problem exists. Any fix to this?

Thanks,
Jianrong

[Mesa3d-users] Mesa 7.4.4 release

[Brian P. <br...@vm...>]

I've made a 7.4.4 release to fix a couple regressions that slipped 
into the i915/i965 DRI drivers.

It can be downloaded at 
https://sourceforge.net/project/showfiles.php?group_id=3

-Brian

[Mesa3d-users] Mesa 7.4.3 released

[Brian P. <br...@vm...>]

Mesa 7.4.3 can be downloaded from 
https://sourceforge.net/project/showfiles.php?group_id=3

This is a bug-fix release.  See the release notes for details.

This will probably be the last release in the 7.4.x series.

-Brian

Re: [Mesa3d-users] DRI with ATI M6 (RV100) PCI on RHEL/CentOS 5

[Gordan B. <go...@bo...>]

José JORGE wrote:
> A Sunday 14 June 2009 12:15:10, Gordan Bobic escreveu:
>> Can you elaborate? What do you mean? What's wrong with the packages?
> 
> Maybe 3D support was disabled on RH builds, maybe the card doesn't have enough 
> memory for 3D. Anyway, you should provide your Xorg log file to know.

I figured it out. It turns out the RHEL5 package has a patch applied 
that disabled DRI on the RV100. I unpatched and rebuild the package and 
it's now running fine. :)

Thanks.

Gordan

[Mesa3d-users] glXCreateWindow on Ubuntu 8.04

[Andrey T. <tsy...@is...>]

Hello,

I'm new to openGL. I read some documentation about GL and GLX from official
openGL site and try to run example from there
http://www.opengl.org/sdk/docs/man/xhtml/glXIntro.xml.

On Ubuntu 8.04(with libgl1-mesa-glx 7.2-1 installed) it creates and
shows window, but then immediately aborts with error:

failed to create drawable
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  55 (X_CreateGC)
  Resource id in failed request:  0x200004
  Serial number of failed request:  19
  Current serial number in output stream:  21

It seems that this error is result of the following line:

glxWin = glXCreateWindow( dpy, fbConfigs[0], xWin, NULL );

When this line is replaced with simple

glxWin = xWin;

everything  becomes ok(window appears, is filled with yellow, and disappears
after 10 seconds).

I think I'm missing something trivial, but I cannot find out what.
Could someone help me? Or, at least, point to previous discussion of
this problem.

Thanks in advance.
-- 
Andrey Tsyvarev
 
 Linux Verification Center, ISPRAS
 web:    http://www.linuxtesting.org
 e-mail: tsy...@is...

Re: [Mesa3d-users] DRI with ATI M6 (RV100) PCI on RHEL/CentOS 5

[José J. <lis...@fr...>]

A Sunday 14 June 2009 12:15:10, Gordan Bobic escreveu:
> Can you elaborate? What do you mean? What's wrong with the packages?

Maybe 3D support was disabled on RH builds, maybe the card doesn't have enough 
memory for 3D. Anyway, you should provide your Xorg log file to know.

Re: [Mesa3d-users] DRI with ATI M6 (RV100) PCI on RHEL/CentOS 5

[Gordan B. <go...@bo...>]

José JORGE wrote:
> A Wednesday 10 June 2009 21:38:59, Gordan Bobic escreveu:
>> xorg-x11-server-Xorg 1.1.1
>> xorg-x11-drv-ati 6.6.3
> 
> This looks like a packaging problem from RH... no one will be able to hlp you 
> here!

Can you elaborate? What do you mean? What's wrong with the packages?

Gordan

Re: [Mesa3d-users] DRI with ATI M6 (RV100) PCI on RHEL/CentOS 5

[José J. <lis...@fr...>]

A Wednesday 10 June 2009 21:38:59, Gordan Bobic escreveu:
> xorg-x11-server-Xorg 1.1.1
> xorg-x11-drv-ati 6.6.3

This looks like a packaging problem from RH... no one will be able to hlp you 
here!

Re: [Mesa3d-users] Does MESA support OpenGL ES?

[Chia-I Wu <ol...@gm...>]

Hi,

On Fri, Jun 12, 2009 at 09:11:07AM -0600, Brian Paul wrote:
> We're in the process of integrating OpenGL ES 1.1 and 2.0 into Mesa 
> now.  The 'opengl-es' branch in git has the code and there's some 
> documentation in the docs/ directory.  I need to spend a bit more time 
> on it before merging it to master...
Could you give some indications on what need to be worked on?

I was playing with opengl-es branch (merged into master), and after
fixing a compilation error (missing attrib.h and
`_mesa_PushClientAttrib` in main/debug.c), I was able to run torus with
egl_softpipe.so.  I also modifed torus.c to use EGL MESA_screen_surface
extension and it sort of worked with EGL_i915.so.  I could see the
torus, but there was no texture.  I will look into this issue next week.

Other than that, I was also confused why EGL_i915.so is linked to
libmesagallium.a while egl_softpipe.so isn't.  The latter makes more
sense to me.

I am new to mesa and I am not sure if they are real issues, or how they
should be fixed.  I am willing to help if you could provide some
guidances.

-- 
Regards,
olv

Re: [Mesa3d-users] shadowtex program

[Brian P. <br...@vm...>]

R. Aditya Kadambi wrote:
> Hi Brian;
> 
> I was testing mesa demo programs on my Fedora 11 system. "shadowtex" 
> program gave me these "errors"
> 
> Using GL_ARB_depth_texture
> and GL_ARB_shadow
> and GL_ARB_fragment_program
> and GL_ARB_shadow_ambient
> Using GL_EXT_framebuffer_object
> Keys:
>   a = toggle animation
>   i = show depth texture image
>   m = show depth texture mapping
>   d = show fragment distance from light source
>   n = show normal, shadowed image
>   f = toggle nearest/bilinear texture filtering
>   b/B = decrease/increase shadow map Z bias
>   p = toggle use of packed depth/stencil
>   M = cycle through fragment program modes
>   v = toggle vertex program modes
>   cursor keys = rotate scene
>   <shift> + cursor keys = rotate light source
>   o = cycle through comparison modes
> *********************************WARN_ONCE*********************************
> File r300_render.c function r300Fallback line 432
> Software fallback:r300->radeon.Fallback
> ***************************************************************************
> CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 
> vs 7
> CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> Please report at bugzilla.freedesktop.org <http://bugzilla.freedesktop.org>
> CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 
> vs 7
> CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> Please report at bugzilla.freedesktop.org <http://bugzilla.freedesktop.org>
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> Please report at bugzilla.freedesktop.org <http://bugzilla.freedesktop.org>
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> Please report at bugzilla.freedesktop.org <http://bugzilla.freedesktop.org>
> CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 
> vs 7
> CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> Please report at bugzilla.freedesktop.org <http://bugzilla.freedesktop.org>
> CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 
> vs 7
> CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> Please report at bugzilla.freedesktop.org <http://bugzilla.freedesktop.org>
> Mesa 7.5-devel implementation error: unexpected texture format in 
> setup_hardware_state
> ------------------------------------------------------------------------------------------------------------------
> 
> I have  a ATI X1950Pro card. Hence it might be a R500 driver issue. Is 
> this a real bug for me to report?

There's been a lot of work on the radeon drivers recently on the 
Mesa/master branch.  Perhaps this is already fixed.  I don't have any 
Radeon hardware to test with.

Either file a bug or report this on the mesa3d-dev list.

-Brian

[Mesa3d-users] shadowtex program

[R. A. K. <rak...@gm...>]

Hi Brian;

I was testing mesa demo programs on my Fedora 11 system. "shadowtex" program
gave me these "errors"

Using GL_ARB_depth_texture
and GL_ARB_shadow
and GL_ARB_fragment_program
and GL_ARB_shadow_ambient
Using GL_EXT_framebuffer_object
Keys:
  a = toggle animation
  i = show depth texture image
  m = show depth texture mapping
  d = show fragment distance from light source
  n = show normal, shadowed image
  f = toggle nearest/bilinear texture filtering
  b/B = decrease/increase shadow map Z bias
  p = toggle use of packed depth/stencil
  M = cycle through fragment program modes
  v = toggle vertex program modes
  cursor keys = rotate scene
  <shift> + cursor keys = rotate light source
  o = cycle through comparison modes
*********************************WARN_ONCE*********************************
File r300_render.c function r300Fallback line 432
Software fallback:r300->radeon.Fallback
***************************************************************************
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs
7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
Please report at bugzilla.freedesktop.org
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs
7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
Please report at bugzilla.freedesktop.org
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
Please report at bugzilla.freedesktop.org
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
Please report at bugzilla.freedesktop.org
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs
7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
Please report at bugzilla.freedesktop.org
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs
7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
Please report at bugzilla.freedesktop.org
Mesa 7.5-devel implementation error: unexpected texture format in
setup_hardware_state
------------------------------------------------------------------------------------------------------------------

I have  a ATI X1950Pro card. Hence it might be a R500 driver issue. Is this
a real bug for me to report?

Re: [Mesa3d-users] Does MESA support OpenGL ES?

[Brian P. <br...@vm...>]

Molsi Annie Varghese wrote:
> Hi,
>  
> I'm new to MESA, and I'm trying out OpenGL2.0 programs on it.
> I also have a few OpenGL 2.0 ES programs, but I see that I get a few 
> linker errors with some functions.
>  
> Does MESA support OpenGL2.0 ES?

We're in the process of integrating OpenGL ES 1.1 and 2.0 into Mesa 
now.  The 'opengl-es' branch in git has the code and there's some 
documentation in the docs/ directory.  I need to spend a bit more time 
on it before merging it to master...

-Brian

[Mesa3d-users] Does MESA support OpenGL ES?

[Molsi A. V. <mol...@gm...>]

Hi,

I'm new to MESA, and I'm trying out OpenGL2.0 programs on it.
I also have a few OpenGL 2.0 ES programs, but I see that I get a few linker
errors with some functions.

Does MESA support OpenGL2.0 ES?

Thanks,
Molsi

[Mesa3d-users] DRI with ATI M6 (RV100) PCI on RHEL/CentOS 5

[Gordan B. <go...@bo...>]

Hi,

I'm struggling to get this to work. The driver works fine in 2D, but 3D 
fails. I get this in Xorg log:

  AIGLX: Screen 0 is not DRI capable

and GLX falls back to MESA-PROXY.

I tried the latest snapshot (ancient - 2006-04-03), and while it all 
builds OK (after changing
#define __put_page(p) atomic_dec(&(p)->count)
to
#define __put_page(p) atomic_dec(&(p)->_count)
in drm_compat.h)
and the kernel modules seem to work OK on RHEL5's 2.6.18-128.1.10 
kernel, the Xorg drivers don't - they fail saying that the drivers use 
ABI major version 0 while Xorg has major version 1.

Is there a later snapshot of the radeon DRI package that I can build and 
try somewhere?

My versions are:
xorg-x11-server-Xorg 1.1.1
xorg-x11-drv-ati 6.6.3

Thanks in advance.

Gordan

Re: [Mesa3d-users] OpenGL on linux-mips arch

[tom f. <tf...@al...>]

bay area <bay...@gm...> writes:
> Hi All,
> I'm trying to run 32-bit opengl application on my target board without
> x-window. I used linux-osmesa option to build MESA-3D gl library.
> following libraries are created -
> libOSMesa32.so.7.4.2,  libGLU.so.1.3.070402
> 
> when I'm trying to link it linker is giving me error as
> skipping incompatible /usr/lib/libOSMesa32.so when searching for -lOSMesa32

You've almost certainly built the Mesa libraries on a host which
is 64bit by default [1].  You'll need to setup a cross compilation
environment, though if the archs are similar enough you might be able
to force 32bit mode on your arch using gcc's `-m32' option.

-tom

[1] You can run file on /usr/lib/libOSMesa32.so to verify this is what
    happened.