Translation(s): none

DebianOn is an effort to document how to install, configure and use Debian on some specific hardware. Therefore potential buyers would know if that hardware is supported and owners would know how get the best out of that hardware.

The purpose is not to duplicate the Debian Official Documentation, but to document how to install Debian on some specific hardware.

If you need help to get Debian running on your hardware, please have a look at our user support channels where you may find specific channels (mailing list, IRC channel) dedicated to certain types of hardware.

Models covered
Turris MOX A

Overall Status

Core Components

[ATTACH]

Boot Standard Kernel:

{OK}

LAN network card:

{OK}

MMC:

/!\

USB:

/!\

Extra Features

CPU Frequency Scaling

[?]

Hibernation

[?]

Sleep / Suspend

[?]

Modem

[?]

Wireless/Wifi

[?]

Legend :
{OK} = OK ; {X} Unsupported(No Driver) ; /!\ = Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable
{i} = Configuration Required; X-( = Only works with a non-free driver and or firmware

Important Note

{i} Turris MOX comes with an internal SPI flash hosting u-boot. Such u-boot is good enough for the Debian Installer needs, therefore you don't need to build and install any.

{i} Installing Debian from a standard iso image, via SD card or USB stick, does not work. You need to prepare your installation SD card from the parts in https://deb.debian.org/debian/dists/stable/main/installer-arm64/current/images/netboot/SD-card-images/ as follows (replace /dev/sdX with the actual device name of your media):

{i} The stock u-boot looks for FDT file mvebu-turris_mox.dtb while the rest of us identifies this board with marvell/armada-3720-turris-mox.dtb, as per upstream Linux. Therefore you need to modify the installation media as follows:

Once the system is installed, the Debian's u-boot script will use the right FDT file and you can forget mvebu-turris_mox.dtb entirely unless you want to install u-boot-menu, in that case you need to do the following right after installing u-boot-menu:

/!\ There are issues with MMC and USB3 once you try to boot the installed system. It's not clear why none of them seem to affect the Debian Installer's kernel though.

Investigation on the FDT is ongoing, see https://lore.kernel.org/all/20200513175648.GA7561@dumbo/.

Configuration

Power Management

WiFi

Modem


System Summary

lspci

lsusb

lsusb -v | grep -E '\<(Bus|iProduct|bDeviceClass|bDeviceProtocol)' 2>/dev/null

USB Host controllers entries (without OHCI, UHCI, EHCI) are removed too.

Resources

Attachments

Other reports

Credits