Petitboot, yet another bootloader based on KEXEC

[tobetter]

I was not even testing the Samsung card for this particular problem.
I am sorry, I do not understand your instructions. I have few different SD card, and I can load any OS you would like me to test.

So basically, after flashing the latest Petitboot, i am stuck at u-boot. Feels like Irrespective of what boot media i am using, this issue is different.

I can use Etcher to flash SD card with any OS you want me to try. I can take emmc out and boot said SD card, with BOOT switch on eMMC.

Can you grab the logs from U-boot?

I need to connect via UART to get U-boot logs right? Will have to buy a USB-UART Module for it, i dont current own one.

I´ve got these 3 uSD. The 128 GB Sandisk is brand-new ~ 3 days old. With the 8GB Sandisk I only make Petitboot updates. I use the 128GB Sandisk and 32GB Samsung to test. I don´t think that they both are faulty because I can flash every single one and boot up e.g. Android without problems with eMMC switch enabled (without eMMC inserted). I just can´t boot the same sd cards with Petitboot enabled (with switch set to SPI) That´s the one problem with Petitboot + sd cards.
The other problem is that if I flash e.g. Android to eMMC, SPI=Petitboot=enabled, I also can´t boot up. But I can boot up the eMMC Android image with eMMC switch=enabled. Perhaps I have a different firmware or hardware revision? (I need a...) Is there a full image with "factory reset" and stable working Petitboot?

When you boot the Android from eMMC by the Petitboot, did you attach the SD card? If so, can you please test without it?

"Tapatalk wishes you to have fun with ODROID"

[roterdrachen]

@Sholander
Yes, the Android version "Android PIE-R.06 4GB image from secuflag" starts normaly with only uSD card inserted and SPI switch=eMMC.

@tobetter
I flashed with Etcher the Android version "Android PIE-R.06 4GB image from secuflag" 4GB_arm64_PIE-R.06_selfinstall-odroidn2.img.xz.
I can boot this image from eMMC with switch=eMMC, no sdcard inserted.
During the next steps SPI=always on
I can´t boot this same Android image with clean install of Petitboot 20191127, no sdcard inserted.
During booting the TV went black, then no signal, after a while I saw the Hardkernel Logo.
Then I saw the attached error screen. (No Petitboot screen)
Now I can´t get to the Petitboot screen anymore.
If I power cycle it (with SPI=on) I always get this error screen.
I must make a "factory reset" and wipe the data.
Then I´m able to go back to the Petitboot screen.

[c9v87kh2]

[...]

• We already have a couple of changes on the source code of **Petitboot** as well as **kexec-tools** and has been uploaded to Github. And Buildroot is being used to build the complete SPI which is consisted with U-boot, Linux kernel, and ramdisk which is limited to 8MB.
  https://github.com/JeonghwaCho/petitboo ... ve-network
  https://github.com/tobetter/kexec-tools ... id-v2.0.18
  https://wiki.odroid.com/odroid-n2/softw ... _petitboot

[...]

Hello @tobetter,

