Difference between revisions of "Projects:Orange Pi 4 Workstation"

From Dejvino's Knowledge Base
Jump to navigation Jump to search
Line 37: Line 37:
 
#* {{IconTodo}} Image & flash an SD card
 
#* {{IconTodo}} Image & flash an SD card
 
#* {{IconTodo}} Flash updates
 
#* {{IconTodo}} Flash updates
 +
# {{IconTodo}} Build on the target device
  
 
=== Target Stage ===
 
=== Target Stage ===
 
* [[Mainline Linux on Orange Pi 4]]
 
* [[Mainline Linux on Orange Pi 4]]
 
* [[Arch Linux ARM on Orange Pi 4]]
 
* [[Arch Linux ARM on Orange Pi 4]]

Revision as of 20:58, 16 April 2020

Project: Workstation computer built using Orange Pi 4 running Linux fulfilling Goal:Technology.

Requirements

  • open source software
    • ability to build all of the components and utilities from source
  • standalone and independent
    • ability to build on the target hardware in order to be independent
  • up-to-date software
    • mainline kernel (with only a few necessary patches)
    • actively maintained distribution
  • NO binary blobs

Hardware

Details: Orange Pi 4 Hardware

  • multiple 64-bit ARM cores which provides enough horsepower for common tasks
  • 4 GB of LPDDR4 RAM is sufficient for common tasks given it will run Linux
  • 1 Gbps Ethernet & WiFi & Bluetooth for solid connectivity
  • tiny form factor frees up lots of space (compared to a standard desktop tower PC)
  • low power consumption makes this cheap to run
  • low noise levels thanks to a single slow running fan

Software

Experimental Stage

  1. Try pre-built images
  2. Try custom-built images
    • BSP Linux on Orange Pi 4: [+] collection of shell scripts useful for studying, [–] couldn't get it to boot, not very robust.
    • Armbian on Orange Pi 4: [+] generic build system, patch files applied to mainline repositories, [–] x86_64 Ubuntu build system not usable on the target device
      • Legacy kernel, standard console image: OK
      • Current kernel, minimal console image: Kernel doesn't boot
      • Current kernel (5.4.32), standard console image: ?
  3. Design a custom image-building process
  4. Build on the target device

Target Stage