OpenEmbedded console-tdx-image does not load gfx kernel module correctly

Hi,

I followed closely the instructions to build the console-tdx-image, which succeeds without problem. After that, I created an SD card to boot the image as described here. This works too, but then when booting the image, I get the following:

         Starting Load Kernel Modules...
[    7.824982] galcore: Unknown symbol viv_fence_create (err 0)
[    7.832258] galcore: Unknown symbol viv_sync_timeline_destroy (err 0)
[    7.840879] galcore: Unknown symbol viv_sync_timeline_create (err 0)
[    7.849118] galcore: Unknown symbol sync_file_get_fence (err 0)
[    7.856685] galcore: Unknown symbol sync_file_create (err 0)
[FAILED] Failed to start Load Kernel Modules.

There is also periodic spam on the console output, like this (a monitor is attached to VGA):

[  192.190784] mxc_sdc_fb fb@0: 640x480 h_sync,r,l: 64,16,80  v_sync,l,u: 4,3,13 pixclock=23750000 Hz
[  192.247325] mxc_sdc_fb fb@0: 640x480 h_sync,r,l: 64,16,80  v_sync,l,u: 4,3,13 pixclock=23750000 Hz
[  192.307872] mxc_sdc_fb fb@0: 640x480 h_sync,r,l: 64,16,80  v_sync,l,u: 4,3,13 pixclock=23750000 Hz
[  192.367320] mxc_sdc_fb fb@0: 640x480 h_sync,r,l: 64,16,80  v_sync,l,u: 4,3,13 pixclock=23750000 Hz
[  192.428228] mxc_sdc_fb fb@0: 640x480 h_sync,r,l: 64,16,80  v_sync,l,u: 4,3,13 pixclock=23750000 Hz

What is the problem here? Thanks

Hi

The BSP 3.0b1 has been released for Apalis iMX8QM only. All other SoM types may or may not work when built from that BSP version.

We are working on BSP 3.0b2 which will support all SoM types including the Colibri iMX6.

Max

I was able to repro this issue. Freshly build Colibri-imx6_Console-image-Tezi-3.0b1-2019xxxx demonstrate the same issue.

fbset output:

mode "640x480-59"
        # D: 23.750 MHz, H: 29.688 kHz, V: 59.375 Hz
        geometry 640 480 640 480 16
        timings 42105 80 16 13 3 64 4
        accel false
        rgba 5/11,6/5,5/0,0/0
endmode

Ok, thanks.

We were able to fix the problem - the Colibri iMX6 kernel defconfig apparently was missing the CONFIG_SYNC and CONFIG_SYNC_FILE

This may fix the issue with whatever combination of linux-kernel, linux-imx-headers and the galcore kernel module you now have.
In 3.0b2 this components will be compatible to each other out of the box.