bernid wrote:
Hi,
I have problem with squeezelite high cpu usage (96%) after finishing
planing (eg playlist).
I use SoA (squeezelite) with Raspberry Pi B+:
Code:
NAME=-n RPI
AUDIO_DEV=-o hw:CARD=ALSA
ALSA_PARAMS=-a 120:4::
MAX_RATE=-r 192000:
Hi,
I have problem with squeezelite high cpu usage (96%) after finishing
planing (eg playlist).
I use SoA (squeezelite) with Raspberry Pi B+:
Code:
NAME=-n RPI
AUDIO_DEV=-o hw:CARD=ALSA
ALSA_PARAMS=-a 120:4::
MAX_RATE=-r 192000:
UPSAMPLE=-u vI:::28:::
DOP=-D
Krisbee wrote:
Do you mean just the web interface is unreachable, or that the
Cubietruck looses it's network connection and you can't get to a command
line via SSH. If you can still get to the Cubietruck command line via
SSH as root, what happens if you restart the web interface?
Code:
Man in a van wrote:
It's a dead parrot :p
You need to connect to the cubietruck via SSH and monitor the install
from the beginning to gain some idea of what is happening. You say it's
dead - but have you attached a monitor/keyboard to your cubietruck,
rebooted etc, to see what happens?
Krisbee wrote:
You need to connect to the cubietruck via SSH and monitor the install
from the beginning to gain some idea of what is happening. You say it's
dead - but have you attached a monitor/keyboard to your cubietruck,
rebooted etc, to see what happens?
I'll have another go later
Krisbee wrote:
Do you mean just the web interface is unreachable, -*or that the
Cubietruck looses it's network connection *-and you can't get to a
command line via SSH. If you can still get to the Cubietruck command
line via SSH as root, what happens if you restart the web interface?
Lestrad wrote:
Well, since I couldn't scan my collection and consequently couldn't play
any music through my Squeezebox, I decided to try uninstalling and
reinstalling LMS 7.9. When I do, this happens:
error: inflate: data stream error (incorrect data check)
error: failed to read object
Man in a van wrote:
Well,
I have tried another install and SSH'd into the cubietruck, but then
realised I did not knowthe command line instruction to see what was
happening.:mad:
I have attached a copy of the text displayed during the install (must be
similar, I would think) and the
Re: Cubietruck SOA install failure.
If you use Triode's Cubietruck install image
https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-cubietruck.img.zip,
then a script runs called create-sdcard-soa-cubietruck.sh, part of
which is to build a first boot script and systemd
chrissy wrote:
Hi
But in a earlier version it installed. I have a version up and running.
It updates everything and seems to be getting more stable, although it
is still a way to go to get the stability of the Slovenia Image.
Frequent reboots, especially after updates. The Slovenia Image,
Krisbee wrote:
I can't remember if the system is meant to auto reboot at the end of
the SAO install process or not.
Install on raspberry B+ and on hummingboard is auto reboot into the web
gui
Ronnie
Man in a
Man in a van wrote:
Install on raspberry B+ and on hummingboard is auto reboot into the web
gui
Ronnie
Thanks, I can see that now. See my post #1296 above.
Krisbee's Profile:
Hi,
I had the wandboard working properly till today. All of a sudden, the
website does not display, not able to SSH into the wandboard either.
Ping works and I do see a display when connecting HDMI to a TV.
Any pointers? This did happen a few times and had corrected itself after
restart but not
Hi
But in a earlier version it installed. I have a version up and running.
It updates everything and seems to be getting more stable, although it
is still a way to go to get the stability of the Slovenia Image.
Frequent reboots, especially after updates. The Slovenia Image, once
installed is
Hi,
The error messages can be found in post 1106. After this, the cubie is
dead, although
I didn't have a screen attached to it, so I don't know itid last words
;-).
I posted a detailed description on how to install the Slovenia Image
and get LMS up and running in a German forum, so I have
vinodt1347 wrote:
Hi,
I had the wandboard working properly till today. All of a sudden, the
website does not display, not able to SSH into the wandboard either.
Ping works and I do see a display when connecting HDMI to a TV.
Any pointers? This did happen a few times and had corrected
Krisbee wrote:
You say all of a sudden. Had your Wandboard had been operating
normally for several hours before this suddenly happened, or was it
after a cold boot, for example. Presumingly you always remember to halt
the system before removing the power plug to avoid SD card corruption.
So I finally got the share mounted as NFS after I enabled and started
rpcbind.
But now LMS is unable to scan my collection. Here are the last lines of
the scan log:
[15-04-04 07:50:14.1566]
Slim::Utils::Scanner::Local::Async::__ANON__ (146) Found
/mnt/netnas/Music/tags-upload_discussion
I gave up tying to mount using the web interface - if it's any help this
is the fstab line that works for me with my readynas - this probably has
more in it than strictly necessary:
Code:
192.168.0.198:/c/media /media/netdrive nfs
I reverted back to my previous set-up, with the share mounted as CIFS.
Still the scan crashes.
Logically, the share being both CIF and NFS on the NAS is the problem.
That's the only thing that's different. But come to think of it, I was
having scan failures even before I changed anything.
Within the previous four weeks or so, I have successfully installed SoA
on a pi B+ and Cu-box i4Pro.
And very pleased I am too.:)
Today, after several fruitless hours I have installed and used Volumio
on a Cubietruck.:p
Why? you may well ask?
Well, because SoA does not install.
I have used
chrissy wrote:
Hi Ronnie,
so it is not fixed so far. I posted a somewhat detailed report on this a
couple of weeks ago. But triode seems to be off the record since
beginning of February. Hope he is well. Alternatively you can use the
Debian image of Slovenia (igor pop..., I don't know
Hi Ronnie,
so it is not fixed so far. I posted a somewhat detailed report on this a
couple of weeks ago. But triode seems to be off the record since
beginning of February. Hope he is well. Alternatively you can use the
Debian image of Slovenia (igor pop..., I don't know the exact name). It
is
Well, since I couldn't scan my collection and consequently couldn't play
any music through my Squeezebox, I decided to try uninstalling and
reinstalling LMS 7.9. When I do, this happens:
error: inflate: data stream error (incorrect data check)
error: failed to read object
chrissy wrote:
Hi Ronnie,
so it is not fixed so far. I posted a somewhat detailed report on this a
couple of weeks ago. But triode seems to be off the record since
beginning of February. Hope he is well. Alternatively you can use the
Debian image of Slovenia (igor pop..., I don't know
Lestrad wrote:
Thanks. A few words as to how to find and install this Slovenia image
would be most appreciated by us Linux-challenged people.
TIA
Think Chrissy means this
http://www.igorpecovnik.com/2013/12/24/cubietruck-debian-wheezy-sd-card-image/
I know Adrian is a good chap, I
Man in a van wrote:
The process runs through stage one and two; there is a message to
refresh the browser web page, and then there is nothing, the Cubietruck
just drops clean off the network. :o
Any suggestions by anyone (especially Triode, Please, please,please!).
atb
Ronnie.
Lestrad wrote:
The Wandboard needs only read access.
Oh yes, the CIFS share mounts. But I was told it would be better to
mount it as NFS. I'll have to be sure I can access the share as NFS from
Windows before I make the change. It's supposed to be possible...
If you keep your playlists
Krisbee wrote:
Had another look on the Arch Linux forum and this post rang a few bells:
https://bbs.archlinux.org/viewtopic.php?id=193410
...
Let me know if this works for you.
Yes!! It works! That was it. Once I started *rpcbind *I was able to
mount the share with no problem. SOA has
Had another look on the Arch Linux forum and this post rang a few bells:
https://bbs.archlinux.org/viewtopic.php?id=193410
I now have a version 3 NFS client connection working on my RPi. I was
reminded that to make a version 3 mount of a NFS share requires rpcbind,
but this is disabled by
Krisbee wrote:
If you did step one above and leave your /etc/fstab as you have shown,
then your NFS share should be (re)mounted after a re-boot. There's
nothing else to do.
I wouldn't have thought you needed write access to data on your
Wandboard as you can edit the data via your
Lestrad wrote:
So the rpcbind service will start all by itself?
I see your point - I'll be writing via the NAS, to which I have rw
access via Windows. The Wandboard needs only read access.
Oh yes, the CIFS share mounts. But I was told it would be better to
mount it as NFS. I'll have to
bakker_be wrote:
From experience, I'd suggest you stick to CIFS (actually SMB) when using
Windows ...
Hi. So it's not a problem to leave the share with both CIFS and NFS
enabled, and for Windows to access it as CIFS and the Wandboard as NFS?
The Wandboard can access it as read-only, it
Lestrad wrote:
Yes!! It works! That was it. Once I started *rpcbind *I was able to
mount the share with no problem. SOA has added a line to the fstab:
# start added by soa-web
192.168.0.14:/media /mnt/netnas nfs vers=3 0 0
# end added by soa-web
Now all I need to know
Lestrad wrote:
So the rpcbind service will start all by itself?
I see your point - I'll be writing via the NAS, to which I have rw
access via Windows. The Wandboard needs only read access.
Oh yes, the CIFS share mounts. But I was told it would be better to
mount it as NFS. I'll have to
Lestrad wrote:
I'm trying to get my music share mounted as NFS too. I've enabled the
NFS service on the NAS and set the default permissions to rw. Then I
went to the Storage tab in the SOA frontend and entered /mnt/netnas (a
directory I'd created on the Wandboard) under Mountpoint and
Krisbee wrote:
The error message is telling you what is wrong. In the Network share
box you should have entered:
Code:
192.168.0.15:/media
Why not use one of the inbuilt mount points - /mnt/disk1, etc?
Thanks. I entered
Krisbee wrote:
OK, possible version clash of nfs versions on wandboard ( vers4) and
ReadyNAs (vers 3 ?). You could try to add a vers=3 option to the
mount command, but SOA might not handle this correcty, e.g:
Code:
mount -t nfs -v -o vers=3
steve-g
Try adding the line
192.168.0.198:/c/media /mnt/disk1 nfs
vers=3,nolock,users,auto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,noatime
0 0
to your /etc/fstab and reboot
Simon.
simoh's Profile:
Krisbee wrote:
Make that journalclt -n 50 and post again. Looking for log entry
similar to this soa-rpi sudo[343]: root : TTY=unknown ; PWD=/ ;
USER=root ; COMMAND=/usr/sbin/mount -t nfs -o defaults,_netdev
192.168.0.20:/media/musdata/Te to show what command was executed.
Here's what I get:
steve-g wrote:
Thanks Krisbee
This seems to be the relevant bit of journalctl:
Code:
Apr 01 10:25:35 soa-wandboard systemd[1]: Starting RPC Port Mapper.
Apr 01 10:25:35 soa-wandboard systemd[1]: Reached target RPC Port Mapper.
Apr 01 10:25:35
Lestrad wrote:
Here's what I get:
-
[root@soa-wandboard /]# mount -t nfs -v -o vers=3 192.168.0.15:/media
mnt/netnas
mount.nfs: timeout set for Wed Apr 1 11:49:20 2015
Job for rpc-statd.service failed. See systemctl status
rpc-statd.service and journalctl -xe for
Krisbee wrote:
OK, possible version clash of nfs versions on wandboard ( vers4) and
ReadyNAs (vers 3 ?). You could try to add a vers=3 option to the
mount command, but SOA might not handle this correcty, e.g:
Code:
mount -t nfs -v -o vers=3
steve-g wrote:
Thanks Simon - that works!
Update on that - the Wandboard locked up after a few seconds play of
some music (hi-def if that makes any difference)
Simon has manually the /etc/fstab file. I would prefer to solve the
problem using the SOA web storage page if possible without the
Lestrad wrote:
--
Apr 01 10:08:37 soa-wandboard systemd[14802]: Starting Timers.
Apr 01 10:08:37 soa-wandboard systemd[14802]: Reached target Timers.
Apr 01 10:08:37 soa-wandboard systemd[14802]: Starting Sockets.
Apr 01 10:08:37 soa-wandboard systemd[14802]: Reached target Sockets.
simoh wrote:
steve-g
Try adding the line
192.168.0.198:/c/media /mnt/disk1 nfs
vers=3,nolock,users,auto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,noatime
0 0
to your /etc/fstab and reboot
Simon.
Thanks Simon - that works!
Lestrad wrote:
Is there a DUHHH.. smiley? I just realized I was using the wrong IP
address. Sorry. I'll get back to you in a bit...
Here's what I get when I use the right IP address:
rpcinfo -u 192.168.0.14 nfs:
program 13 version 2 ready and waiting
program 13 version 3 ready and
Krisbee wrote:
As you've confirmed your NFS server accepts version4 connections,
shouldn't your manual mount command be (the v switch is for verbose
output):
Code:
mount -v -t nfs4 192.168.0.14:/c/media
Here's the result I get:
Lestrad wrote:
Here's what I get when I use the right IP address:
rpcinfo -u 192.168.0.14 nfs:
program 13 version 2 ready and waiting
program 13 version 3 ready and waiting
program 13 version 4 ready and waiting
and
showmount -e 192.168.0.14:
Export list for
steve-g wrote:
Its fun this isn't it!
The '-o' in mount -t nfs -o 192.168.0.14:/c/media media/netdrive is the
problem - -o causes the '192.168.0.14:/c/media' to be treated as an
option string.
Without the '-o' I get: mount.nfs: an incorrect mount option was
specified
I'm beginning
Lestrad wrote:
Thanks. I entered 192.168.0.15:/media and got this error message:
*mount.nfs: an incorrect mount option was specified *
I tried with /mnt/disk1 and got the same error...
Post the last few lines of journalctl -f output here, this should show
you the mount command executed
Krisbee wrote:
Post the last few lines of journalctl -f output here, this should show
you the mount command executed by webinterface.
--
Apr 01 10:08:37 soa-wandboard systemd[14802]: Starting Timers.
Apr 01 10:08:37 soa-wandboard systemd[14802]: Reached target Timers.
Apr 01 10:08:37
Lestrad wrote:
Here's what I get when I use the right IP address:
rpcinfo -u 192.168.0.14 nfs:
program 13 version 2 ready and waiting
program 13 version 3 ready and waiting
program 13 version 4 ready and waiting
and
showmount -e 192.168.0.14:
Export list for
Could you now try -o nolock
Simon.
simoh's Profile: http://forums.slimdevices.com/member.php?userid=56305
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
Krisbee wrote:
Steve,
Ok, as I suspected SOA can have a problem when the option for a NFS
version 3 connections is specified. On the Wandboard you can check what
version of NFS connections your NFS server will accept with this
command:
Code:
rpcinfo -u
Krisbee wrote:
Well there's no evidence of what happened there, but I notice
rpc-statd.service failed. You need to check your NFS configuration from
the Wandboard as root:
Is there a DUHHH.. smiley? I just realized I was using the wrong IP
address. Sorry. I'll get
simoh wrote:
Could you now try -o nolock
Simon.
Thanks. Here's the result:
[root@soa-wandboard /]# mount -v -t nfs4 -o nolock 192.168.0.14:/c/media
media/netdrive mount.nfs4: timeout set for
Wed Apr 1 15:08:17 2015
mount.nfs4: trying text-based options
OK. I'm just trying to remember how I solved this a couple of months
ago. Whatever the solution was didn't allow for auto-mounting after a
reboot, which is why I resorted to the fstab entry.
Simon.
simoh's Profile:
simoh wrote:
OK. I'm just trying to remember how I solved this a couple of months
ago. Whatever the solution was didn't allow for auto-mounting after a
reboot, which is why I resorted to the fstab entry.
Simon.
I don't mind using fstab. That's how I'm now mounting the share via CIFS
-
Lestrad wrote:
Thanks. Here's the result:
[root@soa-wandboard /]# mount -v -t nfs4 -o nolock 192.168.0.14:/c/media
media/netdrive mount.nfs4: timeout set for
Wed Apr 1 15:08:17 2015
mount.nfs4: trying text-based options
On the RPI at least, the NFS mount survives a reboot without problems:
'[image: http://s23.postimg.org/slyvnysmf/soanfs1.jpg]'
(http://postimg.org/image/slyvnysmf/)
'[image: http://s29.postimg.org/l5shvx3xf/soanfs2.jpg]'
(http://postimg.org/image/l5shvx3xf/)
Code:
Krisbee wrote:
Without seeing both the NFS exports file and NFS config files on your
NAS, I'd be guessing. ( These are /etc/exports and
/etc/default/nfs-kernel-server on a default debian install for example,
what are they on your NAS).
I'll go into the NAS and get
Krisbee wrote:
Lestrad wrote:
While you're doing that, I did a bit of googling over at the arch linux
forums. This recent thread may be relevant:
https://bbs.archlinux.org/viewtopic.php?id=193834
The suggestion is to try this in the mount command:
Code:
Lestrad wrote:
Is that rpc-statd indispensable? Sorry to be so ignorant. I know a lot
about opera and '60s rock, but obviously not a lot about Linux files
systems and security services...
No apology needed, the whole point of the SOA webui is to isolate the
user from the need to know the
Lestrad wrote:
Krisbee wrote:
Without seeing both the NFS exports file and NFS config files on your
NAS, I'd be guessing. ( These are /etc/exports and
/etc/default/nfs-kernel-server on a default debian install for example,
what are they on your NAS).
Yes I have NFS enabled in the readynas - at least the readynas says I
have!
The ouput of the command is:
[root@soa-wandboard ~]# showmount -e 192.168.0.198
Export list for 192.168.0.198:
/c/media *
/c/backup *
192.168.0.198 is the IP address for the readynas.
Here is my fstab entry to mount share at boot time;
nasc69f4c.fritz.box:music /mnt/disk1 nfs
vers=3,nolock,users,auto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,noatime
0 0
I don't no if it's the best or most efficient way, but it works for me!
HTH,
Krisbee wrote:
OK so it looks like your Wandboard can see the NFS shares. Let's see if
you can mount the share at the command line. Connect to your Wandboard
as root via SSH. Then use this command:
Code:
mount -t nfs -o ro 192.168.0.198:/c/media /mnt/disk1
steve-g wrote:
The mount command fails:
Code:
[root@soa-wandboard ~]# mount -t nfs -o ro 192.168.0.198:/c/media /mnt/disk1
mount.nfs: an incorrect mount option was specified
You're right my music files are in the media
steve-g wrote:
If still fails - this is the verbose output:
Code:
[root@soa-wandboard ~]# mount -t nfs -v 192.168.0.198:/c/media /mnt/disk1
mount.nfs: timeout set for Tue Mar 31 18:53:07 2015
mount.nfs: trying text-based options
Krisbee wrote:
Hmm, drop the read only option and try again.
Code:
mount -t nfs 192.168.0.198:/c/media /mnt/disk1
If still fails - this is the verbose output:
Code:
[root@soa-wandboard ~]# mount -t
steve-g wrote:
Yes I have NFS enabled in the readynas - at least the readynas says I
have!
The ouput of the command is:
[root@soa-wandboard ~]# showmount -e 192.168.0.198
Export list for 192.168.0.198:
/c/media *
/c/backup *
192.168.0.198 is the IP address for the readynas.
OK so
I've recently installed SOA and LMS (7.81) on to a Wandboard Quad mainly
to get BBC radio working again as the sparc processor that my Readynas
uses does not have the horse power to run this.
I have my music stored on the readynas (a Readynas Duo V1) and have
mounted the share on the wand board
steve-g wrote:
I'm not using squeezelite it's LMS I'm trying to get to work -
communicates to a couple of touches to do the actual replay.
This is the entry in the fstab:
//192.168.0.198/media /media/netdrive cifs
steve-g wrote:
It seems to fail with an abort message:
- Extracting a6e7fc58e6912986d003598ed79bb6a391a2113c.tar.gz with
bsdtar
== Starting prepare()...
/aur/soa-aur/linux-wandboard/PKGBUILD: line 34: patch: command not
found
== ERROR: A failure occurred in prepare().
Aborting...
Lestrad wrote:
Just go the IP address of your Wandboard and you should see the SoA Home
page. Go to the Update tab and look for a check box. Check it and hit
Install/Remove. Let us know what happens...
PS It's mentioned somewhere in this thread, but I can't figure out how
to search...
It
Lestrad wrote:
I believe that Triode, the developer of SOA, had said that the Updated
Kernel needs to be installed for sampling rates above 44.1 kHz. Have you
installed it?
No - I didn't realise there is one - do you know where I can get it from
and the process involved in installing it?
steve-g wrote:
No - I didn't realise there is one - do you know where I can get it from
and the process involved in installing it?
Just go the IP address of your Wandboard and you should see the SoA Home
page. Go to the Update tab and look for a check box. Check it and hit
Install/Remove. Let
Krisbee wrote:
You may have gigabit rated hardware, but have you tested the actual
connection speeds between your various devices?
Apart from this, a couple of other things spring to mind. Firstly,
adjusting the squeezelite params may iron out the re-buffering on
hi-res playback.
Lestrad wrote:
I've been advised to enable the NFS service on the ReadyNAS and mount
using NFS. What problems did you have with NFS?
I have enabled NFS on the readynas - I've just not found any combination
of commands in the fstab file that will actually mount - I can't recall
the actual
The actual error message with nfs - as reported in WinScp is:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Just wish I knew what it means.
steve-g's Profile:
Lestrad wrote:
Doggone. And the creator of this thread seems to have dropped completely
out of sight, after having been a model of availability for just such
problems as this for so long...
All I can say is, reboot the Wandboard and try again. That's what I
ended up doing a bunch of
steve-g wrote:
The actual error message with nfs - as reported in WinScp is:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Just wish I knew what it means.
Exactly what is in your fstab? Or are you trying to mount manually?
steve-g wrote:
I've recently installed SOA and LMS (7.81) on to a Wandboard Quad mainly
to get BBC radio working again as the sparc processor that my Readynas
uses does not have the horse power to run this.
I have my music stored on the readynas (a Readynas Duo V1) and have
mounted the
steve-g wrote:
I've recently installed SOA and LMS (7.81) on to a Wandboard Quad mainly
to get BBC radio working again as the sparc processor that my Readynas
uses does not have the horse power to run this.
I have my music stored on the readynas (a Readynas Duo V1) and have
mounted the
Krisbee wrote:
Not a good idea to have NFS and CIFS running simultaneously on the same
data on your ReadyNAS, use one or the other. It really should not be a
case of trial and error manual editing of your /etc/fstab. Triode
designed SOA for you to mount shares via its web interface
steve-g wrote:
I don't try to have both at the same time - I only try one or the
other.
I'm obvoiusly being thick but I can't get the web interface- storage
to work at all - hence the manual edit.
Ok, let's see if we can sort this out. Do you have NFS running now on
the ReadyNAS? What
steve-g wrote:
I have enabled NFS on the readynas - I've just not found any combination
of commands in the fstab file that will actually mount - I can't recall
the actual error message but something like device not found I'll try it
again and report thre actual message.
Have you got it
Lestrad wrote:
Exactly what is in your fstab? Or are you trying to mount manually?
The main problem is I don't actually know what to put in fstab - I've
tried a whole range of different lines from very simple with no options
to more or less a copy of the cifs options and I can't get anything
I've given up trying to mount my ReadyNAS music folder on SoA. I've been
at it for two solid days. If anybody would like to try to help, please
look at this thread:
http://forums.slimdevices.com/showthread.php?103319-LMS-on-Wandboard-with-ReadyNAS-and-Squeezebox-Touch
I got it sorted out. See this post:
http://forums.slimdevices.com/showthread.php?103319-LMS-on-Wandboard-with-ReadyNAS-and-Squeezebox-Touchp=813220#post813220
Seems there's a bug in mount.cifs...
Lestrad's Profile:
took rather longer to work out how to mount the network drive on my
readynas to get at my music
Please, can you explain how you did this? I've edited etc/fstab to look
like this:
#
# /etc/fstab: static file system information
#
# file system dir type options dump pass
Flashed a new SD card and tried the Install again. This time after
manually cold-rebooting the Wandboard, the second phase came up and is
now executing.
I'll report back as I get time over a busy weekend.
Lestrad's
steve-g wrote:
I got a Wandboard Quad yesterday and LMS up and running in about an hour
- took rather longer to work out how to mount the network drive on my
readynas to get at my music but all up and running now.
I'm very impressed by the smooth way it worked so I would like to say
I got a Wandboard Quad yesterday and LMS up and running in about an hour
- took rather longer to work out how to mount the network drive on my
readynas to get at my music but all up and running now.
I'm very impressed by the smooth way it worked so I would like to say
thanks for ALL those
ian_heys wrote:
Thanks for the pointers. I now have it working.
1. Place binary in /usr/bin
2. Create sq2upnp.service file and place in /usr/lib/systemd/system
3. Start service with systemctl enable sq2upnp.service
4. Reboot
Here is sq2upnp.service file:
[Unit]
JRatron wrote:
Hi all,
I went to set up a fresh Wandboard dual this evening, but I'm getting as
far as phase 2 in the installer, then it's hanging. Clicking the
progress bar to view the details shows a repetition of
Code:
Mar 19 22:35:52 soa-wandboard
Krisbee wrote:
As far as I can tell, all elements of SOA are online at github. I can
only suggest checking your own internet connections and staring the
install to SD card from scratch.
thanks, I'll give it another go today :)
kesey wrote:
Hi Lestrad, using the USB Image Tool burning the .img file to your micro
SD card is drag and drop. It will work with your external card reader,
you just have to ensure you are pointing to the correct drive by
verifying its location with Windows Explorer. Similarly. backing up
JRatron wrote:
thanks, I'll give it another go today :)
I tried this again about an hour ago and it's working nicely now.
I didn't change anything in the way I ran it, so possibly a temporary
issue with either my internet connection or the repository last night?
I still got the same errors in
301 - 400 of 1548 matches
Mail list logo
