Hey all,
I'm running ubuntu 8.04 hardy heron on my macbook pro, and everything seems to be in good working order, except when I try and create a gem window. The moment I create a gem window, X11 crashes and restarts. If I take away the fglrx driver and use the opensource version of ati's drivers, it seems to work just fine, but I'd prefer not to have to use one driver for pd/gem and another for everything else since it screws with my xorg.conf when i switch in between. Any of you hard-core linux guys know a workaround for this, like a setting in a config file or something of that nature?
Andy
I have this problem too. I don't think it will be as simple as tweaking any config files though. Perhaps the eventual arrival of DRI2 will improve things. I don't know too much about the fglrx situation either, other than what I've read at the Phoronix forums. Perhaps help can be found there.
This issue came after the Hardy upgrade though, right? weird. I may try compiling against opengl 1.5, as I did in gutsy.
But yes, any opengl/X/linux wizards, please help. Will gladly post X logs.
On Thu, May 1, 2008 at 10:55 AM, Philip Rivera retrogradeprogression@gmail.com wrote:
Hey all,
I'm running ubuntu 8.04 hardy heron on my macbook pro, and everything seems to be in good working order, except when I try and create a gem window. The moment I create a gem window, X11 crashes and restarts. If I take away the fglrx driver and use the opensource version of ati's drivers, it seems to work just fine, but I'd prefer not to have to use one driver for pd/gem and another for everything else since it screws with my xorg.conf when i switch in between. Any of you hard-core linux guys know a workaround for this, like a setting in a config file or something of that nature?
Andy
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Tim wrote:
I have this problem too. I don't think it will be as simple as tweaking any config files though. Perhaps the eventual arrival of DRI2 will improve things. I don't know too much about the fglrx situation either, other than what I've read at the Phoronix forums. Perhaps help can be found there.
This issue came after the Hardy upgrade though, right? weird. I may try compiling against opengl 1.5, as I did in gutsy.
does the problem still persist in recent Gem builds? (with recent i mean *post* 2008-05-05)
i would be interested to hear how things perform with my recent hacks. additionally it would also be good to hear from linuxers using intel-gfx cards whether these changes have improved anything on their side.
fgamsdr IOhannes
Me too, I'm not able to play with Gem under Fedora 8 with fglrx driver. I'll give more info about this problem.
***** Here's my Fedora and graphic driver versions: Linux localhost.localdomain 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:54:46 EDT 2008 i686 i686 i386 GNU/Linux display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI MOBILITY RADEON X700 OpenGL version string: 2.1.7412 Release
***** Here's the Gem lib (cvs compiled) loaded by Pd: GEM: Graphics Environment for Multimedia GEM: ver: 0.91-cvs GEM: compiled: May 7 2008 GEM: maintained by IOhannes m zmoelnig GEM: Authors : Mark Danks (original version) GEM: Chris Clepper GEM: James Tittle GEM: IOhannes m zmoelnig GEM: with help by Guenter Geiger, Daniel Heckenberg, Cyrille Henry, et al. GEM: found a bug? miss a feature? please report it: GEM: homepage http://gem.iem.at/ GEM: bug-tracker http://sourceforge.net/projects/pd-gem/ GEM: mailing-list http://lists.puredata.info/listinfo/gem-dev/ GEM: compiled for SIMD architecture: MMX GEM: using MMX optimization
***** Here's the dmesg output concerning the X server crash [fglrx] PCIe has already been initialized. Reinitializing ... [fglrx] Reserve Block - 0 offset = 0X7ffb000 length = 0X5000 [fglrx] Reserve Block - 1 offset = 0X0 length = 0X40000 [fglrx] Reserve Block - 2 offset = 0X7fbb000 length = 0X40000 [fglrx] interrupt source 20008000 successfully enabled [fglrx] enable ID = 0x00000004 [fglrx] Receive enable interrupt message with irqEnableMask: 20008000 [fglrx] interrupt source 10000000 successfully enabled [fglrx] enable ID = 0x00000005 [fglrx] Receive enable interrupt message with irqEnableMask: 10000000
Hope this helps :-) Tommaso
IOhannes m zmoelnig wrote:
Tim wrote:
I have this problem too. I don't think it will be as simple as tweaking any config files though. Perhaps the eventual arrival of DRI2 will improve things. I don't know too much about the fglrx situation either, other than what I've read at the Phoronix forums. Perhaps help can be found there.
This issue came after the Hardy upgrade though, right? weird. I may try compiling against opengl 1.5, as I did in gutsy.
does the problem still persist in recent Gem builds? (with recent i mean *post* 2008-05-05)
i would be interested to hear how things perform with my recent hacks. additionally it would also be good to hear from linuxers using intel-gfx cards whether these changes have improved anything on their side.
fgamsdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
tommaso bianco wrote:
Me too, I'm not able to play with Gem under Fedora 8 with fglrx driver. I'll give more info about this problem.
[...]
Hope this helps :-)
unfortunately it does not. i don't see any problems here...(but noticed that you are indeed using the latest and greatest Gem)
when does it crash? (does it crash at all?): when you load Gem? when you create a window? when you destroy the window? when you turn rendering on?
does setting the environmental-variable GEM_SINGLE_CONTEXT=1 help?
fgmasdr IOhannes
For me, X crashes when I try to create a window. I'm using pd-extended 4/28 right now.. I'll try to get a newer build, and test with GEM_SINGLE_CONTEXT=1. There haven't been any hardy autobuilds in the last few days for whatever reason, and I'm having some build troubles of my own (with hidio) that I've posted about on PD-dev.
Looks like somebody else was having a similar problem a few months ago, but things may have changed since then. http://www.mail-archive.com/pd-list@iem.at/msg16027.html
PS I'm using fglrx 8.47.3
On Wed, May 7, 2008 at 5:01 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
tommaso bianco wrote:
Me too, I'm not able to play with Gem under Fedora 8 with fglrx driver. I'll give more info about this problem.
[...]
Hope this helps :-)
unfortunately it does not. i don't see any problems here...(but noticed that you are indeed using the latest and greatest Gem)
when does it crash? (does it crash at all?): when you load Gem? when you create a window? when you destroy the window? when you turn rendering on?
does setting the environmental-variable GEM_SINGLE_CONTEXT=1 help?
fgmasdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ok just built the latest sources disabling hidio and gem2pdp because of errors, and it looks like verything is back to normal. I set GEM_SINGLE_CONTEXT=1 too. Cool. Thanks
On Wed, May 7, 2008 at 1:49 PM, Tim tjones01@gmail.com wrote:
For me, X crashes when I try to create a window. I'm using pd-extended 4/28 right now.. I'll try to get a newer build, and test with GEM_SINGLE_CONTEXT=1. There haven't been any hardy autobuilds in the last few days for whatever reason, and I'm having some build troubles of my own (with hidio) that I've posted about on PD-dev.
Looks like somebody else was having a similar problem a few months ago, but things may have changed since then. http://www.mail-archive.com/pd-list@iem.at/msg16027.html
PS I'm using fglrx 8.47.3
On Wed, May 7, 2008 at 5:01 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
tommaso bianco wrote:
Me too, I'm not able to play with Gem under Fedora 8 with fglrx driver. I'll give more info about this problem.
[...]
Hope this helps :-)
unfortunately it does not. i don't see any problems here...(but noticed that you are indeed using the latest and greatest Gem)
when does it crash? (does it crash at all?): when you load Gem? when you create a window? when you destroy the window? when you turn rendering on?
does setting the environmental-variable GEM_SINGLE_CONTEXT=1 help?
fgmasdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Tim wrote:
Ok just built the latest sources disabling hidio and gem2pdp because of errors, and it looks like verything is back to normal. I set GEM_SINGLE_CONTEXT=1 too. Cool. Thanks
so it does not crash with GEM_SINGLE_CONTEXT=1 (?) does it (still) crash without setting it?
fgmasdr Ihannes
Hi, I confirm. It definitively works for me just after setting the environmental variable (in ~/.bashrc) GEM_SINGLE_CONTEXT=1. Before that, X was shutting down and going back to the gdm login after each Gem window creation. The environmental variable GEM_SINGLE_CONTEXT=1 must be "on" both in compile time and in run time. Tommaso
IOhannes m zmölnig wrote:
Tim wrote:
Ok just built the latest sources disabling hidio and gem2pdp because of errors, and it looks like verything is back to normal. I set GEM_SINGLE_CONTEXT=1 too. Cool. Thanks
so it does not crash with GEM_SINGLE_CONTEXT=1 (?) does it (still) crash without setting it?
fgmasdr Ihannes
tommaso bianco wrote:
Hi, I confirm. It definitively works for me just after setting the environmental variable (in ~/.bashrc) GEM_SINGLE_CONTEXT=1. Before that, X was shutting down and going back to the gdm login after each Gem window creation. The environmental variable GEM_SINGLE_CONTEXT=1 must be "on" both in compile time and in run time.
thanks, i will add this to the FAQ. (btw, GEM_SINGLE_CONTEXT=1 at compile-time means nothing and is ignored; seems i was unclear about this)
one last thing for all the brave ubuntu testers: could you try to find out what get's posted when Gem crashes?
like: % export GEM_SINGLE_CONTEXT=0 % pd -stderr -lib Gem > gemcrash.log 2>&1 ..create a gemwindow (and crash X) ..send me the gemcrash.log
mfg.adsr IOhannes
Tim wrote:
This issue came after the Hardy upgrade though, right? weird. I may try compiling against opengl 1.5, as I did in gutsy.
oh, btw: Gem now makes runtime-checks based on glew; there is no need nor possibility) to compile against a maximum openGL-version (1.5) any more.
fgmadsr IOhannes
-
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Philip Rivera -
Tim -
tommaso bianco