jd68 wrote:
> What is working? The display is working with DietPi and PiCorePlayer?
>
>
> Do you use pCP or DietPi for the player?
> If you use DietPI, why don't you use a web browser with Material Skin
> instead of Jivelite?
> If you use pCP then you can install Jivelite easily via the Web-GUI of
> pCP.
>
> Is that really the complete line in your script 'jivelite.sh'?
> >
Code:
--------------------
> > EVENTNO=$(cat /proc/bus/input/devices | awk '/ADS7846
Touchscreen/{for(a=0;a>=0;
--------------------
> >
>
> That cannot work because the closing bracket ')' and more is missing.
Thanks!
- I tried it with DietPi and PiCorePlayer. The display and the
framebuffer works, as it displays all colored characters of the boot
message. This result was also the same on my external hdmi (connected
via DVI) when it was not connected to the 5"inch touch display
- I have bought the touch display to have a stand alone solution for
my bathroom
- I use PiCorePlayer now
- The starting colored splash screen comes up
- boot messages comes up
- The PiCorePlayer logo comes up in nice shape
- After that the framebuffer reconfigures to settings and it looks
like above
- The script above of jivelite.sh was lazily copied from console
window. It has the closing brackets
The question left now is, why is framebuffer configured correctly until
"PiCorePlayer" Logo Startup screen and then turns crappy (like in the
above photo), where I guess something is messed up with the control of
the framebuffer (wrong lines, overscan, whatever...). What causes the
system to finally screw up? What happens last after PiCorePlayer startup
screen?
Br
------------------------------------------------------------------------
peddanet's Profile: http://forums.slimdevices.com/member.php?userid=70331
View this thread: http://forums.slimdevices.com/showthread.php?t=115691
_______________________________________________
diy mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/diy
