Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    13612

  • Joined

  • Last visited

 Content Type 

Posts posted by Igor

    Odroid XU4 - Ubuntu Xenial doesn't run on eMMC

    in Odroid XU4

    Posted

    @Nerten

     

    This does not look to be Armbian boot, at least no recent.

     

    This is how it looks like on SD card:

     

     

     

    U-Boot 2012.07 (Feb 06 2017 - 16:16:49) 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: 29.8 GiB
MMC Device 1: [ERROR] response timeout error : 00000104 cmd 1
Card did not respond to voltage select!
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 
there are pending interrupts 0x00000001

** Unable to use mmc 0:1 for fatload **
Loading file "/boot/boot.ini" from mmc device 0:1 xxa1
9509 bytes read
Loading boot.ini from ext4 0:1
Find boot.ini file from FAT/Ext4 Area!!
boot.ini command = setenv rootdev "/dev/mmcblk0p1"
boot.ini command = setenv initrd_high "0xffffffff"
boot.ini command = setenv fdt_high "0xffffffff"
boot.ini command = setenv macaddr "00:1e:06:61:7a:55
boot.ini command = setenv bootrootfs "console=tty1 loglevel=1 root=${rootdev} rootwait ro fsck.repair=yes"
boot.ini command = setenv vout "hdmi"
boot.ini command = setenv cecenable "false" # false or true
boot.ini command = setenv governor "performance"
boot.ini command = setenv HPD "true"
boot.ini command = setenv hdmi_tx_amp_lvl  "31"
boot.ini command = setenv hdmi_tx_lvl_ch0      "3"
boot.ini command = setenv hdmi_tx_lvl_ch1      "3"
boot.ini command = setenv hdmi_tx_lvl_ch2      "3"
boot.ini command = setenv hdmi_tx_emp_lvl      "6"
boot.ini command = setenv hdmi_clk_amp_lvl     "31"
boot.ini command = setenv hdmi_tx_res      "0"
boot.ini command = setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}"
boot.ini command = ext4load mmc 0:1 0x40008000 /boot/zImage || fatload mmc 0:1 0x40008000 zImage || ext4load mmc 0:1 0x40008000 zImage
Loading file "/boot/zImage" from mmc device 0:1 xxa1
3392352 bytes read
boot.ini command = ext4load mmc 0:1 0x42000000 /boot/uInitrd || fatload mmc 0:1 0x42000000 uInitrd || ext4load mmc 0:1 0x42000000 uInitrd
Loading file "/boot/uInitrd" from mmc device 0:1 xxa1
6351654 bytes read
boot.ini command = ext4load mmc 0:1 0x44000000 /boot/dtb/exynos5422-odroidxu3.dtb || fatload mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb || ext4load mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb
Loading file "/boot/dtb/exynos5422-odroidxu3.dtb" from mmc device 0:1 xxa1
52006 bytes read
boot.ini command = fdt addr 0x44000000
boot.ini command = if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi
boot.ini command = setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control} ${extraargs}"
boot.ini command = bootz 0x40008000 0x42000000 0x44000000
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6351590 Bytes = 6.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
## Flattened Device Tree blob at 44000000
   Booting using the fdt blob at 0x44000000
   Using Device Tree in place at 44000000, end 4400fb25

Starting kernel ...

     

     

    I need bootlog from any of those images:

     

    https://www.armbian.com/odroid-xu4

     

    written on eMMC. Well, in worse case I'll need to get eMMC and see what's going on :(

    0

    How to change motd?

    in Allwinner sunxi

    Posted

    Result:  Editing /etc/motd now does the right thing - and my system no longer hangs for 30 seconds upon login simply to produce a colour ASCII art banner that tells me what CPU I'm running and what IP I'm logging in from.  

     

    None of mentioned thing eats much time., login takes around 1-2 seconds on an fully booted system. Measured on old A20 board ... (only) when system still loads, this can takes 10s or more.

    0

    Status of mainline kernel?

    in Allwinner sunxi

    Posted

    So, for now it's better to still use the old 3.x kernel?

     

    Now it depends of the use scenario. Old kernel is also not perfect, has bugs and ... it's old, general support is fading.

     

    Mainline kernel is still considered development with H3 chips ... so I would not stand on neither side, while I would recommend mainline kernel for older Allwinner chips, A10 and A20. There, it's clearly a better choice in most use cases, instead of old stock kernel. Soon, here (H3, H5, A64, ...) it will be the same.

    0

    Odroid XU4 - Ubuntu Xenial doesn't run on eMMC

    in Odroid XU4

    Posted

    I guess this is the reason why my XU4 stopped working suddenly (using legacy kernel). Have been running it for long time with no problems, but after updating the kernel yesterday my XU4 server does not boot anymore. Also using original 64GB eMMC from Hardkernel.

     

    Board lights up the red led and fan starts spinning, but the display port does not give any output (HDMI).

    I guess you also doesn't have serial console? We would really like to fix this, instead going back to older schema.

    0

    What's needed to upgrade Orange Pi 2E+ from legacy?

    in Advanced users - Development

    Posted

    If I want to try mainline kernel on my opi+2e what do u recommend?

    Basically I am using my opi for NAS - nextcloud

    And I want latest kernel for docker to work.

    Please recommend me mainline for NAS- nextcloud and docker

     

    Thanks in adv.

    If you want to try, just go ahead, but if it doesn't work you are on your own - pleads for help will be ignored. That's the main difference between supported and unsupported board / kernel.

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept