Changes between Version 50 and Version 51 of ventana/ubuntu


Ignore:
Timestamp:
01/23/2020 05:12:13 PM (5 years ago)
Author:
Tim Harvey
Comment:

general cleanup

Legend:

Unmodified
Added
Removed
Modified

  • ventana/ubuntu

    v50 v51  
    77
    88This page is dedicated details regarding running Ubuntu on an Gateworks Ventana Board.
     9
     10For a full Board Support Package providing building a Linux distro from source, please see the OpenWrt, Yocto, or Android BSP from the [wiki:ventana#bsp Ventana BSP] page
    911
    1012See also:
    … …  
    1416[=#prebuilt]
    1517== Gateworks pre-built Ubuntu Disk Images ==
    16 Gateworks provides some pre-built Ubuntu firmware images for the Ventana Family:
    17 ||= Name              =||= Size =||= Features =||= Notes =||
    18 || bionic-ventana 18.04 || ~1.2GB^^^1^^^ || console support - Gateworks 4.20 kernel/drivers || **Recommended** ||
    19 || xenial-ventana 16.04 || ~1.2GB^^^1^^^ || console support - Gateworks 4.20 kernel/drivers || ||
    20 || trusty-ventana 14.04 || ~210MB  || console support - Gateworks 3.14 kernel/drivers || ||
    21 || trusty-mm-ventana 14.04 || ~650MB^^^1^^^ || HW acclerated gstreamer/gstreamer-imx - Gateworks 3.14 kernel/drivers || ||
    22  1. requires 2GB and larger storage
    23 
    24 For a full Board Support Package providing building a Linux distro from source, please see the OpenWrt, Yocto, or Android BSP from the [wiki:ventana#bsp Ventana BSP] page
    25 
    26 
    27 === Ubuntu 18.04 LTS (Bionic Beaver) console image (**Recommended**) ===
    28 - *** Note ***: This is a mainline kernel that does not have Video Hardware Acceleration support for gstreamer and a few other Gateworks specific items. For more information, read [wiki:ventana#MainlineLinuxKernelsupport Gateworks Mainline Linux Support].
    29 
    30 A pre-built console image created using the  [#debootstrap debootstrap] method for [http://releases.ubuntu.com/18.04/ Ubuntu 18.04 (Bionic Beaver)] can be downloaded:
    31  * [http://dev.gateworks.com/ventana/images/bionic-ventana_normal.ubi bionic-ventana_normal.ubi] - UBI image for 2K page size 'normal' geometry FLASH (see [wiki:/linux/ubi/#flashgeometry here] to determine your flash geometry)
     18Gateworks provides a pre-built Ubuntu firmware images for the Ventana Family:
     19 * Compressed Disk Image containing boot firmware, kernel and root filesystem '''(Recommended for microSD / eMMC booting)'''
     20  - [http://dev.gateworks.com/ventana/images/bionic-ventana.img.gz bionic-newport.img.gz]
     21  - To update the firmware on a microSD card see [wiki:linux/blockdev#UsingaDiskImage]
     22 * UBI images '''(Recommended for RAW NAND FLASH booting)'''
     23  - [http://dev.gateworks.com/ventana/images/bionic-ventana_normal.ubi bionic-ventana_normal.ubi] - UBI image for 2K page size 'normal' geometry FLASH
     24  - [http://dev.gateworks.com/ventana/images/bionic-ventana_large.ubi bionic-ventana_large.ubi] - UBI image for 4K page size 'large' geometry FLASH
     25  - see [wiki:/linux/ubi/#flashgeometry here] to determine your flash geometry
    3226  - see [wiki:/linux/ubi#BasicMethod here] for info about flashing UBI images
    33   - sha256sum: 74dd09d90833eac04449a1c3f50f66207474088d8e1323fedb0b66c05d6206be
    34  * [http://dev.gateworks.com/ventana/images/bionic-ventana_large.ubi bionic-ventana_large.ubi] - UBI image for 4K page size 'large' geometry FLASH (see [wiki:/linux/ubi/#flashgeometry here] to determine your flash geometry)
    35   - see [wiki:/linux/ubi#BasicMethod here] for info about flashing UBI images
    36   - sha256sum: 20c1e44bb93b35dbb0bfccf49651c43914a82e9aab19d9f20914b0083576f020
    37  * [http://dev.gateworks.com/ubuntu/bionic/bionic-armhf.tar.xz bionic-armhf.tar.xz] - tarball of rootfs you can use to image onto microSD / mSATA
    38   - see [wiki:linux/blockdev linux/blockdev] for instructions
    39   - sha256sum: 7ec750dbe14ce3c4adffea322f575a759da25a407af906061cce05a785cd1758
     27 * [http://dev.gateworks.com/ubuntu/bionic/bionic-armhf.tar.xz bionic-armhf.tar.xz] - tarball of rootfs (not including kernel) you can use to image onto microSD / mSATA. See [wiki:linux/blockdev linux/blockdev] for instructions
     28 * [http://dev.gateworks.com/ventana/images/gateworks-linux-4.20.tar.xz gateworks-linux-4.20.tar.xz] Kernel, device-tree, bootscript, and modules that can be combined with a root filesystem to create a bootable system. See [wiki:linux/blockdev linux/blockdev] for instructions
     29
     30'''Login Information (default)'''
     31 * Username: root
     32 * Password: root
    4033
    4134Features:
    42 - Ubuntu 18.04.1 LTS (from debootstrap instructions)
    43 - Ubuntu Bionic kernel (Linux 4.20 based) with drivers/firmware
    44 - custom bootscript supporting NAND/UBI, MMC, SATA, USB boot devices and root filesystems
    45 - extra packages: openssh-server can-utils i2c-tools usbutils pciutils
    46 - eth0 dhcp
    47 - user root passwd root
     35- Ubuntu arm core (created via debootstrap)
     36- Gateworks Ventana Linux kernel (Linux 4.20 based)
     37- eth0 dhcp with a 30 second timeout
     38- User: root password: root
     39- Packages installed on top of core including:
     40 * Updated modemmanager/libqmi-utils/libmbim-utils (see [wiki:ubuntu#modem ubuntu/modem])
     41 * Misc wireless: wpasupplicant iw
     42 * Misc utils: vim can-utils i2c-tools usbutils pciutils screen watchdog binutils
     43 * Misc network: wget ethtool iperf iperf3 openssh-server iptables
     44 * Linux firmware
     45 * mmc-utils from https://packages.debian.org/sid/utils/mmc-utils
     46 * Gateworks [https://raw.githubusercontent.com/Gateworks/meta-gateworks/master/recipes-support/hostapd-conf/hostapd-conf/hostapd-conf hostapd-conf script]
     47 * Filesystem tools: e2fstools parted
     48- first-boot script to grow root filesystem partition and filesystem (useful when putting disk images on removable storage devices)
     49- use ifupdown tools instead of netplan (we find them easier to understand and configure)
    4850
    4951
    … …  
    116118[=#debootstrap]
    117119== Building the Root Filesystem via debootstrap
    118 The preferred way to create a Ubuntu root filesystem is to use the {{{deboostrap}}} utility on a Debian or Ubuntu host. This tool provides a 2-stage install where the second stage is within a chroot environment using qemu-arm.
     120A popular way to create a Ubuntu root filesystem is to use the {{{deboostrap}}} utility on a Debian or Ubuntu host. This tool provides a 2-stage install where the second stage is within a chroot environment using qemu-arm.
     121
     122Gateworks uses a script to do this which you may find at ​http://github.com/Gateworks/ubuntu-rootfs
    119123
    120124Requirements:
    121125- Linux Ubuntu or Debian System with network connection and sudo permissions
    122 - Linux Kernel (ie Gateworks latest pre-built 3.14 kernel with full hardware support, Ubuntu pre-built kernel (missing full video in/out support but more up-to-date), or a vanilla mainline kernel (still missing full video in/out support but even more up-to-date), or a kernel of your own) - see below steps for more detail
     126- Linux Kernel
    123127- Ventana target board with bootloader
    124128- Boot device with 2GB+ of free space (micro-SD, USB mass storage, mSATA, 1GB/2GB NAND flash)
    125129
    126130Important notes:
     131 * These steps are not always exactly what we do in our script but give you an idea of how you would go about doing it yourself if you wanted to customize something
    127132 * We set and use '''target''' and '''distro''' env variables in step 2 and use those env variables in the remaining steps to make this tutorial more version-agnostic. Please be aware of this and do not deviate from the steps unless or until you completely understand what you are doing.
    128133 * While operating under the qemu chroot (ie on the host system) you may encounter 'qemu: Unsupported syscall'. Note that messages from QEMU about unsupported syscalls are often harmless, because typically they only appear for relatively new syscalls which QEMU hasn't implemented yet. The guest code will have a fallback path so it works on older kernels which don't implement the syscall, so a message is printed but the application still runs. So if the guest program is failing then it is quite likely to be for an entirely unrelated reason to the missing syscalls.