Ubuntu 22.04 for ODROID-N2/C4/HC4

[Teashum]

Hi,
I’ve just upgraded my HC4 from Ubuntu 20.04/kernel 5.13 to Ubuntu 22.04.2/kernel 5.15 (do-release-upgrade + apt-get update + apt-get dist-upgrade) :
Before :
Linux naz 5.13.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.13.16-202207222133~focal (2022-07-22) aarch64 aarch64 aarch64 GNU/Linux
After :
root@naz:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
root@naz:~# uname -a
Linux naz 5.15.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.15.90-202301261933~jammy (2023-01-26) aarch64 aarch64 aarch64 GNU/Linux

Everythings seem to be ok, except the autoboot with Petitboot (version 20221228) which no longer works. After a poweroff, the boot partition Ubuntu 22.04.2 on disk sda1 is perfectly detected and shown in the petitboot menu, but Petitboot is unable to autoboot the HC4. However, when I manualy select “Ubuntu 22.04.2” in the menu, the HC4 boots up without any problem. The reboot also works without any concern (sudo reboot).
Is there any issue with this petitboot version and 5.15 Kernel ? Do I need to downgrade to kernel 5.13 or install another kernel ?

Thanks

Still no answer to my question.
Is my configuration supported ?

[tobetter]

Hi,
I’ve just upgraded my HC4 from Ubuntu 20.04/kernel 5.13 to Ubuntu 22.04.2/kernel 5.15 (do-release-upgrade + apt-get update + apt-get dist-upgrade) :
Before :
Linux naz 5.13.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.13.16-202207222133~focal (2022-07-22) aarch64 aarch64 aarch64 GNU/Linux
After :
root@naz:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
root@naz:~# uname -a
Linux naz 5.15.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.15.90-202301261933~jammy (2023-01-26) aarch64 aarch64 aarch64 GNU/Linux

Everythings seem to be ok, except the autoboot with Petitboot (version 20221228) which no longer works. After a poweroff, the boot partition Ubuntu 22.04.2 on disk sda1 is perfectly detected and shown in the petitboot menu, but Petitboot is unable to autoboot the HC4. However, when I manualy select “Ubuntu 22.04.2” in the menu, the HC4 boots up without any problem. The reboot also works without any concern (sudo reboot).
Is there any issue with this petitboot version and 5.15 Kernel ? Do I need to downgrade to kernel 5.13 or install another kernel ?

Thanks

Still no answer to my question.
Is my configuration supported ?

I don't think it's kernel version issue. Are you able to capture the video how Petitboot does not work after power on?

[Teashum]

Ok, I will capture and post the video tomorow because it's midnight for me now.
Thanks

[Teashum]

@Tobetter
Here is the video of Petitboot when the HC4 is powered on :
https://drive.shadow.tech/s/bnXDzWcDZq99rRJ
Nothing else after the black screen.
Does it try a PXE boot before the end of the timeout, and that prevent booting on the SSD ?
The Petitboot settings are the same as they where when the autoboot worked with Ubuntu 20.04 :

IMG_20230218_193203.jpg (151.17 KiB) Viewed 3119 times

IMG_20230218_193102.jpg (152.2 KiB) Viewed 3119 times

Thanks for your help.

[tobetter]

Does it try a PXE boot before the end of the timeout, and that prevent booting on the SSD ?

I guess so, can you please change the timeout like 10?

[Teashum]

Does it try a PXE boot before the end of the timeout, and that prevent booting on the SSD ?

I guess so, can you please change the timeout like 10?

Increasing the timeout to 10 seconds (or shortening it to 3) does not change anything : no autoboot.
Is it possible to disable PXE boot, since there is only the SSD in the boot order ?
Anyway, I'm not sure now that the PXE boot maters because with a 3 seconds timeout, the autoboot should boot on the SSD before the PXE try.
Any other idea ? Bug in Petitboot v20221228 ?

[Teashum]

Precision : the petitboot version displayed is dev.20221228. Does it matters ?

[tobetter]

Precision : the petitboot version displayed is dev.20221228. Does it matters ?

I think it does not matter of the version, PXE could be disabled if you set Static IP address in System Configuration. Can you try?

[Teashum]

Ok, static IP is now set, but still no autoboot working... See video.
https://drive.shadow.tech/s/eJzopdtr3EDzyxA

[tobetter]

Ok, static IP is now set, but still no autoboot working... See video.
https://drive.shadow.tech/s/eJzopdtr3EDzyxA

That's very odd....never seen the problem yet.
Can you try install the Petitboot again after completely remove it? Run below commands and install using the recovery image.

Code: Select all

flash_eraseall /dev/mtd0
flash_eraseall /dev/mtd1
flash_eraseall /dev/mtd2
flash_eraseall /dev/mtd3

