I've moved this over from the pCP6/Pi4 thread, where it wasn't really on-topic.
The Jivelite on Alpine Linux thread prompted me to have another go at getting Jivelite to work on the little Pirate Audio 240x240 display. After following JQW's instructions for getting the screen to show the boot up messages, and copying over Ralphy's file to configure detailed logging, I'm then trying to start Jivelite from a keyboard connected to the RPi, via a slightly modified script:
I included the TSLIB_FBDEVICE variable in an attempt to get jivelite to use the correct framebuffer device for this little screen - not sure if that's the correct approach.
All that happens when I run the script is that the cursor on the screen stops flashing. The jivelite process is evidently running (I can see it as a process with PS), and the the logfile rapidly starts filling up. The only way I can get control back on the keyboard/screen is by killing the jivelite process from an SSH terminal.
I think the fbset command is telling me that the little screen has a bit depth of 16
..whereas /dev/fb0 has a bit depth of 32
I can't seem to match the jivelite log file to either of these devices:
JiveLite 0.1.0
[0;33m20200118 09:01:11.587 INFO jivelite - JiveMain.lua:312 JiveLite version 0.1.0[0m
[0;33m20200118 09:01:11.587 INFO jivelite.ui.draw - jiveL_initSDL:232 initSDL[0m
[0;33m20200118 09:01:11.710 INFO jivelite.ui.draw - jiveL_initSDL:245 656,416 32 bits/pixel 4 bytes/pixel [R<<16 G<<8 B<<0][0m
[/code]
Is that fourth line telling me that the device is 656x416, with bit depth 32?
So I'm wondering if Jivelite is sending the output somewhere else. What's the correct way to force it to use /dev/fb1 ?
The Jivelite on Alpine Linux thread prompted me to have another go at getting Jivelite to work on the little Pirate Audio 240x240 display. After following JQW's instructions for getting the screen to show the boot up messages, and copying over Ralphy's file to configure detailed logging, I'm then trying to start Jivelite from a keyboard connected to the RPi, via a slightly modified script:
Code:
#!/bin/sh
if [ ! -z ${SDL_TOUCHSCREEN} ]; then
export JIVE_NOCURSOR=1
fi
export HOME=/home/tc
export JIVE_FRAMERATE=22
export JL_SCREEN_WIDTH=240
export JL_SCREEN_HEIGHT=240
export TSLIB_FBDEVICE=/dev/fb1
#while true; do
# sleep 3
/opt/jivelite/bin/jivelite >> /var/log/jivelite.log 2>&1
#doneAll that happens when I run the script is that the cursor on the screen stops flashing. The jivelite process is evidently running (I can see it as a process with PS), and the the logfile rapidly starts filling up. The only way I can get control back on the keyboard/screen is by killing the jivelite process from an SSH terminal.
I think the fbset command is telling me that the little screen has a bit depth of 16
Code:
fbset -fb /dev/fb1 -s
mode "240x240-0"
# D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
geometry 240 240 240 240 16
timings 0 0 0 0 0 0 0
accel false
rgba 5/11,6/5,5/0,0/0
endmodeCode:
fbset -fb /dev/fb0 -s
mode "800x600-72"
# D: 50.000 MHz, H: 48.077 kHz, V: 72.188 Hz
geometry 800 600 800 600 32
timings 20000 64 56 23 37 120 6
accel false
rgba 8/16,8/8,8/0,8/24
endmodeJiveLite 0.1.0
[0;33m20200118 09:01:11.587 INFO jivelite - JiveMain.lua:312 JiveLite version 0.1.0[0m
[0;33m20200118 09:01:11.587 INFO jivelite.ui.draw - jiveL_initSDL:232 initSDL[0m
[0;33m20200118 09:01:11.710 INFO jivelite.ui.draw - jiveL_initSDL:245 656,416 32 bits/pixel 4 bytes/pixel [R<<16 G<<8 B<<0][0m
[/code]
Is that fourth line telling me that the device is 656x416, with bit depth 32?
So I'm wondering if Jivelite is sending the output somewhere else. What's the correct way to force it to use /dev/fb1 ?