Ubuntu 20.04 (Focal Fossa)

[CoolGames]

@CoolGames, well...I would try to run Ubuntu Studio sometime soon. It looks a bit new for me...Are you trying to use Ubuntu Studio on ODROID-C4 and ODROID-N2 both?

I only have N2 !

Also Keyboard is mistyping and HDTV HDMI loses sync when logout to greeter requiring numerous switch back and forth between inputs.

I have time in seconds on panel bar to show if hung or not responding.
I can recover without rebooting by using F1 command line to restart lightdm.
Also would login ssh to do same while watching display for ominous behavior.

I am using Chromium-browser (because of sync for fast recovery after re-flash) in XFCE4 when it happens.

I just switched to Ubuntu with Wayland to see if it has these artifacts.
Definitely usable but not reliable.

I will begin to explore sequence from boot to headphone jack selected as output in panel mixer this week.

I assume the DTB is incorrect for ALSA sub system for all three outputs as it was in 18.04 lts with mate.
I copied the 18.04 mate img to mount and explore files to compare.

First indication is dmesg with (-22) Invalid arguments.

[10398.064731] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: can't set i2s-hifi hw params: -22
[10398.064741] axg-sound-card sound: ASoC: PRE_PMU: be.dai-link-4-playback event failed: -22
[10398.089802] hdmi-audio-codec hdmi-audio-codec.4.auto: Not able to map channels to speakers (-22)
[10398.089817] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: can't set i2s-hifi hw params: -22
[10398.089826] axg-sound-card sound: ASoC: PRE_PMU: be.dai-link-4-playback event failed: -22

Pulse Audio seems happy so assume the ALSA is culprit.
I can see and select TB 450 headphones.

Print Screen to clipboard then 50% to make smaller for upload viewing.

PrintScreen.5.png (128.38 KiB) Viewed 5073 times

Code: Select all

$ systemctl --user status pulseaudio
● pulseaudio.service - Sound Service
     Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2020-05-09 17:18:19 EDT; 22min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 33014 (pulseaudio)
     CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
             └─33014 /usr/bin/pulseaudio --daemonize=no --log-target=journal

May 09 17:18:18 cooldroidn2 systemd[32554]: Starting Sound Service...
May 09 17:18:19 cooldroidn2 systemd[32554]: Started Sound Service.

[emk2203]

I only have N2 !

This confuses the heck out of me. Why is this in the Odroid C4 forum then?

It is not helpful to read about another board's issues when trying to see what is important for the board the forum was intended for.

[CoolGames]

I only have N2 !

This confuses the heck out of me. Why is this in the Odroid C4 forum then?

It is not helpful to read about another board's issues when trying to see what is important for the board the forum was intended for.

Even less helpful when same people are working on both simultaneously and one succeeds and the other fails.
Sometimes the fix comes by another's efforts.

Also, C4 is newer product and has same early issues that N2 sees daily.
Please, don't be confused but be looking at where there is related effort to bring completeness to the chart of solution.

Look at note 20 and 21...
Odroid Ubuntu 20.04 with sound and video acceleration.
Pointing to knowledge when developers may be not reading deemed unrelated forums.

[tobetter]

Linux kernel 5.7-rc5 (20200511)

• Linux kernel is updated to Linux kernel 5.7-rc5 and new CPU frequencies, 2.016GHz and 2.100GHz, are appeneded

In order to apply new CPU frequencies, please do follow up the commands.

Code: Select all

$ sudo rm -f /etc/default/cpufrequtils
$ sudo apt update
$ sudo apt -y upgrade
$ sudo reboot

After rebooting, ODROID-C4 has new CPU frequencies up to 2.1GHz, previously it was 1.908GHz. But 2.1GHz is the very edge clock that could cause to boot failure or unexpected system halt anytime, especially when using the performance governor rather than ondemand.

Code: Select all

$ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies 
100000 250000 500000 666666 1000000 1200000 1404000 1500000 1608000 1704000 1800000 1908000 2016000 2100000

Therefore, this update limits the maximum frequency as 2.016MHz that is specified in the file /etc/default/cpufrequtils.

Code: Select all

$ cat /etc/default/cpufrequtils 
GOVERNOR=performance
MIN_SPEED="1000MHZ"
MAX_SPEED="2016MHZ"

You can change the value of MAX_SPEED="2016MHZ" to MAX_SPEED="2100MHZ" and apply this change with the command sudo /etc/init.d/cpufrequtils restart or reboot. /sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq will show you the maximum clock applied.

Code: Select all

$ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq 
2100000

@hominoid made a great thermal test with ODROID-C4 and compare with other ODROID boards. I very much appreciate the efforts.
viewtopic.php?p=292082#p292082

Again, you can set 2.1GHz as an overclocking frequency and it may or may not work with your ODROID-C4.
Enjoy!!

[erg]

Is there an easy way to get the rtl8812au usb wifi dongle working? I don't see it listed with ``ip addr list`` and I tried https://github.com/gordboy/rtl8812au-5.6.4.2 but it's not working yet. Also there's no networking icon in the top right, how do I enable that?

Some commands that show the device/drivers:

Code: Select all

➜  ~ inxi -nx
Network:   Device-1: meson-axg-dwmac driver: meson8b_dwmac v: N/A port: N/A bus ID: N/A 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:1e:06:48:0a:6d 
           Device-2: Realtek RTL8811AU 802.11a/b/g/n/ac WLAN Adapter type: USB 
           driver: usb-network bus ID: 1-1.1:3 

➜  ~ dkms status
mali-bifrost, 24.0+202005011205~focal, 5.7.0-odroid-arm64, aarch64: installed
rtl8812au, 5.7.0, 5.7.0-odroid-arm64, aarch64: installed (WARNING! Diff between built and installed module!)

➜  ~ apt search rtl8812
Sorting... Done
Full Text Search... Done
rtl8812au-dkms/focal,now 4.3.8.12175.20140902+dfsg-0ubuntu12 all [installed]
  dkms source for the r8812au network driver

Code: Select all

➜  ~ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:1e:06:48:0a:6d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.120/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 84852sec preferred_lft 84852sec
    inet6 fe80::21e:6ff:fe48:a6d/64 scope link 
       valid_lft forever preferred_lft forever

I'm kind of just trying stuff.

[alansrobotlab]

Linux kernel 5.7-rc5 (20200511)

• Linux kernel is updated to Linux kernel 5.7-rc5 and new CPU frequencies, 2.016GHz and 2.100GHz, are appeneded

Sounds like fun! Do you know when the update will hit the .kr repositories? I'm not seeing the update through apt yet.

Alan

[tobetter]

Linux kernel 5.7-rc5 (20200511)

• Linux kernel is updated to Linux kernel 5.7-rc5 and new CPU frequencies, 2.016GHz and 2.100GHz, are appeneded

Sounds like fun! Do you know when the update will hit the .kr repositories? I'm not seeing the update through apt yet.

Alan

It's already uploaded. Did you try sudo apt update?
http://ppa.linuxfactory.or.kr/pool/main ... _arm64.deb

[alansrobotlab]

It's already uploaded. Did you try sudo apt update?
http://ppa.linuxfactory.or.kr/pool/main ... _arm64.deb

Thanks! I don't understand why, but reapplying the .deb worked.
Before that I double checked and you're right, synaptic insisted that rc5 was already installed, but then the timestamps in /boot were from yesterday. Weird.

Works a charm, now for some burn-in tests.

Thank you so much!

Code: Select all

odroid@focal:~$ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
100000 250000 500000 666666 1000000 1200000 1404000 1500000 1608000 1704000 1800000 1908000 2016000 2100000

Alan

[tobetter]

It's already uploaded. Did you try sudo apt update?
http://ppa.linuxfactory.or.kr/pool/main ... _arm64.deb

Thanks! I don't understand why, but reapplying the .deb worked.
Before that I double checked and you're right, synaptic insisted that rc5 was already installed, but then the timestamps in /boot were from yesterday. Weird.

Works a charm, now for some burn-in tests.

Thank you so much!

Code: Select all

odroid@focal:~$ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
100000 250000 500000 666666 1000000 1200000 1404000 1500000 1608000 1704000 1800000 1908000 2016000 2100000

Alan

Ok, good luck!!

[miskol]

Can we get more? Like 2,4GHz ?
Qualcomm with A55 can get 2,4GHz without any problem

[odroidn2user]

It's already uploaded. Did you try sudo apt update?
http://ppa.linuxfactory.or.kr/pool/main ... _arm64.deb

Thanks! I don't understand why, but reapplying the .deb worked.
Before that I double checked and you're right, synaptic insisted that rc5 was already installed, but then the timestamps in /boot were from yesterday. Weird.

Works a charm, now for some burn-in tests.

Thank you so much!

Code: Select all

odroid@focal:~$ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
100000 250000 500000 666666 1000000 1200000 1404000 1500000 1608000 1704000 1800000 1908000 2016000 2100000

Alan

Ok, good luck!!

I did a normal apt update / apt upgrade routine, and got the same result with 210000.
With this as well:

Code: Select all

$ cat /etc/default/cpufrequtils 
GOVERNOR=performance
MIN_SPEED="1000MHZ"
MAX_SPEED="2016MHZ"

So it seems no special tricks are required to benefit from these recent updates!
Many thanks, this image rocks!

Any ideas / leads on solving the green line yet?

[hominoid]

I'm trying to compile the 5.7.0-RC5 kernel to do some further testing and ran into a few issues. Am I using the right git, are any patches needed and Is there a special script you use, or in other words, where is my mistake?

Code: Select all

git clone --depth 1 https://github.com/tobetter/linux.git -b odroid-5.7.y
cd linux

Edit ~/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts

Code: Select all

&cpu_opp_table {
	opp-2016000000 {
		opp-hz = /bits/ 64 <2016000000>;
		opp-microvolt = <1000000>;
	};
	opp-2100000000 {
		opp-hz = /bits/ 64 <2100000000>;
		opp-microvolt = <1022000>;
	};
	opp-2200000000 {
		opp-hz = /bits/ 64 <2200000000>;
		opp-microvolt = <1022000>;

Code: Select all

make oldconfig
make -j4
sudo make modules_install
sudo make install

Code: Select all

sh ./arch/arm64/boot/install.sh 5.7.0-rc5+ \
arch/arm64/boot/Image System.map "/boot"
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc5+ /boot/vmlinuz-5.7.0-rc5+
run-parts: executing /etc/kernel/postinst.d/dkms 5.7.0-rc5+ /boot/vmlinuz-5.7.0-rc5+
 * dkms: running auto installation service for kernel 5.7.0-rc5+                                                                               
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...(bad exit status: 2)
make -j4 KERNELRELEASE=5.7.0-rc5+ -C drivers/gpu/arm/midgard SCONS_CFLAGS='-DCONFIG_MALI_MIDGARD=m -DCONFIG_MALI_DEVFREQ=y -DCONFIG_MALI_PLATFORM_NAME=meson -DCONFIG_MALI_PLATFORM_POWER_DOWN_ONLY=y -Wimplicit-fallthrough=2' CONFIG_MALI_MIDGARD=m CONFIG_MALI_DEVFREQ=y CONFIG_MALI_PLATFORM_NAME=meson CONFIG_MALI_PLATFORM_POWER_DOWN_ONLY=y...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.7.0-rc5+ (aarch64)
Consult /var/lib/dkms/mali-bifrost/24.0+202005011205~focal/build/make.log for more information.
                                                                                                                                        [ OK ]
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc5+ /boot/vmlinuz-5.7.0-rc5+
update-initramfs: Generating /boot/initrd.img-5.7.0-rc5+
Using DTB: amlogic/meson64_odroidc4.dtb
Installing /home/hominoid/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtb into /boot/dtbs/5.7.0-rc5+/amlogic/meson64_odroidc4.dtb
Installing new meson64_odroidc4.dtb.
Ignoring old or unknown version 5.7.0-rc5+ (latest is 5.7.0-odroid-arm64)
Use --force if you want version 5.7.0-rc5+.
Installing /home/hominoid/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtb into /boot/dtbs/5.7.0-odroid-arm64/amlogic/meson64_odroidc4.dtb
Taking backup of meson64_odroidc4.dtb.
Installing new meson64_odroidc4.dtb.
flash-kernel: installing version 5.7.0-odroid-arm64
Generating boot script u-boot image... done.
Taking backup of boot.scr.
Installing new boot.scr.
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 5.7.0-rc5+ /boot/vmlinuz-5.7.0-rc5+
Using DTB: amlogic/meson64_odroidc4.dtb
Installing /home/hominoid/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtb into /boot/dtbs/5.7.0-rc5+/amlogic/meson64_odroidc4.dtb
Taking backup of meson64_odroidc4.dtb.
Installing new meson64_odroidc4.dtb.
Ignoring old or unknown version 5.7.0-rc5+ (latest is 5.7.0-odroid-arm64)

[tobetter]

@hominoid, you did nothing wrong...the problem is DKMS which does not properly compile the driver. You would have two options to apply the device tree change.

[1] Removing the package 'mali-bifrost-dkms' before compiling...
[2] Just do 'make dtbs' in stead of 'make', this will build the device trees only in the kernel tree. Then you can copy 'arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtb' to '/boot/dtbs/5.7.0-odroid-arm64/meson64_odroidc4.dtb'. This would be much easier if you do not need to change the kernel source tree.

By the way, I thought the same to build the device tree and share it with you. In the lab test with a number of ODROID-C4, 40-50% of them randomly halted when running 2.2GHz even after the active cooler was attached.

[hominoid]

By the way, I thought the same to build the device tree and share it with you. In the lab test with a number of ODROID-C4, 40-50% of them randomly halted when running 2.2GHz even after the active cooler was attached.

Thanks @tobetter, I appreciate the thought but I needed to learn the nuances of the mainline kernel build for this device anyway. I remember you, @odroid or someone mentioning that the yield for 2.2GHz wasn't great but I also need to know if I won the silicon lottery.

[Tomtom]

Greetings @all!

@tobetter: I hope you don't mind me bothering you with my noobish questions in this place. I'm newly registered and not privileged sending you PMs, yet. On the other hand, maybe someone else might be interested in this as well.

I'm an experienced Linux user, but mostly just the basics. I don't consider myself being experienced enough to answer these question by myself:

I'd like to set up my C4 as a server for basic services such as MySQL, lighttpd (Nextcloud), host based IDS, Icinga, PDF-generator (cron + getmail + latex + mutt), Telegram-bot, site-to-site-VPN gateway and pihole. I don't need a fancy desktop, so I wanted to go for a Ubuntu 20.04 LTS server image. But I'm pretty sure, a server image will never officially be offered and supported. So:

- What are the differnces between server and minimal? Does it make sense to use the minimal image for my scenario? I just want to make sure to have as few processes running as possible.

- The release of the official minimal image might take some time. I don't mind waiting a couple of weeks for that. But would there be a problem using your minimal installation and (somehow) switching to the official one once it's released? Is that even possible? Don't get me wrong. I highly appreciate your work. I just thought, using the official release would be safer, when it comes to support occuring issues. Also I'm unsure, what would happen in future in case you might lose interest in maintaining this.

If it's possible to switch, I would start setting up the system now instead of waiting. I just don't want to have to reinstall the OS again from scratch and redo all the services. I'm just unsure if it is easy like e.g. just changing repositories in sources.list and run an update/upgrade or something like that.

I hope my questions aren't too dumb.

[tobetter]

- What are the differnces between server and minimal? Does it make sense to use the minimal image for my scenario? I just want to make sure to have as few processes running as possible.

The "server" vs "minimal" is to prevent the confusion of the image file name from Hardkernel or me. For your use case, it sounds like you have to install a bunch of packages no matter you use minimal or server.

- The release of the official minimal image might take some time. I don't mind waiting a couple of weeks for that. But would there be a problem using your minimal installation and (somehow) switching to the official one once it's released? Is that even possible? Don't get me wrong. I highly appreciate your work. I just thought, using the official release would be safer, when it comes to support occuring issues. Also I'm unsure, what would happen in future in case you might lose interest in maintaining this.

I believe that the official minimal image would come sometime soon, I cannot commit when it is. The major difference between the official image and mine are 1) my image is based on upstream kernel by default - currently 5.7 - while the official image will be based on 4.9 version and 2) the official image will use the Hardkernel repository while my image will use my own repository. And the file system layout is a bit different, my image does not use the FAT partition.

