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.

suchende

Members
  • Joined

Reputation Activity

  1. Like
    suchende got a reaction from balbes150 in Odroid C1 (S805)   
    Works like charm.
    logfile_odroid_2.log
     
  2. Like
    suchende got a reaction from balbes150 in Odroid C1 (S805)   
    Booting using the fdt blob at 0x11800000 Loading Kernel Image ... OK OK uboot time: 5690452 us. Using machid 0xf81 from environment faild to get aml_reserved_end address the default relocate ramdisk and fdt address-relocate_addr: 0x20000000 Loading Device Tree to 1fff6000, end 1ffff038 ... OK libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Starting kernel ... [ 0.183645] lima d00c0000.gpu: IRQ ppmmu2 not found [ 0.183687] lima d00c0000.gpu: IRQ ppmmu3 not found [ 0.187786] lima d00c0000.gpu: IRQ ppmmu4 not found [ 0.192637] lima d00c0000.gpu: IRQ ppmmu5 not found [ 0.197498] lima d00c0000.gpu: IRQ ppmmu6 not found [ 0.202360] lima d00c0000.gpu: IRQ ppmmu7 not found [ 0.207403] lima d00c0000.gpu: IRQ pp2 not found [ 0.211828] lima d00c0000.gpu: IRQ pp3 not found [ 0.216428] lima d00c0000.gpu: IRQ pp4 not found [ 0.221030] lima d00c0000.gpu: IRQ pp5 not found [ 0.225632] lima d00c0000.gpu: IRQ pp6 not found [ 0.230235] lima d00c0000.gpu: IRQ pp7 not found [ 0.235440] debugfs: Directory 'd00c0000.gpu-mali' with parent 'VDDEE' already present! [ 0.262215] dummy-irq: no IRQ given. Use irq=N [ 0.264896] mtdoops: mtd device (mtddev=name/number) must be supplied [ 0.289184] remoteproc remoteproc0: request_firmware failed: -2 [ 0.289939] no UART detected at 0x1 [ 0.462107] meson-drm d0100000.vpu: meson_vclk_setup(1, 148500, 148500, 148500, 0) [ 0.769930] meson-mx-ao-arc-firmware ao-arc-firmware: Failed to request mbox channel #0 [ �QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1; -----------------------------------------------3C0001 S/N : HKC1CC0349CD6833 0x0000009f check SD_boot_type:0x1 card_type:0x1 Loading U-boot...success. U-boot-00000-g3b0181fd0a(odroidc@3b0181fd) (Jul 17 2018 - 18:49:05) DRAM: 1 GiB relocation Offset is: 2ff20000 MMC: SDCARD: 0, eMMC: 1 IR init is done! vpu clk_level = 3 set vpu clk: 182150000Hz, readback: 182150000Hz(0x701) mode = 6 vic = 4 set HDMI vic: 4 mode is: 6 viu chan = 1 config HPLL config HPLL done reconfig packet setting done MMC read: dev # 0, block # 33984, count 12288 ... 12288 blocks read: OK There is no valid bmp file at the given address ============================================================ Vendor: Man 035344 Snr 70732735 Rev: 8.0 Prod: SC16G Type: Removable Hard Disk Capacity: 15193.5 MB = 14.8 GB (31116288 x 512) ------------------------------------------------------------ Partition Start Sector Num Sectors Type 1 32768 1048576 c 2 1081344 30034944 83 ============================================================ Net: Meson_Ethernet init suspend firmware done. (ret:0) Hit Enter key to stop autoboot -- : 0 exit abortboot: 0 reading boot.ini 662 bytes read Loading boot.ini from mmc0:1 (vfat) Executing the script... setenv env_addr "0x11400000" setenv dtb_addr "0x11800000" setenv kernel_addr "0x14000000" setenv boot_start bootm ${kernel_addr} - ${dtb_addr} video dev open 1080P mode = 8 vic = 16 set HDMI vic: 16 mode is: 8 viu chan = 1 config HPLL config HPLL done reconfig packet setting done if fatload mmc 0 ${env_addr} uEnv.txt; then env import -t ${env_addr} ${filesize}; setenv bootargs ${APPEND}; else exit; fi; if fatload mmc 0 ${kernel_addr} ${LINUX}; then if fatload mmc 0 ${dtb_addr} ${FDT}; then run boot_start; fi; fi; reading uEnv.txt 171 bytes read reading /KERNEL 12837304 bytes read reading /dtb/amlogic/meson8b-odroidc1.dtb 24633 bytes read ## Booting kernel from Legacy Image at 14000000 ... Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 12837240 Bytes = 12.2 MiB Load Address: 00208000 Entry Point: 00208000 Verifying Checksum ... OK ## Flattened Device Tree blob at 11800000 Booting using the fdt blob at 0x11800000 Loading Kernel Image ... OK OK uboot time: 5584013 us. Using machid 0xf81 from environment faild to get aml_reserved_end address the default relocate ramdisk and fdt address-relocate_addr: 0x20000000 Loading Device Tree to 1fff6000, end 1ffff038 ... OK libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Starting kernel ... [ 0.186405] lima d00c0000.gpu: IRQ ppmmu2 not found [ 0.186448] lima d00c0000.gpu: IRQ ppmmu3 not found [ 0.190548] lima d00c0000.gpu: IRQ ppmmu4 not found [ 0.195402] lima d00c0000.gpu: IRQ ppmmu5 not found [ 0.200259] lima d00c0000.gpu: IRQ ppmmu6 not found [ 0.205121] lima d00c0000.gpu: IRQ ppmmu7 not found [ 0.210140] lima d00c0000.gpu: IRQ pp2 not found [ 0.214589] lima d00c0000.gpu: IRQ pp3 not found [ 0.219189] lima d00c0000.gpu: IRQ pp4 not found [ 0.223791] lima d00c0000.gpu: IRQ pp5 not found [ 0.228393] lima d00c0000.gpu: IRQ pp6 not found [ 0.232995] lima d00c0000.gpu: IRQ pp7 not found [ 0.238201] debugfs: Directory 'd00c0000.gpu-mali' with parent 'VDDEE' already present! [ 0.264890] dummy-irq: no IRQ given. Use irq=N [ 0.267625] mtdoops: mtd device (mtddev=name/number) must be supplied [ 0.289609] remoteproc remoteproc0: request_firmware failed: -2 [ 0.292283] no UART detected at 0x1 [ 0.460748] meson-drm d0100000.vpu: meson_vclk_setup(1, 148500, 148500, 148500, 0) [ 0.780460] meson-mx-ao-arc-firmware ao-arc-firmware: Failed to request mbox channel #0 That is the boot log from libreelec. So far the systems boots up and show the kodi UI. I will test the armbian image at the weekend.

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.