Embedded Linux / Framebuffer / No screens available
-
wrote on 10 May 2016, 00:44 last edited by
Dear all,
I am a newbie on Qt, but we decided to move on that framework.
Our custom platform is based on Buildroot 2016.x and Qt 5.5.1. The CPU is an ARM (without HW acceleration).
We use a small color TFT 320x240 16 bits colors.We were able to compile Qt and even to run console-only Qt applications.
However, any app (for instance examples/gui/rasterwindow) fails with the same error:
Failed to open framebuffer /dev/fb0 (Permission denied) linuxfb: Failed to initialize screen Cannot create window: no screens available
The app is running under root user and /dev/fb0 exists and works fine (I can push a raw image directly to fb0). Its permissions are a+rwx and belongs to root:root.
Could you help me?
Thanks in advance
-
wrote on 11 May 2016, 06:30 last edited by
Hi @TopKool ,
Can you tell me how you launch the examples on your platform ?
-
Hi @TopKool ,
Can you tell me how you launch the examples on your platform ?
wrote on 16 May 2016, 18:37 last edited byI made a tiny Qt app called test2 with a simple button, and I tried to run using different parameters:
./test2 ./test2 -platform linuxfb ./test2 -platform linuxfb:fb=/dev/fb0
The error is always the same:
Failed to open framebuffer /dev/fb0 (Permission denied) linuxfb: Failed to initialize screen no screens available, assuming 24-bit color Cannot create window: no screens available Aborted
However, the fbv tool (http://freecode.com/projects/fbv) is able to display a PNG image.
-
I made a tiny Qt app called test2 with a simple button, and I tried to run using different parameters:
./test2 ./test2 -platform linuxfb ./test2 -platform linuxfb:fb=/dev/fb0
The error is always the same:
Failed to open framebuffer /dev/fb0 (Permission denied) linuxfb: Failed to initialize screen no screens available, assuming 24-bit color Cannot create window: no screens available Aborted
However, the fbv tool (http://freecode.com/projects/fbv) is able to display a PNG image.
wrote on 16 May 2016, 18:53 last edited byI figured out the issue. It was due to our kernel configuration. I still do not know exactly what it is the root cause, but once some custom security features disabled in the kernel, Qt works.
Thanks for your support.
-
wrote on 10 Aug 2020, 07:36 last edited byThis post is deleted!
-
wrote on 10 Aug 2020, 07:56 last edited by
I also encountered the problem, I can't resolve the problem so far, so could you tell me your means to
solve the problem? thank you!