If it's possible to switch, I would start setting up the system now instead of waiting. I just don't want to have to reinstall the OS again from scratch and redo all the services. I'm just unsure if it is easy like e.g. just changing repositories in sources.list and run an update/upgrade or something like that.

Since both images use a different repository server and a different package scheme, it's not easy to switch from one to another. If you think your use case needs more modern kernel features supported after 4.9 kernel, you should go for my server image or alternatively Armbian OS which is popular. I don't know how your system is complicated but since you are concerning the discontinued support, I do recommend building a docker image for your services. If your services are mostly based on official Ubuntu packages, you would not worry about the case if your server won't be supported except U-boot and kernel. Having a docker image for your system, Docker is not a swiss army knife, you would have less headache of faulty system or unexpected discontinued supports.

I hope my questions aren't too dumb.

I am having similar questions recently, I totally understand your concerns about whether your system can be supported long. So I think your question is reasonable.

[marcelk]

The major difference between the official image and mine are 1) my image is based on upstream kernel by default - currently 4.7 - while the official image will be based on 4.9 version […]

I think you meant 5.7 (current upstream kernel).

[tobetter]

The major difference between the official image and mine are 1) my image is based on upstream kernel by default - currently 4.7 - while the official image will be based on 4.9 version […]

I think you meant 5.7 (current upstream kernel).

Thank you for the correction!!

[Tomtom]

That's nice. Thank you very much for the quick and detailed reply.

[erg]

Is there a trick to getting the rtl8812au usb wifi dongle working?

[downunder52]

this will work for both N2 and C4

https://github.com/aircrack-ng/rtl8812au
You must change the Makefile to
CONFIG_PLATFORM_ARM64_RPI = y

[erg]

It took a bit of work to undo my first attempt, but I got the rtl8812au working! Thank you!

[elatllat]

ubuntu-20.04-minimal-odroidc4-20200421.img.xz works for me on the microSD as well. No problems. But just a apt full-upgrade which installs a new 5.4 and your 5.7 kernel renders the system unbootable. Maybe there's some configuration in your 20200421 kernel version which works for microSD?

