odroid XU4 boot error after kernel upgrade

Having issues with your DietPi installation, or, found a bug? Post it here.
Allamur
Posts: 30
Joined: Mon Jun 26, 2017 2:58 pm

odroid XU4 boot error after kernel upgrade

Post by Allamur »

well I'm quiet unlucky with my XU4 :(

Using v157 and upgraded the kernel to 3.10.106+ (I think. I'm using Yunohost with it and it upgraded everything automatically)
Now the XU4 doesn't boot anymore
Exchanging the boot.ini, a recommendation from fourdee on twitter, with this: https://raw.githubusercontent.com/Fourd ... ot_xu4.ini
wasn't successful.

I already had a similar issue two months ago and replaced a number in the boot.ini file and after another try to boot the odroid, I reverted that change.
Both didn't help
here the topic: http://dietpi.com/phpbb/viewtopic.php?f ... t=xu4+boot

I'm pretty sure, that another uboot-upgrade is the root cause of this issue. I had that package a long time marked as hold (apt), but tried it two or three weeks ago and everything went fine after upgrading it - maybe there was something I missed.

Connecting the XU4 via HDMI doesn't output anything, so I cannot share a bootlog or similar.

And no - I don't have a backup. No backup - no mercy - I know, but hopefully there's a fix I can try before starting from scratch :)
Allamur
Posts: 30
Joined: Mon Jun 26, 2017 2:58 pm

Re: odroid XU4 boot error after kernel upgrade

Post by Allamur »

Shameless selfbump - does nobody have an idea?
User avatar
k-plan
Posts: 416
Joined: Sun Feb 28, 2016 5:28 pm

Re: odroid XU4 boot error after kernel upgrade

Post by k-plan »

Allamur wrote:Shameless selfbump - does nobody have an idea?
http://dietpi.com/phpbb/viewtopic.php?t=2425#p9428
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal and Bitcoin.
Allamur
Posts: 30
Joined: Mon Jun 26, 2017 2:58 pm

Re: odroid XU4 boot error after kernel upgrade

Post by Allamur »

thank you for your hint, but this time this doesn't work - that was the fix mentioned in my first post - second link...
The behavior doesn't change and it's still hanging. (the fan is constantly rotating, the harddrive leds are blinking for 10 sec or so, after that they shutdown, the blue and yellow leds on the side are blinking too for a bit)

I've to add, that I have a cloudshell 2 with two harddrives in a RAID1, booting from the SD but the filesystem itself is copied onto that harddrives.
Do you think I have to change there something as well?
Maybe this is the reason, why I can't find the file xynos5422-odroidxu4.dtb in boot - but the odroidxu3.dtb isn't on the SDcard too.

Here's my boot.ini located on boot/boot.ini

Code: Select all


ODROIDXU-UBOOT-CONFIG

# U-Boot Parameters
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"

# Mac address configuration
setenv macaddr "00:1e:06:61:7a:72"

#------------------------------------------------------------------------------------------------------
# Basic Ubuntu Setup. Don't touch unless you know what you are doing.
# --------------------------------
setenv bootrootfs "console=tty1 root=UUID=a4f12232-1670-43f4-8eca-49bfbe4d01ee rootwait ro fsck.repair=yes"

# --- Screen Configuration for HDMI --- #
setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080.bin"

# --- HDMI / DVI Mode Selection ---
# ------------------------------------------
# - HDMI Mode
setenv vout "hdmi"
# - DVI Mode (disables sound over HDMI as per DVI compat)
# setenv vout "dvi"

# --- CPU Governor Setup ---
# - DietPi will override this setting to user configured in dietpi-config > Performance Options > CPU gov.
setenv governor "performance"

#------------------------------------------------------------------------------
#
# HDMI Hot Plug detection
#
#------------------------------------------------------------------------------
#
# Forces the HDMI subsystem to ignore the check if the cable is connected or
# not.
# false : disable the detection and force it as connected.
# true : let cable, board and monitor decide the connection status.
#
# default: true
#
#------------------------------------------------------------------------------
setenv HPD "true"

#------------------------------------------------------------------------------
#
#  TMDS data amplitude control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  tx_amp_lvl : 0 = 760 mVdiff(Min), 31 = 1380 mVdiff(Max)
#
#  Hardkernel default hdmi_tx_amp_lvl = 31(1380 mVdiff);
#------------------------------------------------------------------------------
setenv hdmi_tx_amp_lvl  "31"

#------------------------------------------------------------------------------
#
#  TMDS data amplitude fine control for each channel.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  tx_lvl : 0 = 0 mVdiff(Min), 3 = 60 mVdiff(Max)
#
#  Hardkernel default
#      hdmi_tx_lvl_ch0 = 3, hdmi_tx_lvl_ch1 = 3, hdmi_tx_lvl_ch2 = 3,
#------------------------------------------------------------------------------
setenv hdmi_tx_lvl_ch0      "3"
setenv hdmi_tx_lvl_ch1      "3"
setenv hdmi_tx_lvl_ch2      "3"

#------------------------------------------------------------------------------
#
#  TMDS data pre-emphasis level control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to -0.45dB emphasis level except for 1
#  tx_emp_lvl : 0 = 0 db(Min), 1 = -0.25 db, 2 = 0.7 db, 15 = -7.45 db(Max)
#
#  Hardkernel default hdmi_tx_emp_lvl = 6 (-2.50 db);
#------------------------------------------------------------------------------
setenv hdmi_tx_emp_lvl      "6"

#------------------------------------------------------------------------------
#
#  TMDS clock amplitude control.
#
#------------------------------------------------------------------------------
#
#  1LSB corresponds to 20 mVdiff amplitude level.
#  clk_amp_lvl : 0 = 790 mVdiff(Min), 31 = 1410 mVdiff(Max)
#
#  Hardkernel default hdmi_clk_amp_lvl = 31 (1410 mVdiff)
#------------------------------------------------------------------------------
setenv hdmi_clk_amp_lvl     "31"

#------------------------------------------------------------------------------
#
#  TMDS data source termination resistor control.
#
#------------------------------------------------------------------------------
#
#  tx_res :
#      0 = Source Termination OFF(Min), 1 = 200 ohm, 2 = 300 ohm, 3 = 120 ohm(Max)
#
#  Hardkernrel default hdmi_tx_res = 0 (Source Termination OFF)
#------------------------------------------------------------------------------
setenv hdmi_tx_res      "0"

#------------------------------------------------------------------------------

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}"

# Load kernel, initrd and dtb in that sequence
fatload mmc 0:1 0x40008000 zImage
fatload mmc 0:1 0x42000000 uInitrd
fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb

# set FDT address
fdt addr 0x44000000

if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi

# final boot args
setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control} ${hid_quirks}"
# drm.debug=0xff"
# Boot the board
bootz 0x40008000 0x42000000 0x44000000

PorterDon
Posts: 19
Joined: Tue May 23, 2017 4:53 pm
Location: Wang Nam Yen, Thailand

Re: odroid XU4 boot error after kernel upgrade

Post by PorterDon »

Something appears to be very wrong in DietPi XU4 world. I tried all day yesterday, using 2 different boards, to download the latest DietPi image and boot up. Absolutely no luck doing something I've done dozens of times before. The board never powered off as it was supposed to, and the blue light never turned off as expected. Both red and blue lights blinked as well as the ethernet yellow lights but no love. Nothing ever appeared on my hdmi monitor except for repeated occasional flashing on/off. After switching every conceivable component (cables, monitor, SDs, checking voltages, trying emmc, etc.) I have gotten nowhere. Thinking maybe something in my environment here was a problem, I tried the C2, a Pine 64 and a Pi 3 -- with no boot problems.

I also had no xynos5422-odroidxu4.dtb in boot. In Allamur's example below he also didn't show that file in his boot, but it appeared in his boot.ini?

We need some assistance here soon please.
Allamur
Posts: 30
Joined: Mon Jun 26, 2017 2:58 pm

Re: odroid XU4 boot error after kernel upgrade

Post by Allamur »

PorterDon wrote:Something appears to be very wrong in DietPi XU4 world. I tried all day yesterday, using 2 different boards, to download the latest DietPi image and boot up. Absolutely no luck doing something I've done dozens of times before. The board never powered off as it was supposed to, and the blue light never turned off as expected. Both red and blue lights blinked as well as the ethernet yellow lights but no love. Nothing ever appeared on my hdmi monitor except for repeated occasional flashing on/off. After switching every conceivable component (cables, monitor, SDs, checking voltages, trying emmc, etc.) I have gotten nowhere. Thinking maybe something in my environment here was a problem, I tried the C2, a Pine 64 and a Pi 3 -- with no boot problems.

I also had no xynos5422-odroidxu4.dtb in boot. In Allamur's example below he also didn't show that file in his boot, but it appeared in his boot.ini?

We need some assistance here soon please.
Have you tried the boot.ini I've linked to in post 1?
Does it work for you?
PorterDon
Posts: 19
Joined: Tue May 23, 2017 4:53 pm
Location: Wang Nam Yen, Thailand

Re: odroid XU4 boot error after kernel upgrade

Post by PorterDon »

I just did. No luck (after waiting the obligatory 5 minutes). Now I am going to go into dietpi/dietpi-config and make the suitable changes there and try. I wanted to do only the root.ini substitution first. Give me 10 minutes...
PorterDon
Posts: 19
Joined: Tue May 23, 2017 4:53 pm
Location: Wang Nam Yen, Thailand

Re: odroid XU4 boot error after kernel upgrade

Post by PorterDon »

Umm, I think that is the wrong config.file :oops: It appears that gets generated when the user runs dietpi-config program and is referenced upon reboot. So I am redirecting myself to the boot level config (.txt).... Let's hang in here together until we, one way or another, get our XU4s and my HC1 working again. BTW, I am in Thailand, and you?
Last edited by PorterDon on Sun Nov 12, 2017 3:41 pm, edited 1 time in total.
PorterDon
Posts: 19
Joined: Tue May 23, 2017 4:53 pm
Location: Wang Nam Yen, Thailand

Re: odroid XU4 boot error after kernel upgrade

Post by PorterDon »

Well, another day of getting nowhere. :( Fourdee PLS give us a hand! Or whomever! This isn't any fun anymore.
Allamur
Posts: 30
Joined: Mon Jun 26, 2017 2:58 pm

Re: odroid XU4 boot error after kernel upgrade

Post by Allamur »

Does anybody have a working installation?
This may be a way to find out what's wrong with ours.
Post Reply