I got it work! Kind of a stupid problem but when comparing the config 
between RCN's 3.12 and 3.13 kernel, I realized that CONFIG_FB_DA8XX was no 
longer set. SGX is now working, when I start the PVR service I still get 
one set of symbol errors.

/opt/gfxlibraries/gfx_rel_es8.x # /etc/init.d/rc.pvr start
[   77.420860] omaplfb: Unknown symbol register_vsync_cb (err 0)
[   77.427111] omaplfb: Unknown symbol unregister_vsync_cb (err 0)
Loaded PowerVR consumer services.

/opt/gfxlibraries/gfx_rel_es8.x # lsmod
omaplfb 12126 0 - Live 0xbf048000 (O)
da8xx_fb 11448 1 omaplfb, Live 0xbf041000
pvrsrvkm 179069 1 omaplfb, Live 0xbf000000 (O)

All the demos appear to run fine.

On Friday, March 28, 2014 12:41:51 PM UTC-6, Brett wrote:
>
> I am having trouble getting the SGX libs to work properly with kernel 3.13 
> from https://github.com/RobertCNelson/linux-dev. I did have to modify 
> sgx_build_modules.sh to enable FBDEV, my requirements are no X. The first 
> sign of trouble is during the build of the SGX libs I am seeing this 
> warning:
>
> Building modules, stage 2.
> MODPOST 3 modules
> WARNING: "unregister_vsync_cb" 
> [/home/fse/Documents/BBB/linux-dev/ignore/ti-sdk-pvr/Graphics_SDK/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb.ko]
>  
> undefined!
> WARNING: "register_vsync_cb" 
> [/home/fse/Documents/BBB/linux-dev/ignore/ti-sdk-pvr/Graphics_SDK/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb.ko]
>  
> undefined!
>
> This however does not stop the build. After installing the kernel/modules 
> then booting up the BBB I get the following error when trying to kick off 
> the PVR service:
>
>  # /etc/init.d/rc.pvr start
> [  137.596132] omaplfb: Unknown symbol register_vsync_cb (err 0)
> [  137.602219] omaplfb: Unknown symbol unregister_vsync_cb (err 0)
> [  138.046878] omaplfb: Unknown symbol register_vsync_cb (err 0)
> [  138.053136] omaplfb: Unknown symbol unregister_vsync_cb (err 0)
> modprobe: 'extra/omaplfb.ko': unknown symbol in module or invalid parameter
>
> This problem came up after upgrading from kernel 3.12 to 3.13. I can see 
> that register_vsync_cb and unregister_vsync_cb are defined in da8xx-fb.c. 
> Maybe this is a linking problem? Has anyone run into this problem before? 
> Any ideas as to what changed between 3.12 and 3.13?
>
> Thanks!
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to