Announce: piCorePlayer 8.0.0

[streifenleopard]

I bought a new micro-sd-card, installed PCP 8.2.0 on it. I inserted it into the RPI, started it up. First thing I tried to do was to select the Hifiberry 2HD. After I saved this setting, I let the RPI reboot only to find that after reboot it said Squeezelite is not running"
I already had re-written PCP on to the sd-card and I have also checked with the old installation / sd-card which runs fine. What is wrong? Thanks!

EDIT right now I see that the old sd-card has PCP v 8.1.0 and piCore version 13.1. I thought I had updated...

[Man in a van]

paul-

I guess you are now aware that the rpi folk have the 6.1 kernel as part of the apt repository.

I made a new 32bit Bullseye Lite image this morning, ran the usual updates, and noticed this

pi@3bpluslite:~ $ uname -a
Linux 3bpluslite 6.1.19-v7+ SMP Tue Mar 14 11:04:52 GMT 2023 armv7l GNU/Linux

I don't how long it has been there

ronnie

From the raspberry pi forum

We will do this in a few stages. Initially updating the "next" firmware branch to the 6.1 kernel.
Assuming testing is positive, we will update the master rpi-update firmware branch.
Eventually the 6.1 kernel will appear with "apt upgrade" and on new RPiOS images in the future.

[paul-]

Yes, they rolled to 6.1 about three weeks ago on git and rpi-update. I’m actually rolling a completely new aarch64 base. Latest glibc and compilers. Still a ways off for pCP, I don’t see any major enhancements…..other than staying current.

[slartibartfast]

paul-

I guess you are now aware that the rpi folk have the 6.1 kernel as part of the apt repository.

I made a new 32bit Bullseye Lite image this morning, ran the usual updates, and noticed this

pi@3bpluslite:~ $ uname -a
Linux 3bpluslite 6.1.19-v7+ SMP Tue Mar 14 11:04:52 GMT 2023 armv7l GNU/Linux

I don't how long it has been there

ronnie

From the raspberry pi forum

We will do this in a few stages. Initially updating the "next" firmware branch to the 6.1 kernel.
Assuming testing is positive, we will update the master rpi-update firmware branch.
Eventually the 6.1 kernel will appear with "apt upgrade" and on new RPiOS images in the future.

I didn't get updated to 6.1 using
sudo apt full-upgrade Still on 5.15 I think.

[paul-]

Let’s not confuse folks with RaspiOS conversation.

[zubenubi]

Im running the latest community firmware on a fully updated piCorePro for about a month now. Since then I periodically need to restart LMS as it becomes unreachable. I retrieved this from the server log:

[23-04-06 04:38:40.0606] Slim::Networking::SqueezeNetwork::Players::_player s_error (378) Unable to get players from SN: Connect timed out: , retrying in 900 seconds
[23-04-06 04:39:40.0185] Slim::Networking::SqueezeNetwork::Players::_player s_error (378) Unable to get players from SN: Connect timed out: Bad file descriptor, retrying in 900 seconds
[23-04-06 04:41:16.1361] Slim::Utils::Misc::msg (1325) Warning: [04:41:16.1354] EV: error in callback (ignoring): Unrecognised protocol tcp at /usr/local/slimserver/CPAN/Net/HTTPS/NB.pm line 168.
[23-04-06 04:41:18.0104] Slim::Utils::Timers::__ANON__ (272) Error: Timer Slim::Networking::SqueezeNetwork::Players::fetch_p layers failed: Unrecognised protocol tcp at /usr/local/slimserver/CPAN/Net/HTTPS/NB.pm line 168.
[23-04-06 04:46:06.0330] Slim::Utils::Misc::msg (1325) Warning: [04:46:06.0326] EV: error in callback (ignoring): Unrecognised protocol tcp at /usr/local/slimserver/Slim/Networking/Async/HTTP.pm line 166.
[23-04-06 05:09:55.1254] Slim::Utils::Misc::msg (1325) Warning: [05:09:55.1251] EV: error in callback (ignoring): Unrecognised protocol tcp at /usr/local/slimserver/CPAN/Net/HTTPS/NB.pm line 168.
[23-04-06 06:05:12.1190] Slim::Utils::Misc::msg (1325) Warning: [06:05:12.1185] EV: error in callback (ignoring): Unrecognised protocol tcp at /usr/local/slimserver/CPAN/Net/HTTPS/NB.pm line 168.

Anything that I can do to remedy?

[mherger]

Please provide the full server.log.zip, or at least since you started LMS last time.

[zubenubi]

Here is the server.log.zip since the last restart of LMS

[mherger]

Not much in there. But what is in there points at some networking issues. As if your pCP wasn't able to bind LMS to the network interface. Might be caused by LMS starting too soon, before the network was up. What if you restarted LMS alone?

[paul-]

pCP waits for the network before starting LMS (But will timeout after about 30-50 seconds)

You can look at the pCP diagnositc logs to see what happens with network during startup.

[zubenubi]

LMS was restarted alone. pCP is connected via ethernet port (not wifi) on a static ip so it should be coming up immediately

[paul-]

Should be coming up immediately and IS coming up immediately with proper connection are drastically different things.

Few things on the list
1) Check/Change power supply
2) Check/Change ethernet Cable
3) Plug into a different port on your network.
4) Can you ping both ways to and from the device?

[zubenubi]

After I restart LMS on the pCP, it operates without issue for days. Then I discover that I can no longer connect to LMS. So I load the pCP site and go to the LMS tab where I restart LMS. Then everything works again for days. I checked the ping both ways and it works very well (no drops, very low ping times).

What should I check prior to re-starting LMS next time? Please be aware I cannot reach LMS so it would need to be on pCP itself (http or ssh ok).
Thanks

[Fahzz]

Is PiCore usable on an Allo Boss2 Player?

[CJS]

Is PiCore usable on an Allo Boss2 Player?

piCorePlayer should work on an Allo Boss2 Player. On the Squeezelite Settings tab of the pCP web interface (pCP v8.2.0), there is an option to select the "Allo Boss2 Dac" as audio output device.