Supported hardware ################## For development, the `GL.iNet GL-MT300A `_ is an attractive choice as it has a builtin "debrick" procedure in the boot monitor and is also comparatively simple to attach serial cables to (soldering not required), so it is lower-risk than some devices. For a more powerful device, something with an ath10k would be the safe bet, or the Linksys E8450 which seems popular in the openwrt community. Belkin RT-3200 / Linksys E8450 ****************************** This device is based on a 64 bit Mediatek MT7622 ARM platform, and is "work in progress" in Liminix. .. note:: The factory flash image contains ECC errors that make it incompatible with Liminix: you need to use the `OpenWrt UBI Installer `_ to rewrite the partition layout before you can flash Liminix onto it (or even use it with :ref:`system-outputs-tftpboot`, if you want the wireless to work). Hardware summary ================ - MediaTek MT7622BV (1350MHz) - 128MB NAND flash - 512MB RAM - b/g/n wireless using MediaTek MT7622BV (MT7615E driver) - a/n/ac/ax wireless using MediaTek MT7915E Installation ============ Installation is currently a manual process (you need a :ref:`serial ` conection and TFTP) following the instructions at :ref:`system-outputs-ubimage` GL.iNet GL-AR750 **************** Hardware summary ================ The GL-AR750 "Creta" travel router features: - QCA9531 @650Mhz SoC - dual band wireless: IEEE 802.11a/b/g/n/ac - two 10/100Mbps LAN ports and one WAN - 128MB DDR2 RAM - 16MB NOR Flash - supported in OpenWrt by the "ath79" SoC family The GL-AR750 has two distinct sets of wifi hardware. The 2.4GHz radio is part of the QCA9531 SoC, i.e. it's on the same silicon as the CPU, the Ethernet, the USB etc. The device is connected to the host via `AHB `_ and it is supported in Linux using the ath9k driver. 5GHz wifi is provided by a QCA9887 PCIe (PCI embedded) WLAN chip, supported by the ath10k driver. Installation ============ As with many GL.iNet devices, the stock vendor firmware is a fork of OpenWrt, meaning that the binary created by :ref:`system-outputs-mtdimage` can be flashed using the vendor web UI or the U-Boot emergency "unbrick" routine. For flashing from an existing Liminix system (we believe that) it is necessary to first boot into a :ref:`system-outputs-kexecboot` system, otherwise you'll be overwriting flash partitions while they're in use - and that might not end well. Vendor web page: https://www.gl-inet.com/products/gl-ar750/ OpenWrt web page: https://openwrt.org/toh/gl.inet/gl-ar750 GL.iNet GL-MT300A ***************** The GL-MT300A is based on a MT7620 chipset. For flashing from U-Boot, the firmware partition is from 0xbc050000 to 0xbcfd0000. WiFi on this device is provided by the rt2800soc module. It expects firmware to be present in the "factory" MTD partition, so - assuming we want to use the wireless - we need to build MTD support into the kernel even if we're using TFTP root. Installation ============ The stock vendor firmware is a fork of OpenWrt, meaning that the binary created by :ref:`system-outputs-mtdimage` can be flashed using the vendor web UI or the U-Boot emergency "unbrick" routine. For flashing from an existing Liminix system (we think) it is necessary to first boot into a :ref:`system-outputs-kexecboot` system, otherwise you'll be overwriting flash partitions while they're in use - and that might not end well. Vendor web page: https://www.gl-inet.com/products/gl-mt300a/ OpenWrt web page: https://openwrt.org/toh/gl.inet/gl-mt300a GL.iNet GL-MT300N-v2 ******************** The GL-MT300N-v2 "Mango" is is very similar to the :ref:`MT300A , but is based on the MT7628 chipset instead of MT7620. It's also marginally cheaper and comes in a yellow case not a blue one. Be sure your device is v2 not v1, which is a different animal and has only half as much RAM. Installation ============ The stock vendor firmware is a fork of OpenWrt, meaning that the binary created by :ref:`system-outputs-mtdimage` can be flashed using the vendor web UI or the U-Boot emergency "unbrick" routine. For flashing from an existing Liminix system (we think) it is necessary to first boot into a :ref:`system-outputs-kexecboot` system, otherwise you'll be overwriting flash partitions while they're in use - and that might not end well. Vendor web page: https://www.gl-inet.com/products/gl-mt300n-v2/ OpenWrt web page: https://openwrt.org/toh/gl.inet/gl-mt300n_v2 QEMU MIPS ********* This target produces an image for QEMU, the "generic and open source machine emulator and virtualizer". MIPS QEMU emulates a "Malta" board, which was an ATX form factor evaluation board made by MIPS Technologies, but mostly in Liminix we use paravirtualized devices (Virtio) instead of emulating hardware. Building an image for QEMU results in a :file:`result/` directory containing ``run.sh`` ``vmlinux``, and ``rootfs`` files. To invoke the emulator, run ``run.sh``. The configuration includes two emulated "hardware" ethernet devices and the kernel :code:`mac80211_hwsim` module to provide an emulated wlan device. To read more about how to connect to this network, refer to :ref:`qemu-networking` in the Development manual. QEMU Aarch64 ************ This target produces an image for the `QEMU "virt" platform `_ using a 64 bit CPU type. ARM targets differ from MIPS in that the kernel format expected by QEMU is an "Image" (raw binary file) rather than an ELF file, but this is taken care of by :command:`run.sh`. Check the documentation for the :ref:`QEMU` (MIPS) target for more information. QEMU ARM v7 *********** This target produces an image for the `QEMU "virt" platform `_ using a 32 bit CPU type. ARM targets differ from MIPS in that the kernel format expected by QEMU is an "Image" (raw binary file) rather than an ELF file, but this is taken care of by :command:`run.sh`. Check the documentation for the :ref:`QEMU` (MIPS) target for more information. TP-Link Archer AX23 / AX1800 Dual Band Wi-Fi 6 Router ***************************************************** Hardware summary ================ - MediaTek MT7621 (880MHz) - 16MB Flash - 128MB RAM - WLan hardware: Mediatek MT7905, MT7975 Limitations =========== Status LEDs do not work yet. Uploading an image via tftp doesn't work yet, because the Archer uboot version is so old it doesn't support overriding the DTB from the mboot command. The tftpboot module doesn't support this yet, see https://gti.telent.net/dan/liminix/pulls/5 for the WiP. Turris Omnia ************ This is a 32 bit ARMv7 MVEBU device, which is usually shipped with TurrisOS, an OpenWrt-based system. Rather than reformatting the builtin storage, we install Liminix on to the existing btrfs filesystem so that the vendor snapshot/recovery system continues to work (and provides you an easy rollback if you decide you don't like Liminix after all). The install process has two stages, and is intended that you should not need to open the device and add a serial console (although it may be handy for visibility, and in case anything goes wrong). First we build a minimal installation/recovery system, then we reboot into that recovery image to prepare the device for the full target install. Installation using a USB stick ============================== First, build the image for the USB stick. Review :file:`examples/recovery.nix` in order to change the default root password (which is ``secret``) and/or the SSH keys, then build it with .. code-block:: console $ nix-build -I liminix-config=./examples/recovery.nix \ --arg device "import ./devices/turris-omnia" \ -A outputs.mbrimage -o mbrimage $ file -L mbrimage mbrimage: DOS/MBR boot sector; partition 1 : ID=0x83, active, start-CHS (0x0,0,5), end-CHS (0x6,130,26), startsector 4, 104602 sectors Next, copy the image from your build machine to a USB storage medium using :command:`dd` or your other most favoured file copying tool, which might be a comand something like this: .. code-block:: console $ dd if=mbrimage of=/dev/path/to/the/usb/stick \ bs=1M conv=fdatasync status=progress The Omnia's default boot order only checks USB after it has failed to boot from eMMC, which is not ideal for our purpose. Unless you have a serial cable, the easiest way to change this is by booting to TurrisOS and logging in with ssh: .. code-block:: console root@turris:/# fw_printenv boot_targets boot_targets=mmc0 nvme0 scsi0 usb0 pxe dhcp root@turris:/# fw_setenv boot_targets usb0 mmc0 root@turris:/# fw_printenv boot_targets boot_targets=usb0 mmc0 root@turris:/# reboot -f It should now boot into the recovery image. It expects a network cable to be plugged into LAN2 with something on the other end of it that serves DHCP requests. Check your DHCP server logs for a request from a ``liminix-recovery`` host and figure out what IP address was assigned. .. code-block:: console $ ssh liminix-recovery.lan You should get a "Busybox" banner and a root prompt. Now you can start preparing the device to install Liminix on it. First we'll mount the root filesystem and take a snapshot: .. code-block:: console # mkdir /dest && mount /dev/mmcblk0p1 /dest # schnapps -d /dest create "pre liminix" # schnapps -d /dest list ERROR: not a valid btrfs filesystem: / # | Type | Size | Date | Description ------+-----------+-------------+---------------------------+------------------------------------ 1 | single | 16.00KiB | 1970-01-01 00:11:49 +0000 | pre liminix (``not a valid btrfs filesystem: /`` is not a real error) then we can remove all the files .. code-block:: console # rm -r /dest/@/* and then it's ready to install the real Liminix system onto. On your build system, create the Liminix configuration you wish to install: here we'll use the ``rotuer`` example. .. code-block:: console build$ nix-build -I liminix-config=./examples/rotuer.nix \ --arg device "import ./devices/turris-omnia" \ -A outputs.systemConfiguration and then use :command:`min-copy-closure` to copy it to the device. .. code-block:: console build$ nix-shell --run \ "min-copy-closure -r /dest/@ root@liminix-recovery.lan result" and activate it .. code-block:: console build$ ssh root@liminix-recovery.lan \ "/dest/@/$(readlink result)/bin/install /dest/@" The final steps are performed directly on the device again: add a symlink so U-Boot can find :file:`/boot`, then restore the default boot order and reboot into the new configuration. .. code-block:: console # cd /dest && ln -s @/boot . # fw_setenv boot_targets "mmc0 nvme0 scsi0 usb0 pxe dhcp" # cd / ; umount /dest # reboot Installation using a TFTP server and serial console =================================================== If you have a :ref:`serial` console connection and a TFTP server, and would rather use them than fiddling with USB sticks, the :file:`examples/recovery.nix` configuration also works using the ``tftpboot`` output. So you can do .. code-block:: console build$ nix-build -I liminix-config=./examples/recovery.nix \ --arg device "import ./devices/turris-omnia" \ -A outputs.tftpboot and then paste the generated :file:`result/boot.scr` into U-Boot, and you will end up with the same system as you would have had after booting from USB. If you don't have a serial console connection you could probably even get clever with elaborate use of :command:`fw_setenv`, but that is left as an exercise for the reader. Zyxel NWA50AX ******************** Zyxel NWA50AX is quite close to the GL-MT300N-v2 "Mango" device, but it is based on the MT7621 chipset instead of the MT7628. Installation ============ This device is pretty, but, due to its A/B capabilities, can be a bit hard to use completely. The stock vendor firmware is a downstream fork of U-Boot: with restricted boot commands. Fortunately, OpenWrt folks figured out trivial command injections, so you can use most of the OpenWrt commands without trouble by just command injecting atns, atna or atnf, e.g. atns "; $real_command". From factory web UI, you can upload the result of the zyxel-nwa-fit output. From another operating system, you need to `dumpimage -T flat_dt -p 0 $zyxel-nwa-fit -o firmware.bin`, `flash_erase $(mtd partition of the target partition firmware or zy_firmware) 0 0`, then you complete by `nandwrite -p $(mtd partition of the target partition firmware or zy_firmware) firmware.bin`. How to put the firmware.bin on the machine is left to you as an exercise, e.g. SSH, TFTP, whatever. From serial, you have two choices: - Flash this system via U-Boot: same reasoning as from an existing Linux system, two choices: - ymodem the binary, perform the write manually, you can inspire yourself from the `script` contained in the vendor firmware, those are just a FIT containing a script. - prepare a FIT containing a script executing your commands, tftpboot this. - boot from an existing Liminix system, e.g. TFTPBOOT image. - boot from an OpenWrt system, i.e. follow OpenWrt steps. Once you are in a Linux system, understand that this device has A/B boot. OpenWrt provides you with `zyxel-bootconfig` to set/unset the image status and choice. The kernel is booted with `bootImage=` which tells you which slot are you on. You should find yourself with 10ish MTD partitions, the most interesting ones are two: - firmware: 40MB - firmware_1: 40MB In the current setup, they are split further into kernel (8MB) and ubi (32MB). Once you are done with first installation, note that if you want to use the A/B feature, you need to write a _secondary_ image on the slot B. There is no proper flashing code that will set the being-updated slot to `new` and boot on it to verify if it's working. This is a WIP. Upgrading your system can be achieved via: - `liminix-rebuild` for the userspace. - `flash_erase` + `nandwrite` for the kernelspace to the other slot than the one you are booted on, note that you can just nandwrite the mtd partition corresponding to the *kernel* and not the whole firmware. If you soft-bricked your AP, i.e. you cannot boot anything in U-Boot, no worries, just plug the serial console, prepare a TFTP server (via `tufted` for example), download vendor firmware, set up `atns`, `atnf`, etc. and run `atnz`. This will reflash everything back to normal via TFTP. If you hard-bricked your AP, i.e. U-Boot is telling you to transfer a valid bootloader via ymodem, just extract a U-Boot from the vendor OS, send it via ymodem and use the previous operations to perform a full flash this time of all partitions. Note that if you erased your MRD partition, you lost your serial and MAC address. There's no way to recover the original one except by reading the physical label on your… device! If you super-hard-bricked your AP, i.e. no output on serial console, congratulations, you reached one of the rare state of this device. You need an external NAND flasher to repair it and write the first stage from Mediatek to continue the previous recovery operations. Development TODO list: - Better support for upgrade automation w.r.t. to A/B, e.g. automagic scripts. - Mount the logs partition, mount / as overlayfs of firmware ? rootfs and rootfs_data for extended data. - Jitter-based entropy injection? Device can be slow to initialize its CRNG and hostapd will reject few clients at the start because of that. - Defaults for hostapd based on MT7915 capabilities? See the example for one possible list. - Remove primary/secondary hack and put it in preinit. - Offer ways to reflash the *bootloader* itself to support direct boot via UBI and kernel upgrades via filesystem rewrite. Vendor web page: https://www.zyxel.com/fr/fr/products/wireless/ax1800-wifi-6-dual-radio-nebulaflex-access-point-nwa50ax OpenWrt web page: https://openwrt.org/inbox/toh/zyxel/nwa50ax OpenWrt tech data: https://openwrt.org/toh/hwdata/zyxel/zyxel_nwa50ax