You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OF_FULLSCREEN seems not works with PandaboardES #80
For me OF_WINDOW or OF_FULLSCREEN do the same ( instead OF_FULLSCREEN should do a real fullscreen mode ) i don't know if it is a bug or a functionality not yet implemented in the arm branch . Just want to make a flag note.
This is implemented on Raspberry Pi, but may not be working on the x11 pandaboard ofAppEGLWindow yet. I'll take a look at it as I continue to update the ofAppEGLWindow class, but @arturoc is the current expert on x11 windowing on the Pandaboard side, so he might have some thoughts.
./customEGLWindowSettings.app
[ofAppEGLWindow::getScreenSize:error] Tried to get display size, but failed. x11Screen is not inited.
[ofAppEGLWindow::getScreenSize:error] Tried to get display size, but failed. x11Screen is not inited.
[ofAppEGLWindow::createSurface:notice] Setting up EGL Display
PVR:(Warning): LoadWSModule: Window system module libpvrws_KMS.so did not validate native display [98, /generic_ws.c]
PVR:(Warning): LoadWSModule: Window system module libpvrws_WAYLAND.so did not validate native display [98, /generic_ws.c]
[ofAppEGLWindow::createSurface:notice] EGL Display correctly set.
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 1 (X_CreateWindow)
Value in failed request: 0x0
Serial number of failed request: 8
Current serial number in output stream: 10
PVR:(Fatal): Debug assertion failed! [468, /rec_mutexes_cond_using_pthread_condvars.c]
Aborted (core dumped)
(gdb) run
Starting program: /home/walter/OF-develop-raspberrypi/openFrameworks/examples/gles/customEGLWindowSettings/bin/customEGLWindowSettings.app
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[ofAppEGLWindow::getScreenSize:error] Tried to get display size, but failed. x11Screen is not inited.
[ofAppEGLWindow::createSurface:notice] Setting up EGL Display
PVR:(Warning): LoadWSModule: Window system module libpvrws_KMS.so did not validate native display [98, /generic_ws.c]
PVR:(Warning): LoadWSModule: Window system module libpvrws_WAYLAND.so did not validate native display [98, /generic_ws.c]
[ofAppEGLWindow::createSurface:notice] EGL Display correctly set.
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 1 (X_CreateWindow)
Value in failed request: 0x0
Serial number of failed request: 8
Current serial number in output stream: 10
PVR:(Fatal): Debug assertion failed! [468, /rec_mutexes_cond_using_pthread_condvars.c]
Program received signal SIGABRT, Aborted.
__libc_do_syscall ()
at ../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S:47
47 ../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S: No such file or directory.
(gdb)
can you type bt in gdb after the crash? that will give you the full stack trace so we can see exactly were the error is. i'm busy right now but will give this a try assoon as i have a moment
Hey @kalwalt the error [ofAppEGLWindow::getScreenSize:error] Tried to get display size, but failed. x11Screen is not inited. is the one I thought I fixed with the last commit. Basically, in the previous version, the ofAppEGLWindow::createX11NativeWindow was attempting to get the screen size, but the ofAppEGLWindow::getScreenSize method was requiring the x11 window to be inited before giving the screen size -- it is currently using:
@arturoc perhaps you know a way to get the screen size without first initing the x11Screen var.
Anyway, can you make sure that you have ofLogLevel set to verbose so we can see how far it gets? And also confirm that you compiled your debug lib with this commit 9f85ffc (which is where I thought I fixed this a few minutes ago)?
That said -- it looks like a beta for the accelerated x11 drivers for RPi have been released so I'll look into testing it on the Pi. No promises yet ... :)
hi @bakercp Fullscreen mode works with Rpi? because i have purchased a Rpi , it will arrive in 10 days about, and if this issue can't be solved , i will migrate to Rpi for my project...
Last time I checked it worked on the pi.
On Feb 1, 2013 7:46 AM, "Walter Perdan" notifications@github.com wrote:
hi @bakercphttps://github.com/bakercp Fullscreen mode works with Rpi?
because i have purchased a Rpi , it will arrive in 10 days about, and if
this issue can't be solved , i will migrate to Rpi for my project...
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/80#issuecomment-12992622.
Yes, fullscreen works on the pi (at least it did yesterday :)).
Also, there are new x11 hardware drivers for the Raspberry pi now. They are very "alpha" but as soon as they become a little bit more stable, I'll install them and test out the x11 stuff on the pi. If we can fix it there on the Pi, it will probably work on the Pandaboard as well.
i'm thinking to use glfw instead. I think should works also for arm and i'have already used in linux64 bit. Do you think there is some reason to do not this?
i'm thinking to use glfw instead. I think should works also for arm and
i'have already used in linux64 bit. Do you think there is some reason to do
not this?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/80#issuecomment-13859106.
hi @bakercp@arturoc and all, i have my raspberrypi now and fullscreen works very well with it! for now i tested only some examples... for now i switch to raspberrypi for my projects until this issue will definetely solved (i mean with the pandaboard...) . I have also tried the glfw lib with my pandaboard ... but i got some errors that i don't know how to solve . the good is glfw works good in armhf , basically the errors are related to OF and linking lib excluded. I will open a separate issuefor this. I think will be good to have glfw support !
p.s. Now i finish my exams for this session and i'm a bit free...
Hei @kalwalt I will be getting a few pcDuinos in the mail soon, which should have x11 working. At that time, I'll be able to make sure that ofEGLWindow is running correctly with X11 etc.
Did you see in the video where you have to have a USB keyboard plugged in
to activate the HDMI. I have two on order myself. One for Linux and one for
Android. I want to see if of for Android will run on it.
On Mar 6, 2013 1:29 PM, "Christopher Baker" notifications@github.com
wrote:
Hei @kalwalthttps://github.com/kalwalt I will be getting a few pcDuinos
in the mail soon, which should have x11 working. At that time, I'll be able
to make sure that ofEGLWindow is running correctly with X11 etc.
—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/80#issuecomment-14516757
.
Did you see in the video where you have to have a USB keyboard plugged in
to activate the HDMI. I have two on order myself. One for Linux and one for
Android. I want to see if of for Android will run on it.
On Mar 6, 2013 1:29 PM, "Christopher Baker" notifications@github.com
wrote:
Hei @kalwalthttps://github.com/kalwalt I will be getting a few
pcDuinos in the mail soon, which should have x11 working. At that time,
I'll be able to make sure that ofEGLWindow is running correctly with X11
etc.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/80#issuecomment-14516757
.
Activity
bakercp commentedon Dec 14, 2012
This is implemented on Raspberry Pi, but may not be working on the x11 pandaboard
ofAppEGLWindowyet. I'll take a look at it as I continue to update theofAppEGLWindowclass, but @arturoc is the current expert on x11 windowing on the Pandaboard side, so he might have some thoughts.kalwalt commentedon Dec 14, 2012
ok thank's @bakercp for the feedback. we'll see for the @arturoc thoughts.
arturoc commentedon Dec 15, 2012
yes fullscreen is not implement yet, will do when i have a moment,
bakercp commentedon Jan 2, 2013
This should be fixed in b6a2310 Please test.
bakercp commentedon Jan 2, 2013
Closing for now. Please reopen if it is not working.
kalwalt commentedon Jan 2, 2013
@bakercp don't works for me:
i think this is related to: #76
bakercp commentedon Jan 2, 2013
Hi @kalwalt please try the latest. The issue was with x11 window creation in the latest (I couldn't test it so an obvious error snuck past) 9f85ffc.
kalwalt commentedon Jan 2, 2013
ok @bakercp i will try again with the 9f85ffc
kalwalt commentedon Jan 2, 2013
hi @bakercp see here gdb:
arturoc commentedon Jan 2, 2013
can you type bt in gdb after the crash? that will give you the full stack trace so we can see exactly were the error is. i'm busy right now but will give this a try assoon as i have a moment
bakercp commentedon Jan 2, 2013
Hey @kalwalt the error
[ofAppEGLWindow::getScreenSize:error] Tried to get display size, but failed. x11Screen is not inited.is the one I thought I fixed with the last commit. Basically, in the previous version, theofAppEGLWindow::createX11NativeWindowwas attempting to get the screen size, but theofAppEGLWindow::getScreenSizemethod was requiring the x11 window to be inited before giving the screen size -- it is currently using:screenWidth = XWidthOfScreen(x11Screen); screenHeight = XHeightOfScreen(x11Screen);@arturoc perhaps you know a way to get the screen size without first initing the x11Screen var.
Anyway, can you make sure that you have ofLogLevel set to verbose so we can see how far it gets? And also confirm that you compiled your debug lib with this commit 9f85ffc (which is where I thought I fixed this a few minutes ago)?
underdoeg commentedon Jan 2, 2013
I had a similar problem with the display manager within ofxFenster and I ended up reopening the display based on common addresses. It's not that nice as a solution but maybe works in your case as well? https://github.com/underdoeg/ofxFenster/blob/master/src/ofxDisplayManager.cpp#L56
17 remaining items
arturoc commentedon Jan 20, 2013
will take a look tomorrow
bakercp commentedon Jan 20, 2013
That said -- it looks like a beta for the accelerated x11 drivers for RPi have been released so I'll look into testing it on the Pi. No promises yet ... :)
kalwalt commentedon Jan 20, 2013
many thanks to all!
underdoeg commentedon Jan 20, 2013
I was afraid this might happen and the fullscreen wouldn't work everywhere. I took the code and adapted it from the ghost library. There are different ways to go fullscreen with X11, of which ghost has implemented two. I just took the first one that worked on my machine and thought I'll add the other one later on... I used the netwm method here: https://github.com/underdoeg/ghost/blob/master/intern/GHOST_WindowX11.cpp#L931 but you cold also do it with motif. https://github.com/underdoeg/ghost/blob/master/intern/GHOST_WindowX11.cpp#L982
kalwalt commentedon Feb 1, 2013
hi @bakercp Fullscreen mode works with Rpi? because i have purchased a Rpi , it will arrive in 10 days about, and if this issue can't be solved , i will migrate to Rpi for my project...
danzeeeman commentedon Feb 1, 2013
Last time I checked it worked on the pi.
On Feb 1, 2013 7:46 AM, "Walter Perdan" notifications@github.com wrote:
kalwalt commentedon Feb 1, 2013
very good! thanks for the answer @danthemellowman !
bakercp commentedon Feb 1, 2013
Yes, fullscreen works on the pi (at least it did yesterday :)).
Also, there are new x11 hardware drivers for the Raspberry pi now. They are very "alpha" but as soon as they become a little bit more stable, I'll install them and test out the x11 stuff on the pi. If we can fix it there on the Pi, it will probably work on the Pandaboard as well.
kalwalt commentedon Feb 20, 2013
i'm thinking to use glfw instead. I think should works also for arm and i'have already used in linux64 bit. Do you think there is some reason to do not this?
bakercp commentedon Feb 20, 2013
Currently (at least at last check) glfw wasn't hardware optimized for PI.
But with the new X11 hardware optimization, it may work now. Worth a try.
http://christopherbaker.net
On Wed, Feb 20, 2013 at 3:55 PM, Walter Perdan notifications@github.comwrote:
kalwalt commentedon Mar 6, 2013
hi @bakercp @arturoc and all, i have my raspberrypi now and fullscreen works very well with it! for now i tested only some examples... for now i switch to raspberrypi for my projects until this issue will definetely solved (i mean with the pandaboard...) . I have also tried the glfw lib with my pandaboard ... but i got some errors that i don't know how to solve . the good is glfw works good in armhf , basically the errors are related to OF and linking lib excluded. I will open a separate issuefor this. I think will be good to have glfw support !
p.s. Now i finish my exams for this session and i'm a bit free...
bakercp commentedon Mar 6, 2013
Hei @kalwalt I will be getting a few pcDuinos in the mail soon, which should have x11 working. At that time, I'll be able to make sure that
ofEGLWindowis running correctly with X11 etc.kalwalt commentedon Mar 6, 2013
Great! i saw your post about pcDuino....
danzeeeman commentedon Mar 6, 2013
That is the new SparkFun board I was talking about.
On Mar 6, 2013 6:50 PM, daniel.james.moore@gmail.com wrote:
Did you see in the video where you have to have a USB keyboard plugged in
to activate the HDMI. I have two on order myself. One for Linux and one for
Android. I want to see if of for Android will run on it.
On Mar 6, 2013 1:29 PM, "Christopher Baker" notifications@github.com
wrote:
Hei @kalwalt https://github.com/kalwalt I will be getting a few pcDuinos
in the mail soon, which should have x11 working. At that time, I'll be able
to make sure that ofEGLWindow is running correctly with X11 etc.
—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/80#issuecomment-14516757
.
danzeeeman commentedon Mar 6, 2013
Did you see in the video where you have to have a USB keyboard plugged in
to activate the HDMI. I have two on order myself. One for Linux and one for
Android. I want to see if of for Android will run on it.
On Mar 6, 2013 1:29 PM, "Christopher Baker" notifications@github.com
wrote: