If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
PiCorePlayer "Main" page > Diagnostics button > Raspberry Pi tab > Internet, what do you see there?
[ATTACH]39043[/ATTACH]
Hi Kidstypike, many thanks for replying. Yes you're right, I followed the path you suggested and there was a red cross against the pC repository (I've tried to add my screenshot but not sure if it works). Yesterday I took my RPi into work and the LMS download worked from there, so there must be something in my home network that's preventing access to these files, although I have not idea what it might be as I haven't configured my home router/wifi for anything like this.
So I now have LMS working courtesy of my employers' network, but it would be great to understand what might be causing the isue here at home. Any ideas?
At the bottom of the pCP Main Page have you selected Player/Server or Beta tab ?
ronnie
Hi Ronnie, thanks for replying. I had selected Beta, as suggested in the pCP documentation "https://docs.picoreplayer.org/projects/build-simple-lms-server/". Looks like my home network is restricting access to the repository (see other responses). I have it working now but there is still some mystery (for me) as to what is stopping access to the repository.
What is your ISP? I have seen similar behaviour on Virgin Media (UK) due to their flaky DNS
Hi gwlevans. Thanks for replying, my ISP is Vodafone. I guess it could be DNS, perhaps if I somehowe reconfigure my DNS (to Google?) that might solve the issue. I'll have a look at that. As an experiment I'm going to hang the Pi off a wifi hotpot from my mobile phone, to see if that changes anything, this appeared to work yesterday at work, when I was talking to a developer colleague about possibly using Docker to deploy LMS over another RPi OS and he had to reconfig DNS to access the Docker files.
Hi gwlevans. Thanks for replying, my ISP is Vodafone. I guess it could be DNS, perhaps if I somehowe reconfigure my DNS (to Google?) that might solve the issue. I'll have a look at that. As an experiment I'm going to hang the Pi off a wifi hotpot from my mobile phone, to see if that changes anything, this appeared to work yesterday at work, when I was talking to a developer colleague about possibly using Docker to deploy LMS over another RPi OS and he had to reconfig DNS to access the Docker files.
Hi Kidstypike, many thanks for replying. Yes you're right, I followed the path you suggested and there was a red cross against the pC repository (I've tried to add my screenshot but not sure if it works). Yesterday I took my RPi into work and the LMS download worked from there, so there must be something in my home network that's preventing access to these files, although I have not idea what it might be as I haven't configured my home router/wifi for anything like this.
So I now have LMS working courtesy of my employers' network, but it would be great to understand what might be causing the isue here at home. Any ideas?
Cheers, Tony
OK so something weird (probably weird because I'm unfamiliar with pCP) happened. I edited the conf file with wifi access details, erased my home network details and added my mobile hotspot details, then replaced the microSD card into the RPi and rebooted - and it reconnected to my home network again! How did that happen? I could not get it to connect to my mobile personal hotspot. Does the RPi retain information about previous wifi access points? I thought RPi was memoriless and could only use the config file on the microSD card to access and do other stuff, but then what do I know? Anyway, I'm stuck now until I get back into work as I need to DL interface protocol configs to connect to my NAS share folders. So strange.
ce
tce-load -w git rpi-vc python3.6 (You can omit if you already have these)
tce-load -i git rpi-vc python3.6
git clone https://github.com/piCorePlayer/rpi-eeprom.git (This is a clone from rpi's git, with a few tweaks to the scripts for pcp.
cd rpi-eeprom
sudo ./rpi-eeprom-update -a (This will update to the 9-10-2019 eeprom binary that is now the default)
pcp rb (reboot to load the bootloader)
But the version of python in piCoreplayer is python 3.8
When running rpi-eeprom-update I get rpi-eeprom-digest not found
ce
tce-load -w git rpi-vc python3.6 (You can omit if you already have these)
tce-load -i git rpi-vc python3.6
git clone https://github.com/piCorePlayer/rpi-eeprom.git (This is a clone from rpi's git, with a few tweaks to the scripts for pcp.
cd rpi-eeprom
sudo ./rpi-eeprom-update -a (This will update to the 9-10-2019 eeprom binary that is now the default)
pcp rb (reboot to load the bootloader)
But the version of python in piCoreplayer is python 3.8
When running rpi-eeprom-update I get rpi-eeprom-digest not found
This is the procedure I use (rpi Imager Tool) to update the rpi4b eeprom PRIOR to installing the pCP card.
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).
Hi. I’m wondering if anyone could set me right on configuring an Innomaker PCM5122 I2S DAC hat on a Pi4b. Everything is assembled and LMS and squeezelite are both up to date and running, but I’m getting nothing from the RCA outs. In output settings I have tried using both the Allo Boss2 DAC and Allo Boss DAC (and MiniBoss) as device output presets—I understand this DAC is a clone of the Allo Boss and is recommended by Innomaker for set up on Volumio and other platforms but, although they claim it works with PcP, there’s no guidance offered. Output settings are set to equal. I see mentions elsewhere that a dtoverlay(?) might be required in the config(?) file, but I’m floundering rather at this point. Grateful for any advice or pointers. Thanks
Hi. I’m wondering if anyone could set me right on configuring an Innomaker PCM5122 I2S DAC hat on a Pi4b. Everything is assembled and LMS and squeezelite are both up to date and running, but I’m getting nothing from the RCA outs. In output settings I have tried using both the Allo Boss2 DAC and Allo Boss DAC (and MiniBoss) as device output presets—I understand this DAC is a clone of the Allo Boss and is recommended by Innomaker for set up on Volumio and other platforms but, although they claim it works with PcP, there’s no guidance offered. Output settings are set to equal. I see mentions elsewhere that a dtoverlay(?) might be required in the config(?) file, but I’m floundering rather at this point. Grateful for any advice or pointers. Thanks
Thanks both. That sounds pretty straightforward though I’m waiting for my Mac to finish rebuilding from Time Machine before I can give it a whirl. Will be sure to report back.
Thanks both. That sounds pretty straightforward though I’m waiting for my Mac to finish rebuilding from Time Machine before I can give it a whirl. Will be sure to report back.
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
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment