opengl problem?

[devlaam]

When i use FreeCad i get the following message:

Code: Select all

Can't set up a valid OpenGL canvas, something is seriously wrong with the system!
Application will exit

I discussed this on the freecad forum http://sourceforge.net/apps/phpbb/free- ... ?f=4&t=151, but it seems to be an installation problem of opengl. This message originates from SoQt http://soqt.sourcearchive.com/documenta ... ource.html

Hmm, how can i research this further?
Does it make sense to rebuild some of the packages? I saw some messages passing by about this when i was upgrading, but missed the content, when dealing with other errors. Or is there some other action possible?

btw, FreeCad https://sourceforge.net/apps/mediawiki/ ... =Main_Page seems a nice program, should have gentoo package too i quess, but has a lot of dependencies.

[Kulfaangaren!]

Hi

Easiest way to see if you are running HW accelerated opengl or software rendered opengl is to use the command

Code: Select all

root@machine ~># glxinfo

In the third readable text block it should say which provider of opengl you are using and which version. If it says something with '...Mesa...' then you use software to rendered opengl and it might not support the opengl commands/functions that your program requires.

If something is wrong it makes sense to rebuild your graphics drivers, like for instance nvidia-drivers if you have an nvidia GPU.
All the recompiling in the world won't help you if your X11 configuration is not set to use the driver however, so check that first as described above.

Good luck!

// Fredrik

[devlaam]

Easiest way to see if you are running HW accelerated opengl or software rendered opengl is to use the command: glxinfo

I do not have that command on my machine. I looked it up, it should be in xorg-x11 http://bugs.gentoo.org/81440, but it is not.

Code: Select all

wolf ruud # glxinfo
  bash: glxinfo: command not found

wolf ruud # cat /etc/make.conf
  # These settings were set by the catalyst build script that automatically built this stage
  # Please consult /etc/make.conf.example for a more detailed example  
  CFLAGS="-O2 -march=opteron -pipe"
  CHOST="x86_64-pc-linux-gnu"
  CXXFLAGS="${CFLAGS}"
  USE="source apache2 unicode -gnome X kde opengl qt3 qt4 alsa oss arts mp3 vorbis xine jpeg gif png source mysql sql webkit mng"
  MAKEOPTS="-j3"
  AUTOCLEAN="yes"
  GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo"
  SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage"

wolf ruud # USE="opengl" emerge -p xorg-x11
  These are the packages that would be merged, in order:
  Calculating dependencies... done!
  [ebuild   R   ] x11-base/xorg-x11-7.4-r1

wolf ruud # USE="opengl" emerge --quiet xorg-x11
  >>> Verifying ebuild manifests 
  >>> Emerging (1 of 1) x11-base/xorg-x11-7.4-r1
  >>> Installing (1 of 1) x11-base/xorg-x11-7.4-r1

  * Messages for package x11-base/xorg-x11-7.4-r1:
  *
  * Please note that the xcursors are in /usr/share/cursors/xorg-x11.
  * Any custom cursor sets should be placed in that directory.
  *
  * If you wish to set system-wide default cursors, please create
  * /usr/local/share/cursors/xorg-x11/default/index.theme
  * with content: "Inherits=theme_name" so that future
  * emerges will not overwrite those settings.
  *
  * Listening on TCP is disabled by default with startx.
  * To enable it, edit /usr/bin/startx.
  *
  * Visit http://www.gentoo.org/doc/en/index.xml?catid=desktop
  * for more information on configuring X.
  *
  * GNU info directory index is up-to-date.

wolf ruud # glxinfo
  bash: glxinfo: command not found

On the other hand, i know on beforehand that i should(!) have software rendering, since i have a Matrox Parhelia P750 graphics card. I thought this only made 3D slower, but not dysfunctional. Can this explain my problems?

Suppose i want to recompile just the graphics part of my system, just to test, how do i know which parts i should recompile, or in other words, how do i find all packets that are linked to xorg / x11?

[Kulfaangaren!]

Hi again

According to the Gentoo Linux Documentation - Hardware 3D Acceleration Guide, glxinfo and glxgears are part of the mesa-progs ebuild.
Make sure it is installed and you should have those commands.

There are binary drivers for your Matrox card. Some info on how to set it up can be found on this site and even though it is for Debian it should most likely work almost identically on Gentoo.

Not all opengl implementations are identical and they don't all implement the full specs (I think). If your program uses something that's not implemented in Mesa it might crash the program.

Good luck

// Fredrik

[devlaam]

First, thanks for your ongoing support!

According to the Gentoo Linux Documentation - Hardware 3D Acceleration Guide, glxinfo and glxgears are part of the mesa-progs ebuild. Make sure it is installed and you should have those commands.

Interesting, so glxinfo has moved. OK, i installed mesa-progs, and this is the result:

Code: Select all

wolf ruud # glxinfo
  name of display: :0.0
  X Error of failed request:  GLXUnsupportedPrivateRequest
    Major opcode of failed request:  154 (GLX)
    Minor opcode of failed request:  17 (X_GLXVendorPrivateWithReply)
    Serial number of failed request:  14
    Current serial number in output stream:  14

Now that does not look good at all. I have to sort this out, but i assume that this call should have returned something more sensible.

There are binary drivers for your Matrox card.

Of course, i have those running. Without them, no image a all. (P750 is a nice card. It is already five years old, but supports three screens!)

Not all opengl implementations are identical and they don't all implement the full specs (I think). If your program uses something that's not implemented in Mesa it might crash the program.

Lets hope that this is not the case

[Kulfaangaren!]

Hello again

First, thanks for your ongoing support!

No problem! It is always nice to be appreciated even though I don't always solve the problem people have.
I try my best to be helpful when I can, that is what makes Gentoo great, people that tries to help others and that is one of the reasons why I stuck around the community.

The message you get from glxinfo does not look good indeed. It is as if you had no opengl support what so ever.
Can you please post your /etc/X11/xorg.conf, but please remove all comments from it to save us the spam.

Code: Select all

root@machine ~># grep -vP '^\s*#' /etc/X11/xorg.conf > /tmp/output.txt

// Fredrik

[devlaam]

Can you please post your /etc/X11/xorg.conf, but please remove all comments from it to save us the spam.

I recently cut out the comments too, since throught the comments i could not see the actual information any more. Here it is.

Code: Select all

wolf ruud # cat /etc/X11/xorg.conf

  Section "ServerLayout"
    Identifier     "Simple Layout"
    Screen         "screen_0"
    InputDevice    "Mouse1" "CorePointer"
    InputDevice    "Keyboard1" "CoreKeyboard"
  EndSection

  Section "Files"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/75dpi"
    FontPath     "/usr/share/fonts/100dpi"
    FontPath     "/usr/share/fonts/Type1"
  EndSection

  Section "Module"
    Load  "dbe"  # Double buffer extension
    Load  "extmod"
    Load  "type1"
    Load  "freetype"
    Load  "glx"
    Load  "mtxcfg"
  EndSection

  Section "InputDevice"
    Identifier  "Keyboard1"
    Driver      "kbd"
    Option      "AutoRepeat" "500 30"
    Option      "XkbRules" "xorg"
    Option      "XkbModel" "pc104"
    Option      "XkbLayout" "us"
  EndSection

  Section "InputDevice"
    Identifier  "Mouse1"
    Driver      "mouse"
    Option      "Protocol" "Auto"   # Auto detect
    Option      "Device" "/dev/input/mice"
    Option      "ZAxisMapping" "4 5 6 7"
  EndSection

  Section "Modes"
    Identifier     "MatroxModeLine"
  EndSection

  Section "Monitor"
    Identifier   "monitor_0"
    HorizSync    24.0 - 80.0
    VertRefresh  55.0 - 75.0
    DisplaySize  1129 301
  EndSection

  Section "Device"
    Identifier  "device_0"
    Driver      "mtx"
    BusID       "PCI:1:0:0"
    Screen      0
  EndSection

  Section "Screen"
    Identifier "screen_0"
    Device     "device_0"
    Monitor    "monitor_0"
    DefaultDepth    24
    DefaultFbbpp    32
    Option "TripleHead"
    Option "DigitalScreen1" "on"
    SubSection "Display"
      Depth    24
      Virtual 3840 1024
      Modes    "1280x1024"
    EndSubSection
  EndSection

