I just attempted an insitu update in my main server from 6.0.0-b1 to
rc1. To my surprise it seems to have worked fairly well - features that
weren't in b1 are now present (e.g. the Jivelite frambuffer settings),
and the footer shows that I'm on rc1. I know that somewhere between b1
and rc1 the
paul- wrote:
> If you grab the latest pcp6 update/image, you can play with the new
> overlay. Detailed configuration info is in the overlays/README file
>
> dtoverlay=st7789v-spi
That's great, thanks Paul
I did an insitu update, then replaced both modprobe commands in
/opt/bootlocal.sh with
Thanks for the suggestions Paul - still no joy I'm afraid. I'll have a
bit of a read and see what I can find.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
paul- wrote:
> Are you sure they are SPI?SDA and SDL are typically i2c signals.
Well I don't really know enough to know the difference, but 'this one'
(https://www.amazon.co.uk/gp/product/B07QGQ1SR2) says '4-Wire SPI
Interface' in the description, and on the back of the PCB it says
ian_heys wrote:
> I used to export/edit/import the file.
>
When you right click on a pCP file in the right pane of FileZilla, then
'View/Edit', that's effectively what it does too - it's not really an
'in place' edit. It downloads a copy, opens it in the editor, and then
prompts you to
KeBul wrote:
>
> So my issue was something in my process and tools on my Mac - probably
> TextEdit.
>
Use 'BBEdit'
(https://www.barebones.com/support/bbedit/updates.html#up12) (ex
'TextWrangler'). The free version is a great full-featured text editor
that works perfectly with Linux text
paul- wrote:
> I picked up a cheap st7789v based display.works just fine with the
> new driver and overlay.
>
> This display and driver do not use the MISO channel on the SPI
> interface, so you can leave it unwired. The Pirate Audio board actually
> reuses this for DC. I used an
paul- wrote:
> Cant you just hook up to bcm7/CE1?
D'Oh, yes, of course I can. What threw me initially was that I'd wired
it up as per the pinout diagram 'here'
(https://pinout.xyz/pinout/pirate_audio_line_out), yet still I needed to
change the CS pin in the modprobe command. I believe that
paul- wrote:
>
> All rotations work. I'll likely change the name of the overlayI did
> this to make sure I did not have other driver conflicts.)
> >
Code:
> >
> dtoverlay=piratelcd
> dtoverlay=piratelcd,rotation=90
>
castalla wrote:
>
>
> So, and it's a big ask I know, would it be possible to provide JfJ with
> the later bionic kernel or using the development version?
>
That's a bit unlikely in the immediate future I'm afraid. I'll see if
it's simply a matter of copying some files over from the earlier
paul- wrote:
>
> Looking at the MIPI drivers, they are really simple. I wonder if one
> of them would work.or maybe just write the driver, and compile it.
You mean something based on the easyfb.c example? When I looked at that
I did not understand the benefit of a dedicated driver
Indeed, a 270 rotation is also possible now, using your 80 pixel offset.
So in summary we have:
0 degrees (ribbon cable connection at the bottom of the display):
Code:
-1,0x36,0x00,\
90 degrees (ribbon cable connection to the right of the
nincompoop wrote:
>
> I looked at the ST7789 data sheet for a long time but in the end 'a
> blog'
> (https://krystof.io/mirroring-raspberry-pi-hdmi-video-to-a-st7789-1-3-inch-lcd-display/)
> helped me out. An extra line did the trick as is mentioned in the data
> sheet in 9.1.29 Vertical
Grumpy Bob wrote:
> Finally in its case...
> 29357
>
> This is with the PirateAudio headphone amp board, and is the latest
> addition to the Raspberry Pi players I have...
>
> Robert
That looks like a nice print. It doesn't look like extruded filament.
Do you know what type of printer was
Oh, and another thing to keep in mind - it was pointed out 'earlier'
(https://forums.slimdevices.com/showthread.php?111502-Jivelite-on-a-Pirate-Audio-240x240-screen=962304=1#post962304)
that newer versions of the Pirate Audio boards will use a different GPIO
for the Y button. Going forward I
paul- wrote:
> Just thinking out loud here. So I think the best way to handle startup
> of the screen is through managing a screen extension.
>
Have you decided against an overlay? What you have suggested makes
sense, and having an automated way to make use of all the features of
the board
I have to say, elegance in the code is one of the things that appeals to
me in programming, and this bit of the script now seems rather elegant.
The problem I face is that I can barely make bash do what I want it to,
so my efforts end up rather 'clunky'! It's always a pleasure to see how
That works perfectly, thanks Greg, and Greg :-)
If I run this as a user script (without sudo), rather than as a start-up
user command, then pigpiod doesn't start, so I get the 10 second
time-out. If I run it with sudo then it initialises after the first
loop though, i.e. it takes a second to
Greg Erskine wrote:
> Is this a ash/sh Linux script?
>
> Is this line OK?
>
> if (( count-- <= 0 )) ; then
Apparently it's not ok. I'm running this under pCP6-b9. I changed my
script to look like this, so that that line is line 16:
Code:
#!/bin/sh
# start
mherger wrote:
>
> And I thought I had committed them myself already... thanks anyway!
>
There was also a Dutch translation to include, as well as other
'brightness' translations, so I thought it was easier on Ralphy for me
to consolidate them into one place.
I'm not sure if it's my place
mherger wrote:
> > I have the patch ready for JiveMain and will rebuild jivelite when
> the
> > strings file is ready and Michael has added German and French
> > translations for the Square QVGA skin.
>
> Uh, oh... what file? French? I hope there isn't much more than a few
> words :-D
>
I
castalla wrote:
>
> Any ideas?
>
Nope. Is Roobarb's comment related to the Bionic images that I started
from, or the newer image that he's made? I don't have an OF2, and
wouldn't know how to go about trying the broadcom-wl driver I'm afraid.
ralphy wrote:
> Do you get the When Off menu item in the screen->screensavers with the
> pirate audio?
Yes. And separately, the 'Brightness when off' menu is a setting under
the piCorePlayer applet.
chill's Profile:
castalla wrote:
> It currently shows the line-ou+speaker on start-up
Yeah, that's not right. The Joggler retains the last used setting
across a reboot, and the applet should show whatever the current setting
is.
The version in the attached zip does this properly now. Whenever the
the screen
castalla wrote:
> Thanks - seems to work!
Ok, good. I need to update it to read the current mode at start-up, so
that the correct option is selected when the applet first loads.
chill's Profile:
ralphy wrote:
> I have the patch ready for JiveMain and will rebuild jivelite when the
> strings file is ready and Michael has added 'German and French
> translations for the Square QVGA skin'
> (https://github.com/ralph-irving/jivelite/commit/3cbbd84842b482a838cde3a434ca6dcd4388298e).
I've
castalla wrote:
> Thanks.
>
> Another thought: how about an applet which could switch the line-out
> between the 3 options in alsamixer?
Try this draft version. Download the attached zip and put the resulting
folder in /root/.jivelite/userpath/applets, then restart Jivelite. The
applet
castalla wrote:
> Thanks.
>
> Another thought: how about an applet which could switch the line-out
> between the 3 options in alsamixer?
That seems possible. The command line version is:
Code:
amixer sset 'Auto-Mute Mode' 'Line Out+Speaker' (or 'Speaker Only' or
CURRENT BEST STEPS AS OF 09FEB2020 (TO SUIT NEW B9 IMAGE):
Put a fresh pcp6-b9 image on the SD card.
Whilst the SD card is still in the laptop:
Enter wifi credentials in wpa_supplicant.conf.sample and save as
wpa_supplicant.conf
Add these parameters to the end of cmdline.txt. All of the
gregklanderman wrote:
> FWIW you should be able to simplify that loop to
>
> >
Code:
> >
> while ! pigs t >/dev/null 2>&1 ; do
> #printf "\nWaiting for pigpiod to initialize\n"
> sleep 1
> done
> printf "\npigpiod is running\n"
>
paul- wrote:
> I had my boards for a few days, but left them in the box until I could
> get the next pCP images out. I have the board with headphones out
> (And a line out board). Working perfectly...I'll see if I can
> streamline some of the install.
>
Thanks Paul - looking forward
castalla wrote:
> A little off current development. I'd like to have a custom wallpaper
> (plain dark red) - how to achieve that?
Make a PNG image that's 800x480, give it a name with the prefix 'pcp_',
e.g. 'pcp_DarkRed.png', then copy it to
/root/.jivelite/userpath/wallpapers.
Nearly there I think.
I have an 'LMS' applet that sits under the 'settings' section:
[image:
http://www.cjh.me.uk/MyPhotobucket/cache/DIYHifi/Jivelite/Settings%20with%20LMS_640.jpg]
It currently allows the LMS service to be disabled or enabled (referred
to as 'Autostart LMS'), and it allows
Paul Webster wrote:
> Is it using systemd to start it?
> As in systemctl start
>
> If it is the you can leave it all set-up and then
> systemctl enable
> To enable it to start on boot
> and
> systemctl disable
> To stop it starting on boot
Oh good grief - that's much simpler. Thank you
I've made my own init.d script file so that LMS can autostart, or not,
depending on a condition. It does this by conditionally calling the
original script file, which I've moved to a different location. I just
need an applet to set a flag now. And LMS can be
started/stopped/restarted from the
chill wrote:
> So the applet could set a flag, but I don't know how to start the
> service at boot depending on the status of that flag. Any ideas?
I think this will be easier than I anticipated. I took the
'logitechmediaserver' script file out of /etc/init.d, and placed it
somewhere
I've installed LMS 7.9.3, added a bit of music to a third partition on
the USB stick, added Spotty and configured DSTM, and we're away. It's a
nice little stand-alone server/player/controller.
I think an applet to toggle LMS will be straightforward, but I doubt
that most people would want to
castalla wrote:
> Sounds good.
>
> Could you make the LMS applet installable on my existing setup?It
> took ages to set up LMS with all my plugins and pref files
Yes, applets can be added manually. But you can backup the settings
from one installation and use them to update a fresh
Great - ok, I guess that file was somehow left out of the original
Bionic build that I made the external image from. It's probably worth
me updating the USB image to correct this, but first I'll have a play
with LMS to see if I can include it in the image with an Applet to
toggle it on or off.
There are some useful threads on the jogglerwiki forum. I think the
solution to this is to update one file. It worked on my 4th Joggler, so
can you give it a go on yours?
I believe you'll find a file in /etc/modprobe.d called
of1-stac9202.conf. On mine I think it was 77 bytes, but empty. If
castalla wrote:
> Sqpos is different - same as your second image
>
> Very strange
This is all new territory for me. I guess it's something to do with the
alsa setup, so I'll see what I can learn by comparing the two versions.
Hmm - I've spotted the connection. Of my four Jogglers, the odd one out
is the one that's running from a USB memory stick. If I boot one of the
others from the same USB image, rather than in the internal image
they've been using, then alsamixer no longer offers the headphone option
or the
It seems like the autoswitching can be configured, using alsamixer. But
I'm seeing differences between my 4th Joggler and one of the others. If
you ssh in and type 'alsamixer' you should see a screen something like
this:
[image:
castalla wrote:
> Same unit:
>
> Sqpos - sound on internal without cable. Sound disappears when cable
> inserted.-plays on external speaker
>
> Jivelite - sound on internal. Sound continues on internal when cable
> inserted - no sound on external speaker
I can't explain that. I'll try
castalla wrote:
> Problem, I'm afraid.
>
> Sound plays on internal speakers - a line-out doesn't cut the internal
> speakers and no sound on wired speaker ((unlike sqpos 3 where the sound
> is only on the line out)
I've just tried this on 4 different Jogglers. On three of them the
sound
castalla wrote:
> I use the terminal commands via ssh
>
> service logitechmediaserver stop -start - restart
Thanks.
castalla wrote:
>
> (I need to read up the thread items on enabling Squeelite - with output
> to the audio jack to redirect to a stereo amplifier - any tips?)
Yep -
If you want to remove the non-functional 'Display Standby' applet, just
remove the /opt/jivelite/share/jive/applets/JogglerStandby folder
altogether.
I'm going to have a play with LMS. Maybe a new USB image with it
already built in would be handy. Is there a command line method to
start and
Having now looked into the 'Display Standby' applet, I don't think it's
worthwhile to modify this applet for this Jivelite build.
There's this comment at the top of the applet:
> This applet sets the display standby time on O2 Jogglers running the
> native operating system.
Within the code it
castalla wrote:
> Ah! I really would appreciate something to blank the screen - bit of a
> glow would be acceptable!
I've just connected up a spare Joggler in order to start looking at
this, but I thought I should point out that the 'Blank Screen'
screensaver is already implemented the way I
One last call for translations before I ask Ralphy to go ahead with what
we've got.
I have three languages so far:
DE
[image:
http://www.cjh.me.uk/MyPhotobucket/cache/DIYHifi/Jivelite/240x240/Languages/DE%20On.jpg]
[image:
carsten_h wrote:
> It is working.
>
>
>
> Yes, CCC ist using rsync internally. I started it to test yesterday, but
> there are always all files synced. There has to be some problem with
> dates or filenames or so.
What is the format of the two disks? I encountered various issues like
this
carsten_h wrote:
> Ok, this seems to be interesting. I think it should also be possible to
> mount the disk via smb on the Mac if this is installed in piCorePlayer?
> So I only have to let CCC to do the synchronization automatically when
> the disk is mounted.
> Or is FileZilla able to do a
castalla wrote:
> Ah! I really would appreciate something to blank the screen - bit of a
> glow would be acceptable!
I'll see if I can remember how to tackle this then!
chill's Profile:
castalla wrote:
> Run into a problem!
>
> Screen display settings - eg. standby - don't seem to be working.
> Screen is always on.
>
> Have I missed something?
No, I never did find out how to turn off the display - the method used
in sqpos doesn't seem to work under this Bionic build.
carsten_h wrote:
>
> Yes, that is correct, but on my Mac where the music is stored, I have
> only support for these. I have to install extra software for ext*
> support because this is not really supported here.
I also use a Mac, and I adopted EXT4 for my music storage attached to my
RPi4.
castalla wrote:
> After a few failed attempts, I finally got LMS to install. It works
> really well.
>
Good man! I did wonder how well LMS would run on the Joggler. Is it
responsive enough?
chill's Profile:
Thanks Carsten - I'm collecting all the updates in my own local copy of
these strings. I'll make those two corrections.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
ralphy wrote:
> It is private. Attached are Michael's updates.
Perfect, thanks Ralphy. And thanks Michael, they're even shorter than
the EN versions.
chill's Profile:
M-H wrote:
> OKE Chill, here is the Dutch input:
>
> >
Code:
> >
> # SLT: QVGA refers to the "quarter VGA" resolution of the display
> EN QVGA 240x240 Square Skin
> # NL QVGA Landscape-skin
mherger wrote:
>
>
> The brightness change is on the pCP repository, which is hosted on
> Gitlab:
>
> https://gitlab.com/piCorePlayer/pCP/commit/3c36e770e3b0b0c668984aaed6b74fa856dd2841#330811c1a2db0faf1918dde1b5d7e599152f1586
>
I'm guessing this might be a private, or hidden, project.
Thanks Michael - I'll definitely investigate.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread: http://forums.slimdevices.com/showthread.php?t=111502
Thanks Michael. I'm struggling to keep up with all this repo talk! Can
you point me to where the updates are?
I was going to maintain a list of the updated strings, so that Ralphy
can commit them. If you've updated the repo already, then so much the
better, but I'd also like to add the
mherger wrote:
>
> (oh... it's not up to date - in particular not the strings file)
>
I think it is up to date - but the brightness-related strings are in the
piCorePlayer applet's strings file.
chill's Profile:
mherger wrote:
> > Great, thanks Michael. I don't have a github respository, so I'm
> > attaching the files below. They should both be named 'strings.txt'
> (as
> > you're well aware), but I've prefixed them so that I can attach them
> > both here.
>
> I'm a bit confused about the
mherger wrote:
> > The other translations I'd appreciate some help with relate to
> > 'minimised' versions of what is shown on the brightness screens.
> These
>
> Do you have a github repository? My German is quite ok :-D.
>
> > Code:
> >
> >
Thanks M-H
You are correct - the new text strings should not have any reference to
landscape or portrait. My EN 'exemplars' (without the preceding #) are
the strings that need to be translated - I only left the old strings in
there for information, but since they are preceded by the # symbol
I've almost finished the changes to the 240x240 skin and the rest of
Jivelite to make the brightness controls work. One outstanding task is
the multilingual translations of various on-screen messages. One of the
really nice things about Jive/Lua is that the language support is built
in - we
M-H wrote:
>
> But it might not be enough sound while driving you camper.
> It helps to power them at the max voltage of 5,5 Volts with decent wires
> and capacitor.
>
You're absolutely right. The radio has to be quite loud when driving at
speed, thanks to a combination of road, engine and
I'm embarrassed to say that simply enabling the equaliser in the audio
tweaks section worked beautifully on another fresh install. So it was
my misunderstanding of the process, and my unnecessary manual install of
alsaequal.tcz, that caused my problems.
I tried this Pirate Audio 3W amp board
M-H wrote:
>
> So do not install the .tzc yourself .
Ah, ok, that's different from the way I've been doing it. I've found
that I can edit /usr/local/etc/pcp/pcp.cfg to set OUTPUT="equal", and
then it all works fine. I assumed that installing the .tcz and enabling
the equaliser would do this
mark f wrote:
> FYI - Adafruit has a dual SPI display card for Raspberry PIs called the
> animated eyes bonnet (https://www.adafruit.com/product/3356). I realize
> it would need to stack with an I2S DAC or digital AMP. It just might
> make wiring something like this a bit easier. Then again,
paul- wrote:
>
> And equal has to be in the squeezelite output string for it to work.
> That should be locked that way when alsaequal is installed.
I'm having trouble with this. It seems the 'HiFiBerry DAC Zero/MiniAMP'
isn't the issue after all, but rather coercing '-o equal' into the
...and the equaliser settings DO affect the output of the 'line out'
version - even my tiny portable speaker can be made to sound better.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this
I changed the output device under Squeezelite to 'Generic/simple TI5102
DAC' and now it's working properly. The output setting now shows
'equal', and the sliders work as expected. The only oddity is that
under 'Audio Tweaks', it is still saying that the equaliser device is
M-H wrote:
> As there were multiple difference, I swapped out my /etc/asound.conf for
> yours. And still I can use the equaliser.
> What output device does your squeezelite use?
> >
Code:
> > ps | grep squeezelite
> >
> M-H
Hmmm. My squeezelite
paul- wrote:
> You have to press the "Test" button after moving the slidersthen
> finally Save.
>
> I've not encountered any device that doesn't work. Even works with
> Bluetooth devices. Can you post a copy of your /etc/asound.conf after
> setting up alsaequal?
'Test' doesn't change
paul- wrote:
> Alsaequal is done before the audio is passed to the hardware. Should
> not be a problem
Hmm - must be user error then. I loaded alsaequal.tcz (nothing else),
and it gave me the ALSA 10 band equaliser option in Audio Tweaks, but
nothing I do with the sliders makes any
M-H wrote:
> I have to learn more on SPI too but looking at 'this'
> (https://pinout.xyz/pinout/spi) the BMC 7/8 are for SPI0 and there is
> a full second set.
> It looks like a chipselect, where 2 slaves can co-exist on the same
> serial bus, and the SC directs which one is addressed.
> The
M-H wrote:
> Nice optimisation Chill,
> For use in your camper your could do with a few buttons or rotary+push
> controllers.
>
> And just thinking out loud, There are 2 SPI controllers in the Pi, Would
> the driver be able to drive 2 screens in parallel ?
> And if techn
chill wrote:
>
> RST: BCM27 (This one is not present on the Pirate Audio boards, but is
> needed in the fbtft_device setup. I suspect other pins can be used.)
> BL: BCM13 (A different pin can be used here, provided the backlight
> brightness script is adjusted accordingly)
>
paul- wrote:
> I simplified, and put some comments in the code for you..
>
Marvellous - thanks Paul.
I removed an unnecessary output, added some 'new lines', and tidied up
the comments so that it better reflects how it works.
Code:
#!/bin/sh
# start
carsten_h wrote:
> Hello!
>
> Today I found an interesting case for a Pi zero W with a display and
> buttons included (German):
> https://www.berrybase.de/raspberry-pi-co/raspberry-pi-zero/gehaeuse/gpi-case-handheld-gaming-geh-228-use-f-252-r-raspberry-pi-zero
> Here is the link to the
chill wrote:
> ... so the display setup and the 240 skin should all work out of the box
> I hope.
Well it wasn't quite 'out of the box', and it involved more reading of
spec sheets and manuals that I was expecting, but finally I have 'this
display' (https://www.amazon.co.uk/gp/p
Paul Webster wrote:
> I assume it is because the script that is calling your script is
> spawning off the various steps in parallel (to make it faster and
> tolerant/ignorant of issues in lower level scripts).
>
> Might not be much that you can do about it in your script - expect
> perhaps put
chill wrote:
>
> * Aargh - I've just noticed that the modified sbpd script is creating a
> file called '0' in the root folder - evidently something to do with that
> 'while ! [ $(pigs t) > '0' ] ' line, but my scripting isn't up to fixing
> that right now!
Ug
M-H wrote:
>
> So set the usercommand in the tweaks and rebooted .
> And it worked right away.
>
Grumpy Bob wrote:
> I've added this to my install - works well, and everything's working
> sweetly.
>
Great - thanks to both of you for letting me know. Looks like we're
there in principle.
By the way, when I copied the Pirate Audio configuration into the
modprobe commands, the change from speed=3200 to speed=1600 was
a mistake - the menu 'slides' in Jivelite have some noticeable tearing
with the slower speed. 3200 is good, and 6400 may be even
better, but barely
paul- wrote:
> pigpiod is a forking daemon, not sure how long it takes to initialize
> internally. Rather than a a set sleep timer, it would probably be best
> to query the daemon to make sure it's started.
Will this be robust?
Code:
#!/bin/sh
# start pigpiod
paul- wrote:
> Chill,
>
> Can you update your instructions with references to where you got the
> flexfb and fbtft_device driver init strings from?
>
> Paul
I've added some links to 'this post'
(https://forums.slimdevices.com/showthread.php?111502-Jivelite-on-a-Pirate-Au
Grumpy Bob wrote:
> Chill - many thanks, your new bootlocal.sh has done the trick!
> A colleague at work has a 3D printer, so hopefully one of those cases
> will be with me shortly.
>
> Robert
Excellent - thanks for the update. Just M-H t
Yatsushiro wrote:
> Thanks for this, Paul.
>
> This has fixed my sound issues, and explains why the Pimoroni Mopidy
> install had no issues.
>
> Now to package this up with some speakers and a battery...
Excellent - added to the setup instructions 'here'
I don't have that line on either of my boards at the moment, and 'pigs r
25' returns 1 on both of them. I assume that means they're already
'high', somehow.
chill's Profile:
paul- wrote:
> I ordered a board...but has to cross the pond. I'll be able to help out
> in a bit.
Not a moment too soon! Good news.
paul- wrote:
>
>
> I have not noticed anyone saying this, but do you have
>
> gpio=25=op,dh
>
> In your config.txt? According to the website, this is
Yatsushiro wrote:
> Yes, indeed. But I have to use sudo.
>
To run sbpd-script.sh? That shouldn't be necessary if it's started as a
user command (bottom of the 'Tweaks' page).
chill's Profile:
Yatsushiro wrote:
>
> Edit 2: Scratch the above, I'm an idiot in that I forgot to backup after
> making the changes. It does now indeed survive a reboot. Thanks for your
> help.
>
That sounds promising. So just to check - with sbpd-script.sh set as a
user command you're now getting boot up
Yatsushiro wrote:
> Hi
>
> Despite my best efforts so far, I'm still getting poor sound quality.
> Would you mind sharing your ALSA settings?
>
> Also, Chill, I'm experiencing the same problems as M_H and Grumpy Bob on
> startup with sbpd-script.sh set to run on startup
Grumpy Bob wrote:
> I see the boot messages if I don't have /home/tc/sbpd-script.sh entered
> as a User Command in Tweaks. Then the piCorePlayer splash screen and
> Jivelite comes up
>
Well I'm thoroughly confused in that case. The sbpd script file only
runs after pCP has finished all it's
Grumpy Bob wrote:
> If I reboot via the Main page of the PCP web interface, I see the usual
> shutdown messages, finishing with "Requesting system reboot". This
> screen remains once the Pi has booted, squeezelite is running and music
> can be heard.
How odd. The boot up messages should
Grumpy Bob wrote:
>
> 2. With /home/tc/sbpd-script.sh entered in the User Commands in Tweaks,
> on rebooting, the Pi doesn't reach Jivelite.
Just to be sure, can you clarify what you see on the screen on
rebooting? Does it look like 'shutdown' messages, or 'startup'
messages?
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
301 - 400 of 745 matches
Mail list logo
