I don't know how to remove the dot, because that is what the fritz.box (the device acting as NAS) defaults. It shouldn't be a problem anyway.
Hi guys,
an rpi newbie here. I've just got Raspberry Pi 2B rev. 1.2, I picked it since a) it has no noisy WIFI and b) it already has a 64-bit core, would like to replace my Bluesound Node. Unfortunately, it does not like the latest piCorePlayer version (8.2.0) - with 64-bit version, it stops while booting just showing a color palette screen with no activity on LAN, and with 32-bit version it even does not connect to the display.
Then I decided to try some legacy and yes, it works with e.g. v3.21.0, kudos for developers!
So, I have two questions:
- was there any support drop for old Raspberry Pi versions like mine 2B rev. 1.2?
- could you suggest some older piCorePlayer release, which was "the best" for my board version? (according to my needs, please, see below)
Software-wise, at the beginning I'd like to run both LMS and Squeezelite on the same board for my initial experiments, so preferably LMS with streaming (like deezer) should already be supported. Maybe I'll split them after, having one board with LMS on a "dirty" side of my setup and another one with the player on a "clean" side just near the DAC.
Hardware-wise it's very simple: I only need a generic I2S support for TDA1543 and other legacy DACs, so no fancy modern stuff here.
P.S.: I hope this thread is still alive
an rpi newbie here. I've just got Raspberry Pi 2B rev. 1.2, I picked it since a) it has no noisy WIFI and b) it already has a 64-bit core, would like to replace my Bluesound Node. Unfortunately, it does not like the latest piCorePlayer version (8.2.0) - with 64-bit version, it stops while booting just showing a color palette screen with no activity on LAN, and with 32-bit version it even does not connect to the display.
Then I decided to try some legacy and yes, it works with e.g. v3.21.0, kudos for developers!
So, I have two questions:
- was there any support drop for old Raspberry Pi versions like mine 2B rev. 1.2?
- could you suggest some older piCorePlayer release, which was "the best" for my board version? (according to my needs, please, see below)
Software-wise, at the beginning I'd like to run both LMS and Squeezelite on the same board for my initial experiments, so preferably LMS with streaming (like deezer) should already be supported. Maybe I'll split them after, having one board with LMS on a "dirty" side of my setup and another one with the player on a "clean" side just near the DAC.
Hardware-wise it's very simple: I only need a generic I2S support for TDA1543 and other legacy DACs, so no fancy modern stuff here.
P.S.: I hope this thread is still alive
@Michael G.
Download and install the raspberry pi Bulleseye Lite 64 bit
That should "set the bit"
you can check with
uname -a
in a terminal
Then re-image for piCorePlayer.
ronnie
Download and install the raspberry pi Bulleseye Lite 64 bit
That should "set the bit"
you can check with
uname -a
in a terminal
Then re-image for piCorePlayer.
ronnie
Yeah, I've seen that also, but not e.g. in 8.0 or 7.x. So far managed to setup everything with pCore 6.1, will try to pre-run a vanilla Pi OS Lite 64-bit first, thanks for a tip!
Found in https://forums.slimdevices.com/foru...nix/112082-new-rpi-zero-2-w/page3#post1507857 that this is set only for rpi zero 2, not an old rpi 2. I just changed this to [PI2], and "magically" piCore version 8.2 is up and running now. Would be interesting to see an answer from one of the devs, if this is not a mistake, or if Raspberry Pi 2 64 bit is intentionally not supported in that release.
Hi there! I also just built a Raspberry Pi 4 with PiCoreplayer + LMS. Works great connected to an external USB DAC, but whenever I turn the DAC off and back on, it loses the connection and I have to reboot LMS in the web interface. It sees the DAC according to the logs, it also doesn't help to define a specific device in the ALSA settings... there was a script floating around that supposedly rebooted LMS automatically when the DAC was found again, but I am a total noob and don't know what to do with that or where to put it?
Does anyone have experience with that?
Cheers!
Does anyone have experience with that?
Cheers!
You are rebooting the Raspberry Pi, nothing to do with LMS. Ensure your DAC is on before you boot pCP. The DAC needs to be on, and recognised before Squeezelite starts otherwise squeezelite fails to start.
I power my USB DAC via the RPi USB, so never have this issue.
There are a few solutions, but I have not found one that works in all situations, otherwise I would have included it in pCP.
There are a few threads here: https://forums.slimdevices.com/
BTW: We have included some changes in the next version of pCP that will make these "scripts" simpler and more reliable.
I power my USB DAC via the RPi USB, so never have this issue.
There are a few solutions, but I have not found one that works in all situations, otherwise I would have included it in pCP.
There are a few threads here: https://forums.slimdevices.com/
BTW: We have included some changes in the next version of pCP that will make these "scripts" simpler and more reliable.
Thank you for the response!
People were mentioning udev rules a lot, I know nothing about unix scripting and that kind of stuff, but by now I got the gist of what they are talking about - basically a rule that restarts Squeezelite, because that's really all I need to do every time, that triggers whenever a "new" usb device is connected. Wouldn't even matter which one, because it's always just that DAC.
What kind of changes are you talking about, something that would make this accessible to a complete novice like me, or more in the sense of, if you already know what you're doing, now you can do it faster?
Sounds like you have a reasonable understanding of udev. When testing some of the solutions I noted there were circumstances where the results were not as expected or consistent.
I made the squeezelite start/stop/restart/force script more robust.
Added the following to the pcp CLI
This should help make people's scripts simpler and more reliable.
I made the squeezelite start/stop/restart/force script more robust.
Added the following to the pcp CLI
This should help make people's scripts simpler and more reliable.
I tried this guide:
https://docs.picoreplayer.org/how-to/add_usb_hdd/
But no luck. I just wanted a usb SSD attached via my ASUS router or directly in the Pie. But nothing works, even though I can actually see the mounted USB SSD in picoreplayer UI. I might just turn on my NAS again - since that actually worked. But a simple SSD via USB seemed more simple a less power usage.
https://docs.picoreplayer.org/how-to/add_usb_hdd/
But no luck. I just wanted a usb SSD attached via my ASUS router or directly in the Pie. But nothing works, even though I can actually see the mounted USB SSD in picoreplayer UI. I might just turn on my NAS again - since that actually worked. But a simple SSD via USB seemed more simple a less power usage.
I have USB (not SSD) drives working fine on my pCP RPi's and also connected to my router as a network drive.
Obviously not exactly the same drive or router.
Someone over at https://forums.slimdevices.com/ may help ??
Obviously not exactly the same drive or router.
Someone over at https://forums.slimdevices.com/ may help ??