I was thinking, would it be sensible just to rebuild the whole (graphics) system? I already rebuild my modules, but that did not help a lot:

Code: Select all

emerge -p xf86-input-evdev xf86-input-keyboard xf86-input-mouse xf86-video-ati xf86-video-fbdev xf86-video-glint xf86-video-intel xf86-video-mach64 xf86-video-mga xf86-video-neomagic xf86-video-nv xf86-video-openchrome xf86-video-r128 xf86-video-savage xf86-video-sis xf86-video-tdfx xf86-video-trident xf86-video-vesa

The question is how do i make sure every packet is rebuild? And would it help at all.
I also did http://www.gentoo.org/proj/en/desktop/x ... -guide.xml but it came back with

Code: Select all

wolf ruud # /usr/portage/x11-libs/libxcb/files/xcb-rebuilder.sh
 * Fixing broken libtool archives (.la)
 * Scanning for libraries requiring libxcb-xlib.so...
 * No broken libraries detected 

So that seems to be ok. But stil

Code: Select all

wolf ruud # glxinfo
name of display: :0.0
X Error of failed request:  GLXUnsupportedPrivateRequest
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  17 (X_GLXVendorPrivateWithReply)
  Serial number of failed request:  14
  Current serial number in output stream:  14

So ... what's next?

[qdii]

I might be wrong, but your xorg.conf is missing
Load "dri" and the Dri section as well no ?

[devlaam]

I might be wrong, but your xorg.conf is missing
Load "dri" and the Dri section as well no ?

Well, according to Xorg.0.log, that is loaded by default, the relevant part

Code: Select all

... 
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dbe"
...

Other parts dealing with dri:

Code: Select all

... 
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
	compiled for 1.6.3.901, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib64/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
	compiled for 1.6.3.901, module version = 1.1.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "mtx"
...

Code: Select all

... 
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) config/hal: Adding input device Logitech Optical USB Mouse
...

So maybe the latter is not as it should be. I google a bit on the error message, but did not get any wiser until now.
Indeed, there is no "DRI" section, that is because this xorg.conf is copied from the matrox-wizard generated configuration file for the most part. Should i add one, and what should be in there?

I also checked if the libs are all there. Seems so:

Code: Select all

wolf ruud # cd /usr/
wolf usr # find -name libGL.so*
./lib64/libGL.so
./lib64/opengl/xorg-x11/lib/libGL.so.1.3.0
./lib64/opengl/xorg-x11/lib/libGL.so.1
./lib64/opengl/xorg-x11/lib/libGL.so
./lib32/libGL.so
./share/matrox/backup/libGL.so.1
./share/matrox/backup/libGL.so.1.2
./share/matrox/backup/libGL.so
./share/matrox/backup/libGL.so_1
./share/matrox/backup/libGL.so.1_1
./share/matrox/backup/libGL.so.1.2_1
./share/matrox/backup/libGL.so_2
./share/matrox/backup/libGL.so_3
./share/matrox/current/libGL.so.1.3.0
./share/matrox/current/lib64/libGL.so.1.3.0

So, i am still open for suggestions...

[qdii]

According to http://dri.freedesktop.org/wiki/DriTroubleshooting, adding

Code: Select all

Section "DRI"
    Mode 0666
EndSection

to your xorg.conf enables DRI for all users.

According to the same website, three OpenGL so should be there :
/usr/lib/libGL.so
/usr/lib/libGL.so.1
/usr/lib/libGL.so.1.2

but you have libGL.so.1.3 and not libGL.so.1.2.
This might be needed. ( Compiz, on my computer, is making use of it right now )