Just some logs FYI:

Looks like shutdown is not working;

Code: Select all

bl31 reboot reason: 0x8
bl31 reboot reason: 0x8
system cmd  0.
bl30 get wakeup sources!
process command 00000006
bl30 enter suspend!
Little core clk suspend rate 1908000000
Error: Wait for CPU3 Power off state timeout
Error: Wait for CPU2 Power off state timeout
Error: Wait for CPU1 Power off state timeout
Error: Wait for CPU0 Power off state timeout
Error: Power switching is denied by A55!!
Error: wait power state change failed
store restore gp0 pll
store restore gp1 pll
suspend_counter: 1
Enter ddr suspend
ddr suspend time: 15us
alarm=0S
process command 00000001
cec ver:2018/07/03
CEC cfg:0x0000
WAKEUP GPIO cfg:0x00000000
WAKEUP GPIO FAIL - invalid key 
fffffe71
kern log_addr:0x00
cec T: 00
err: tx not finish flag
cec reset
Set cec pinmux:0x11
Set cec log_addr:0x10,ADDR0:10

and after a power cycle upgrade broke the boot;

Code: Select all

U-Boot 2015.01 (Apr 14 2020 - 01:55:53)

DRAM:  3.5 GiB
Relocation Offset is: d6eef000
spi_post_bind(spifc): req_seq = 0
register usb cfg[0][1] = 00000000d7f83b88
MMC:   aml_priv->desc_buf = 0x00000000d3edf7c0
aml_priv->desc_buf = 0x00000000d3ee1b00
SDIO Port C: 0, SDIO Port B: 1
card in
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x182000
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 12
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk_level = 7
vpu: vpu_power_on
vpu: set_vpu_clk
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100)
vpu: set_vpu_clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: g12a/b osd1 matrix rgb2yuv ..............
vpp: g12a/b osd2 matrix rgb2yuv..............
vpp: g12a/b osd3 matrix rgb2yuv..............
cvbs: cpuid:0x2b
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
41831 bytes read in 14 ms (2.8 MiB/s)
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]set initrd_high: 0x3d800000
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]VPP_OFIFO_SIZE:0xfff01fff
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=3840, height=1440
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
[OSD]osd_hw.free_dst_data: 0,1919,0,1079
USB3.0 XHCI init start
Net:   dwmac.ff3f0000
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0
## Attempting fetch boot.ini in mmc:0...
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
** Bad device mmc 0 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in mmc:0...
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
** Bad device mmc 0 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.ini in mmc:1...
** File not found boot.ini **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in mmc:1...
2692 bytes read in 14 ms (187.5 KiB/s)
## Executing script at 04000000
27338760 bytes read in 1652 ms (15.8 MiB/s)
47446 bytes read in 56 ms (827.1 KiB/s)
11866766 bytes read in 735 ms (15.4 MiB/s)
Booting Debian 5.7.0-odroid-arm64 from mmc 1:...
[rsvmem] get fdtaddr NULL!
rsvmem - reserve memory

Usage:
rsvmem check                   - check reserved memory
rsvmem dump                    - dump reserved memory

rsvmem check failed
active_slot is <NULL>
Unknown command 'store' - try 'help'
No dtbo patitions found
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 20000000
   Booting using the fdt blob at 0x20000000
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
No valid dtbo image found
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[rsvmem] fdt get prop fail.
   Loading Ramdisk to 3ccae000, end 3d7ff28e ... OK
   Loading Device Tree to 000000001fff1000, end 000000001ffff955 ... OK

Starting kernel ...

uboot time: 7408867 us

so

Code: Select all

apt-mark hold linux-image-5.7.0-odroid-arm64 udev

if using the img for now.

[Raymond Day]

I installed this on a 64GB eMMC on my Odroid-C4. I just want the server. So no desktop.

How can I get it to get a IP?

Can do "ip add show" it shows a eth0 I have a Ethernet plug in it and no LED's are flashing by the Ethernet cable. So it don't looks like eth0 is even on.

I did a "dhclient eth0" and after a while it comes back but "ip add show" don't change.

Without installing the desktop how can I get this to get a IP?

Looked through all the messages here and I can't find a place were it says it.

There is no ifconfig or nano installed on this.

-Raymond Day

[tobetter]

I installed this on a 64GB eMMC on my Odroid-C4. I just want the server. So no desktop.

How can I get it to get a IP?

Can do "ip add show" it shows a eth0 I have a Ethernet plug in it and no LED's are flashing by the Ethernet cable. So it don't looks like eth0 is even on.

I did a "dhclient eth0" and after a while it comes back but "ip add show" don't change.

Without installing the desktop how can I get this to get a IP?

Looked through all the messages here and I can't find a place were it says it.

There is no ifconfig or nano installed on this.

-Raymond Day

Having the Desktop is not mandatory, so your set up is just fine to run a server and IP must be set without changing if you have DHCP server.
Did you tightly insert the cable?
Do you have eth0 when running ip a?

[Raymond Day]

I plug in a USB to Ethernet and then it auto got a IP. I then installed nano and net-tools and plug the Ethernet back in and rebooted then it auto got a IP.

Then unplug the USB to Ethernet because the on board one is now working.

-Raymond Day

[tobetter]

Kernel update to 5.7.0 notice

I've managed and uploaded the new kernel version 5.7.0 last night, but the new kernel package cannot be updated with apt upgrade due to malformed package version rule I made. Therefore, if you like to upgrade your kernel, please use the commands or just skip the version if you do not have any issue to use the current version.

Code: Select all

$ sudo apt update
$ sudo apt install linux-image-5.7.0-odroid-arm64=5.7.0-202006022004~focal

[specs]

Is there any reason to disable HDMI sound in the kernel config?

Code: Select all

CONFIG_SND_HDA=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_CODEC_HDMI=m
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDA_CORE=m

I believe this was already documented as a solution to get sound working on the Odroid C4 (at least with the HDMI out).

[tobetter]

Is there any reason to disable HDMI sound in the kernel config?

Code: Select all

CONFIG_SND_HDA=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_CODEC_HDMI=m
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDA_CORE=m

I believe this was already documented as a solution to get sound working on the Odroid C4 (at least with the HDMI out).

Don't you have sound out over HDMI?
Do you have the package odroid-alsa with your setup?
Where is it documented regarding the kernel config?

[specs]

Right now I have the choice between the prebuild kernel with perfect video or my selfbuild kernel with sound.
Almost

Earlier in this thread it was mentioned that audio would work at least over HDMI. That's why I was surprised /boot/config-5.7.0-odroid-arm64 seems to skip the CONFIG_SND_HDA for the C4.
I guess there is still much left to do, so I could imagine this had not the highest priority.

[tobetter]

Right now I have the choice between the prebuild kernel with perfect video or my selfbuild kernel with sound.
Almost

Earlier in this thread it was mentioned that audio would work at least over HDMI. That's why I was surprised /boot/config-5.7.0-odroid-arm64 seems to skip the CONFIG_SND_HDA for the C4.
I guess there is still much left to do, so I could imagine this had not the highest priority.

Sorry, I am not clear...so you cannot have audio over HDMI with my kernel package but your kernel has with CONFIG_SND_HDA*? I never enabled them with my kernel package but had audio out over HDMI after installing Ubuntu Desktop and odroid-alsa package is for this.

[specs]

It works like you say.
I had odroid-alsa installed but not the ubuntu-desktop.

I'm not a great fan of ubuntu-desktop, that explains why I did not have it installed.

Code: Select all

Need to get 330 MB of archives.
Do you want to continue? [Y/n] 

[elatllat]

Sounds like odroid-alsa is missing a dependency...

[specs]

Most likely libgsound0 or libsbc1

(I removed both ubuntu-desktop and ubuntu-dektop-minimal which both fullfill the requirements)

[tobetter]

Regarding to GBM Support
I've been asked many times if Linux kernel 5.x on my server image can support GBM without GNOME Desktop. Probably you can simply test kmscube after installing the Wayland userspace driver and see if it meets your requirements.

Code: Select all

$ sudo apt install mali-bifrost-wayland-driver kmscube
$ sudo reboot

[bergaliv]

Hello.
I just tried using this image booting from SD-card. It doesn't work for some reason. All i get is a (pretty enough) hardkernel splash screen. Are sd-boot not supported?

[tobetter]

Hello.
I just tried using this image booting from SD-card. It doesn't work for some reason. All i get is a (pretty enough) hardkernel splash screen. Are sd-boot not supported?

Sorry, I found your post now.
The image should work with SD card, what's the vendor/model of your SD card?
Do you see the blue LED is on or blink when the power is supplied?

[bergaliv]

No worries mate. I appreciate your hard works, so i fully understand if it takes a while
I've tried with three brands of SD-Cards, same result on all.
I also tried all the versions of the dist here, the desktop, minimal, and netboot installer(both minimal and desktop). I also tried using a sdd. The result is the same on all. I get the hardkernel splash screen, heartbeat blue led, and nothing more.
I tried removing "quiet" from boot args, but i still can't see the kernel messages for some reason, so i can't tell for sure what is going on. My guess is that it's "kernel panic, no rootfs found"
(edit) All sd-cards works with the "Official" ubuntu image

[tobetter]

