Grumpy Bob wrote:
> I can't see anything obvious written in the card, but I might have to
> disassemble the device to have a look. The Y button operates as
> specified in your script file.
>
> I ran through your latest instructions twice yesterday evening, always
> with the same result: if I place the sbpd-script.sh command in the User
> Commands, the Pi won't boot to Jivelite. The only deviation was to
> install nano, which is my preferred editor.
>
> I need to boot without the User Command to reach Jivelite, then run sudo
> /home/tc/sbpd-script.sh & in a terminal to get Jivelite to respond to
> the buttons. If I run the command in a terminal as user tc, it throws an
> error and the buttons remain inoperable.
>
> I'm accessing the pi via ssh using Terminal on a Mac, logging in as user
> tc. I pasted your script into the file using nano - this did need some
> reformatting, so maybe there's an error I didn't note.
>
> Robert
Thanks for persevering. OK, so there's evidently something real here,
but it's odd that I can't reproduce it with either of my Pirate Audio
boards, or on two different RPis. If the Y button is responding with my
script loaded, then you must have the pre-Jan 23rd version. And if you
can get Jivelite and the buttons working simply by running the sbpd
script after Jivelite has started, then that would seem to rule out
possible errors in the script.*
I think you've mentioned in the past that your RPi sits at the
'Requesting system poweroff' screen, without ever launching Jivelite.
But that screen is part of the shutdown process, not the boot process,
so can you clarify whether you do in fact see the RPi booting up again?
Do you see the boot up messages on screen, including this header?:
Code:
--------------------
_ _____ ___ __
___ (_) ___/__ _______ / _ \/ /__ ___ _____ ____
/ _ \/ / /__/ _ \/ __/ -_) ___/ / _ `/ // / -_) __/
/ .__/_/\___/\___/_/ \__/_/ /_/\_,_/\_, /\__/_/
/_/ /___/
--------------------
If you do, then perhaps we should be looking into the log file to see
what's happening at boot to prevent Jivelite from loading. You can turn
on all logging with Ralphy's instructions 'here'
(https://forums.slimdevices.com/showthread.php?111488-Jivelite-on-Alpine-Linux&p=960815&viewfull=1#post960815).
Jivelite.log can then be found in /var/log/. If it's booting but not
launching Jivelite at all, then I guess that file might not be created,
or might be empty, in which case the log files in the Diagnostics
section of pCP might help.
* By the way, if you're using a Mac, I can recommend FileZilla as a way
to access the RPi - it gives you a graphical interface to transfer
files. And if you also install TextWrangler you can set up FileZilla to
use TextWrangler as the default editor. This allows you to right-click
in a folder on the RPi to create a new blank file, then right-click on
that new file in order to View/Edit it, and it will load into
TextWrangler. You can then paste the script in, and there should be no
formatting differences.
------------------------------------------------------------------------
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread: http://forums.slimdevices.com/showthread.php?t=111502
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
