Devuan BEOWULF ARM builds ======================= These are some of the image types offered: * MEDIA IMAGES - Images with already installed Operating System * NETBOOT INSTALABLE IMAGES - Images which the unique purpose is, to Install the Operating System Later, new MEDIA Images could apear when ready.. See https://www.devuan.org/os/filenaming for Filenaming Conventions. We kindly ask to test them and report all weirdness as a Devuan bug (bugs.devuan.org), or on the #devuan-arm IRC channel. Beowulf 3.0.0 Images -------------------- Consult https://git.devuan.org/sdk/arm-sdk/blob/master/doc/quirks.md to see if there is anything you should know about a specific image. Beowulf 3.1.0 Images -------------------- For Raspberry Pi Beowulf 3.1.0 images, the build system that generated the images is at https://github.com/pyavitz/rpi-img-builder, configured with Raspberry Pi Foundation non-mainline kernel built from source on RPi3 arm64 running Beowulf 3.1.0. MEDIA DEVICE IMAGES ------------------- Media supported images: * RaspberryPi{1,2,3,4,zero,zerow,cm1,cm3,cm4} * OrangePi One Plus * Olinuxino Lime 2 * BananaPi m2 Zero * Radaxa RockPi4{A,B} * Pine64 RockPro64 * nanoPI NEO Air * nanoPI R2S * Kobol Helios4(Not yet availlable) * Others Current Media supported Allwinner boards: * [armhf] Olimex OLinuXino Lime2 (A20) * [armhf] BananaPi m2 Zero (H2+) * {armhf] nanoPI NEO Air (H3) * [arm64] OrangePi One Plus (H6) Current Media supported Broadcom boards: * [armel] RaspberryPi{1,zero,zerow,cm1} (BCM2835) * [armhf] RaspberryPi2 (BCM2836) * [arm64] RaspberryPi{3,cm3,4,cm4} (BCM2837,BCM2711) Current Media supported RockChip boards: * [arm64] Radaxa RockPi4{A,B} (RK3399) * [arm64] Pine64 RockPro64 (RK3399) * [arm64] nanoPI R2S (RK3328) MEDIA IMAGE CREDENTIALS ----------------------- The devices should startup a openssh-server, but you won't be able to login directly over ssh, as root user.. Instead, login as devuan user, and change then to root, by issuing: 'sudo su -' and typing your *devuan* password Beowulf 3.0.0 credentials: devuan:'devuan' root :'toor' Chimaera 4.0.0 credentials: devuan:'devuan' root :'toor' Beowulf 3.1.0 RaspBerryPi{0,2,3,4} credentials (rpi-img-builder based): pi:'board' (with passwordless SUDO :-O ) MEDIA INSTALLATION ------------------ other useful documentation can be found here: * https://www.raspberrypi.org/documentation/installation/installing-images/mac.md 1. -- Download the image you want: ; curl -O https://files.devuan.org/devuan_beowulf/embedded/devuan_beowulf_3.0.0_armhf_sunxi.img.xz 2. -- Download the shasums and the signature: ; curl -O https://files.devuan.org/devuan_beowulf/embedded/SHA256SUMS ; curl -O https://files.devuan.org/devuan_beowulf/embedded/SHA256SUMS.asc 3. -- Verify: ; gpg --verify SHA256SUMS.asc && sha256sum -c SHA256SUMS 4. -- dd the raw image to a medium of your choice (little less than 2GB): ; xzcat devuan_beowulf_3.0.0_armhf_sunxi.img.xz | sudo dd of=/dev/mmcblk0 bs=2M 5. -- In case it's a sunxi image, grab your respective u-boot blob, and flash it: ; curl -O https://files.devuan.org/devuan_beowulf/embedded/u-boot/Cubieboard2_defconfig.bin ; sudo dd if=Cubieboard2_defconfig.bin of=/dev/mmcblk0 bs=1024 seek=8 && sync OTHER MEDIA DEVICE IMAGES ------------------------- In the Path bellow you will find Media Image options for some Devices: * [ armel ] http://http://deb.devuan.org/devuan/dists/beowulf/main/installer-armel/current/images NETBOOT INSTALLABLE DEVICE IMAGES --------------------------------- In the Paths bellow you will find a netboot installer Image option for some boards: * [ armhf ] http://deb.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/netboot/SD-card-images * [ arm64 ] http://deb.devuan.org/devuan/dists/beowulf/main/installer-arm64/current/images/netboot/SD-card-images Installable supported images: * A10-OLinuXino-Lime * A20-OLinuXino-Lime * A20-OLinuXino-Lime2 * A20-OLinuXino-MICRO * A20-Olimex-SOM-EVB * BananaPi * BananaPiM2Berry * BananaPro * BeagleBoard-X15 * BeagleBoneBlack * Cubieboard * Cubieboard2 * Cubietruck * Cubietruck_plus * Firefly-RK3288 * Lamobo_R1 * MX6_Cubox-i * MX53LOCO * NanoPiNeo * Novena * PandaBoard * Sinovoip_BPI_M3 * Wandboard * orangepi_plus * pcDuino * pcDuino3 * a64-olinuxino * nanopi_neo2 * orangepi_zero_plus2 * pine64_plus * pinebook * teres_i NETBOOT IMAGE CREATION ---------------------- NetBoot Images have 2 Component Types: * firmware..img.gz - Characteristics related only with the Board in cause * partition.img.gz - Commom part, common to all boards( Same OS Architecture ). 1. -- The Combined result of both images, will form the real Image( that will be writen to sdcard ): ; zcat firmware..img.gz partition.img.gz > .img 2. -- Now you can write the complete image to sdcard: ; sudo dd if=PATH_TO/.img of=/dev/sd_card conv=sync OBS: This Image will serve only the purpose of Installing the final Operating System. An Example, For A20-OLinuXino-Lime2 Board: * firmware.A20-OLinuXino-Lime2.img.gz * partition.img.gz 1. -- Now combine both: ; zcat firmware.A20-OLinuXino-Lime2.img.gz partition.img.gz > A20-OLinuXino-Lime2.img 2. -- Write Image to sd-card: ; sudo dd if=PATH_TO/A20-OLinuXino-Lime2.img of=/dev/sd_card conv=sync NETBOOT INSTALLATION -------------------- The Image is needed in sd-card( see section above: "INSTRUCTIONS TO NETBOOT IMAGE CREATION" ). 1. -- Insert sd-card into sbc board. 2. -- Two ways to interact with the image: * Conecting Display/Keyboard to sbc board * Using a USB-Serial converter and connect via uart USING USB-SERIAL CONVERTER OPTION --------------------------------- 1. -- connect usb-serial cable to your computer and sbc board 2. -- Open the serial conection, with picocom/minicom/screen, etc.. 3. -- Only then, apply power Using above section example: A20-OLinuXino-Lime2 - has a serial baudrate of 115200 bps, Connect like this: 2. -- ; picocom /dev/your_serial_device -b 115200 3. -- Only then, apply power to the board It will prompt with a ncurses based text menu installer.. From now on, you are in the usual text-based Installer Process. OBS: Make sure that you mark the partition containing '/boot' with flag 'boot'