Supported Devices
==============
Install images are available for the following platforms:
Raspberry PI - model B and B+
Wandboard - duallite and quad
Cubox-i/Hummingboard
Cubietruck
Installation Instructions
==================
The simplest way to install SoA is to download one of the installer images, unzip it and flash the resulting 12M image file to a 4G or larger micro sdcard.
Insert the sdcard in your device and boot the device with a wired Ethernet connection. It should obtain an IP address and display a web page if you connect to this IP address with your browser. The web page shows a disclaimer statement and allows you to initiate download of Arch Linux ARM and the SoA components.Code:https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-wand-dual.img.zip https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-wand-quad.img.zip https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-cubox-i.img.zip https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-cubietruck.img.zip https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-rpi.img.zip
Installation will take ~20-40 minutes depending on the device and your internet connection speed. During this time the device will reboot one or more times. If you do not see activity after this time, try manually rebooting the device.
---------------------------------------------------------------------------------------------------------------------------
Older instructions for previous install scripts:
(removed - this method has been depreciated)
---------------------------------------------------------------------------------------------------------------------------
You can also install more manually on top of an arch linux installation:
1) install arch linux on an sdcard for your device, for example for a wandboard:
http://archlinuxarm.org/platforms/ar...cale/wandboard
(go to the install tab for instructions of how to download and flash an image)
At present you need an existing linux machine for this. However if you use a wandboard then you can use the second microsd slot as the target card and perform the above instructions while running another linux image on the main microsd slot. The second slot is /dev/mmcblk1 (use in place of /dev/sdX in the arch install instructions) If you have a fresh wandboard then you can load the standard ubuntu image to enable you to do this.
2) boot the device from the arch linux image and ssh to the device using the username root and password root
3) follow the instructions at https://github.com/SqueezeOnArch/soa-aur which explain how to build and install squeeze on arch applications. This requires several minutes, but should be self explanatory for people used to the command line.
4) reboot the device and attach to it using the web interface from a browser.
Results 1 to 10 of 1622
Hybrid View
-
2014-05-28, 16:17 #1
- Join Date
- Apr 2005
- Posts
- 8,410
Announce: Squeeze on Arch - developer version
Last edited by Triode; 2014-12-31 at 09:17.
-
2014-05-28, 17:39 #2
- Join Date
- May 2005
- Posts
- 2,300
Just curious - why Arch? Is there something that makes it preferable to other distros for this use case?
-
2014-05-28, 23:51 #3
- Join Date
- Feb 2013
- Posts
- 376
Triode,
I'll give this a go in QEMU A.S.A.P as I don't have any ARM based devices. However, I'm not sure what the current Arch arm systemd version is, and the last time a tried to build an emulation using the ARCH rfs and load/update additional ARCH packages in dynamic QEMU it ground to a halt as a later version of systemd seemed to be a problem. Of course, this is not relevant to those with real hardware.
The question about ARCH Linux is relevant, as I guess some would have hoped that debian might have, or could have, been used as there are base images of one form or another known to work on the beaglebone black, Wandboard and Cubietruck.
Anyway, you work is much appreciated, and I do like the licence notice on the "Squeeze on Arch (SOA) Arch User Repository"
-
2014-05-29, 02:25 #4
- Join Date
- Feb 2013
- Posts
- 376
Triode,
Up and running in dynamic QEMU now:
It's not real hardware, but allows basic testing.
Will attempt LMS install via static QEMU ASAP.
Brilliant work, as always.
Will need to check what if any ARCH ARM base images exist for Cubieboard. Will also test install in x86_64 in VirtualBox on ARCH base and Manjaro.
For ref:
Wandboard image built on Debain unstable for QEMU test as follows:
Code:dd if=/dev/zero of=awcard.img bs=1M count=2000
Code:modprobe loop max_part=63 losetup -f awcard.img
Code:fdisk /dev/loop0 (follow web page to create single parititon starting at 8192 ref given by triode above) fdisk -lu /dev/loop0 mkfs.ext4 /dev/loop0p1 mount /dev/loop0p1 /mnt/tmp tar -xf ArchLinuxARM-wand-latest.tar.gz -C /mnt/tmp sync umount /mnt/tmp dd if=u-boot-dual.imx of=/dev/loop0 bs=512 seek=2 sync Check awcard.img is OK.
Code:#! /bin/bash ############################################################################ # Boot Arch Wandbaord image QEMU Emulation ############################################################################ # Note: All files in same directory and bridged tap0 already configured # for full network access. DHCP on host via router # # Arch ARM for Wandboard image # Qemu kernel compiled from latest stable source: 3.13.6 at time of writing. # ############################################################################# qemu-system-arm -m 1024M \ -M vexpress-a9 \ -kernel zImage3.13AA \ -append "root=/dev/mmcblk0p1 rw rootfstype=ext4 rootwait console=ttyAMA0,115200n console=ttyS0" \ -drive if=sd,cache=writeback,file=awcard.img \ -serial stdio \ -net nic \ -net tap,ifname=tap0,script=no
-
2014-05-29, 12:47 #5
- Join Date
- Apr 2005
- Posts
- 8,410
I went for arch mainly because of the ease of creating build scripts to download and install packages - which is what soa-aur is. Its also a small lean and mean base install with the ability to install more as you want (there's no users other than root in the base file system for instance) - this makes it good for using as a base os for this activity. It also support armv6 so may work on a Pi...
We can evolve to binary repos and more automated installation, but at present my target is to get back to most features of a CSOS without needing to host any binaries and hence not have any short term issues on the legal side...
-
2014-08-02, 09:59 #6
- Join Date
- Apr 2005
- Posts
- 8,410
Cubox-i / Hummingboard install script
I've created a new install script for SolidRun's cubox-i / hummingboard. This is tested on a hummingboard 1 so I would be interested for positive results from other SolidRun products if anyone has them.
To create the install image from a linux machine, where /dev/sdX is the device containing the sdcard.
Code:wget https://raw.githubusercontent.com/SqueezeOnArch/soa-installers/master/create-sdcard-soa-cubox-i.sh chmod 755 create-sdcard-soa-cubox-i.sh sudo ./create-sdcard-soa-wand.sh /dev/sdX
I must say I am reasonably impressed with a hummingboard 1 - its a single core, but can run squeezelite and jivelite at the same time with only some slowing down of jivelite if upsampling with squeezelite.Last edited by Triode; 2014-08-03 at 10:42.
-
2014-08-03, 07:16 #7
- Join Date
- Feb 2013
- Posts
- 376
Triode,
I think you have inadvertently given the wrong url for your new build script. Is the hummingboard 1"" you've tested the "HummingBoard-i1 " as described here?
http://www.solid-run.com/wiki/HummingBoard_Hardware
1. Do you intended to test the performance of LMS on this device?
2. Have you tested audio out over the in-built coax SPDIF for function and SQ? I believe it's limited to 48KHz.
-
2015-02-03, 07:48 #8
- Join Date
- Feb 2015
- Posts
- 6
New to SOA
Hi,
After a few attempts , I was successful in installing SOA on a pogoplug , but I do have an issue with squeezelite not working. The Web GUI for squeezelite states
Status loaded/enabled
Active failed/Result : exit code
With the advanced option check , it states on the comment field
[18:02:13.360365] test_open:294 playback open error: No such file or directory
but if I Disable squeezelite using the GUI button
then access the pogoplug via ssh and just enter squeezelite on the cmd line it works . I can now see the player on the LMS server
I am guessing that something is wrong with the way that squeezelite is started thru the GUI
Any clue on where I should check
Thanks
-
2015-02-03, 11:42 #9
- Join Date
- Sep 2005
- Location
- Vienna/Austria
- Posts
- 17
@tobyjug: I tried some reboots now, but no success. After the first boot, it even doesn't request an IP anymore, so it seems that it doesn't boot at all.
Any ideas someboody?
-
2015-02-06, 01:55 #10
- Join Date
- Feb 2015
- Posts
- 6
I was able make squeezelite work partly by commenting out in
"/usr/lib/systemd/system/squeezelite.service "
#EnvironmentFile=/etc/squeezelite.conf
[Unit]
Description=Squeezelite Player
After=network.target
[Service]
Nice=-10
LimitRTPRIO=99
LimitMEMLOCK=infinity
#ControlGroup=cpu:/
User=squeezelite
Group=squeezelite
SupplementaryGroups=audio
#EnvironmentFile=/etc/squeezelite.conf
ExecStart=/usr/bin/squeezelite -n SoA Player\
$OPTIONS\
$NAME $MAC $PRIORITY\
$MAX_RATE $AUDIO_DEV\
$BUFFER $CODEC $ALSA_PARAMS $VOLUME\
$LOG_FILE $LOG_LEVEL\
$UPSAMPLE $DOP $VISULIZER $SERVER_IP
[Install]
WantedBy=multi-user.target
I am not sure why the file is not found ,as the file "squeezelite.conf" is in the correct directory and in fact I could list out the file contents...
Clues .. anyone