The recover image is from here, http://ppa.linuxfactory.or.kr/images/pe ... 222.img.xz, flash this image to SD card and boot from it.

Before this, can you boot your HC4 after detaching USB keyboard so no input device.

[Teashum]

Ok, autoboot works fine now !
The problem was not the Petitboot version, but the boot order configuration : If the boot partition sda1 of my SSD is first and alone in the boot order (like on IMG_20230218_193203.jpg above), then autoboot failed.
If "Any device" or "Any network device" is first in boot order and sda1 or "Any disk device" is second, then autoboot works.
I will try again these settings tomorow with last Petitboot version to confirm.

[Teashum]

Ok, autoboot works fine now !
The problem was not the Petitboot version, but the boot order configuration : If the boot partition sda1 of my SSD is first and alone in the boot order (like on IMG_20230218_193203.jpg above), then autoboot failed.
If "Any device" or "Any network device" is first in boot order and sda1 or "Any disk device" is second, then autoboot works.
I will try again these settings tomorow with last Petitboot version to confirm.

I’ve just updated Petitboot back to v20221228 but unfortunately, autoboot never work with this version, whatever the boot order settings is. I actually think about an issue with v20221228 (which I have updated to, to have RTC wakeup).
@Tobetter, is there a chance to have both autoboot and RTC wake up working ?

[tobetter]

Ok, autoboot works fine now !
The problem was not the Petitboot version, but the boot order configuration : If the boot partition sda1 of my SSD is first and alone in the boot order (like on IMG_20230218_193203.jpg above), then autoboot failed.
If "Any device" or "Any network device" is first in boot order and sda1 or "Any disk device" is second, then autoboot works.
I will try again these settings tomorow with last Petitboot version to confirm.

I’ve just updated Petitboot back to v20221228 but unfortunately, autoboot never work with this version, whatever the boot order settings is. I actually think about an issue with v20221228 (which I have updated to, to have RTC wakeup).
@Tobetter, is there a chance to have both autoboot and RTC wake up working ?

I don't think it's Petitboot version issue since I use Petitboot everyday with ODROID-N2/HC4/M1 and their autoboot works. Also, Only thing the auto boot does not work, I know, is when the boot delay is too short or somehow input device works when Petitboot start. Maybe it's an unknown Petitboot bug, but then I would be reported by many users already.

As I mentioned in previous post, please try to clear your SPI flash memory and reinstall Petitboot.

I think RTC wake up would work, let me check again.
By the way, what's your kernel version now?

[Teashum]

Sorry, I realize that I forget some details : yesterday, as you explained, I’ve cleared SPI flash memory and reinstalled Petitboot version 20201222. With this version, autoboot works, depending on boot order as discribed in previous post.
So today I update Petitboot to 20221228, the version you’ve uploaded after my post on this topic viewtopic.php?p=362592#p362592, because RTC wakeup didn’t work with previous version.

Also, I’ve already set boot delay to 20 seconds and unpugged the keyboard without any success for autoboot.

My kernel is 5.15 :
Linux naz 5.15.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.15.90-202301261933~jammy (2023-01-26) aarch64 aarch64 aarch64 GNU/Linux

[tobetter]

Sorry, I realize that I forget some details : yesterday, as you explained, I’ve cleared SPI flash memory and reinstalled Petitboot version 20201222. With this version, autoboot works, depending on boot order as discribed in previous post.
So today I update Petitboot to 20221228, the version you’ve uploaded after my post on this topic viewtopic.php?p=362592#p362592, because RTC wakeup didn’t work with previous version.

Also, I’ve already set boot delay to 20 seconds and unpugged the keyboard without any success for autoboot.

My kernel is 5.15 :
Linux naz 5.15.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.15.90-202301261933~jammy (2023-01-26) aarch64 aarch64 aarch64 GNU/Linux

Testing the same version on ODROID-HC4 on my end, having not the same problem with multiple storage I have regardless the kernel version. The kernel version actually is not the matter for the autobooting.

It was around 2022/Dec/28 when you test the image, since then autoboot didn't work at all? Or at some point after updating, it does not work?

EDIT:
Just in case, please run flash_eraseall /dev/mtd1 in the command line of Petitboot (v20221228).

[Teashum]

It was around 2022/Dec/28 when you test the image, since then autoboot didn't work at all? Or at some point after updating, it does not work?

EDIT:
Just in case, please run flash_eraseall /dev/mtd1 in the command line of Petitboot (v20221228).

Autoboot doesn’t work since Ubuntu upgrade to 22.04. Please find herebelow a sumup history of what was done and what work with my HC4 configuration:

1.Before 2022-12-28 :
Linux naz 5.13.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.13.16-202207222133~focal (2022-07-22) aarch64 aarch64 aarch64 GNU/Linux
Petitboot v20220317
RTC Wakeup : failed
Autoboot : OK (with 5 seconds timeout)

2. 2022-12-28 -> Upgrade Petitboot to v20221228 (viewtopic.php?p=362592#p362592)
RTC Wakeup : OK
Autoboot : OK

3. 2023-02-17 -> Upgrade Ubuntu to 22.04 :
Linux naz 5.15.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.15.90-202301261933~jammy (2023-01-26) aarch64 aarch64 aarch64 GNU/Linux
RTC Wakeup : hardware wakeup OK, but then autoboot failed.
Autoboot : failed after poweroff, whatever is the timeout (5 10 20). Boot partition sda1 is first and alone in boot order (see IMG_20230218_193203.jpg above). But autoboot is OK when I reboot.

4. 2023-02-28 -> Clear flash memory and reinstall Petitboot
Petitboot : v20201222
RTC Wakeup : failed
Autoboot OK with default boot order, but failed if the boot partition is first and alone in boot order.

5. 2023-03-01 -> Upgrade Petitboot (to have RTC wakeup working)
Petitboot : v20221228
RTC Wakeup : hardware wakeup OK, but then autoboot failed.
Autoboot : failed after poweroff, whatever is the boot order (but reboot OK)

6. 2022-03-02 (today) -> flash_eraseall /dev/mtd1
RTC Wakeup : hardware wakeup OK, but then autoboot failed.
Autoboot : failed after poweroff, whatever is the boot order (but reboot OK)

Also, I noticed 2 different behaviours of led indicators at the end of the autoboot timeout :
When autoboot fails : red led (power) stays on and blue led (heartbeat) stays blinking
When autoboot succeds after a reboot or with Petitboot v20201222 : red and blue leds turn off shortly (as for a hard reset ?) and then turn on again and Ubuntu boots…

Ubuntu is installed on 1 Samsung SSD 870 EVO 1Tb (firmware SVT02B6Q)

Hoping these details help troubleshooting.
Thanks for the time you spend on this.

[Teashum]

Hi,

I know it may be hard to admit, but I ran further tests which seem to confirm that autoboot doesn’t work with a HC4 having Petitboot v20221228 installed and running Ubuntu 22.04 on a Samsung SSD EVO 1 Tb.
Here are my tests :
If I replace my Samsung SSD by a WesternDigital Scorpio blue HDD where I’ve cloned Ubuntu 22.04, then autoboot works.
If I clear Petitboot and reinstall v20201222 on the HC4, then autoboot works with the Samsung SSD.
If I downgrade Ubuntu to 20.04 on the Samsung SSD, then autoboot works.
But with Petitboot v20221228 + Ubuntu 22.04 + Samsung SSD EVO 1 Tb, then autoboot NEVER works.

Does anybody has the opportunitie to confirm this ?
Thanks for your answers.

[loso]

Hi Friends,

is there any success story with N2+ + Ubuntu 22.04 + panfrost + CEC? If so, what are the right kernel versions, cmdline options, devicetree setup(s) or anything else?

My previous story: more than year I was living with CoreElec kernel booting from the SD card and with my custom rootfs of Ubuntu 20.04 living on external USB SSD drive. Using systemd-nspawn I was able to start nicely HW accelerated Kodi from CoreElec image in Ubuntu with CEC and everything working fine and I was able to exit back to Xorg based Ubuntu desktop, whole setup had only one issue: missing VSYNC in Xorg so any video i.e. youtube in firefox was tearing and bad.

Few days ago: I tried Ubuntu 22.04 from linuxfactory (another SD card) and I was wondering how panfrost is doing nice VSYNC with gnome-wayland. N2+ seems to have enough CPU computing power for 1080p so I can live without HW acceleration until new era. But the issue is that I'm unable to bring /dev/cec0 to be working.
Default kernel from linuxfactory doesn't create /dev/cec0 even /dev/aocec at all. (I tried from 5.15 up to 6.2)

Now I'm trying to setup my kernel (coming from tobetter's odroid-5.15.y) with various combinations but only partial success: non working /dev/cec0 is created and I'm getting:

Code: Select all

root@odroid:~# ln -fs /dev/cec0 /dev/aocec; ll /dev/aocec; cec-client -l
lrwxrwxrwx 1 root root 9 Apr 20 20:33 /dev/aocec -> /dev/cec0
libCEC version: 6.0.2, compiled on Linux-4.15.0-166-generic ... , features: P8_USB, DRM, P8_detect, randr, RPi, Exynos, AOCEC
WARNING: [              23]	Open: ioctl(CEC_IOC_SET_OPTION_SYS_CTRL) failed
ERROR:   [              23]	could not open a connection (try 1)
WARNING: [              23]	Close: ioctl(CEC_IOC_SET_OPTION_SYS_CTRL) failed
....

I'm playing with the following options I found across whole internet but I didn't find strait forward doc how to deal with cec and drm

Code: Select all

root@odroid:~# egrep '.*CEC.*=|CONFIG_CEC_CORE|CONFIG_DRM_DW_HDMI|CONFIG_DRM_MESON|CONFIG_DRM_MESON_DW_HDMI' odroidN2Plus/linux/.config
CONFIG_TABLET_USB_ACECAD=m
CONFIG_CEC_CORE=y
CONFIG_CEC_NOTIFIER=y
CONFIG_MEDIA_CEC_SUPPORT=y
CONFIG_CEC_MESON_AO=y
CONFIG_CEC_MESON_G12A_AO=y
CONFIG_VIDEO_VIVID_CEC=y
CONFIG_DRM_I2C_ADV7511_CEC=y
CONFIG_DRM_DW_HDMI=m
# CONFIG_DRM_DW_HDMI_AHB_AUDIO is not set
CONFIG_DRM_DW_HDMI_I2S_AUDIO=m
# CONFIG_DRM_DW_HDMI_CEC is not set
CONFIG_DRM_MESON=m
CONFIG_DRM_MESON_DW_HDMI=m

also I was trying to play with, but without any success despite device file creation:

Code: Select all

root@odroid:~# grep cec /boot/boot.txt
#setenv cecenable "true"
setenv bootargs "${bootargs} hdmitx=cec3f"

Could you please point me to the right direction, how to deal with CEC device on N2+ and new kernel(s).
Thank you for your knowledge/experience/help.

[alphahere]

Is is possible to get a kernel module added to the stock kernel?

Thanks

[tobetter]

Is is possible to get a kernel module added to the stock kernel?

Thanks

Please specify what kernel you mean.

[loso]

long story short, /dev/cec0 was functional all the time in custom kernel, checked by cec-compliance from much conservative piece of package v4l-utils than ubuntu dist. cec-utils.
Custom compilation libcec 6.0.2 brings more fun, it is somehow locked for RPI platform (HAVE_RPI_API=0 doesn't help in my case), and needs to be compiled with HAVE_LINUX_API=1... simply remove craps for #raspberry pi in CheckPlatformSupport.cmake and you can compile it also on odroid.... finally replace system's libcec.so.6 (installed by kodi's dependency) by new shared lib...ldconfig etc.... and everything starts to work with default dist. kodi...enjoy the CEC...

[rooted]

That's fine detective work @loso

[lfriedri]

Hi,
trying to fix some issues with a USB device and an N2+ (see viewtopic.php?f=180&t=47141) I would like to try 5.15 kernel.

Unfortunately, I am a bit lost on how to actually use this distribution. The wiki tells me, that ubuntu 22.04 image has kernel version 4.9 (https://wiki.odroid.com/odroid-n2/os_im ... u/20220622). Is this outdated?
If I start from that image and do apt update + apt upgrade, I still see a kernel version 4.9.

I never used petitboot, should I invest time to learn it, or is there some image I can start from and eventually upgrade to kernel 5.15?

[tobetter]

Hi,
trying to fix some issues with a USB device and an N2+ (see viewtopic.php?f=180&t=47141) I would like to try 5.15 kernel.

Unfortunately, I am a bit lost on how to actually use this distribution. The wiki tells me, that ubuntu 22.04 image has kernel version 4.9 (https://wiki.odroid.com/odroid-n2/os_im ... u/20220622). Is this outdated?
If I start from that image and do apt update + apt upgrade, I still see a kernel version 4.9.

No, forget about Wiki about the installation or version management when you start to think of using this version.

I never used petitboot, should I invest time to learn it, or is there some image I can start from and eventually upgrade to kernel 5.15?

If you are intended to try the version for USB issue, please visit the link and download an image and flash the image to your memory card. Once you boot with an image, do sudo apt update && sudo apt upgrade in order to update your memory card with the latest versions.
https://docs.linuxfactory.or.kr/install ... image.html

[lfriedri]

Thank you, I will try.

I did not know this page. Why is it not presented much more prominent...?

The front page https://docs.linuxfactory.or.kr/ does not list Ubuntu 22.04 as support OS, is this outdated?

[lfriedri]

I tested
ubuntu-22.04-server-odroidn2plus-20221115.img from https://docs.linuxfactory.or.kr/install ... image.html

It seems to be identical to
ubuntu-22.04-server-odroidn2plus-20221115.img.xz from http://ppa.linuxfactory.or.kr/images/raw/arm64/jammy/

Unfortunately, it did not improve the situation in my USB issue (see viewtopic.php?f=180&t=47141&p=374361#p374361)