Announce: piCorePlayer 8.0.0

[themicksa]

It says in the blurb to use Allo-Boss in the dropdown

I don't have the dac hat but Allo Boss DAC (and MiniBoss) in the pCP Audio output device settings selects the correct overlay

[ATTACH]39105[/ATTACH]

ronnie

Sorry to be so long in replying (Time Machine and Ventura...hmm. There's 3 days of my life I'll not be getting back.)

Anyway I finally got round to adding that overlay code to the config.txt file and that seemed to do the trick. All up and running now.

If I can ask one last daft question: I've put this pi together for use in my daughter's flat. Is setting it up as it's running now simply a matter of changing wifi details, or are there other things need adjusting? I tried something similar at a friend's place the other week and couldn't get the player—a DAC32 that had been connecting happily by wifi at home—to connect to the pi. Perhaps it was something on friend's router, but I ran out of time to check. Not a big deal, but wonder if I'm overlooking something.

Thanks your ongoing generous help.

[Man in a van]

Sorry to be so long in replying (Time Machine and Ventura...hmm. There's 3 days of my life I'll not be getting back.)

Anyway I finally got round to adding that overlay code to the config.txt file and that seemed to do the trick. All up and running now.

If I can ask one last daft question: I've put this pi together for use in my daughter's flat. Is setting it up as it's running now simply a matter of changing wifi details, or are there other things need adjusting? I tried something similar at a friend's place the other week and couldn't get the player—a DAC32 that had been connecting happily by wifi at home—to connect to the pi. Perhaps it was something on friend's router, but I ran out of time to check. Not a big deal, but wonder if I'm overlooking something.

Thanks your ongoing generous help.

I would

a) Connect with Ethernet and enter the required wifi details either before you go to the flat or when you are at the flat, whichever is easier.

b) Burn a copy of a working configuration to another SD card and check that it works, take it with you as insurance and if all goes well, leave it at the flat as a backup, or make a copy at the flat and check before you leave. Remember a SD card reader

ronnie

[paul-]

Yes, glibc is generally the issue. pCP was generally ahead of RaspiOS distribution. So I had to maintain separately.

I’ve been working on some other projects with the Pico, but I should be able to get AudioScan updated.

[themicksa]

Configuring an PCM5122 I2S DAC hat on a Pi4b

I would

a) Connect with Ethernet and enter the required wifi details either before you go to the flat or when you are at the flat, whichever is easier.

b) Burn a copy of a working configuration to another SD card and check that it works, take it with you as insurance and if all goes well, leave it at the flat as a backup, or make a copy at the flat and check before you leave. Remember a SD card reader

ronnie

Sounds good. I look forward to giving it a whirl tomorrow. Thanks for the advice.

[mr-b]

LMS unresponsive - TCP out of mem errors

Hi

LMS on my PCP seems to be unresponsive both from players and the PCP LMS UI page just hangs.
The main PCP admin pages are fine though.

Diagnostics shows quite few of these (though my music lib server is working and accessible via CIFS from another machine):

[5433590.068175] CIFS: VFS: \\192.168.1.3 has not responded in 180 seconds. Reconnecting...
[5433961.911655] CIFS: VFS: \\192.168.1.3 has not responded in 180 seconds. Reconnecting...
[5434335.035200] CIFS: VFS: \\192.168.1.3 has not responded in 180 seconds. Reconnecting...
[5434543.403947] TCP: out of memory -- consider tuning tcp_mem
[5434543.404859] TCP: out of memory -- consider tuning tcp_mem
[5434543.414137] TCP: out of memory -- consider tuning tcp_mem
[5434543.420116] TCP: out of memory -- consider tuning tcp_mem
[5434543.429620] TCP: out of memory -- consider tuning tcp_mem
[5434543.453499] TCP: out of memory -- consider tuning tcp_mem
[5434556.027709] usb 1-1.1: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0xa00, type = 1
[5434556.040343] usb 1-1.1: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0xa00, type = 1
[5434556.289103] TCP: out of memory -- consider tuning tcp_mem
[5434556.654969] usb 1-1.1: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0xa00, type = 1
[5434556.668279] usb 1-1.1: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0xa00, type = 1
[5434811.026638] TCP: out of memory -- consider tuning tcp_mem
[5434813.373934] usb 1-1.1: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0xa00, type = 1
[5434813.386070] usb 1-1.1: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0xa00, type = 1

Before I try rebooting PCP and losing the info is there anything else amiss?

[paul-]

Just reboot, if you continue to see memory issues. You may need to turn down the memory usage setting in LMS, or turn on a swap file.

[mr-b]

Tx for that. I should have mentioned that this is a RPi 4B/4GB and LMS has 100k tracks and Database Memory Config = max.
Will keep an eye on it, but have had no issues before.

[Viragored]

8.2.0 - LMS still won't install

Yup - weird alright. I chose 8.0.0 when 8.2.0 wouldn't play nicely because that's what's running on my Pi Zero W that serves music over BT to my Sony headphones. And that's been rock solid 24/7*365 (apart from a little hiccup that turned out to be nothing to do with pCP or LMS).
My PC downloaded the target file with no problem at the same time the Pi was failing.
Anyway 8.0.0 is doing fine for me at the mo.

Just an update from an issue that arose a couple of weeks back - https://forums.slimdevices.com/showt...=1#post1063624

Today I needed to recover from a dead SD card in a Pi 3B (damn those local 2-second power cuts....) I downloaded a fresh image of pCP 8.2.0 onto a 32GB card, and with the Pi on ethernet went through the steps before installing LMS. Same result as before - "There was a error downloading slimserver.tcz"
So I downloaded a fresh image of 8.1.0 and all went as it should, slimserver.tcz just downloaded and that's now got my music player running once more.