3rd link is broken, so how could I build the last stable version (viewtopic.php?f=182&t=33873&start=150#p273785) ?

Thank you

[baalho]

Yes, I thought you have one since you said you are stuck at U-boot. Can you please test to boot from eMMC after remove the SD card?

"Tapatalk wishes you to have fun with ODROID"

@tobetter,
With Petitboot, 20200118, if the boot select switch is on SPI i get no signal to TV, and N2 has solid Red LED when i have only eMMC. When the switch is on eMMC, N2 boots CoreElec without a problem.
With any older revision of Petitboot, i have no issue at all. When I made this summary before, you said i might be stuck at u-boot.
I am a newbie, so i am not sure if I am infact stuck in u-boot or what the issue is.
The last couple post i have made on the latest revision of Petitboot is unchanged.

For the time being I have reverted back to the last stable release of Petitboot, will try to debug some more if and when I get UART module.
I will not mess with dual booting, just run CoreElec on eMMC.

Regardless, I do want to thank your for your patience and providing insight on what the issue could have been with using the latest "experimental" build.

[Samveen]

@tobetter I am very interested in getting netboot portion of petitboot to work, so I followed the petitboot source link for Joy's petitboot repo posted in the first post. however I see that it has not been updated for a year, and the same is the case with your fork of Joy's repo . would you point out where you are doing your development, so that I can contribute to getting PXE in petitboot to work? Ideally I am looking for the documentation of the SPI image build process that you are using.

Background: I am working on setting up a 10 N2 cluster (with hopes of expanding it into a cluster of 40). The aim is to create a testbed for Kubernetes in a heterogenous OS environment, with the possibility of changing the OS via network install. I was hoping to port and use a cluster management framework that I use extensively to a new architecture in the hopes of creating a micro Data center. For any starting point for this, the client requirement is such that I need PXE support to be baked into the SPI itself.

[tobetter]

It's been a year since I've started this thread already and I planned to release yet another improved version for the celebration.
Unfortunately, it's not optimistic but I still have another 18 hours KST.

The upcoming feature is:
1. Fixing the display issue for some users who meets the black screen issue.
2. Supporting PXE boot using the Petitboot which I've tried to learn how PXE works on the Petitboot since last Dec/2019, this requires a bit of documentation.
3. Some minor fixes on kernel/U-boot upgrades.

Stay tuned.

[mad_ady]

PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...

[tobetter]

PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...

Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.

[mad_ady]

Sounds like a great wiki page and article idea

[brad]

Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.

This is a very nice feature (either petitboot or uboot) for PXE on spi meaning we can have diskless N2's booting linux

Linux kernel supports 3 remote configurations for remote disk / filesystem

- iSCSI (block device) rootfs
- NFS rootfs (network filesystem)
- CIFS / SMB (experimental feature network rootfs - being integrated into recent mainline versions)

[mxmilkb]

Aside; when I got this laptop, my previous was dead and I had no free USB stick, so I used the Servers Ultimate Android app to run a PXE server and host netboot.xyz which I booted my laptop with to install Arch Linux from the internet with.

[Samveen]

PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...

Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.

Actually not just dnsmasq, but any combination of a DHCP server that supports the boot-file and next-server opts and a tftp server to host the files (I've had to use udhcpd and in.tftpd via xinetd in a pinch from an Ubuntu Bionic LiveCD (18.04.03) ).

This will make the process of provisioning a whole bunch of N2s so so so so much easier: a huge step towards a true Micro Data-centre

[tobetter]

PXE soulds great. I thought you would need to ditch petitboot and bake a custom uboot for something that resembles pxe...

Fortunately, apparently it's not and absolutely as you may or may not know that the current U-boot (v2015.01) also supports PXE boot. What a surprise is that even I aware that the Petitboot support PXE Netboot, it was quite simple to enable it - a single line. I just had to spend some time to learn from the Petitboot code and building an image. If you know how to set up a PXE server using dnsmasq and create the PXE config file, you can instantly use PXE netboot using TFTP or HTTP.

Actually not just dnsmasq, but any combination of a DHCP server that supports the boot-file and next-server opts and a tftp server to host the files (I've had to use udhcpd and in.tftpd via xinetd in a pinch from an Ubuntu Bionic LiveCD (18.04.03) ).

This will make the process of provisioning a whole bunch of N2s so so so so much easier: a huge step towards a true Micro Data-centre

True.
FYI, I've set up the example PXE server for Debian/Ubuntu Netboot installer and it works, I am going to upload the working version here today or tomorrow.
http://ppa.linuxfactory.or.kr/installer ... ODROID-N2/

[tobetter]

20200224

Let me introduce a new version of the year 2020, please click spiboot-20200224.img to download and copy the file to your uSD card as spiboot.img or you can update with pb-update command in shell of the Petitboot if you have the version after 20191127
https://wiki.odroid.com/odroid-n2/os_im ... grade_mode

What's improved:

• Blank screen issue on 4K TV is improved.

Many users using 4K TV had an issue that nothing shows after Petitboot due to a bug, that's been fixed but need more test with various TV vendors.[/list]

• UHS (Ultra High Speed) is off by default.

Some users with a certain micro SD card had a booting issue, specifically Samsung EVO, and this issue could be resolved after disabling UHS support since version 20200118. But more users start to use the same memory cards and due to the difficulty to set the flag, it's been disabled by default. Please visit the link for more detail, viewtopic.php?f=182&t=33873&hilit=20200 ... 00#p278201

• PXE support is enabled.

PXE is the very new feature that can support network booting if you have DHCP and TFTP/HTTP server. This is not necessary feature for a regular user but very helpful for a system with multiple N2.

Running PXE
I've set up the example PXE server at http://ppa.linuxfactory.or.kr/installer ... ODROID-N2/, N2 will display multiple boot entries of Debian/Ubuntu Netboot installers like this.

IMG_20200224_2236216.jpg (304.31 KiB) Viewed 10182 times

In order to run PXE, you need to set up DHCP server by default and TFTP or HTTP server is required. I've done using Apache for HTTP server and dnsmasq for DHCP server. In order to make DHCP server to fetch the PXE configuration, DHCP configuration needs to be modified and this is my change for dnsmasq. Most important change for PXE in the change is the lines that start with dhcp-option-force= and these two lines offers the server where to fetch the PXE menus when Petitboot establish the dynamic IP address by the same DHCP server.

Code: Select all

--- dnsmasq.conf.orig   2020-02-15 03:43:46.828796708 +0900
+++ dnsmasq.conf        2020-02-22 00:18:47.845256410 +0900
@@ -64,6 +64,8 @@
 # Add other name servers here, with domain specs if they are for
 # non-public domains.
 #server=/localnet/192.168.0.1
+server=8.8.8.8
+server=8.8.4.4
 
 # Example of routing PTR queries to nameservers: this will send all
 # address->name queries for 192.168.3/24 to nameserver 10.1.2.3
@@ -141,7 +143,7 @@
 # 2) Sets the "domain" DHCP option thereby potentially setting the
 #    domain of all systems configured by DHCP
 # 3) Provides the domain part for "expand-hosts"
-#domain=thekelleys.org.uk
+domain=linuxfactory.or.kr
 
 # Set a different domain for a particular subnet
 #domain=wireless.thekelleys.org.uk,192.168.2.0/24
@@ -160,7 +162,7 @@
 # is needed for networks we reach the dnsmasq DHCP server via a relay
 # agent. If you don't know what a DHCP relay agent is, you probably
 # don't need to worry about this.
-#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
+dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
 
 # This is an example of a DHCP range which sets a tag, so that
 # some DHCP options may be set only for this network.
@@ -328,7 +340,8 @@
 
 # Override the default route supplied by dnsmasq, which assumes the
 # router is the same machine as the one running dnsmasq.
-#dhcp-option=3,1.2.3.4
+dhcp-option=3,192.168.0.1
+dhcp-option=6,192.168.0.2
 
 # Do the same thing, but using the option name
 #dhcp-option=option:router,1.2.3.4
@@ -429,9 +442,9 @@
 # Magic number - needed before anything else is recognised
 #dhcp-option-force=208,f1:00:74:7e
 # Configuration file name
-#dhcp-option-force=209,configs/common
+dhcp-option-force=209,pxeboot/ODROID-N2/default
 # Path prefix
-#dhcp-option-force=210,/tftpboot/pxelinux/files/
+dhcp-option-force=210,http://ppa.linuxfactory.or.kr/installer/
 # Reboot time. (Note 'i' to send 32-bit value)
 #dhcp-option-force=211,30i

In order to achieve the same result or for quick testing, you can run this command in the shell prompt of the Petitboot and this command will fetch the PXE config file from my server directly without DHCP server setup.

Code: Select all

pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer/pxeboot/ODROID-N2/default

I have not tested to use TFTP instead of HTTP, but it will work for sure and if you have NFS server and set up the command line properly Linux kernel can mount a directory in the NFS server, this will make diskless ODROID-N2 system. Maybe PXE support is necessary to be forked to other threads?

Please keep sharing your experience with the Petitboot.

[minoccio]

does the uhs-unable feature reduce the speed of uSD during the normal use?

[tobetter]

does the uhs-unable feature reduce the speed of uSD during the normal use?

The feature only affects the Petitboot, normal OS will initiate the uSD speed when its own kernel starts.

[joschi]

I've been trying to get petitboot running on my ODROID-N2 and it's working strictly speaking, but it never shows anything on the display.
For the whole boot process it only shows a blank screen until the OS (CoreELEC 9.2.1) from the SD card has been booted.

I've tried with petitboot 20191127 and with petitboot 20200224, both with the same result: Only a blank (black) screen while booting until CoreELEC/Kodi comes up.

I think this has to do with the fact that the display (an old Toshiba TV) is "lying" about the display resolutions it supports.
The display advertises 1080i50hz as preferred resolution, but only supports up to 720p60hz.

Is there a way to force petitboot to use a specific display resolution?

Here are some details about the display, please let me know if you need anything else.

Code: Select all

# cat /sys/class/amhdmitx/amhdmitx0/disp_cap
480i60hz
576i50hz
480p60hz
576p50hz
720p60hz
1080i60hz
720p50hz
1080i50hz*

Code: Select all

# cat /sys/class/amhdmitx/amhdmitx0/edid
Rx Manufacturer Name: TSB
Rx Product Code: 0106
Rx Serial Number: 01010101
Rx Product Name: TOSHIBA-TV
Manufacture Week: 255
Manufacture Year: 2008
Physcial size(cm): 105 x 59
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0x97
Source Physical Address[a.b.c.d]: 2.0.0.0
native Mode 71, VIC (native 20):
ColorDeepSupport 0
20 19 18 22 17 21 5 4 3 7 2 6 1
Audio {format, channel, freq, cce}
{1, 1, 7, 7}
Speaker Allocation: 0
Vendor: 0xc03 ( HDMI device)
MaxTMDSClock1 80 MHz
vLatency:  Invalid/Unknown
aLatency:  Invalid/Unknown
i_vLatency:  Invalid/Unknown
i_aLatency:  Invalid/Unknown
SCDC: 0
RR_Cap: 0
LTE_340M_Scramble: 0

checkvalue: 0x97260000

[tobetter]

@joschi, you mean that you have never seen the face of the Petitboot but CoreELEC boots?
There are two ways to select different display resolutions.
1. Create a file petitboot.cfg in the root directory of a uSD, for example, if you like to use 720p60hz instead of 1080p60hz which is the default resolution. You can try multiple times to find out the best resolution supported by your TV. This method won't store the resolution, so if you remove the uSD, the default display resolution will be applied.

Code: Select all

[petitboot]
hdmimode=720p60hz

2. In the shell of the Petitboot, you can store the display resolution to SPI flash memory. This method is good after looking for the best resolution with petitboot.cfg.

Code: Select all

# spimmc.sh
# fw_setenv hdmimode 720p60hz

[joschi]

@joschi, you mean that you have never seen the face of the Petitboot but CoreELEC boots?

Yes, exactly.

1. Create a file petitboot.cfg in the root directory of a uSD, for example, if you like to use 720p60hz instead of 1080p60hz which is the default resolution. You can try multiple times to find out the best resolution supported by your TV. This method won't store the resolution, so if you remove the uSD, the default display resolution will be applied.

Code: Select all

[petitboot]
hdmimode=720p60hz

This works like a charm, thank you so much!

After creating the configuration file at /flash/petitboot.cfg (where the first partition of the SD card is mounted) and rebooting, I can finally see the petitboot screen.

[Bubblefish0815]

So , I tested the new petitboot (20022020) - always the same

I see the Hardkernel logo , switch between
* Core elec
* Emuelec
* Ubunto
select one ... enter .. black screen , but all systems are booting and I see the screen after switch off/on the LCD


( I tested also the older petitboot - booting from petitboot is fine - but then black screen )
4 K LCD

any hints ?

[Sav]

Maybe you have to manual set the screen resolution editing the boot.ini files. You also have to set to false the aitodetect variable.

Inviato dal mio GM1913 utilizzando Tapatalk

[brad]

Hi @tobetter,
I notice new patch series coming for mainline linux to support SPIFC - https://patchwork.kernel.org/project/li ... ies=255937

By default it would be off but with device tree changes it could be enabled along side emmc (emmc downgraded from 8 bit to 4 bit in this case). May be helpful for petiboot to flash new images or accessing emmc during SPI boot process.

[tobetter]

Hi @tobetter,
I notice new patch series coming for mainline linux to support SPIFC - https://patchwork.kernel.org/project/li ... ies=255937

By default it would be off but with device tree changes it could be enabled along side emmc (emmc downgraded from 8 bit to 4 bit in this case). May be helpful for petiboot to flash new images or accessing emmc during SPI boot process.

Thank you for pointing me out the patches. I've tried a similar approach with Linux 4.9 earlier but no luck and not spent much time to figure out since it could reduce the performance of eMMC. Instead, I've made the drivers for SPI and eMMC as a kernel module so that they can switch one to another by loading and unloading the module accordingly. I would try sometime later...

[tobetter]

So , I tested the new petitboot (20022020) - always the same

I see the Hardkernel logo , switch between
* Core elec
* Emuelec
* Ubunto
select one ... enter .. black screen , but all systems are booting and I see the screen after switch off/on the LCD


( I tested also the older petitboot - booting from petitboot is fine - but then black screen )
4 K LCD

any hints ?

Are you running this version? Since I never had released any Petitboot in the year 2002.
viewtopic.php?f=182&t=33873&p=286050#p282985

And like @Sav mentioned, can you try to edit boot.ini to set display_autodetect as false? in the Ubuntu image and can you let me know the output with the command cat /proc/cmdline?
Let me know the branch and model of your TV if possible?

[Bubblefish0815]

So,
Sorry , yes I run the latest Version.

I change the boot.ini testing in Ubunto / flash boot.ini coreelec - ( display autodetect and resulution ).
SPI right mmc - corelec boots fine also emuelec
SPI left petitboot - petitboot logo / screen with coreelec/emuelec /ubunto

I tested all 3 , all are booting but the screen of my LCD is black - power switch off/on my LCD - all are working , tested on different HDMI inputs and No Switch or Receiver between N2 / LCD
( plugoff / plugin HDMI cable -- no effect )

Tested on Thosiba 4K (55') , Medion 4K (65') , Samsung 4K(55')

Hmm,unfortunately I have no more ideas

PS: Today I take the N2 and tested on a Philips 55' 1080p - working perfectly !

Problem are 4K panels

[tobetter]

So,
Sorry , yes I run the latest Version.

I change the boot.ini testing in Ubunto / flash boot.ini coreelec - ( display autodetect and resulution ).
SPI right mmc - corelec boots fine also emuelec
SPI left petitboot - petitboot logo / screen with coreelec/emuelec /ubunto

I tested all 3 , all are booting but the screen of my LCD is black - power switch off/on my LCD - all are working , tested on different HDMI inputs and No Switch or Receiver between N2 / LCD
( plugoff / plugin HDMI cable -- no effect )

Tested on Thosiba 4K (55') , Medion 4K (65') , Samsung 4K(55')

Hmm,unfortunately I have no more ideas

PS: Today I take the N2 and tested on a Philips 55' 1080p - working perfectly !

Problem are 4K panels

For your 4K TV, can you try one of these for hdmimode in your boot.ini? So like, instead of setenv hdmimode 1080p60hz, use setenv hdmimode 2160p30hz or so.

# "2160p60hz" | 3840x2160 Progressive 60Hz
# "2160p50hz" | 3840x2160 Progressive 50Hz
# "2160p30hz" | 3840x2160 Progressive 30Hz
# "2160p25hz" | 3840x2160 Progressive 25Hz
# "2160p24hz" | 3840x2160 Progressive 24Hz

Also, please let me know the output with cat /proc/cmdline once you have booted with any OS if you can connect through SSH or when screen comes after off/on your TV.

[umiki]

Sorry, if it has been asked before:

Is it possible to set the initarg remotewake for IR remotes somehow?
It works well if I boot the SD card directily (Coreelec, there it is set in config.ini), but I did not succeed to set this when booting through Petitboot.
I have tried boot.ini in the flash partition of Coreelec without any effect.

thanks!

[thering1975]

EDIT - Update

Okay i decided to do a test and even though the latest petitboot was meant to have the disable_uhs set automatically, it was not working for me as per below. So i followed the previous release guide for disabling UHS.

When i printed the Env for disable UHS it was set to true (as expected)

However i followed the guide for manually setting the disable_uhs flag and it now boots from both SD Card and EMMC perfectly fine, i did have a black screen when i rebooted from coreelec and petitboot did not show up. I power cycled again and that problem has not appeared so all seems good



Edit - Original Post below

Hi

Apologies if this has been answered before, i have tried various steps but still suffer an issue which i thought the latest update was meant to resolve.

Setup is N2 4G Edition.
Emmc is Android 32gb
SD Card is CoreElec latest build
SD Card make is the Samsung Evo Select (same as plus but exclusive to Amazon) 64gb
Petitboot version - dev.20200224

If i boot with switch set to MMC the following all works fine

Only SD Card inserted - Core Elec Boots
Only MMC inserted - Android Boots

If i set switch to SPI the following occurs

Select Android - BOOTS Fine
Select CoreElec (sdcard) - Error Panics and various messages as per pics below

Just wondering if i am missing something

[vzoltan]

Hello there, so that's weird. I've flashed the latest Petitboot (20200224), and although there are USB devices connected, I also selected them in the system configuration menu (boot order), NOTHING is displayed. Obviously I also cannot boot from anything:

- Petitboot automatically won't boot
- I also cannot select any of the USB devices, because nothing is displayed to select from...

What is wrong here? I'm having the 4GB N2.

petitboot_usb_devices.jpg (107.33 KiB) Viewed 5780 times

petitboot_nothing.jpg (56.05 KiB) Viewed 5780 times

Any feedback is appreciated. Thanks!

[tobetter]

Hello there, so that's weird. I've flashed the latest Petitboot (20200224), and although there are USB devices connected, I also selected them in the system configuration menu (boot order), NOTHING is displayed. Obviously I also cannot boot from anything:

- Petitboot automatically won't boot
- I also cannot select any of the USB devices, because nothing is displayed to select from...

What is wrong here? I'm having the 4GB N2.

Any feedback is appreciated. Thanks!

What I can see from the picture is that your two storage is mounted but it fails to read the boot script "boot.ini" or "boot.scr", they must be in the root directory or /boot in each storage. Can you please check if you have the files and share the files if you have. By the way, which OS did you flashed and how?

[vzoltan]

What I can see from the picture is that your two storage is mounted but it fails to read the boot script "boot.ini" or "boot.scr", they must be in the root directory or /boot in each storage. Can you please check if you have the files and share the files if you have. By the way, which OS did you flashed and how?

Thank you for your prompt reply! I believe we are getting closer and I'm the noob here.

I actually moved an armbian installation from SD to the my USB SATA enclosure and also to a UFD stick. I suppose the "nand-sata-install" script doesn't copy the content of /boot.

Having said that... Do I understand it correctly that by a proper "flashing" I could totally abandon the SD for boot purposes, and solely use the my USB SSD? Could you please point me to any how-to / guide which describes what needs to be done?

[tobetter]

What I can see from the picture is that your two storage is mounted but it fails to read the boot script "boot.ini" or "boot.scr", they must be in the root directory or /boot in each storage. Can you please check if you have the files and share the files if you have. By the way, which OS did you flashed and how?

Thank you for your prompt reply! I believe we are getting closer and I'm the noob here.

I actually moved an armbian installation from SD to the my USB SATA enclosure and also to a UFD stick. I suppose the "nand-sata-install" script doesn't copy the content of /boot.

Having said that... Do I understand it correctly that by a proper "flashing" I could totally abandon the SD for boot purposes, and solely use the my USB SSD? Could you please point me to any how-to / guide which describes what needs to be done?

I am not familiar with the script 'nand-sata-install', but I am assuming that it's OS transferring tool between two different storages. If you already have SD card that boots from N2, insert it to USB card reader and attach the card reader to USB host port on ODROID-N2, then start the Petitboot. It would show you boot entry when the contents in the SD card is correct, I used to test other OS images in the same manner.

[vzoltan]

I am not familiar with the script 'nand-sata-install', but I am assuming that it's OS transferring tool between two different storages. If you already have SD card that boots from N2, insert it to USB card reader and attach the card reader to USB host port on ODROID-N2, then start the Petitboot. It would show you boot entry when the contents in the SD card is correct, I used to test other OS images in the same manner.

You are spot on here - Petitboot works as expected, and boots off my SD card.

Another story is that I do not need the SD at all, but that's offtopic here and I'll do further research how to make this properly functional. Thanks again!

[tobetter]

I am not familiar with the script 'nand-sata-install', but I am assuming that it's OS transferring tool between two different storages. If you already have SD card that boots from N2, insert it to USB card reader and attach the card reader to USB host port on ODROID-N2, then start the Petitboot. It would show you boot entry when the contents in the SD card is correct, I used to test other OS images in the same manner.

You are spot on here - Petitboot works as expected, and boots off my SD card.

Another story is that I do not need the SD at all, but that's offtopic here and I'll do further research how to make this properly functional. Thanks again!

If your SD card works with the Petitboot as you expected, flash the OS image you have downloaded to your USB stick or SSD/HDD using Etcher directly without any tool. It will work. Using SD card is a test method if the OS image is flashed correctly and USB port works properly.

[bright_plastik]

In order to achieve the same result or for quick testing, you can run this command in the shell prompt of the Petitboot and this command will fetch the PXE config file from my server directly without DHCP server setup.

Kim, unfortunately we live far away. If I had you chilling around, I'd hug you, such is the amaze for the work you've done on this board. No surprise the HardKernel team respect you so much. They should literally submerge you in coins.
So, I bought the N2 two days ago, I updated petitboot with latest version, my screen is working perfectly fine, no problem whatsoever with the microsd, the ppa url you gave us just did the magic, and at this point I'm eagerly running toward a multiboot of several different OS on the same 32Gb emmc (hopefully, if I don't fuck up something).

So, this is only to tell you that YOU are the proof that a good board design doesn't make its success. The community does. I was reading your articles even before I sent my order for a N2, weeks ago. The kit is awesome, but with you, and people like @hominoid and others I'll meet round the forum, I think we can really use the board for aims that are waaaaay further the tipical productivity.
So thank you so so much. As soon as I'll make a dime out of this machine I'll reward you guys.

[tobetter]

@bright_plastik, this is way more than beautiful 'THUMBS UP'!! I am very happy to see someone had tried to launch the Netboot Installer using the Petitboot and trying to install Debian or Ubuntu to ODROID-N2 natively, this is actually one of goal I wanted to achieve with the Petitboot. This heals me from the overnight work, I would like to share the credit with other ODROID fans who help me to debug.

Anyway, have fun with your ODROID and keep sharing your experience.

[bright_plastik]

My pleasure, to relate with such capable geeks.
two things I noticed:

• General offline experiences both with forum.odroid.com, and with the servers used to install ubuntu from the installer. Seems like during night time (Italy time), between midnight and 2 o clock, odroid servers and ubuntu servers are unavail. This means not every moment is a good moment to post on the forum, as well as installing ubuntu.

• My first attempt to install ubuntu on the N2 was writing the url you provided in petitboot shell. Followed installation of 19.04, aiming for a gnome DE. I recall the acceleration is compatible only with gnome. Dunno why, but the packages available when installing from url are different from the ones you provide in the netboot installer, and even selecting "vanilla Gnome desktop" I ended up with a somewhat working server version with only terminal, unsuitable for a noob like me. Reattempting yesterday night during online server hours, and using a sd card with netboot installer, I simply chose Gnome Desktop, and this completed the setup nicely.

My two (noob) cents, trying to be useful in some way...

[tobetter]

My pleasure, to relate with such capable geeks.
two things I noticed:

• General offline experiences both with forum.odroid.com, and with the servers used to install ubuntu from the installer. Seems like during night time (Italy time), between midnight and 2 o clock, odroid servers and ubuntu servers are unavail. This means not every moment is a good moment to post on the forum, as well as installing ubuntu.

Both servers are physically different and even not sharing the network bandwidth, just a coincidence I think. The servers are heavily loaded sometimes.

• My first attempt to install ubuntu on the N2 was writing the url you provided in petitboot shell. Followed installation of 19.04, aiming for a gnome DE. I recall the acceleration is compatible only with gnome. Dunno why, but the packages available when installing from url are different from the ones you provide in the netboot installer, and even selecting "vanilla Gnome desktop" I ended up with a somewhat working server version with only terminal, unsuitable for a noob like me. Reattempting yesterday night during online server hours, and using a sd card with netboot installer, I simply chose Gnome Desktop, and this completed the setup nicely.

My two (noob) cents, trying to be useful in some way...

Currently ARM Mali Wayland driver works with Gnome Desktop only, I was trying to enable KDE but KDE window manager is not compatible. I've researched some and figured out the kinda reason, but still, KDE keeps crashing. I am not looking into it as of now but will visit again sometime soon. By the way, which desktop have you tried on other than gnome?

[bright_plastik]

Sincerely, I've only ever wanted to go with Gnome DE, on the Odroid. I'ts light, accelerated and suitable for mining too, plus I knew already you were making excellent progress with graphics and kernels.
Therefore, my first attempt was with the 19.04 version grabbed at this server, as you pointed out:

Code: Select all

pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer/pxeboot/ODROID-N2/default

What I'm trying to say is that this method delivered a different build, and the available packages and DE were different from the one I managed to install through SD card and netboot installer. The url version didn't have MATE, for instance, and a weird "vanilla Gnome desktop" I choose but was not good.
I don't know if it makes sense, and if I'm making a correct assumption, but is seemed to me that the build with the url has a problem and the netboot img doesn't. Or maybe it is related to some problem with the servers and I'm mixing all things together.

[specs]

I'm a little stuck at petitboot.
To play with the netboot installation images I installed a recent verion.

I tried starting the stock Ubuntu 18.04 from petitboot without succes.
Starting directly from eMMC everything works.
Starting via petitboot the monitor does not work (monitor stays black).

There are a few differences, but assuming the same kernel and initrd are used I expect the problem to be the cmdline.
The difference in cmdline boils down to

Code: Select all

> root=/dev/mmcblk0p2
> hdmimode=1080i60hz
==========
< root=UUID=e139XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
< hdmimode=custombuilt
< modeline=1920,1080,148500,67500,60,1920,2008,2052,2200,1080,1084,1089,1125,1,1,1

Since the system starts I concluded the root= part is not an issue.
Changing the cmdline to hdmimode=720p60hz does not solve the issue.
I do use that mode for petitboot itself.

Is there way to submit a corrected cmdline to petitboot without typing the complete modeline?
Perhaps any other hints?

(With the stock version working from petitboot I hoped to be able to start with the netboot version of Ubuntu 20.04 and the 5.x-kernels.)

Regards.

The complete working cmdline

Code: Select all

root=UUID=e139XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rootwait rw console=ttyS0,115200n8  no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=custombuilt cvbsmode=576cvbs max_freq_a53=1896 max_freq_a73=1800 maxcpus=6 voutmode=hdmi modeline=1920,1080,148500,67500,60,1920,2008,2052,2200,1080,1084,1089,1125,1,1,1 disablehpd=false cvbscable= overscan=100  monitor_onoff=false logo=osd0,loaded hdmitx=cec3f sdrmode=auto

[tobetter]

I'm a little stuck at petitboot.
To play with the netboot installation images I installed a recent verion.

I tried starting the stock Ubuntu 18.04 from petitboot without succes.
Starting directly from eMMC everything works.
Starting via petitboot the monitor does not work (monitor stays black).

There are a few differences, but assuming the same kernel and initrd are used I expect the problem to be the cmdline.
The difference in cmdline boils down to

Code: Select all

> root=/dev/mmcblk0p2
> hdmimode=1080i60hz
==========
< root=UUID=e139XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
< hdmimode=custombuilt
< modeline=1920,1080,148500,67500,60,1920,2008,2052,2200,1080,1084,1089,1125,1,1,1

Since the system starts I concluded the root= part is not an issue.
Changing the cmdline to hdmimode=720p60hz does not solve the issue.
I do use that mode for petitboot itself.

Is there way to submit a corrected cmdline to petitboot without typing the complete modeline?
Perhaps any other hints?

(With the stock version working from petitboot I hoped to be able to start with the netboot version of Ubuntu 20.04 and the 5.x-kernels.)

Regards.

The complete working cmdline

Code: Select all

root=UUID=e139XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rootwait rw console=ttyS0,115200n8  no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=custombuilt cvbsmode=576cvbs max_freq_a53=1896 max_freq_a73=1800 maxcpus=6 voutmode=hdmi modeline=1920,1080,148500,67500,60,1920,2008,2052,2200,1080,1084,1089,1125,1,1,1 disablehpd=false cvbscable= overscan=100  monitor_onoff=false logo=osd0,loaded hdmitx=cec3f sdrmode=auto

Can you try with the version 20191127?
Also, can you please get the output with the command $ cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap when you are able to boot and have time?

[specs]

Code: Select all

$ cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
480p60hz
720p60hz
1080i60hz
1080p60hz*

Will try 20191127 soon.

[specs]

Tried 20191127.
This version uses the modeline, starts correctly, but also does not show anything on the monitor.
Therefore I can't think what the problem is.

I could try to install the default odroid kernel again, perhaps I missed some kernel option.
Or I need to obtain a standard kernel configuration somewhere...

I included the output from the serial console from the 20191127 version and the (working) emmc version.
The logfiles are edited for readability and a little privacy, but I think most of the boot sequence is there.

[tobetter]

Tried 20191127.
This version uses the modeline, starts correctly, but also does not show anything on the monitor.
Therefore I can't think what the problem is.

I could try to install the default odroid kernel again, perhaps I missed some kernel option.
Or I need to obtain a standard kernel configuration somewhere...

I included the output from the serial console from the 20191127 version and the (working) emmc version.
The logfiles are edited for readability and a little privacy, but I think most of the boot sequence is there.

Thanks, can you try to change the values like this in the boot.ini. It would be great if you can try the version 20191127 and the latest one.

Code: Select all

setenv display_autodetect "false"
setenv hdmimode "1080p60hz"
setenv disablehpd "true"

[specs]

Changing the commandline in 20191127 does not change anything, unfortunately.
Also changing the boot.ini does not change anything for the eMMC boot.

Current cmdline

Code: Select all

root=UUID=e139XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rootwait rw console=ttyS0,115200n8  no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=1080p60hz cvbsmode=576cvbs max_freq_a53=1896 max_freq_a73=1800 maxcpus=6 voutmode=hdmi  disablehpd=true cvbscable= overscan=100  monitor_onoff=false logo=osd0,loaded hdmitx=cec3f sdrmode=auto

I think if it does not work for the 20191117 it will not work for the 10200224 version.
On the output from bot versions I found the autodetect to work correctly (which surpirised me a little).

[tobetter]

20200508 - Recommened only for Android-based OS users.

I've urgently built a new version of the Petitboot for the booting issue after updating the very recent Android-based OS, Hardkernel's AOSP Android or LineageOS. In order to update the image, please click spiboot-20200508.img to download and copy the file to your uSD card as spiboot.img.
https://wiki.odroid.com/odroid-n2/os_im ... grade_mode

What's improved:

Android/LineageOS booting failure is fixed
Reported by a couple of users who recently updated their OS image based on Hardkernel's Android OS (v20200507), this issue is caused by the boot script made in the new version and the new boot script was not properly recognized by the Petitboot.
https://wiki.odroid.com/odroid-n2/os_im ... 4_20200507

Default PXE boot script to download the Netboot Installer menu is included.
PXE boot is supported since version 20200224, my own repository server can provide the Debian/Ubuntu Netboot Installer using PXE boot, this will help you to install the clean OS to your memory card instead of flashing an OS image to an uSD or eMMC. The Netboot Installer will appear in the Petitboot menu after running netboot_default in the command line of the Petitboot, you must ensure the ethernet connection and IP address must be set before proceeding. Downloading the Netboot Installer menu and displaying them to the Petitboot could take a couple of minutes. Please refer to another thread about Netboot Installer and what you can install with it.
viewtopic.php?f=182&t=37109

IR/CEC suspend/wakeup is being improved for CoreELEC. - Still testing, not mature yet
One of the issues of the Petitboot is that the CoreELEC cannot make suspend mode when booted by the Petitboot. This is because the CoreELEC uses its own custom bootloader from Hardkernel's one, recently the CoreELEC team gratefully made an update on the bootloader code and can be adapted to the Petitboot bootloader. Still, this is testing with more hardware and it also requires changing the kernel driver, so it would take some time to complete.

Please keep sharing your experience with the Petitboot.

[invenis]

Android/LineageOS booting failure is finxed
Reported by a couple of users who recently updated their OS image based on Hardkernel's Android OS (v20200507), this issue is caused by the boot script made in the new version and the new boot script was not properly recognized by the Petitboot.
https://wiki.odroid.com/odroid-n2/os_im ... 4_20200507

Now it is working, thank you for the quick response.
The only problem is that I need to power off N2 before booting Android - but this is not a big problem for me (tested on Lineage 16 beta 0.1).
Scenario that doesn't work:
Ubuntu desktop -> restart -> Petitboot -> select Android -> stuck at HardKernel logo
Android desktop -> restart -> Petitboot -> select Android -> stuck at HardKernel logo
The scenario that works:
Ubuntu desktop -> restart -> Petiboot -> select Ubuntu -> Ubuntu desktop

[tobetter]

Android/LineageOS booting failure is finxed
Reported by a couple of users who recently updated their OS image based on Hardkernel's Android OS (v20200507), this issue is caused by the boot script made in the new version and the new boot script was not properly recognized by the Petitboot.
https://wiki.odroid.com/odroid-n2/os_im ... 4_20200507

Now it is working, thank you for the quick response.
The only problem is that I need to power off N2 before booting Android - but this is not a big problem for me (tested on Lineage 16 beta 0.1).
Scenario that doesn't work:
Ubuntu desktop -> restart -> Petitboot -> select Android -> stuck at HardKernel logo
Android desktop -> restart -> Petitboot -> select Android -> stuck at HardKernel logo
The scenario that works:
Ubuntu desktop -> restart -> Petiboot -> select Ubuntu -> Ubuntu desktop

Thanks, I will try to reproduce the issue again.

[invenis]

Android/LineageOS booting failure is finxed
Reported by a couple of users who recently updated their OS image based on Hardkernel's Android OS (v20200507), this issue is caused by the boot script made in the new version and the new boot script was not properly recognized by the Petitboot.
https://wiki.odroid.com/odroid-n2/os_im ... 4_20200507

Now it is working, thank you for the quick response.
The only problem is that I need to power off N2 before booting Android - but this is not a big problem for me (tested on Lineage 16 beta 0.1).
Scenario that doesn't work:
Ubuntu desktop -> restart -> Petitboot -> select Android -> stuck at HardKernel logo
Android desktop -> restart -> Petitboot -> select Android -> stuck at HardKernel logo
The scenario that works:
Ubuntu desktop -> restart -> Petiboot -> select Ubuntu -> Ubuntu desktop

Thanks, I will try to reproduce the issue again.

You don't have to reproduce. I have updated Lineage 16.0 to the latest version (beta 0.2) and booting Android after restart from Android/Ubuntu has started working.
No power off needed. Thank you!

[minoccio]

20200508 - Recommened only for Android-based OS users.

I've urgently built a new version of the Petitboot for the booting issue after updating the very recent Android-based OS, Hardkernel's AOSP Android or LineageOS. In order to update the image, please click spiboot-20200508.img to download and copy the file to your uSD card as spiboot.img.
https://wiki.odroid.com/odroid-n2/os_im ... grade_mode

What's improved:

Android/LineageOS booting failure is fixed
Reported by a couple of users who recently updated their OS image based on Hardkernel's Android OS (v20200507), this issue is caused by the boot script made in the new version and the new boot script was not properly recognized by the Petitboot.
https://wiki.odroid.com/odroid-n2/os_im ... 4_20200507

Default PXE boot script to download the Netboot Installer menu is included.
PXE boot is supported since version 20200224, my own repository server can provide the Debian/Ubuntu Netboot Installer using PXE boot, this will help you to install the clean OS to your memory card instead of flashing an OS image to an uSD or eMMC. The Netboot Installer will appear in the Petitboot menu after running netboot_default in the command line of the Petitboot, you must ensure the ethernet connection and IP address must be set before proceeding. Downloading the Netboot Installer menu and displaying them to the Petitboot could take a couple of minutes. Please refer to another thread about Netboot Installer and what you can install with it.
viewtopic.php?f=182&t=37109

IR/CEC suspend/wakeup is being improved for CoreELEC. - Still testing, not mature yet
One of the issues of the Petitboot is that the CoreELEC cannot make suspend mode when booted by the Petitboot. This is because the CoreELEC uses its own custom bootloader from Hardkernel's one, recently the CoreELEC team gratefully made an update on the bootloader code and can be adapted to the Petitboot bootloader. Still, this is testing with more hardware and it also requires changing the kernel driver, so it would take some time to complete.

Please keep sharing your experience with the Petitboot.

Hi. I have LineageOS on uSD and coreelec on eMMC. All was working with petitboot 20191127, and coreelec went correctly in suspend mode. After latest LineageOS upgrade, I upgraded petitboot from 20191127 to 20200508. Now when I try to suspend coreelec, it reboots.