USB Remote Control

[Paul Webster]

This one

https://forums.slimdevices.com/showthread.php?116121-USB-Remote-Control&p=1050769&viewfull=1#post1050769

If you make the 2 changes referred to in there then you should see Jivelite.

The changes are in the file config.txt on /mnt/mmcblk0p1

If you do not know how to use the vi editor then probably the easiest way for you to edit it is to put the SD card back into your PC and then use Notepad++ (not Notepad) to edit the file.
Using Notepad++ (you will have to go out and find it) will preserve the line endings that Unix expects.

Microsoft Windows Notepad has (historically at least) changed the line endings to Windows format.
It will appear to look the same when you look at the file ... but Unix will choke on it.

[Frapicore]

This one

https://forums.slimdevices.com/showthread.php?116121-USB-Remote-Control&p=1050769&viewfull=1#post1050769

If you make the 2 changes referred to in there then you should see Jivelite.

The changes are in the file config.txt on /mnt/mmcblk0p1

If you do not know how to use the vi editor then probably the easiest way for you to edit it is to put the SD card back into your PC and then use Notepad++ (not Notepad) to edit the file.
Using Notepad++ (you will have to go out and find it) will preserve the line endings that Unix expects.

Microsoft Windows Notepad has (historically at least) changed the line endings to Windows format.
It will appear to look the same when you look at the file ... but Unix will choke on it.

I have added the two strings in the config.txt file (file attached).

Now there is no signal in the screen (before was black now no signal at all). The remote is still not working.

[Paul Webster]

Instead of adding them to the bottom …
Find the same info in the top part of the file.
Add a # in front of the gpu command and take off the # in front of the kms line (and remove the lines that you added).

[Frapicore]

I misunderstood, sorry for before. Thank you so much for your great patience, a lo lot apreciated.

Still the same, screen without signal and remote not working.

Am I doing something wrong?

[Paul Webster]

Comment out the gpu one by putting a # at the start of the line

[Frapicore]

Comment out the gpu one by putting a # at the start of the line

It is out, do you mean initial_turbo=60 as well?
#gpu_mem=16
initial_turbo=60

[Paul Webster]

I still see it at the end of the file (although it might be Tapatalk caching the old one)

[Frapicore]

I still see it at the end of the file (although it might be Tapatalk caching the old one)

I have edited:
gpu_mem=16
dtparam=audio=on
dtoverlay=vc4-kms-v3d

as for below

#---pCP----------------------------------------------
# pCP does not use graphics chip by default, free up most memory
#gpu_mem=16
initial_turbo=60

# onboard audio overlay
#dtparam=audio=on
audio_pwm_mode=2

# For Jivelite use with HDMI screens
# Comment out the lines above
# gpu_mem=xx
# dtparam=audio=on
# Then uncomment the following line.
dtoverlay=vc4-kms-v3d

Before the screen was black now there is no signal after the boot (I can see just the rpi boot and after no signal). I have edited the config.txt file with TextEdit via Mac.

The rpi is connected to the monitor via hdmi and I have just installed jivelite from pCP. Can someone see something wrong?

Thanks!!

[Paul Webster]

I replaced my config.txt with yours on my RPI Zero 2 W and rebooted from power off ... and it worked.
I could see Jivelite on the HDMI monitor.
With the keyboard attached I could switch back to the console - ctl+alt+f1 (ctl+alt+f2 to switch back to Jivelite).

Which model Raspberry Pi are you using? You can see it from pCP web interface / Diagnostics / Raspberry Pi.

If it has 2 HDMI ports ... which one are you using?

[Frapicore]

I replaced my config.txt with yours on my RPI Zero 2 W and rebooted from power off ... and it worked.
I could see Jivelite on the HDMI monitor.
With the keyboard attached I could switch back to the console - ctl+alt+f1 (ctl+alt+f2 to switch back to Jivelite).

Which model Raspberry Pi are you using? You can see it from pCP web interface / Diagnostics / Raspberry Pi.

If it has 2 HDMI ports ... which one are you using?

All right, this is a great info, at least I did nothing wrong.

The model is 4B with 2gb. it has 2 micro hdmi outputs.

At the moment the screen is black, so actually is outputting something but cannot see jivelite

[Paul Webster]

Which HDMI port are you using?

If you use the keyboard and do
ctl+alt+f1 (hold all 3 keys down together) does it switch back to the console with the text showing it booting?

[Frapicore]

Which HDMI port are you using?

If you use the keyboard and do
ctl+alt+f1 (hold all 3 keys down together) does it switch back to the console with the text showing it booting?

I am using mainly the one close the usb-C (power) but I have tried also the other one. It seems the same, after the boot the picore logo the screen become black.

Regarding the second question, I am not sure. I have linked an usb keyboard. Sometimes it goes back to the boot/console screen sometimes no. With ctl+alt+f1 nothing happens, but sometimes if I push all the buttons it goes to the console screen and I can also write with the keyboard after it goes back to the black screen. Unfortunately, this is random and I am not able to go to the console whenever I want to.

[Paul Webster]

OK - leave it connected to the one beside the USB-C power socket.

I am running out of ideas ... so next step is to see if we can get an error message out of Jivelite.

Stop the script the script that launching Jivelite because it relaunches it each time that it fails and you will get a huge log file since all of the messages will be appended.

ps -ef | grep jive

#one of the lines will look very similar to this
9515 root 0:00 {jivelite.sh} /bin/sh /opt/jivelite/bin/jivelite.sh

#make a note of the number at the front (it will not be the same as above)
#then
sudo kill -5 xxxx
# but replace the xxxx with the number that you saw from the output of the previous command

# then
ps -ef | grep jive
# and you should see that jivelite.sh is no longer running (not listed any more).

# then create a file called logconf.lua (see contents below - use Unix line endings) - download it and copy it to /home/tc/.jivelite/userpath/logconf.lua
# one easy way to do this is to use the vi editor on the Raspberry Pi
vi /home/tc/.jivelite/userpath/logconf.lua

# if there is already some content in the file then delete it by typing
dd
# then paste in the contents of the file by typing
i
# and then paste it in ... and then
esc
:wq
# where "esc" is the escape or Esc key

# If all of that is too hard then find a program that can transfer files using "scp" - on MS Windows winscp is good.

# If that worked then if you type
cat /home/tc/.jivelite/userpath/logconf.lua
# you should see the contents of the file

return {
  appender={  },
  category={
    ["applet.DesktopJive"]="ERROR",
    ["applet.HttpAuth"]="ERROR",
    ["applet.LogSettings"]="ERROR",
    jivelite="ERROR",
    ["jivelite.applets"]="ERROR",
    ["jivelite.heap"]="ERROR",
    ["jivelite.player"]="ERROR",
    ["jivelite.task"]="ERROR",
    ["jivelite.ui"]="ERROR",
    ["jivelite.ui.draw"]="ERROR",
    ["lua.hooks"]="ERROR",
    ["net.comet"]="ERROR",
    ["net.http"]="ERROR",
    ["net.socket"]="ERROR",
    ["net.thread"]="ERROR",
    ["squeezebox.server"]="ERROR",
    ["squeezebox.server.cache"]="ERROR"
  }

# ... then ...
/opt/jivelite/bin/jivelite

# then examine the end of the log file
tail -20 /var/log/jivelite.log