Skip to content
View in the app

A better way to browse. Learn more.
Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Steve Medley

Members

  • Joined

  • Last visited

View Profile Find content

Reputation Activity

  1. Like
    Steve Medley got a reaction from lafalken in More proper testing - better Armbian experience   
    Thanks. I quickly realised that was the problem when i typed help at the prompt and found the ext4load command missing.
     
    Going to download the sources next so i can build my own test images and get a bit more familiar with the build process. I have built my own Armbian images in the past for CB2, but that was before it was even called Armbian and only supported CB2 and cubietruck. A lot has changed since then
  2. Like
    Steve Medley reacted to zador.blood.stained in More proper testing - better Armbian experience   
    Ext4 support is missing in odroid-specific u-boot config - added with a patch, will need a new test image
  3. Like
    Steve Medley got a reaction from Igor in More proper testing - better Armbian experience   
    OK. I finally got to boot up the image. Got the following:
    U-Boot 2012.07 (Oct 20 2016 - 10:51:36) for Exynos5422 CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7] APLL = 800MHz, KPLL = 800MHz MPLL = 532MHz, BPLL = 825MHz Board: HardKernel ODROID DRAM: 2 GiB WARNING: Caches not enabled TrustZone Enabled BSP BL1 version: / VDD_KFC: 0x44 LDO19: 0xf2 Checking Boot Mode ... SDMMC MMC: S5P_MSHC2: 0, S5P_MSHC0: 1 MMC Device 0: 7.4 GiB MMC Device 1: 29.1 GiB MMC Device 2: MMC Device 2 not found there are pending interrupts 0x00000001 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** Unable to use mmc 0:1 for fatload ** Unknown command 'ext4load' - try 'help' Unknown command 'ext4load' - try 'help' >>> Load Boot Script from mmc 0:1 <<< ** Unable to use mmc 0:1 for fatload ** >>> Load Boot Script from mmc 0:2 <<< ** Partition 2 not valid on device 0 ** ** Unable to use mmc 0:2 for fatload ** >>> Run Default Bootcmd <<< reading kernel..device 0 Start 1263, Count 16384 MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Start 17647, Count 2048 MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK completed Bad Linux ARM zImage magic! Exynos5422 # Going to look into it a bit further...
  4. Like
    Steve Medley got a reaction from wildcat_paris in More proper testing - better Armbian experience   
    No worries. I have an XU4 currently running android on eMMC. i can throw xenial on an SD card and boot it up. i'll have a reply in about 2 hours
  5. Like
    Steve Medley got a reaction from Igor in More proper testing - better Armbian experience   
    No worries. I have an XU4 currently running android on eMMC. i can throw xenial on an SD card and boot it up. i'll have a reply in about 2 hours

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.