No worries mate. I appreciate your hard works, so i fully understand if it takes a while
I've tried with three brands of SD-Cards, same result on all.
I also tried all the versions of the dist here, the desktop, minimal, and netboot installer(both minimal and desktop). I also tried using a sdd. The result is the same on all. I get the hardkernel splash screen, heartbeat blue led, and nothing more.
I tried removing "quiet" from boot args, but i still can't see the kernel messages for some reason, so i can't tell for sure what is going on. My guess is that it's "kernel panic, no rootfs found"
(edit) All sd-cards works with the "Official" ubuntu image

It would be nice to have the vendor/model of your SD card what you have tried such that I can try to reproduce it. In order to save your time, any image from my effort/repository shares the same kernel and packages so if one does not work then others will be the same.
Thanks.

[bergaliv]

card no 1: mixza toaholl 8gb
card no 2: no-name 16gb
card no 3: local swedish brand(rebranded from something other) 64gb class 10
Sorry, that info isn't very useful for you All those cards work with the official ubuntu(hardkenrnels), and they work in raspberry pi zero, pi 3, pi 4.
But, if you say that you can boot from sd card with your images, the error must be in the sd-cards, no matter how well they work in other dists. The images are the same for everyone. I'll buy a couple of other cards and try it with those. Are there any way of showing kernel boot up? removing quiet didn't seem to do anything.

[miskol]

