You are not logged in.
Pages: 1
The partition is in the image. I didnt created it myself.
armbian does work without a fat32 boot partition.
I know the fat32 boot partition only from Raspberry Pi images.
Some days ago I did try devuan on a Raspberry Pi, which wasnt a problem because of the complete Image-file.
Now I want to try it on a sunxi-system (like my Orange Pi Zero H2+) and there you have to "assemble" the image on the sdcard,
because for every supported sunxi-system there is a own uboot .bin-file.
At first I was I was confused about to dd to the device /dev/mmcblk0, because mostly when I did see this device then its the local boot device of my SBC
(the name mmcblk0 is the name of the card WHEN I will boot from it LATER)
So when I would try to create the "assembled" image on /dev/mmcblk0 I would destroy (from my mind) the root/boot-system.
Additionally I wouldnt call if "to flash" the u-boot to the mmcblk0/sdcard
After re-reading the instructions I realized that /dev/mmcblk0 could also be /dev/sdb if I use my single-slot MicroS-Card-Reader/Writer while assembling the image on my NanoPi Neo2 (which is running with armbian).
So I inserted the MicroSDCard with my USB-Reader/Writer to my NanoPi Neo2 and did get (via "dmesg -w"):
[29637.841118] usb 3-1: New USB device found, idVendor=8564, idProduct=4000
[29637.841137] usb 3-1: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[29637.841149] usb 3-1: Product: Transcend
[29637.841160] usb 3-1: Manufacturer: TS-RDF5
[29639.230277] sd 1:0:0:0: [sdb] Attached SCSI removable disk
The get a "clean" card is did delete the partitions with fdisk:
----------------------------------------------
fdisk /dev/sdb
----------------------------------------------
p - for printing partition table
Device Boot Start End Sectors Size Id Type
/dev/sdb1 8192 61896127 61887936 29,5G 83 Linux
d - for deleting a partition
Selected partition 1
Partition 1 has been deleted.
w - for write & exit
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
----------------------------------------------
After that the installation is mostly like on http://devuan.ksx4system.net/devuan_asc … README.txt
BUT firstly I created a own directory (/home/guido/devuan) and did a cd into it - AND I did use here the device /dev/sdb
of my USB-Reader/Writer:
INSTALLATION
------------
(Path /home/guido/devuan here as example for my system):
mkdir /home/guido/devuan
cd /home/guido/devuan
1.
--
Download the image you want:
; curl -O https://files.devuan.org/devuan_ascii/embedded/devuan_ascii_2.0.0_armhf_sunxi.img.xz
2.
--
Download the shasums and the signature:
; curl -O https://files.devuan.org/devuan_ascii/embedded/SHA256SUMS
; curl -O https://files.devuan.org/devuan_ascii/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):
; sudo xzcat ./devuan_ascii_2.0.0_armhf_sunxi.img.xz | sudo dd of=/dev/sdb bs=2M status=progress && sync
5.
--
In case it's a sunxi image (here the Opi Zero), grab your respective u-boot blob, and flash (dd) it to the sdcard:
; curl -O https://files.devuan.org/devuan_ascii/embedded/u-boot/orangepi_zero_defconfig.bin
; sudo dd if=./orangepi_zero_defconfig.bin of=/dev/sdb bs=1024 seek=8 status=progress && sync
After booting the Orange Pi Zero from this card the former /dev/sdb at the NanoPi Neo2 gets now /dev/mmcblk0
BUT on the Orange Pi Zero:
mount:
/dev/mmcblk0p1 on /boot type ext4 (rw,relatime)
or fdisk:
fdisk /dev/mmcblk0
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 264191 262144 128M c W95 FAT32 (LBA)
/dev/mmcblk0p2 264192 29560473 29296282 14G 83 Linux
uname -a:
Linux devuan 4.17.0 #1 SMP Tue Jun 5 16:49:29 CEST 2018 armv7l GNU/Linux
BTW: Keep in mind to (manually) expand the filesystem later for /dev/mmcblk0p2
Generate a /etc/wpa_supplicant/wpa_supplicant.conf (see https://wiki.debian.org/WiFi/HowToUse)
I did create my file with:
su -c "wpa_passphrase myssid my_very_secret_passphrase > /etc/wpa_supplicant/wpa_supplicant.conf"
and did configure my wlan0 in /etc/network/interfaces with
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
or for a static IP (in my network):
# wlan0
auto wlan0
iface wlan0 inet static
address 192.168.6.125
netmask 255.255.255.0
gateway 192.168.6.1
# here are my own 2 Pi-Hole DNS servers
dns-nameservers 192.168.6.20 192.168.6.3
# Google DNS
# dns-nameservers 8.8.8.8 8.8.4.4
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
I downloaded the files and did install them.
I only get wlan0 up and set a static IP-Adress, BUT cant ping/connect to my network like on eth0
root@pi-zero-devuan(192.168.6.125):/# ls -l /lib/firmware/brcm
total 748
-rw-r--r-- 1 root root 388739 Nov 5 20:13 brcmfmac43430-sdio.bin
-rw-r--r-- 1 root root 369577 Nov 5 20:07 brcmfmac43430-sdio.bin_org
-rw-r--r-- 1 root root 1121 Nov 5 20:13 brcmfmac43430-sdio.txt
dmesg:
[ 5.763618] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[EDIT / SOLVED]
The brcmfmac43430-sdio.* files are from the actual raspbian lite (/lib/firmware/brcm) or the link above:
https://github.com/RPi-Distro/firmware- … aster/brcm
How to get the files the easy way (in the comsole of the devuan-pi):
brcmfmac43430-sdio.bin Update brcmfmac43430-sdio.bin 8 months ago
brcmfmac43430-sdio.txt Improved brcmfmac BT coexistence parameters 3 months ago
cd /lib/firmware/brcm
# backup of the old files (if there)
mv /lib/firmware/brcm/brcmfmac43430-sdio.txt /lib/firmware/brcm/brcmfmac43430-sdio.txt_org
mv /lib/firmware/brcm/brcmfmac43430-sdio.bin /lib/firmware/brcm/brcmfmac43430-sdio.bin_org
# get the new files
wget https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/master/brcm/brcmfmac43430-sdio.txt
wget https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.bin
I had in the past used the wpa-command directly in /etc/network/interfaces, but that didnt seem to work nowadays.
I had to switch to use a /etc/wpa_supplicant/wpa_supplicant.conf (see https://wiki.debian.org/WiFi/HowToUse)
I did create the file with:
su -c "wpa_passphrase myssid my_very_secret_passphrase > /etc/wpa_supplicant/wpa_supplicant.conf"
and did configure my wlan0 in /etc/network/interfaces with
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
or for a static IP (in my network):
# wlan0
auto wlan0
iface wlan0 inet static
address 192.168.6.125
netmask 255.255.255.0
gateway 192.168.6.1
# here are my own 2 Pi-Hole DNS servers
dns-nameservers 192.168.6.20 192.168.6.3
# Google DNS
# dns-nameservers 8.8.8.8 8.8.4.4
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
I installed the RPi1 version of devuan on the ZeroW, but did wonder why it seems to be slower than on raspbian lite.
After searching I did found that devuan uses the CPU governor "powersave" while raspbian uses "ondemand"
So after give the command
echo 'ondemand' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
devuan should work fast as raspbian on a Raspberry Pi Zero W
Pages: 1