ODroid XU4- v106 image - problems

Troubleshooting
1

Has any else seen these issues with the Odroid v106 img?

  1. Running with 720 edid (at least on a 1080 tv) only displays about 10 lines
  2. When performing an automated install, when the boot script performs a version check, it fails to contact the server. In trying to debug this, I found that the server was available if I wasn’t performing an automated install. So, I stuck a whiptail msgbox in the script to see what the values were. In the process of this… it didn’t fail to connect. (not sure if, during an automated install, it’s trying to connect before the network is completely up or what)
  3. the v106 img is upgrading the kernel to the same version that it boots, so there is a whiptail prompt/warning to reboot asap. useful info, but not necessary since it’s going to reboot at the end of the automated install anyhow.
  1. I was fine running in 1080 mode, so this issue didn’t bother me until I hook the board up to my 55" across the room… :frowning:
    2 & 3. these present a problem of requiring a USB keyboard to be installed to hit twice during the install. I’ve automated the installation of my bluetooth keyboard (by copying the pairing key, etc to /var/lib/bluetooth during the AutoScript run), so running 2 dongles during installation is a bit of a pain.
2

quick update…

I added the following 2 lines to the Get_Server_Version function in dietpi-update as a test and it resolved my #2 issue
(I’m sure that’s probably overkill, but I was just testing)

Get_Server_Version(){
sleep 10
ping -c 10 raw.githubusercontent.com
#Get server version file
curl -L > https://raw.githubusercontent.com/Fourdee/DietPi/"$GITBRANCH"/dietpi/server_version > > “$FILEPATH_TEMP”/server_version
if (( $? == 0 )); then
SERVER_ONLINE=1

#Get server Version info
VERSION_SERVER=$(sed -n 1p “$FILEPATH_TEMP”/server_version)
DIETPIUPDATE_VERSION_REQUIRED=$(sed -n 2p “$FILEPATH_TEMP”/server_version)

fi
}

3

Hi,

Thanks for the reports, very helpful :slight_smile:

I currently run my XU4 headless. But I will test this setting and see if we can replicate it.

  1. When performing an automated install, when the boot script performs a version check, it fails to contact the server. In trying to debug this, I found that the server was available if I wasn’t performing an automated install. So, I stuck a whiptail msgbox in the script to see what the values were. In the process of this… it didn’t fail to connect. (not sure if, during an automated install, it’s trying to connect before the network is completely up or what)

Strange. The automation runs exactly the same code during install. Can you attach your dietpi.txt with your current automation settings?

  1. the v106 img is upgrading the kernel to the same version that it boots, so there is a whiptail prompt/warning to reboot asap. useful info, but not necessary since it’s going to reboot at the end of the automated install anyhow.

I can see this being an issue with automation, i’ll take a look and see if we can force the update. Although the version claims to be the same, the kernel may contain bug fixes from Meveric.

4

Git Tickets:

XU4 | Automation | User input required for kernel update prompt
https://github.com/Fourdee/DietPi/issues/185

XU4 720p boot only displays 10lines
https://github.com/Fourdee/DietPi/issues/184

5

Hey Fourdee,

I apologize for the delayed response. This week was crazy.
I saw that you’ve already found a fix for the kernel upgrade issue and that the video issue is a known kernel bug. thanks!

Here’s a copy of my dietpi.txt file for the other issue…
(I had to zip it… the forum wouldn’t allow a .txt file)
dietpi.zip (3.04 KB)

6

No worries, i know the feeling :slight_smile:

The automation kernel update will be resolved in next released v109. As for the 720p issue, you’ll have to use a workaround for now (eg: 1080p), until its resolved.

7

just an update on issue #2.

I just copied the same dietpi.txt to a RPi2 install and I’m getting a similar error… github.com is not reachable.

Again, when I tweaked the dietpi-update script to add a

sleep 10
ping -c 10 raw.githubusercontent.com

before it attempts to pull the server_version file, it works.

It definitely seems like it’s trying to access the network before it’s fully initialized.

8

Thanks rhkean,

I’ll run some automation tests today and see if we can get this resolved.

9

Yep, seems you were spot on +1 :slight_smile:

I’ve created a GitTicket for this. You can also track its progress here: https://github.com/Fourdee/DietPi/issues/197

10

Ok, found a workaround and I would like you to test/verify its resolved.

Once you have finished writing your automated image, and prior to powering on the device. Please do the following:

  • open /boot/dietpi/dietpi-update
  • Inside the Get_Server_Version function, change the following line (add a -k to curl)
curl -k -L https://raw.githubusercontent.com/Fourdee/DietPi/"$GITBRANCH"/dietpi/server_version > "$FILEPATH_TEMP"/server_version
  • Save and power on.

Let me know if the issue reoccurs.

11

Sorry that I missed your post yesterday.

I will test this when I get home in about 3 hours on the RPi2.
The Odroid may take me a little longer. It’s in use, so I’ll have to slip in the reboot while everyone’s eating dinner… :smiley:

-rob

P.S.
I’ve got to ask, though… How is the --insecure option going to fix things?

12

tested on the RPi2 and the Odroid XU4…

both worked perfectly!!!


I should have thought to test the

DEBIAN_FRONTEND='noninteractive' apt-get upgrade -y

fix before I gave the server back to the house, but I forgot.

I’ll try later tonight

thanks

13

ha!

brain-fart!

I tried to test the noninteractive fix by editing the dietpi-software script, but since I also applied the curl -k fix, the automation downloaded the new v108 update and overwrote my manual patch… face palm!

switched to the testing branch, though, and it worked like a charm.

I think I saw it throw an error during the “running apt simulation” but I’m not sure what it was as it scrolled by too fast.

The rest (with my v106 dietpi.txt file) seems to be running well. I can’t wait to test out this new version. I’m glad to see lighttpd on here, since apache and nginx are quite a lot for these little boards.

UPDATE…
reran the automated install… no errors.
I did add the following to the end of my automation script, to upgrade the kernel
apt-get install linux-headers-armhf-odroid-xu3 linux-image-armhf-odroid-xu3


(since this fix causes the apt-get upgrade command to skip these packages and upgrading the kernel from 3.10.92+ to 3.10.96+ clears up a couple kernel module load errors on boot)

by that point, my bluetooth keyboard should be loaded if I need it, but I don’t think I will… will follow up again once this install finishes.

14

Hi Rhkean,

Thanks for the update. I’ve seen your replies on the Git tickets, lets continue discussions there: https://github.com/Fourdee/DietPi/issues/197