Weird, eh?

[mr-b]

LMS 8.3 upgrade went smoothly

I recall the last time I had some issues with the LMS update process regarding notifications in the player and then the actual upgrade of LMS on pCP, but this time around I saw the notification of an LMS update to 8.3.0 available, then followed the link.
The link had a lot of scary stuff about source code and scripts and doing it from the CLI but then I spotted at the bottom "For users of piCorePlayer please use This Link".
Following that opened up the PCP UI with an "Update LMS" button, and then it all upgraded fine!
Tx to all for making this process an easy one.

[Bagwit]

Thanks all for suggestions.

So today I completed LMS setup on the network at work (downloading & installing CIFS interface libraries) and brought my Pi home, mounted the remote NAS disk and it all works perfectly. I set the Pi up with a static IP address and re-addressed my other 'player' Pi. And now, completely unexpectedly the piCorePLayer repositories are available. One thing that may have solved it was rebooting my router (which I did because the DHCP wasn't doing what it was told initially), which it appears I haven't done for 132 days. I guess 'have you tried switching it off and back on again' still remains good advice.

Next project - set up the same system with Docker (although am going to use another Pi borrowed from work, I'm happy with my LMS and hope to not have to touch it for a while).

Many thanks all, Tony

I am doing a fresh install of 8.2.0, having been on 6.1 for ages. I have had exactly the same issues as you. Installed fine but, while it insists that my Internet and DNS are fine and it can contact the picore repo, both the picoreplayer main and mirror repo are reported as inaccessible. I already have a static IP set, I have tried a bunch of alternative DNS, I have tried some tweaks on how I route out of my network, and no success. I can install extensions from the picore repo with no issue, but nothing works for the picoreplayer repos. I can ping and traceroute to them with no issue from an SSH session on the Pi itself, and I can access the repo directly from my desktop which has identical routing and DNS to the Pi. I have even tried rebooting my router even though I didn't expect that to change anything. Still no access to picoreplayer repos. I did this all over again with the 64bit version, having tried 32bit to start (am on a Pi3B+). Still no success. Downloaded and installed 8.0.0 instead and it immediately works. I have gone back and also tested all the differing networking setups I did to try and resolve it under 8.2.0, and every single one worked for 8.0.0 with no further actions needed by me. I also then tried 8.1.0 and that also worked without issue, can access the repos and install updates. I tried an in-situ upgrade from 8.1.0 to 8.2.0 which succeeded however I then immediately lost access to the repos again. Reinstalled 8.1.0 and it was working again. So I can only conclude that there is either something wrong somewhere with the 8.2.0 build or it has changed something fundamental to the way it works that causes issues with people's network setups that worked perfectly on previous versions.

[Greg Erskine]

Thanks Bagwit for the detailed testing.

Unfortunately, I can't reproduce the issue. I did see it once on my LMS pCP but it when away after a reboot.

Are you getting all the green ticks on [Main Page] > [Extensions]?

Also, on the bottom right corner of the [Main Page] there is a tab to select the mirror repository. Can you install from there?

[Bagwit]

Thanks Bagwit for the detailed testing.

Unfortunately, I can't reproduce the issue. I did see it once on my LMS pCP but it when away after a reboot.

Are you getting all the green ticks on [Main Page] > [Extensions]?

Also, on the bottom right corner of the [Main Page] there is a tab to select the mirror repository. Can you install from there?

No, I get green ticks on Internet, DNS, and piCore repo. But the piCorePlayer main repo and mirror repos both show red crosses. I hadn't realised there was a tab in the bottom right of the main page, however I was trying to manually select the repo in the extensions page and both of them showed inaccessible there, though the piCore Main repo always showed accessible. I tried multiple reboots too, and left the device running a while in case it was just settling down, but nothing changed with that either. The only thing I cannot try right now is on another network entirely as my work are too locked down for that, but I can try at a friend's at some point to confirm. Would be odd if my network though, as 6.10, 8.0.0, and 8.10 were all fine no matter how I configured my home DNS and routing, and I can directly access the repo page from all other devices on the same network. I noticed a few other people had reported similar issues and that they mysteriously went away after a while, so it seems a bit hard to track down. I have dd cloned my card states, so if you need any testing done or more detailed logs I can easily swap out for that.

EDIT: And to confirm, it is the same situation on my LMS server pCP and my client end pCP devices. I am about to try a Pi2 though, no idea if that will differ so will check and report on that.

[Bagwit]

Confirmed the same issue with my Pi2. I also tried the switch to mirror in the bottom right of Main and no success again. I also went back and tried both on an ethernet wired and wireless setup, just in case something odd was going on there, using both inbuilt RPi wifi and working USB wifi adapters, but same situation. I have yet to try a Pi4 but do have one sitting in my drawer I was going to use for something else but will test that as well shortly and see if anything differs, for both 32 and 64bit.

[Bagwit]

They are all running flawlessly on 8.1.0 though, amazing work as always! My old 6.1.0 devices have been running rock solid for so long I had barely even paid them attention other than that they played my music in the home or remotely while out and about. I've been meaning to donate for a while, going to sling some cash your way as it is well deserved.

[slartibartfast]

They are all running flawlessly on 8.1.0 though, amazing work as always! My old 6.1.0 devices have been running rock solid for so long I had barely even paid them attention other than that they played my music in the home or remotely while out and about. I've been meaning to donate for a while, going to sling some cash your way as it is well deserved.

Have you tried updating from 8.1 to 8.2?

Sent from my Pixel 3a using Tapatalk