@tobetter
Can you add all panfrost related patches from here( https://github.com/chewitt/linux/commits/amlogic )
so people can choose panfrost or mali drivers
panfrost is working on C4
https://www.collabora.com/news-and-blog ... ics-blobs/
So it will be nice

I added it to armbian(waiting in MR)

[khoneini]

First of all thanks for your outstanding help on the custom images and keeping the community alive. I've donated you a couple of coffee's for the hard work your provide. My ODROID C2 arrived and I'm trying to setup Wireguard. However this seems to fail because it seems to be unable to build the kernel module. I'm running the following version:

Code: Select all

root@focal-server:/home/odroid# uname -a
Linux focal-server 5.7.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.7.0-rc3-202004302356~focal (2020-04-30) aarch64 aarch64 aarch64 GNU/Linux

If I try to install wireguard it throws the following error:

Code: Select all

Building initial module for 5.7.0-odroid-arm64
Error!  The /var/lib/dkms/wireguard/1.0.20200413/5.7.0-odroid-arm64/aarch64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.

A simple modprobe shows me the module is indeed missing:

Code: Select all

root@focal-server:/home/odroid# modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory /lib/modules/5.7.0-odroid-arm64

I tried compiling wireguard from source but the same error applies. This guy: https://wesley.sh/solved-attempting-to- ... directory/ seems to have the same issue (on a different architecture) and mentions it has something to do with the kernel and linux-headers not being on the same version. This seems not to be the case here. Any thoughts?

[istanbulls]

I want to ask a beginner question.
I installed Android on eMMC and Ubuntu on uSD card.
No Petitboot, no Jumper.
1. boot eMMC, eMMC 2. should have been booted.

How to start Ubuntu (uSD) when eMMC (Android) is installed. Is there a way?

And the weather got very hot where I live Board 60C in general, I have a small fan I want to plug it in, where should I install the Fan?

[tobetter]

I want to ask a beginner question.
I installed Android on eMMC and Ubuntu on uSD card.
No Petitboot, no Jumper.
1. boot eMMC, eMMC 2. should have been booted.

How to start Ubuntu (uSD) when eMMC (Android) is installed. Is there a way?

And the weather got very hot where I live Board 60C in general, I have a small fan I want to plug it in, where should I install the Fan?

Unfortunately, C4 cannot select a boot media unless one of uSD or eMMC is removed. The eMMC always has a higher priority than uSD.
Can you share which fan are you willing to connect to?

[tobetter]

First of all thanks for your outstanding help on the custom images and keeping the community alive. I've donated you a couple of coffee's for the hard work your provide. My ODROID C2 arrived and I'm trying to setup Wireguard. However this seems to fail because it seems to be unable to build the kernel module. I'm running the following version:

Code: Select all

root@focal-server:/home/odroid# uname -a
Linux focal-server 5.7.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.7.0-rc3-202004302356~focal (2020-04-30) aarch64 aarch64 aarch64 GNU/Linux

If I try to install wireguard it throws the following error:

Code: Select all

Building initial module for 5.7.0-odroid-arm64
Error!  The /var/lib/dkms/wireguard/1.0.20200413/5.7.0-odroid-arm64/aarch64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.

A simple modprobe shows me the module is indeed missing:

Code: Select all

root@focal-server:/home/odroid# modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory /lib/modules/5.7.0-odroid-arm64

I tried compiling wireguard from source but the same error applies. This guy: https://wesley.sh/solved-attempting-to- ... directory/ seems to have the same issue (on a different architecture) and mentions it has something to do with the kernel and linux-headers not being on the same version. This seems not to be the case here. Any thoughts?

Sorry for the late response.
I am seeing that your kernel is a bit outdated, so I suggest upgrading the kernel version to the latest one and try again.
For my mistake in my package repository, you won't upgrade the kernel after the current version (5.7.0-rc3) in your ODROID-C4 so please run this command to have an updated version and can be updated. After updating the kernel, please check if you have the package 'linux-headers-5.7.0-odroid-arm64' with the same version that runs on your ODROID-C4.

Code: Select all

sudo apt install linux-image-5.7.0-odroid-arm64=5.7.2-202006172010~focal

[istanbulls]

I want to ask a beginner question.
I installed Android on eMMC and Ubuntu on uSD card.
No Petitboot, no Jumper.
1. boot eMMC, eMMC 2. should have been booted.

How to start Ubuntu (uSD) when eMMC (Android) is installed. Is there a way?

And the weather got very hot where I live Board 60C in general, I have a small fan I want to plug it in, where should I install the Fan?

Unfortunately, C4 cannot select a boot media unless one of uSD or eMMC is removed. The eMMC always has a higher priority than uSD.
Can you share which fan are you willing to connect to?

Thanks for your reply,
It's a 4cm fan I used for RockPro.

[RafaelKa]

Hey folks,

I have some troubles with installation performance.
The first installation "minimal" was about 30 minutes. I did not change anything in "preseed.ini" on this install.

But now on all my subsequent tries with changes on preseed.ini the installer downloads the packages from apt repository very slowly. So i cancelled last try, which was configured in preseed.ini to install desktop and changed it back again for minimal installation. So the minimal installation currently runs about 12 Hours and is still on installing.

The internet speed at home is about 400+Mb/s. Other devices get packages in nanoseconds from ubuntu/debian/mirrors.
http://archive.canonical.com, http://ftp.hosteurope.de/mirror/ etc.

Is there some way to change apt mirror, which is closer to Germany, in the netinstall settings? I tried to deactivate auto install, there was a prompt to change mirror, but there was only one single, which is very slow.

[RafaelKa]

Hey folks,

I have some troubles with installation performance.
The first installation "minimal" was about 30 minutes. I did not change anything in "preseed.ini" on this install.

But now on all my subsequent tries with changes on preseed.ini the installer downloads the packages from apt repository very slowly. So i cancelled last try, which was configured in preseed.ini to install desktop and changed it back again for minimal installation. So the minimal installation currently runs about 12 Hours and is still on installing.

The internet speed at home is about 400+Mb/s. Other devices get packages in nanoseconds from ubuntu/debian/mirrors.
http://archive.canonical.com, http://ftp.hosteurope.de/mirror/ etc.

Is there some way to change apt mirror, which is closer to Germany, in the netinstall settings? I tried to deactivate auto install, there was a prompt to change mirror, but there was only one single, which is very slow.

Wow,
that was not a network/mirrors issue.

The resistors of EMMC module have had the contact/short to the C4 board soldered parts.
I was lucky, that the board and the EMMC didn't make a pfff.

! @hardkernel, you should deliver the C4s with some bumper sticker and communicate this issue for C4 users.

I solved it currently by adding a thin and tight film(e.g Cig. packet).

[tobetter]

20200716

The new image with Linux kernel 5.7.5 is ready.
Ubuntu 20.04 (Focal Fossa), and flash with the Etcher.

Note:

• The default user account and its password is odroid and odroid

For Ubuntu Gnome Desktop users:
Gnome Desktop with ARM Wayland GPU acceleration can be installed on top of this server image.

Code: Select all

$ sudo apt update
$ sudo apt install ubuntu-desktop mali-bifrost-wayland-driver
$ sudo reboot

[superpowter77]

20200716

The new image with Linux kernel 5.7.5 is ready.
Ubuntu 20.04 (Focal Fossa), and flash with the Etcher.

Note:

• The default user account and its password is odroid and odroid

For Ubuntu Gnome Desktop users:
Gnome Desktop with ARM Wayland GPU acceleration can be installed on top of this server image.

Code: Select all

$ sudo apt update
$ sudo apt install ubuntu-desktop mali-bifrost-wayland-driver
$ sudo reboot

Installation finished without errors, didn't boot, didn't get any HDMI signal. Where are located the boot.ini or config.ini files so I edit them to make them work with my 1080p monitor?
There were only boot.scr, config-5.7.0-odroid-arm64 and System.map-5.7.0-odroid-arm64 text files under boot partition.
I guess, uSD boot doesn't work yet, only eMMC.