[Buildroot] libqeglfs.so not found on imx6

Jagan Teki jagannadh.teki at gmail.com
Mon Mar 6 11:44:23 UTC 2017


On Mon, Mar 6, 2017 at 4:33 PM, Jagan Teki <jagannadh.teki at gmail.com> wrote:
> On Mon, Mar 6, 2017 at 3:49 PM, Gary Bisson
> <gary.bisson at boundarydevices.com> wrote:
>> Hi Fabio,
>>
>> On Sat, Mar 4, 2017 at 8:41 PM, Fabio Estevam <festevam at gmail.com> wrote:
>>> On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam at gmail.com> wrote:
>>>> Hi Gary,
>>>>
>>>> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam at gmail.com> wrote:
>>>>
>>>>> Not yet, still stuck at the "drmModeGetResources failed" error.
>>>>
>>>> I can also get this same error with the new kmscube package from:
>>>> https://cgit.freedesktop.org/mesa/kmscube/log/
>>>>
>>>> # kmscube
>>>> drmModeGetResources failed: Invalid argument
>>>> failed to initialize legacy DRM
>>>>
>>>> It works if I explicitly pass the /dev/dri device:
>>>>
>>>> kmscube -D /dev/dri/card1
>>>>
>>>> I think QT5 is trying to access /dev/dri/card0, but it should be using
>>>> /dev/dri/card1 instead.
>>>
>>> Yes, this is the problem.
>>>
>>> If I do an ugly hack like this:
>>>
>>> --- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>>> +++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>>> @@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
>>>      Q_ASSERT(m_gbm_device == Q_NULLPTR);
>>>
>>>      qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
>>> -    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
>>> | O_CLOEXEC);
>>> +    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
>>>      if (m_dri_fd == -1) {
>>>          qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
>>>          return false;
>>> --
>>> 2.7.4
>>>
>>> Then the demo is launched. It still do not run very well, but at least
>>> it starts.
>>>
>>> Does anyone have an idea on what would be a proper fix?
>>
>> That's strange I didn't have to do that. Worst part is that my demo
>> image is using Qt5.6.2 (same as your image) and that I checked no
>> special env variable is set.
>>
>> Maybe you can try your kernel on my image, see if that works.
>
> I just used rootfs, from the link, and kernel 4.9.13 mainline.
>
> Able to see the demo nicely.
>
> Order:
> - kmscube
> - Boundary devices Tux
> - jellyfish
> - ideas in motion
> - 28 fps (1. Lord of the Rings)
>
> So, I'm investigating config options on buildroot will let you know
> for further update.

And by the way, did anyone find this issue.

In file included from
/workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/egl.h:39:0,
                 from
../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/../../../../../src/platformsupport/eglconvenience/qt_egl_p.h:63,
                 from
../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/qt_egl_p.h:1,
                 from api/qeglfsglobal_p.h:56,
                 from api/qeglfsintegration_p.h:54,
                 from qeglfsmain.cpp:41:
/workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/eglplatform.h:119:22:
fatal error: X11/Xlib.h: No such file or directory
 #include <X11/Xlib.h>
                      ^
compilation terminated.

Look like Qt5.8.0 is unable to build with current tool-chain, 5.6.2 succeeded

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.



More information about the buildroot mailing list