JustRay wrote: > > - The 3.5 TFT display is working flawlessly. At the end of the boot > sequence PcP says "Starting Jivelite...Done." But that's it and I cannot > find any jivelite-entry in "sudo ps". > - The jivelite.sh seems to be located at many different places. > - /mnt/mmcblk02p2/tce/ - of course cause I placed it there > - /var/tmp/tcloop/pcp-jivelite/opt/jivelite/bin/ - this is a of course > tmp one but it is pointing on the next one > - /opt/jivelite/bin/ - this one is strange. It looks pretty much > different then the one I entered. > > could it be that there are inconsistencies which are causing the > negative effect? Are there any logfiles helping detecting?
Hi JustRay, piCorePlayer only supports the "Raspberry Pi official 7" screen" but to make it easier for people attempting to use other screens in the startup script we look for a jivelite.sh in /mnt/mmcblk02p2/tce/ and run that script instead. piCore loop mounts extensions so you will always see the symbolic links. The one in the /opt/jivelite/bin/ is pCP code for starting jivelite (for the official screen). Setting up another screen is fairly straight forward, the only issue is that there are so many different screens! Some have the driver imbedded in the kernel, some have drivers available in Linux, some you have to download the driver, and some use the generic driver with 10 or 20 options. On top of that some generic screens you can use driver(s) that is available in Linux, OR download the driver from at least three different locations, OR use the generic driver. regards Greg ------------------------------------------------------------------------ Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=107366 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
