Re: [SlimDevices: Unix] Announce: piCorePlayer 3.00
Greg Erskine wrote:
> Hi fullerms,
>
> Have you somehow blocked 8.8.8.8?
>
> >
Code:
> > pcp_internet_accessible() {
> ping -w5 -c3 8.8.8.8 >/dev/null 2>&1
> echo $?
> }
>
> >
>
> regard
> Greg
Yes! Thats it. I have blocked Google's public DNS servers.
Thanks Greg. I cannot unblock Google's public DNS servers, how do change
this IP in the code?
fullerms's Profile: http://forums.slimdevices.com/member.php?userid=42627
View this thread: http://forums.slimdevices.com/showthread.php?t=105997
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Slimmer
Hi yes lirc send repeat codes Code: Event: time 1490640797.364041, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640797.364041, -- EV_SYN Event: time 1490640797.564097, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640797.564097, -- EV_SYN Event: time 1490640798.293872, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640798.293872, -- EV_SYN Event: time 1490640798.494190, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640798.494190, -- EV_SYN Event: time 1490640799.024127, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640799.024127, -- EV_SYN Event: time 1490640799.224181, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640799.224181, -- EV_SYN Event: time 1490640799.792859, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640799.792859, -- EV_SYN Event: time 1490640799.992906, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640799.992906, -- EV_SYN Event: time 1490640801.646760, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640801.646760, -- EV_SYN Event: time 1490640801.750286, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.750286, -- EV_SYN Event: time 1490640801.893815, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.893815, -- EV_SYN Event: time 1490640801.933816, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.933816, -- EV_SYN Event: time 1490640801.973827, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.973827, -- EV_SYN Event: time 1490640802.013809, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.013809, -- EV_SYN Event: time 1490640802.053818, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.053818, -- EV_SYN Event: time 1490640802.093814, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.093814, -- EV_SYN Event: time 1490640802.133812, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.133812, -- EV_SYN Event: time 1490640802.173815, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.173815, -- EV_SYN Event: time 1490640802.213816, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.213816, -- EV_SYN Event: time 1490640802.253817, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.253817, -- EV_SYN Event: time 1490640802.293868, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.293868, -- EV_SYN Event: time 1490640802.333825, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.333825, -- EV_SYN Event: time 1490640802.373815, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.373815, -- EV_SYN Event: time 1490640802.413805, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.413805, -- EV_SYN Event: time 1490640802.453817, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.453817, -- EV_SYN Event: time 1490640802.493820, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.493820, -- EV_SYN Event: time 1490640802.533947, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.533947, -- EV_SYN Event: time 1490640802.573814, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.573814, -- EV_SYN Event: time 1490640802.607802, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640802.607802, -- EV_SYN droidbox's Profile: http://forums.slimdevices.com/member.php?userid=66696 View this thread: http://forums.slimdevices.com/showthread.php?t=105819 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Slimmer
Hi Yes lirc send repeat codes Code: Event: time 1490640797.364041, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640797.364041, -- EV_SYN Event: time 1490640797.564097, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640797.564097, -- EV_SYN Event: time 1490640798.293872, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640798.293872, -- EV_SYN Event: time 1490640798.494190, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640798.494190, -- EV_SYN Event: time 1490640799.024127, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640799.024127, -- EV_SYN Event: time 1490640799.224181, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640799.224181, -- EV_SYN Event: time 1490640799.792859, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640799.792859, -- EV_SYN Event: time 1490640799.992906, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640799.992906, -- EV_SYN Event: time 1490640801.646760, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1 Event: time 1490640801.646760, -- EV_SYN Event: time 1490640801.750286, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.750286, -- EV_SYN Event: time 1490640801.893815, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.893815, -- EV_SYN Event: time 1490640801.933816, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.933816, -- EV_SYN Event: time 1490640801.973827, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640801.973827, -- EV_SYN Event: time 1490640802.013809, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.013809, -- EV_SYN Event: time 1490640802.053818, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.053818, -- EV_SYN Event: time 1490640802.093814, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.093814, -- EV_SYN Event: time 1490640802.133812, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.133812, -- EV_SYN Event: time 1490640802.173815, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.173815, -- EV_SYN Event: time 1490640802.213816, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.213816, -- EV_SYN Event: time 1490640802.253817, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.253817, -- EV_SYN Event: time 1490640802.293868, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.293868, -- EV_SYN Event: time 1490640802.333825, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.333825, -- EV_SYN Event: time 1490640802.373815, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.373815, -- EV_SYN Event: time 1490640802.413805, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.413805, -- EV_SYN Event: time 1490640802.453817, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.453817, -- EV_SYN Event: time 1490640802.493820, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.493820, -- EV_SYN Event: time 1490640802.533947, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.533947, -- EV_SYN Event: time 1490640802.573814, type 1 (EV_KEY), code 207 (KEY_PLAY), value 2 Event: time 1490640802.573814, -- EV_SYN Event: time 1490640802.607802, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0 Event: time 1490640802.607802, -- EV_SYN vdr-box's Profile: http://forums.slimdevices.com/member.php?userid=66625 View this thread: http://forums.slimdevices.com/showthread.php?t=105819 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.10
paul- wrote:
> The version of iproute2 is the same. It fails from the piCore repo,
> because the kernel modules needed are not on that repo. Put your
> bonding commands after the pCp startup
>
> In /opt/bootlocal.sh
>
> Make sure you put it after the marker tags in the file. Then do a "pcp
> bu" to backup your settings
Thank you.
This is what I have now in bootlocal.sh:
Code:
tc@berlin-boombox:~$ cat /opt/bootlocal.sh
#!/bin/sh
# put other system startup commands here
GREEN="$(echo -e '\033[1;32m')"
echo
echo "${GREEN}Running bootlocal.sh..."
#pCPstart--
/home/tc/www/cgi-bin/do_rebootstuff.sh 2>&1 | tee -a /var/log/pcp_boot.log
#pCPstop--
echo
echo "Setup eth0+wlan0 link aggregate, eth0 primary..."
modprobe bonding mode=1 primary=eth0 fail_over_mac=1 max_bonds=1 miimon=250
ifconfig bond0 up
ifconfig eth0 down
ifconfig wlan0 down
echo +eth0 > /sys/class/net/bond0/bonding/slaves
echo +wlan0 > /sys/class/net/bond0/bonding/slaves
echo "Get lease for interface bond0"
for PID in $(pidof udhcpc);do kill -USR2 $PID; done
for PID in $(pidof udhcpc);do kill $PID; done
sleep 5
udhcpc -b -i bond0 -x hostname berlin-boombox -p /var/run/udhcpc.bond0.pid
I came to the realisation I wasn't using the "ip" command so extension
iproute2.tcz is not needed.
I'm not sure the sleep 5 (or 2 kill loops instead of one) are needed but
I have had some temporary loss of contact after reboot without them. I
supposed the lease for bond0 was asked a bit too early for any slave to
have become active (I tested with wifi, secondary + needs to
authenticate). Sleep 5 seems to fix that anyway.
The web interface about wifi says reboot is recommended because the wifi
interface has no address, which is true...
Of course with fail_over_mac=active the MAC of the bond changes
according to the active slave, so my dnsmasq entry for this host reads
like this:
Code:
dhcp-host=b8:27:eb:01:20:33,74:da:38:10:11:01,berlin-boombox,172.17.200.10,2h
This format serves the same hostname and IP address to 2 different MACs,
so bond0 will keep the same address when it renews its lease whichever
slave is active at the time.
3 SB 3 Libratone Loop, Zipp Mini iPeng (iPhone + iPad) LMS 7.9
(linux) with plugins: CD Player, WaveInput, Triode's BBC iPlayer by bpa
IRBlaster by Gwendesign (Felix) Server Power Control by Gordon
Harris Smart Mix, Music Walk With Me, What Was That Tune? by Michael
Herger PowerSave by Jason Holtzapple Song Info, Song Lyrics by
Erland Isaksson AirPlay Bridge by philippe_44 WeatherTime by Martin
Rehfeld Auto Dim Display, SaverSwitcher, ContextMenu by Peter Watkins.
epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711
View this thread: http://forums.slimdevices.com/showthread.php?t=106755
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.10
paul- wrote: > Support for shairport-sync will probably be dropped soon. It's too > difficult to manage for something that us developers don't use. Look at > Shairtunes2W. > > Shairtunes2W runs fine on a pCP LMS installation. Hello Is it also working fine on lms running on synology ds916+ ? Thank you Envoyé de mon iPhone en utilisant Tapatalk tparvais's Profile: http://forums.slimdevices.com/member.php?userid=59976 View this thread: http://forums.slimdevices.com/showthread.php?t=106755 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.10
psketch wrote: > Thanks Guys. Very interesting, and in effect gives us both a backup and > migrate option for LMS settings - which is great. I can move them to my > USB hard drive, which is where my music is anyway, and then move it back > again afterwards - as I don't want to keep accessing the USB drive when > it's not needed as I have it set to spin down and don't want it spinning > up in case I'm just listening to tidal or radio. > > Will give this a crack later. > > pete S AFAICT when you click the "Move LMS Data" button, that's what it does, it *moves* the data (not copies) so you won't have a backup if for some reason your SD card fails. LMS 7.9 on a Raspberry Pi 3/piCorePlayer 3.10, playlists and LMS cache on a USB stick, 25K+ music library on a WD MyCloud network drive, Rasberry Pi 2 > piCorePlayer 3.02 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 Raspberry Pi 3/piCorePlayer 3.10/HiFiBerry DAC+ > Cambridge Audio Minx 5 (study) 1 x Boom (dining room) - 1 x Radio (garage) - 1 x Touch (display and controller only) - 1 x SB3 (spare) kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=106755 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.00
fullerms wrote:
> This issue is over a Ethernet Wired connection too. No issues with the
> network, every other device is able to connect, and even the
> PiCoreplayer is able to access the repositories for extensions. Could it
> be a broken link hard coded somewhere?
Hi fullerms,
Have you somehow blocked 8.8.8.8?
Code:
pcp_internet_accessible() {
ping -w5 -c3 8.8.8.8 >/dev/null 2>&1
echo $?
}
regard
Greg
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=105997
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.10
kidstypike wrote: > I'm sorry Paul but you're wrong there, the slimserver folder on the USB > stick contains all LMS installed plugins. > > I've just done it again, burned a pCP image to a new sdcard, removed the > one in current use, set up pCP/resize/Samba/installed LMS/etc., and > everything is EXACTLY as if I'd just reinserted the old sdcard. Thanks Guys. Very interesting, and in effect gives us both a backup and migrate option for LMS settings - which is great. I can move them to my USB hard drive, which is where my music is anyway, and then move it back again afterwards - as I don't want to keep accessing the USB drive when it's not needed as I have it set to spin down and don't want it spinning up in case I'm just listening to tidal or radio. Will give this a crack later. pete S psketch's Profile: http://forums.slimdevices.com/member.php?userid=56555 View this thread: http://forums.slimdevices.com/showthread.php?t=106755 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
