Install the dependencies:
brew install m4 autoconf automake libtool e2fsprogs
Clone and build:
git clone https://github.com/alperakcan/fuse-ext2.git
cd fuse-ext2
Install the dependencies:
brew install m4 autoconf automake libtool e2fsprogs
Clone and build:
git clone https://github.com/alperakcan/fuse-ext2.git
cd fuse-ext2
Since Tensorflow is not yet available via pip for Python 3.7 and pyenv can't build python on the latest macOS, let's install 3.6.5_1
via homebrew and use it in conjunction with pyenv to create an enclosed environment that will use 3.6 only when we need it:
brew unlink python
brew install --ignore-dependencies https://raw.githubusercontent.com/Homebrew/homebrew-core/f2a764ef944b1080be64bd88dca9a1d80130c558/Formula/python.rb
brew switch python 3.7.2_1
Install pyenv if you haven't already, we'll use it to switch to 3.6.5
only when we need it (e.g. jupyter), leaving the latest Python from homebrew as default release (e.g. 3.7.2_1
):
brew install pyenv
pyenv rehash
Yes! You can reuse your old Ubuntu Mate 16.04 installation from a Raspberry Pi 3 with a new B+.
Trying to boot the B+ with the old SD without modifications, will result in the rainbow screen with thunderbolt screen showing up.
From your old Rpi, update the firmware(kernel.img&co) on the boot partition running sudo rpi-update
. This will be enough to boot on the B+ but the wireless card will still not work.
Set a country code for the wireless adapter in your wpa-supplicant.conf (usually under /etc/wpa-supplicant/) adding country=GB
.
Get all the files contained in https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm
and copy them over the content in /lib/firmware/brcm
. This will add a few new and updated drivers for the B+ wireless adapter.
To build a Raspbian toolchain for Swift 3.0.2 a few things need to be changed in the original guide.
Download the Swift 3.0.2 packages instead of the 3.1.1 ones:
curl -o /tmp/swift-3.0.2-RPi1Zero-RaspbianNov16.tgz https://www.dropbox.com/s/dkrkt9ht1c3hog2/swift-3.0.2-RPi1Zero-RaspbianNov16.tgz
curl -o /tmp/swift-3.0.2-RELEASE-osx.pkg https://swift.org/builds/swift-3.0.2-release/xcode/swift-3.0.2-RELEASE/swift-3.0.2-RELEASE-osx.pkg
Launch the script with these parameters:
Disable APFS local snapshots:
sudo tmutil disable localsnapshot
List the current snapshots:
tmutil listlocalsnapshots /
Delete them manually:
tmutil deletelocalsnapshots
Qualche indirizzo shoutcast per ascoltare radio italiane direttamente da itunes ("Open Stream"):
Virgin Radio: http://icecast.unitedradio.it/Virgin.mp3
Lifegate Radio: http://onair11.xdevel.com:8024/
Radio 24: http://shoutcast2.radio24.it:8000/
Radio Marconi: http://onair15.xdevel.com:8922/
diff --git a/CMakeLists.txt b/CMakeLists.txt | |
index 112b5d6..e6f790d 100644 | |
--- a/CMakeLists.txt | |
+++ b/CMakeLists.txt | |
@@ -552,6 +552,8 @@ else() | |
set(SWIFT_HOST_VARIANT_ARCH_default "powerpc64le") | |
elseif("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "s390x") | |
set(SWIFT_HOST_VARIANT_ARCH_default "s390x") | |
+ elseif("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "i686") | |
+ set(SWIFT_HOST_VARIANT_ARCH_default "i686") |
Once you dd the image they provide, you'll notice that you can only boot from eMMC when the SD is not inserted and if you inser it after boot, the system doesn't even discover the devices.
There is an easy fix for this.
At boot, uBoot looks for /boot/bananapi/bpi-m3/linux/uEnv.txt
and loads /boot/bananapi/bpi-m3/linux/script.bin
that contains additional configuration, like how to manage the SD, in binary format.
You just need to follow a few simple steps to enable SD discovery after boot (there is a way to boot from the boot partition on the SD and then load the OS from eMMC but I didn't have time to experiment with that).
Install xz with homebrew:
brew install xz
Insert the SD and get the device name for the SD with df
:
Filesystem 512-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1 487867392 157859992 329495400 33% 2352643 4292614636 0% /
devfs 373 373 0 100% 647 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net