Size: 865
Comment: created
|
Size: 3862
Comment: Disable watchdog to allow completion of the Installation (you have to be quick otherwise :-), document mac address handling
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
The [[https://omnia.turris.cz/en/|Turris Omnia]] is an ARM-based (mostly) open hardware router board developed by [[https://www.turris.cz/en/|Project Turris]] of [[https://www.nic.cz/|CZ.NIC]] and [[http://igg.me/at/turris-omnia|available via Indiegogo]]. | The [[https://omnia.turris.cz/en/|Turris Omnia]] is an ARM-based (mostly) open hardware router board developed by [[https://www.turris.cz/en/|Project Turris]] of [[https://www.nic.cz/|CZ.NIC]]. It was kickstarted at [[http://igg.me/at/turris-omnia|Indiegogo]] and is [[https://omnia.turris.cz/en/#buy|available in a few shops]] now. |
Line 5: | Line 5: |
By default it runs [[https://www.openwrt.org/|OpenWRT]], but Debian armhf userland can run on it, too. For now it though needs a non-vanilla (read non-debian) kernel as well as some binary blog. | By default it runs an [[https://www.openwrt.org/|OpenWRT]] derivative called TurrisOS, but Debian armhf userland can run on it, too. For now it though needs a custom (read non-Debian) kernel as well as some additional scripts to get all the features. The custom kernel is based on some Linux 4.x branch and is maintained [[https://github.com/tmshlvck/omnia-linux/|on Github]]. (Update: it is unclear if that repository is the official one. The official repository is the [[https://github.com/CZ-NIC/turris-os/|OpenWRT fork]] and has a different set of patches.) |
Line 7: | Line 7: |
Since this means that there is yet no Debian Installer support for the Turris Omnia either, the only known way to get Debian running on it is the [[https://github.com/tmshlvck/omnia-debian|omnia-debian project on GitHub]]. It's a script to cross-compile the kernel and to generate an image which with which you can flash Debian armhf on the Turris Omnia. | == Installing vanilla Debian == There is no support in the Debian Installer yet, but the only critical part missing is the device tree. The following works fine after connecting the WAN port to a dhcp managed network: {{{#!highlight sh wget https://d-i.debian.org/daily-images/armhf/daily/netboot/vmlinuz wget https://d-i.debian.org/daily-images/armhf/daily/netboot/initrd.gz wget https://www.kleine-koenig.org/tmp/armada-385-turris-omnia.dtb }}} Then install a tftp server, put the above files in ''/srv/tftp'' and on the serial console enter the following in U-Boot: {{{ mw 0xf1020300 0x403 #disable watchdog dhcp tftpboot 0x01000000 vmlinuz tftpboot 0x02000000 armada-385-turris-omnia.dtb tftpboot 0x03000000 initrd.gz bootz 0x01000000 0x03000000:$filesize 0x02000000 }}} I recommend to use btrfs as rootfs, as U-Boot can handle that and TurrisOS also makes use of it. Before ending the installation put the dtb into the rootfs as ''/boot/dtb''. Then you can boot into your linux using: {{{ setenv mmcboot=btrload mmc 0 0x01000000 boot/vmlinuz\; btrload mmc 0 0x02000000 boot/dtb\; btrload mmc 0 0x03000000 boot/initrd.img\; bootz 0x01000000 0x03000000:$filesize 0x02000000 setenv bootargs console=ttyS0,115200 rootfstype=btrfs rootdelay=2 root=/dev/mmcblk0p1 rootflags=commit=5 rw saveenv }}} There are some missing parts yet, so the SFP and switch port doesn't work and the wlan drivers fail to probe. === Watchdog handling === The bootloader enables the watchdog of the SoC. To handle this you either have to disable it again in the bootloader (see above) or pet it regularly. For the latter just add {{{ [Manager] RuntimeWatchdogSec=10s }}} to `/etc/systemd/system.conf`. === MAC address === U-Boot doesn't provide the mac addresses to be used in the device tree. To make the Debian system use the right ones I did: {{{ cat > /etc/systemd/network/00-eth0.link [Match] Path=platform-f1070000.ethernet [Link] MACAddress=... EOF }}} and the same for eth1 (`platform-f1030000.ethernet`) and eth2 (`platform-f1034000.ethernet`). The mac address reserved for your machine is saved in the crypto chip. To find out the base check U-Boot's ethaddr variable. You "own" this and the two following addresses. === RTC === The in-SoC RTC isn't working properly. It is somewhat working after doing {{{ mw 0xf10184a0 0xfd4d4cfa }}} in U-Boot. If you don't do this, the driver only reads `2016-12-16` from it. == Installing with self-build kernel == For an alternative installation using a self compiled kernel (instead of a debian kernel as above) see the [[https://github.com/tmshlvck/omnia-debian/wiki|omnia-debian wiki]]. If you follow this one, you're not keen on cross-compiling and accept to trust images downloaded unencrypted from the internet, you can find an ready-made image on http://aule.elfove.cz/%7Ebrill/omnia-debian/. |
Installing Debian On The Turris Omnia Router
The Turris Omnia is an ARM-based (mostly) open hardware router board developed by Project Turris of CZ.NIC. It was kickstarted at Indiegogo and is available in a few shops now.
By default it runs an OpenWRT derivative called TurrisOS, but Debian armhf userland can run on it, too. For now it though needs a custom (read non-Debian) kernel as well as some additional scripts to get all the features. The custom kernel is based on some Linux 4.x branch and is maintained on Github. (Update: it is unclear if that repository is the official one. The official repository is the OpenWRT fork and has a different set of patches.)
Installing vanilla Debian
There is no support in the Debian Installer yet, but the only critical part missing is the device tree. The following works fine after connecting the WAN port to a dhcp managed network:
Then install a tftp server, put the above files in /srv/tftp and on the serial console enter the following in U-Boot:
mw 0xf1020300 0x403 #disable watchdog dhcp tftpboot 0x01000000 vmlinuz tftpboot 0x02000000 armada-385-turris-omnia.dtb tftpboot 0x03000000 initrd.gz bootz 0x01000000 0x03000000:$filesize 0x02000000
I recommend to use btrfs as rootfs, as U-Boot can handle that and TurrisOS also makes use of it. Before ending the installation put the dtb into the rootfs as /boot/dtb. Then you can boot into your linux using:
setenv mmcboot=btrload mmc 0 0x01000000 boot/vmlinuz\; btrload mmc 0 0x02000000 boot/dtb\; btrload mmc 0 0x03000000 boot/initrd.img\; bootz 0x01000000 0x03000000:$filesize 0x02000000 setenv bootargs console=ttyS0,115200 rootfstype=btrfs rootdelay=2 root=/dev/mmcblk0p1 rootflags=commit=5 rw saveenv
There are some missing parts yet, so the SFP and switch port doesn't work and the wlan drivers fail to probe.
Watchdog handling
The bootloader enables the watchdog of the SoC. To handle this you either have to disable it again in the bootloader (see above) or pet it regularly. For the latter just add
[Manager] RuntimeWatchdogSec=10s
to /etc/systemd/system.conf.
MAC address
U-Boot doesn't provide the mac addresses to be used in the device tree. To make the Debian system use the right ones I did:
cat > /etc/systemd/network/00-eth0.link [Match] Path=platform-f1070000.ethernet [Link] MACAddress=... EOF
and the same for eth1 (platform-f1030000.ethernet) and eth2 (platform-f1034000.ethernet).
The mac address reserved for your machine is saved in the crypto chip. To find out the base check U-Boot's ethaddr variable. You "own" this and the two following addresses.
RTC
The in-SoC RTC isn't working properly. It is somewhat working after doing
mw 0xf10184a0 0xfd4d4cfa
in U-Boot. If you don't do this, the driver only reads 2016-12-16 from it.
Installing with self-build kernel
For an alternative installation using a self compiled kernel (instead of a debian kernel as above) see the omnia-debian wiki. If you follow this one, you're not keen on cross-compiling and accept to trust images downloaded unencrypted from the internet, you can find an ready-made image on http://aule.elfove.cz/%7Ebrill/omnia-debian/.