2011-06-23, 21:38
Hi,
i use a fresh compiled XBMC (opdenkamp git) on my pandaboard (omap4 running ARM board)
which works with --enable-gles quite nice.
BUT: The VNSI plugin isn't able to be loaded
The VDR works with VNSI, tested by other machines in the wifi,
but the (only) ARM one shows an uncloseable info dialog mentioning the VNSI plugin could not be loaded after activating it.
The log shows:
Does anybody know what the bad status (4) means? Is it documented anywhere?
The same git clone works on a i386 machine with the VDR over VNSI..
i use a fresh compiled XBMC (opdenkamp git) on my pandaboard (omap4 running ARM board)
which works with --enable-gles quite nice.
BUT: The VNSI plugin isn't able to be loaded
The VDR works with VNSI, tested by other machines in the wifi,
but the (only) ARM one shows an uncloseable info dialog mentioning the VNSI plugin could not be loaded after activating it.
The log shows:
Code:
14:29:19 T:1332507648 M:405499904 DEBUG: PVR - Create - creating PVR add-on instance 'VDR VNSI Client'
14:29:19 T:1332507648 M:405499904 DEBUG: ADDON: Dll Initializing - VDR VNSI Client
14:29:19 T:1332507648 M:405499904 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (4) from Create and is not usable
14:29:19 T:1332507648 M:405499904 INFO: Called Add-on status handler for '4' of clientName:VDR VNSI Client, clientID:pvr.vdr.vnsi (same Thread=no)
14:29:19 T:1332507648 M:405499904 ERROR: PVR - LoadClients - can't initialise client 'VDR VNSI Client'
14:29:19 T:1458115584 M:405499904 DEBUG: Thread Addon Status: VDR VNSI Client start, auto delete: 1Does anybody know what the bad status (4) means? Is it documented anywhere?
The same git clone works on a i386 machine with the VDR over VNSI..
