Whoa, this is fast-moving thread! I thought I was all caught up, and
suddenly there are another dozen messages! :-)
I'm pretty impressed by chill's script. Nice work. Keeping track of
all that statefulness, via multiple entry points to the script, is
tricky. The self-installation is a nice
I only use "force" option on the command line. I'm wondering if $0 gets
set correctly if calling from a script.
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread:
Greg Erskine wrote:
> Maybejust maybe
>
> Way back somewhere I mentioned using the "force" option instead of the
> "stop" option during testing.
>
Thanks Greg. I had noticed the 'force' option, but hadn't looked beyond
the comment: "# Force should only be used for testing purposes."
Is it possible to enable piCorePlayer to recognize the CM4's USB port?
I could not do it.
tx2toda's Profile: http://forums.slimdevices.com/member.php?userid=71378
View this thread:
Maybejust maybe
Way back somewhere I mentioned using the "force" option instead of the
"stop" option during testing.
I found when you are testing things manually, you do things like forget
to use "sudo" or use kill, and you end up with the squeezelite process
and the pid file out of
That confirms that the start-stop-daemon isn't stopping the process.
The fact that the process hasn't stopped may or may not be enough to
prevent the subsequent start, but since the same start-stop-daemon is
used to start the process, it may well be failing to do that too.
I'm not sure yet
reboot with dac on
Code:
tc@pCP:~$ ps | grep squeezelite
5405 root 0:01 /usr/local/bin/squeezelite -n piCorePlayer -o
hw:CARD=M6,DEV=0 -a 80 4 1 -v
10084 tc0:00 grep squeezelite
tc@pCP:~$ cat /var/run/squeezelite.pid
5405
tc@pCP:~$
Howard Passman wrote:
> Hmmm, Just double checked my 3.5. Back lighting control works fine. I'm
> running pi3B | piCorePlayer v7.0.1 | www v00016 | linux
> 5.4.83-pcpCore-v8 | piCore v12.0pCP | Squeezelite v1.9.8-1287-pCP.
>
> Might try resetting or reinstalling Jivelite?? Ooops sorry it's
Hmmm, Just double checked my 3.5. Back lighting control works fine. I'm
running pi3B | piCorePlayer v7.0.1 | www v00016 | linux
5.4.83-pcpCore-v8 | piCore v12.0pCP | Squeezelite v1.9.8-1287-pCP.
Might try resetting or reinstalling Jivelite??
Howard
wtnh wrote:
> Hmm - when I try the "Adjust
Bogg wrote:
> As requested this is with dac still off -
>
> >
Code:
> >
> tc@pCP:~$ ps | grep squeezelite
> 6330 root 0:01 /usr/local/bin/squeezelite -n piCorePlayer -o
hw:CARD=M6,DEV=0 -a 80 4 1 -v
> 10355 tc0:00 grep squeezelite
>
Looks like the kill did not work as squeezelite is still running ... but
the pid has gone ... so next step is to work out why the kill did not
work.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc australia,
jeroen2 wrote:
> I am using the precise same display on PiCorePlayer and can adjust the
> backlight brightness from the settings in JiveLite. (It's under the
> PiCorePlayer settings, not under Display settings)
Hmm - when I try the "Adjust Display Backlight Brightness" in
PiCorePlayer settings,
> Boot up as normal with the DAC attached and powered, then turn the DAC
> off. Then:
> And could you also post the log file from this sequence.
As requested this is with dac still off -
Code:
tc@pCP:~$ ps | grep squeezelite
6330 root 0:01
Same here and on the 5" model too.
Howard
jeroen2 wrote:
> I am using the precise same display on PiCorePlayer and can adjust the
> backlight brightness from the settings in JiveLite. (It's under the
> PiCorePlayer settings, not under Display settings)
wtnh wrote:
> The only thing left to do is to figure out how to adjust the backlight,
> which is a little too bright. The standard piCorePlayer adjustment does
> not work since it does not recognize the Osoyoo as an official Raspberry
> Pi display. Osoyoo has a suggestion in their user manual,
Hmmm, I see. Thanks a lot for the reply. Yeah, on Raspbian CEC seems to
work fine, but when it came to Jivelite it was quite slow.
So I guess, for now, it is easiest to get a RPi 2 or later, as that
seems to work for you.
@Bogg - perhaps you could run another quick test.
Boot up as normal with the DAC attached and powered, then turn the DAC
off. Then:
Code:
ps | grep squeezelite
cat /var/run/squeezelite.pid
And could you also post the log file from this
Thanks both Pauls - just working my way through the init.d script now.
WWWROOT is not used. And what I can't fathom is if there's a problem
with the environment in Bogg's fresh pCP7 install, why isn't there a
problem with the environment in my fresh pCP7 install?
Bogg wrote:
> Here's my
Here is a build I just finished using the 3.5" Osoyoo display. I used a
2U "Galaxy" chassis from the 'DIY Audio Store'
(https://diyaudiostore.com/collections/galaxy/products/2u-w-steel-covers?variant=12174833028)
and had them custom CNC the front panel.
This photo shows the display mounted to
Thanks for this tutorial!
Everything working as expected.
Cheers,
CSL
Sent from my iPhone using Tapatalk
tobal2's Profile: http://forums.slimdevices.com/member.php?userid=68995
View this thread:
chill wrote:
> Hi Paul - good to have another pair of eyes on this. No, I don't
> believe there's anything different. I think udev calls the script as
> root, but the crucial line that seems to be acting differently between
> the scenarios is 'sudo'ed anyway.
> >
Code:
Material will be getting its info from LMS - but pCP web interface
possibly doing its own local check ... perhaps checking for pid file.
You could edit the init.d script to put some tracing in it.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france
Here's my adjusted script. The stop part is in there as far I can see.
I've (hopefully) just changed the 2 local bits near the beginning, and
the sudo line just now.
33671
Starting from a fresh reboot, dac on, working sqlite etc, then dac off,
and dac back on.
M6 Log
Code:
and just to check, can you post the contents of your
/etc/udev/rules.d/10-M6.rules file.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
Bogg wrote:
> Twice more, and I made sure I wasn't using --nostop as it had the same
> behaviour
>
> I just did the install and reboot a third time, just to be sure, and
> everything is as I describe above, including not being able to restart
> sqlite from the webpage.
You're right - it does
chill wrote:
> Tsk - that's just muddied the waters even more!
>
> I take it you've done a reboot since making the latest script changes?
Twice more, and I made sure I wasn't using --nostop as it had the same
behaviour
Tsk - that's just muddied the waters even more!
I take it you've done a reboot since making the latest script changes?
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
That's made a lot of difference!
It seems to have the same effect as using --nostop. But I'd have to do
all the same procedures in --nostop to check.
Starting with
Dac on - sqlite showing working in pcp web and default /material / apps
Dac off - now shows Not running in pcp web, BUT now shows
Bogg wrote:
> Hi again. And thanks again. On with the show.
>
> Here are my steps for clarity -
> Dac on - run install without --nostop - pcp br - dac off (sqlite auto
> killed, not showing in material, but showing on pcp web)
>
> >
Code:
> > tc@pCP:~$ ps | grep
Hi again. And thanks again. On with the show.
Here are my steps for clarity -
Dac on - run install without --nostop - pcp br - dac off (sqlite auto
killed, not showing in material, but showing on pcp web)
Code:
tc@pCP:~$ ps | grep squeezelite
6066 root 0:02
Paul Webster wrote:
> I haven't read through this all so apologies if this does not help ...
>
> I assume that when run via udev it is not necessarily being run as the
> same user and with the same environment as when run interactively.
> So - is there anything in the called startup script
I haven't read through this all so apologies if this does not help ...
I assume that when run via udev it is not necessarily being run as the
same user and with the same environment as when run interactively.
So - is there anything in the called startup script that relies on stuff
that is not
Bogg wrote:
> Sorry, in my excitement for progress I wasn't too clear.
> Unfortunatly it only restarts once, and the restart command needs to be
> run each time.
>
> Here's the new sudo output and log when it has worked
> Dac on (working) - dac off - dac on (not working) - run restart
>
> >
33 matches
Mail list logo