Would you mind trying to add a simlink ?
while root : "ln -s /usr/lib/libGL.so.1 /usr/lib/libGL.so.1.2"
The same simlink exists on my computer

[devlaam]

Code: Select all

According to http://dri.freedesktop.org/wiki/DriTroubleshooting, adding ...
to your xorg.conf enables DRI for all users. 

After my post i tried that, no difference.

Code: Select all

Would you mind trying to add a simlink ? 

Normally, you should not add such symlinks yourself, but to test it cannot harm i guess, just to see if we are on the right track. Unfortunately nothing changes if i afterwards try 'glxinfo'. Seems we are running out of ideas .....

[Anon-E-moose]

what does "eselect opengl list" return

[devlaam]

what does "eselect opengl list" return

Code: Select all

wolf ruud # eselect opengl list
  Available OpenGL implementations:
    [1]   xorg-x11 *

I already retried

Code: Select all

eselect opengl set 1

since that command has some side effects too. No improvement.

[Anon-E-moose]

post your /var/tmp/Xorg.0.log file

You can use http://pastebin.com/ just post the link

[devlaam]

I've put it on my server.
http://www.betaresearch.nl/tmp/Xorg-0-log.txt
btw, there is no real problem with running X itself, since that works.
It is just with opengl and an application i tested. (see my original post)
And of course, the strange result of 'glxinfo'.

[Anon-E-moose]

I've put it on my server.
http://www.betaresearch.nl/tmp/Xorg-0-log.txt
btw, there is no real problem with running X itself, since that works.
It is just with opengl and an application i tested. (see my original post)
And of course, the strange result of 'glxinfo'.

the file gives clues about things, at times

II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so

It looks like it's using glx, but only the software version and not DRI


Edit to add: I did a quick google search on xorg.conf and P750 and there are a few things you could try.
Are you using the binary driver?
Do you have agpart turned on in the kernel, and if a module is it loaded?

[devlaam]

It looks like it's using glx, but only the software version and not DRI

Indeed, the question is, how do i activate dri, and, is this needed at all, in other words, does the absence of this explains the problems with opengl. I would guess not, since opengl should isolate me from this kind of hardware dependencies.

Are you using the binary driver?

There is only one (recent, may 2009) driver for P750. It is on the matrox site.

Do you have agpart turned on in the kernel,

I am using the genkernel, so that should be turned on,

and if a module is it loaded?

I will look. just a moment.

[devlaam]

Do you have agpart turned on in the kernel, and if a module is it loaded?

I suppose you mee agpgart? lets see

Code: Select all

wolf log # lsmod | grep agp

Hmm nothing, so that module is not loaded. Is it needed for matrox? I'dd assume that if it was, the card would not run at all. Logs:

Code: Select all

wolf log # tail -n 2000 messages | grep agp
  Oct 30 05:35:19 wolf [mtx] Allocated a MTX agp driver structure
  Oct 30 05:35:20 wolf [mtx] Enabling AGP: agp_status: 0xff00020b
  Oct 30 05:35:20 wolf )<6>agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
  Oct 30 05:35:20 wolf agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
  Oct 30 05:35:20 wolf [mtx] Enabling AGP: agp_status: 0xff00020b
  Oct 30 05:35:20 wolf )<6>agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
  Oct 30 05:35:20 wolf agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
  Oct 30 06:35:36 wolf [mtx] Enabling AGP: agp_status: 0xff00020b
  Oct 30 06:35:36 wolf )<6>agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
  ....

But still, maybe. It seems however that i do not have that module

Code: Select all

wolf log # modprobe agpgart
  FATAL: Module agpgart not found.

Should i try to get and load it? Is it essential?

[Anon-E-moose]

I don't know if it is necessary.
It looks like agpgart is compiled into the kernel vs being a module, so that is fine.

A better place to look for answers might be on the matrox site, in the support area or a forum for matrox support.

I don't know enough about matrox hardware to give much help.

Good luck.


Edit to add: this post is from a ubuntu forum but has links to other places to look for matrox help
http://ubuntuforums.org/showthread.php?t=302353