This how-to uses the piCorePlayer GUI to create a “standard” Wifi setup. To access the piCorePlayer GUI, it needs to be connected to the LAN using wired ethernet. Warning If you have added # Maintained by user to the first line of your wpa_supplicant.conf file, the piCorePlayer GUI will completely ignore your configuration file. It can only be maintained by using a text editor. Prerequisites # piCorePlayer has already been successfully setup.
The preferred method to setup your wifi is through the piCorePlayer Wifi GUI page—see Setup Wifi, but there are situations where adding wpa_supplicant.conf to the boot partition (Using a setup computer) may be the only option. Situations like the following: You have a Raspberry Pi without built-in wired ethernet so wifi is the only option. You want to use Raspberry Pi’s built-in Wifi. You don’t have wired ethernet available. See what networking options are available on the various models of the Raspberry Pi—see Raspberry Pi.
1. Connect the Raspberry Pi and Initial Configuration #Insert the SD card into your Raspberry Pi, attach a wired ethernet connection, and plug in the power. Give your Raspberry Pi a minute or so to power up and connect to your local network. Then look at the boot console. The IP address will be displayed at the end of the boot process. Or launch Advanced IP Scanner to identify the IP address that has automatically been assigned by your network to the Raspberry Pi via DHCP.
It’s easy to install Logitech Media Server on your piCorePlayer using its settings menus. As of this writing piCorePlayer is installing Logitech Media Server 8.0.0. This is a release branch that does not get nightly updates. If you want to select stable bugfix or development branches, then you can follow these instructions. Step-by-step instructions #Step 1Access piCorePlayer via ssh—see Access piCoreplayer via ssh. Step 2$ cd /tmp Step 3$ wget https://raw.
Step 1 - Adding an USB Hard Disk - Preparation #If the USB hard disk you are adding is formatted as FAT32 or NTFS you will need to install the “additional Filesystems pack” before you can load and configure the disk. Note that this step is not required if your disk is formatted as EXT4. Windows users can pre-format such a disk using the free utility MiniTool Partition Manager, and this is in fact what I have done.
If you need to add a third partition to a SD card it is recommended you use the pCP web GUI. This is a lot easier and will do the all calculations for you and will create a third partition in a consistent manner hopefully improving support. The “Manually add a third partition” instructions have been included for information only. Warning It is recommended that you use an additional USB storage device rather than adding a third partition to the SD card.
piCorePlayer includes the extension net-usb-KERNEL.tcz on the pCP image for those occasions when you have a RPi with a spare USB port but no Ethernet port and want to connect to a wired network. By default this extension is not loaded. To facilitate a headless install of net-usb-KERNEL.tcz, piCorePlayer looks for a file named netusb on the boot partition. Step 1 Add an empty file “netusb” to boot partition. This will instruct piCorePlayer to load the appropriate firmware during the boot process.
I’m assuming that you are a Linux noob, like me, and want to connect to a Synology NAS. You have to configure access at both the NAS and the piCorePlayer LMS. For the piCorePlayer LMS you need: A name for the mount point. This will only be used by the piCorePlayer LMS, so I used the name of my Synology NAS. The IP address for the NAS on your local network.
Setup ssh access to piCorePlayers without prompting for passwords. This is useful if you need to use scripts that interact with remote piCorePlayers. Step 1Determine the <IP address> of the remote computer—see Determine your pCP IP address. Step 2aCreate the public/private authentication keys using <Enter> to accept the default values. $ ssh-keygen -t ed25519 Valid encryption types: dsa rsa ed25519 Step 2bOr, create the public/private authentication keys non-interactively.