Odroid u3 linux mint

Odroid U2/U3 Ubuntu 18.04 Desktop image

compressed image: md5sum: daf7312bc65e98ecfdc1b4d9fbf44f03 ubuntu-18.04-4.16.0-v7-desktop-odroid-u2-u3-20190308.img.xz

uncompressed image: md5sum: e46df26b7e08f0e1d6cb3297f91b11da ubuntu-18.04-4.16.0-v7-desktop-odroid-u2-u3-20190308.img

console:
user: root
pass: odroid

graphical UI and console:
user: odroid
pass: ubuntu1804

Please change this as soon as you can!

A xc compressed image containing an installation of Ubuntu 18.04 Desktop for the Odroid U2 or U3 (and possibly the X2, but tested only on Odroid U2 for now).

The uncompressed Size of this Image is 128GB (119 GiBiByte or exacly 127865454592 Bytes), to use it you need a microSDXC card of at least this size (I used a SanDisk Ultra R100 microSDXC 128GB Kit, UHS-I U1, A1, Class 10 (SDSQUAR-128G-GN6MA), which has exactly this size — hence the size of the .img). Burn the image onto the Card using balenaEtcher works best, no need to uncompress the image!

How came this into life?

I was looking for an image to run Ubuntu 18.04 on my Odroid U2 and found this thread, however, the offered image did not work for me (and others). So, after a while browsing the forum, I found this post, which inspired me to try the same. The result is above download.

For those, who don’t trust me or want to do it on their own (for instance, because they don’t own such a large microSD-card) I post the instructions here:

Download the minimal Ubuntu 16.04 image and install it

burn the image onto a microSD-card using dd or use balenaEtcher

log in onto your odroid using ssh root@ from your Laptop/Desktop and then paste the above script into vi , nano or whatever editor you prefer. Save the script as resize.sh

then run the script before and after a reboot:

Upgrade to Ubuntu 18.04

to upgrade to 18.04 (see also https://forum.odroid.com/viewtopic.php?f=77&t=30654&p=232918#p232918 and https://www.cyberciti.biz/faq/ubuntu-bash-do-release-upgrade-command-not-found/):

From Server to Desktop

Some additional things

For some reasons unknown to me gnome-terminal is not working, it crashes on launch. To solve this problem I just installed xterm:

When examining the first image I created in a hex editor, I found that a lot of clutter from deleted Android files was still there (which probably was a leftover of the original Odroid Android from the 16.04 image I downloaded) So I decided to remove this by first defragmenting the disk and then wiping the free disk space:

This also resulted in a smaller xz compressed image file since free space is so much easier to compress … 🙂

Источник

Установка Kali ARM на ODROID U2 и ODROID U3

ODROID U2 — это хитрая железяка без консольного вывода. Идеально, если при покупке ODROID вы также получите кабель USB UART, используемый для серийной отладки процесса загрузки. С этими словами, эта машина (на настоящее время) одна из наиболее впечатляющих по соотношению размера, мощности и доступной памяти.

ODROID-U2 и ODROID-U3 основаны на одной и той же базовой платформе, следовательно, образ U2 будет работать с U3 изменений.

Kali на ODROID U2 – Пользовательская инструкция

Если всё, что вам нужно, это установить Kali на ваш потрясающий ODROID, следуйте этой инструкции:

Возьмите хорошую быструю на 8 GB (или больше) карту microSD. Крайне рекомендуются карты Class 10.
Загрузите образ Kali Linux ODROID U2 с официального сайта.
Используйте утилиту dd для прожига этого файла на вашу карту microSD. В нашем примере мы предполагаем, что дисковое устройство расположено в /dev/sdb. Измените под ваши нужды.

Внимание! Этот процесс сотрёт вашу SD карту. Если вы выберете неправильное дисковое устройство, вы можете снести жёсткий диск вашего компьютера.

Этот процесс займёт какое-то время в зависимости от скорости вашего USB устройства и размера образа. Когда операции dd завершена, загрузите Odroid со вставленной в него microSD. Вас должно встретить приветственный экран логирования Gnome — (root / toor). Всё готово!

Решение проблем

Для решения проблем с процессом загрузки Odroid вам нужно соединить серийный UART кабель к вашему Odroid. После подсоединения кабеля, вы можете выдать следующую команду для соединения к консоле:

Источник

ODROID

Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by kwojtas » Wed Aug 01, 2018 1:04 pm

Hi, I prepared Ubuntu 18.04 image for x2 u2 and u3 boards

It contains uboot from debian repository version u-boot-exynos_2018.05+dfsg-1_armhf.deb
https://packages.debian.org/buster/armh . s/download
It should boot from sd card. If you use emmc card and it does not boot, then maybe your bootloader on emmc card is too old? In such case you can follow this instruction to update u-boot on emmc
https://angband.pl/doc/u2.txt

Linux kernel is mainline 4.17 and is compiled by myself. Config is default with few extra flags enabled for docker, qemu and serial cp210x.

Rootfs is based on xu4. Only kernel package is replaced and libc-dev.
https://wiki.odroid.com/odroid-xu4/os_i . 4/20180531

If you want to use this image for x2 board, then you should change device tree on boot partition firstly:

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by kwojtas » Wed Aug 01, 2018 1:12 pm

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by odroid » Thu Aug 02, 2018 9:22 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by moon.linux » Fri Aug 03, 2018 11:57 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by sihorton » Sat Sep 01, 2018 2:33 am

This looks excellent — would love to get docker running with a newer kernel on my u2.

I downloaded and burned the image to sd card (I don’t have emmc card), the red power light comes on but the live led does not flash even once, looking on the uart I get nothing. Have tried with 3 different sd cards and different writers so that is probably not the problem, and I burned 1604 and booted successfully using the same cards and readers.

Opening up boot.ini I see that it is checking $ and then loading files that do not exist (exynos5422-odroidxu3.dtb, but the image has exynos4412-odroidu3.dtb):

still nothing on the board, nothing on uart and the alive led does not flash. Not sure exactly what to change to get this to boot on a u2, I assume it should all be the same as u3 so if anyone has this working and maybe needed to make changes to boot.ini if you could share that with me I would be very happy!

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by moon.linux » Sat Sep 01, 2018 2:53 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by sihorton » Sat Sep 01, 2018 4:48 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by sihorton » Sat Sep 01, 2018 8:34 am

Since I do not have an emmc but only an sd card I found it easier to work with the sd card image from this post: viewtopic.php?f=77&t=30654&p=232918#p232918. I was then able to do a «do-dist-upgrade» and work through various issues to get everything up and running. I now have an odroid u2 running ubuntu 18.04.1 LTS with docker 18.06.1-ce which is very encouraging!
Thanks for the inspiration!

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by hometecky » Sun Sep 02, 2018 6:49 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by Patjutzu » Mon Sep 17, 2018 1:29 pm

Could you please describe to me exactly how I use your .img Ubuntu 18.04 Minimal OS image for X2 U2 U3
on my odroid X2 bring about my SD Card to work.
Unfortunately I can’t do anything with her statement $ mv exynos4412-odroidx2.dtb exynos.dtb or I don’t know how it’s meant because I am a Windows user.
I would be very grateful for an answer.

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tobetter » Wed Sep 19, 2018 11:30 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by Patjutzu » Wed Sep 19, 2018 10:24 pm

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by sihorton » Sat Sep 22, 2018 5:35 pm

I have attached dts and dtb files from my compile of kernel 4.18.5,

* exynos4412-odroidu3.dtb
* exynos4412-odroidx.dtb
* exynos4412-odroidx2.dtb

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by Patjutzu » Sun Sep 23, 2018 2:55 pm

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by bluemango » Thu Oct 04, 2018 5:08 pm

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by sihorton » Sat Oct 06, 2018 7:41 am

I was not able to get this image to boot on my u2. Rather I started from a different image: viewtopic.php?f=77&t=30654, that has a newer kernel than the stock one (4.16.0-v7), but it has 16.04 rather than 18.04 like this image. I was able to boot that image, and then I was able to do «do-release-upgrade» and get ubuntu to update to 18.04 from 16.04. There were a couple of problems, but I worked through them with help from https://www.nico-maas.de/?p=1491. That then left me with a newer kernel and the latest ubuntu. I was then able to build an even later kernel from that sd card.

My boot.ini has a line:

so what I am guessing is that you can swap the «exynos4412-odroidu3_4.18.5.dtb» for «exynos4412-odroidx2.dtb» from my zip and you will then get the device drivers for your board. It might be that the kernel you are booting has to be the exact same version as the .dtb, with the same kernel options, I am not certain.

There is a uart connection on my u2, hopefully on your board as well. I have a cable that connects from the board to usb using that connector, with that I am able to see the boot process even if it does not boot, it shows errors. So maybe if you try to use the uart you can see what the board is printing out. If you can see what the boot is printing out hopefully that will give a clue as to what is not working.

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by clang » Thu Oct 18, 2018 4:00 pm

Hi everyone,
I’m having some trouble getting the ubuntu 18.04 minimal os image to work on an x2 board.

I have ubuntu mate 16.04 working on this board (which is great), so while I would like the 18.04 minimal image installed I don’t won’t to break my current installation and wind up with nothing working.

I flashed the image to an SD card using dd, and followed the above directions (mv exynos4412-odroidx2.dtb exynos.dtb) but I can’t get the card to boot.
I tried booting just the card with no emmc card connected but that didn’t work (disconnected the emmc card, changed jumper lead to sd boot).
I looked at the instructions about updating u-boot on emmc, but as those relate to Odroid-U2/U3 boards, I’m not exactly sure of what to change to follow these instructions for an x2 board.
When I try booting with the emmc connected, it starts booting and then offers option for root management with the message that firmware is not where expected (?/lib/firmware or some such).
I understand that I might have to teach myself a bit to get this working and I’m happy with that.
Any help much appreciated.

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Mon Oct 29, 2018 4:16 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tve » Tue Dec 18, 2018 11:56 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Sat Dec 22, 2018 10:06 pm

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tve » Sun Dec 23, 2018 2:02 am

I’m not an expert at all this stuff, so I’m sure there are better ways to do it. But so far this has worked for me. The instructions that helped the most and that have more useful snippets if you’re compiling on the U3 itself is https://angband.pl/doc/u2.txt. The worst part of all this is that the U3 doesn’t reboot on its own, I have to manually power cycle it after it shuts down. Looks like this is a defect in the HW design.

I hope this helps!

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Mon Dec 24, 2018 1:55 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tve » Mon Dec 24, 2018 2:08 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Tue Dec 25, 2018 6:15 am

Hi again @tve, followed the instructions with a few changes because I’m doing it on the U3 itself but it wouldn’t boot.
Here’s what I did:

git clone https://git.kernel.org/pub/scm/linux/ke . stable.git
cd linux-stable
git checkout linux-4.17.y
cp . /config-4.17.0 .config
make menuconfig
make INSTALL_MOD_PATH=/tmp -j 4 bzImage modules
make INSTALL_MOD_PATH=/tmp modules_install
du -hs /tmp/lib/modules/*
SUFF=$
VERS=$
rsync arch/arm/boot/zImage /boot/vmlinuz-$VERS-$SUFF
rsync arch/arm/boot/zImage /media/boot/zImage-$VERS-$SUFF
rsync .config /boot/config-$VERS-$SUFF
rsync System.map /boot/System.map-$VERS-$SUFF
rsync -a /tmp/lib/modules/$VERS /lib/modules/$VERS-$SUFF
# make the /boot/boot.txt file with correct version and suffix
update-initramfs -c -k $VERS-$SUFF
mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n uInitrd -d /boot/initrd.img-$VERS-$SUFF /boot/uInitrd-$VERS-$SUFF
cp /boot/uInitrd-$VERS-$SUFF /media/boot/
mkimage -C none -A arm -T script -d boot.txt /media/boot/boot.scr
sync

Everything went through without any errors but it wouldn’t boot.
Any idea what I might have done wrong?
Again thanks for the help

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tve » Tue Dec 25, 2018 6:18 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Tue Dec 25, 2018 6:56 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tve » Tue Dec 25, 2018 11:56 am

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Tue Dec 25, 2018 9:57 pm

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by tve » Wed Dec 26, 2018 2:46 am

Do I assume correctly that you start by putting kwojtas’ image onto the sdcard and then test-boot to make sure it works?
Something I should have told you is to make a backup copy of boot.scr because then if the new kernel doesn’t boot you can restore boot.scr by plugging the sdcard into a laptop, that should bring you back so you can try again.

I believe the blue LED comes on pretty early in the boot process, but without serial adapter it’s really a shot in the dark. Having one is kind’a minimal requirement for all this. I forget whether you need a 1.8V one (which is harder to find) or whether a more std 3.3V works, you need to look that up.

Why don’t you post:

Re: Ubuntu 18.04 Minimal OS image for X2 U2 U3

Post by EWIuser » Wed Dec 26, 2018 3:42 am

I started over again but got stuck at
root@odroid:/boot# update-initramfs -c -k $VERS-$SUFF
update-initramfs: Generating /boot/initrd.img-4.17.19-tve
depmod: WARNING: could not open /var/tmp/mkinitramfs_o1cB9u/lib/modules/4.17.19-tve/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_o1cB9u/lib/modules/4.17.19-tve/modules.builtin: No such file or directory

Here is what I have now

/linux-stable# ls -ls /boot /media/boot
/boot:
total 84672
3004 -rw-r—r— 1 root root 3074838 Jul 30 19:06 System.map-4.17.0
3024 -rw-r—r— 1 root root 3093699 Dec 25 18:09 System.map-4.17.19-tve
4 -rw-r—r— 1 root root 526 Dec 25 17:45 boot.txt
128 -rw-r—r— 1 root root 128229 Jul 30 19:06 config-4.17.0
128 -rw-r—r— 1 root root 128377 Dec 25 18:09 config-4.17.19-tve
3420 -rw-r—r— 1 root root 3500118 May 16 2017 initrd.img-3.10.96+
7996 -rw-r—r— 1 root root 8187777 May 29 2018 initrd.img-4.14.43-138
5048 -rw-r—r— 1 root root 5167858 Jul 30 20:07 initrd.img-4.17.0
5104 -rw-r—r— 1 root root 5224390 Dec 25 18:14 initrd.img-4.17.19-tve
4028 -rw-r—r— 1 root root 4124409 Jul 3 2016 uInitrd-3.10.96-101
4036 -rw-r—r— 1 root root 4128799 Jul 7 2016 uInitrd-3.10.96-113
7996 -rw-r—r— 1 root root 8187841 May 29 2018 uInitrd-4.14.43-138
5948 -rw-r—r— 1 root root 6083682 Dec 13 2017 uInitrd-4.14.5-92
5188 -rw-r—r— 1 root root 5306244 May 11 2017 uInitrd-4.9.27-35
5188 -rw-r—r— 1 root root 5309215 May 15 2017 uInitrd-4.9.28-38
5404 -rw-r—r— 1 root root 5530194 Aug 20 2017 uInitrd-4.9.44-54
5448 -rw-r—r— 1 root root 5577959 Aug 24 2017 uInitrd-4.9.44-56
6708 -rwxr-xr-x 1 root root 6868368 Jul 30 19:06 vmlinuz-4.17.0
6872 -rwxr-xr-x 1 root root 7034592 Dec 25 18:08 vmlinuz-4.17.19-tve

/media/boot:
total 21874
10 -rwxr-xr-x 1 root root 9650 May 29 2018 boot.ini
2 -rwxr-xr-x 1 root root 753 Aug 20 2017 boot.ini.default
2 -rwxr-xr-x 1 root root 550 Jul 30 15:16 boot.scr
124 -rwxr-xr-x 1 root root 126236 Jul 30 15:17 config
54 -rwxr-xr-x 1 root root 53441 Jul 30 15:17 exynos.dtb
54 -rwxr-xr-x 1 root root 53441 Jul 30 15:16 exynos4412-odroidu3.dtb
54 -rwxr-xr-x 1 root root 53253 Jul 30 15:17 exynos4412-odroidx2.dtb
7996 -rwxr-xr-x 1 root root 8187841 May 29 2018 uInitrd
6708 -rwxr-xr-x 1 root root 6868360 Jul 30 15:17 zImage
6870 -rwxr-xr-x 1 root root 7034592 Dec 25 18:09 zImage-4.17.19-tve
root@odroid:

/linux-stable# du -s /lib/modules/$VERS-$SUFF
66492 /lib/modules/4.17.19-tve
root@odroid:

/linux-stable# cat /boot/boot.txt
setenv fdt_high «0xffffffff»

# sd card has priority over emmc
setenv bootcmd «fatload mmc 1:1 0x40008000 zImage-4.17.19-tve || fatload mmc 0:1 0x40008000 zImage-4.17.19-tve; fatload mmc 1:1 0x42000000 uInitrd-4.17.19-tve || fatload mmc 0:1 0x42000000 uInitrd-4.17.19-tve; fatload mmc 1:1 0x44000000 exynos.dtb || fatload mmc 0:1 0x44000000 exynos.dtb; bootz 0x40008000 0x42000000 0x44000000»

setenv bootargs «console=tty1 console=ttySAC1,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro mem=2047M»

I feel there is confusion about .config or config in the steps you described which might be my issue of not understanding clearly.
Here are all the steps I took:
git clone https://git.kernel.org/pub/scm/linux/ke . stable.git
cd linux-stable
git checkout linux-4.17.y
cp /boot/config-4.17.0 .config
make menuconfig

make INSTALL_MOD_PATH=/tmp -j 4 bzImage modules
make INSTALL_MOD_PATH=/tmp modules_install
du -hs /tmp/lib/modules/*

(results of du = 65M /tmp/lib/modules/4.17.19 )

SUFF=$
VERS=$
rsync arch/arm/boot/zImage /boot/vmlinuz-$VERS-$SUFF
rsync arch/arm/boot/zImage /media/boot/zImage-$VERS-$SUFF
rsync .config /boot/config-$VERS-$SUFF
rsync System.map /boot/System.map-$VERS-$SUFF
rsync -a /tmp/lib/modules/$VERS /lib/modules/$VERS-$SUFF
# make the /boot/boot.txt file with correct version and suffix
#
setenv fdt_high «0xffffffff»

setenv bootargs «console=tty1 console=ttySAC1,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro mem=2047M»

update-initramfs -c -k $VERS-$SUFF
mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n uInitrd -d /boot/initrd.img-$VERS-$SUFF /boot/uInitrd-$VERS-$SUFF
cp /boot/uInitrd-$VERS-$SUFF /media/boot/
mkimage -C none -A arm -T script -d boot.txt /media/boot/boot.scr
sync

You don’t know how much I appreciate your guidance here but nonetheless I do need to prepare for the Christmas supper so I wish you a merry Christmas and hope we’ll be able to continue this tomorrow if possible.

Источник

Odroid u3 linux mint

ODROID-U3

SD Card Creation

eMMC Module Creation

HDMI audio