Petitboot, yet another bootloader based on KEXEC

Post Reply
mxmilkb
Posts: 64
Joined: Fri Apr 26, 2019 9:28 am
languages_spoken: English
ODROIDs: N2
Has thanked: 23 times
Been thanked: 21 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by mxmilkb »

Looking at wikipedia; "In television and consumer media, 3840 × 2160 (4K UHD) is the dominant 4K standard, whereas the movie projection industry uses 4096 × 2160 (DCI 4K)."

Sav
Posts: 213
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 57 times
Been thanked: 21 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sav »

mxmilkb wrote:
Fri May 22, 2020 11:18 pm
Looking at wikipedia; "In television and consumer media, 3840 × 2160 (4K UHD) is the dominant 4K standard, whereas the movie projection industry uses 4096 × 2160 (DCI 4K)."
OT: something like this
https://it.jvc.com/pro/videoproiettori- ... DLA-RS640/

User avatar
rooted
Posts: 8043
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 724 times
Been thanked: 255 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by rooted »


tobetter wrote:
ricklar wrote:
Fri May 22, 2020 4:58 pm
tobetter wrote:
Tue May 19, 2020 5:05 pm
@gentillo, by any chance, if you had flashed CE Nightly Build, you should try another version 20200511. Recently I acknowledged that CE team changed their boot script and it is applied to the nightly build.
http://ppa.linuxfactory.or.kr/images/pe ... 200511.img
Thank you, this Petitboot 20200511 version works with Nightly CoreELEC. Still have the problem of Black_screen after reboot with both CE and Android with my 4k Vizio TV, think the problem is because TV has the additional setting of 4096x2160p24 than the standard 4K of 3840x2160p60, it is not big issue can easily change <TV HDMI-input> then switch back to Odroid-N2 input and TV resets resolution to be correct 2160p and screen is viewable again.
Thank you for sharing your experience, I am a bit surprised that your TV resolution is 4096x2160p24... :o
One of my TV's supports 4096x2160p up to 30hz, the other I got a couple weeks ago supports 4096x2160p24.

EDID: http://ix.io/2n0J

New TV:
Image

Going by the EDID of the new TV it seems to fully support 4096x2160 at all frequencies.

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

I updated via OTA from "odroidn2-55-64bit-20200507" to "odroidn2-58-64bit-20200520" and everything went OK. But my problem using Petitboot is still present, it does not boot Android when it's installed on (Sandisk) uSD card, with CoreElec 9.2.2 installed on eMMC.
Android boots OK when SPI switch is in right (eMMC) position, but if I flip the switch to left (SPI) position and choose to boot Android, it does not work. Petitboot reboots and N2 gets stuck at black Hardkernel logo, with no power on USB ports: the same behavior as with fresh install of former "odroidn2-55-64bit-20200507" version.
This happens with both latest Petitboot versions "spiboot-20200508.img" and "spiboot-20200511.img".

With CoreElec 9.2.2 on eMMC and CoreElec nightly on uSD card Petitboot works OK and I can boot any OS I choose.
These users thanked the author Sholander for the post (total 2):
Rmiino (Sun May 24, 2020 10:38 pm) • miro002 (Fri May 29, 2020 4:32 pm)

User avatar
wrxtasy
Posts: 1304
Joined: Wed May 13, 2015 1:59 pm
languages_spoken: english
ODROIDs: C1, C1+, C2, N2
Location: Australia
Has thanked: 3 times
Been thanked: 4 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by wrxtasy »

I've just been playing around with Petitboot as well - using - dev.20200224.
Switch in Left position, eMMC (Android) is recognised and presented as a boot option.... but

I too cannot get it to recognise a microSDHC with a known working CoreELEC image on it.
I swear this was working last time I tested, some months ago.

EDIT: used spiboot-20200511.img @tobetter supplied in previous page and Petitboot working again.

I REALLY wished the default boot behavior of the N2 (without Petitboot) was....

With both microSDHC & eMMC inserted--- > microSDHC had boot priority.
I do not know why HardKernel does this differently vs other AMLogic devices ?
Last edited by wrxtasy on Fri May 29, 2020 7:35 pm, edited 1 time in total.
Kodi Hardware Guru

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

Did you try with newer Petitboot versions https://bit.ly/35FYNWb (20200508) and http://ppa.linuxfactory.or.kr/images/pe ... 200511.img, which are not in official archive, but are reworked to work with new Android versions and CE nightlies ?

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

Sholander wrote:
Sun May 24, 2020 9:48 pm
I updated via OTA from "odroidn2-55-64bit-20200507" to "odroidn2-58-64bit-20200520" and everything went OK. But my problem using Petitboot is still present, it does not boot Android when it's installed on (Sandisk) uSD card, with CoreElec 9.2.2 installed on eMMC.
Android boots OK when SPI switch is in right (eMMC) position, but if I flip the switch to left (SPI) position and choose to boot Android, it does not work. Petitboot reboots and N2 gets stuck at black Hardkernel logo, with no power on USB ports: the same behavior as with fresh install of former "odroidn2-55-64bit-20200507" version.
This happens with both latest Petitboot versions "spiboot-20200508.img" and "spiboot-20200511.img".

With CoreElec 9.2.2 on eMMC and CoreElec nightly on uSD card Petitboot works OK and I can boot any OS I choose.
@tobetter Just to inform you, I solved my Android Petitboot problem :mrgreen:

Since my USB-UART adapter is still on the way, or lost somewhere, I took some time to make new tests. First I used "SPI Recovery Image" with replaced original spiboot.img with latest version ( 20200511) to wipe all SPI data and start fresh. Got latest Petitboot version, but no change - Android still did not start. Then I put latest Petitboot version on my Android uSD card and updated SPI-Petitboot again. And THAT has fixed everything. Now both my Android versions boot OK via Petitboot with CoreElec on eMMC. (The eMMC module was disconnected all the time while updating Petitboot)

So, putting spiboot.img on a working 64bit Android installation on uSD and updating - fixed everything. Before I ALWAYS used my CoreElec uSD installation for updating Petitboot, and have not seen anywhere that there should be any difference. I think that it has to do with different u-boot versions from these OSs, but not sure if that is the only reason...

lightsout
Posts: 87
Joined: Wed Aug 28, 2019 5:26 am
languages_spoken: english
Has thanked: 3 times
Been thanked: 4 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by lightsout »

Hmmm, that's weird, I always use the uSD, where android is, to update petiboot. Still have the issue, been a while since I tested but I think I am on the recent petiboot release.

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

Yes, weird... On uSD card that you use to update Petitboot 20200511 what version of Android is installed?
On my uSD card, with which I fixed dual boot, I have a fresh installation of "selfinstall-odroidn2-58-64bit-20200520" image; burned the card with Etcher, finished Android installation and my settings with only uSD card inserted on N2; eMMC module was removed.

lightsout
Posts: 87
Joined: Wed Aug 28, 2019 5:26 am
languages_spoken: english
Has thanked: 3 times
Been thanked: 4 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by lightsout »

Sholander wrote:
Sun May 31, 2020 2:36 am
Yes, weird... On uSD card that you use to update Petitboot 20200511 what version of Android is installed?
On my uSD card, with which I fixed dual boot, I have a fresh installation of "selfinstall-odroidn2-58-64bit-20200520" image; burned the card with Etcher, finished Android installation and my settings with only uSD card inserted on N2; eMMC module was removed.
I'll look into it, I am using one of the Android TV roms from the forum here. I think the dev's name is Secuflag?

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

Just today I fresh installed his new R.11 ATV version (works perfect :), but did not use that uSD card to update Petitboot...
I think the point is to use a new version of Android, one with new black Hardkernel logo...

lightsout
Posts: 87
Joined: Wed Aug 28, 2019 5:26 am
languages_spoken: english
Has thanked: 3 times
Been thanked: 4 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by lightsout »

I didn't realize there were newer versions of petiboot floating around, I guess its like madvr you have to read the whole thread or you miss releases. Updating to 0511 now.

lightsout
Posts: 87
Joined: Wed Aug 28, 2019 5:26 am
languages_spoken: english
Has thanked: 3 times
Been thanked: 4 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by lightsout »

I got it working, oddly when I switched over to emmc, it tried to boot from Android on the SD card and failed every time
in an endless boot cycle. It's been doing that for me for a while now.

Doesn't matter though because Coreelec is running great, don't even know why I am messing with Android I never use it.

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

lightsout wrote:
Sun May 31, 2020 3:55 am
I didn't realize there were newer versions of petiboot floating around, I guess its like madvr you have to read the whole thread or you miss releases.
Yes, it's also not clear to me why the latest official version on Wiki is from February (20200224), which does NOT work with new Android versions.
Don't see any reason why the new version 20200511 is not there since on new Android versions this is listed as a known issue "Petitboot User need to update next version". To find this "next" version you have to dig into this thread. Pretty sloppy in my opinion...

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

Sholander wrote:
Sun May 31, 2020 6:43 pm
lightsout wrote:
Sun May 31, 2020 3:55 am
I didn't realize there were newer versions of petiboot floating around, I guess its like madvr you have to read the whole thread or you miss releases.
Yes, it's also not clear to me why the latest official version on Wiki is from February (20200224), which does NOT work with new Android versions.
Don't see any reason why the new version 20200511 is not there since on new Android versions this is listed as a known issue "Petitboot User need to update next version". To find this "next" version you have to dig into this thread. Pretty sloppy in my opinion...
Sorry for the inconvenient. It's because I didn't update the 20200511 version which is not tested and I wanted to fix a couple of minor issues including the uSD issues after version 20200508, meantime Android is released. So I've updated the Wiki and my repository to provide the upgrade image.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

lightsout wrote:
Sun May 31, 2020 7:04 am
I got it working, oddly when I switched over to emmc, it tried to boot from Android on the SD card and failed every time
in an endless boot cycle. It's been doing that for me for a while now.

Doesn't matter though because Coreelec is running great, don't even know why I am messing with Android I never use it.
I found the bug in U-boot that happens when CE sits in eMMC and Android in uSD. It's been fixed and the patch is submitted to CE U-boot, I believe next nightly build will have the fix.

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

tobetter wrote:
Mon Jun 01, 2020 10:42 am
I found the bug in U-boot that happens when CE sits in eMMC and Android in uSD. It's been fixed and the patch is submitted to CE U-boot, I believe next nightly build will have the fix.
I'm glad and happy that this has been finally sorted out, began to worry that my N2 is at fault...
Thanx for your help, and keep up your great work, as it makes us all happy :mrgreen:

alex_nemo
Posts: 1
Joined: Thu Apr 05, 2018 6:50 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by alex_nemo »

Please, compile 2 version PetitBoot: with and without LAN/PXE! Or that there would be an opportunity to prohibit downloading over the network (PXE)!
Is it possible to use alternative bootloaders - Grub(2) or Lilo?!!

mad_ady
Posts: 8582
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 578 times
Been thanked: 486 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by mad_ady »

Maybe eth0 state can be set through an env or boot.ini parameter insted.

LILO has been dead for 15 years now, why ressurect it? And grub is nice, but petitboot is nicer (imho) since it gives you full linux userspace in the bootloader.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

alex_nemo wrote:Please, compile 2 version PetitBoot: with and without LAN/PXE! Or that there would be an opportunity to prohibit downloading over the network (PXE)!
Is it possible to use alternative bootloaders - Grub(2) or Lilo?!!
Sorry, I don't get what's the matter having PXE on the Petitboot. PXE only works when you enable it or your DHCP server support for it.

"Tapatalk wishes you to have fun with ODROID"


lightsout
Posts: 87
Joined: Wed Aug 28, 2019 5:26 am
languages_spoken: english
Has thanked: 3 times
Been thanked: 4 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by lightsout »

Sholander wrote:
tobetter wrote:
Mon Jun 01, 2020 10:42 am
I found the bug in U-boot that happens when CE sits in eMMC and Android in uSD. It's been fixed and the patch is submitted to CE U-boot, I believe next nightly build will have the fix.
I'm glad and happy that this has been finally sorted out, began to worry that my N2 is at fault...
Thanx for your help, and keep up your great work, as it makes us all happy :mrgreen:
Great indeed. I was thinking the same thing that maybe the N2 was faulty. Thanks OP!

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

Just for the record, the Petitboot 20191127 has been hit 1000 downloads. :mrgreen:
Screenshot from 2020-06-04 13-00-53.png
Screenshot from 2020-06-04 13-00-53.png (30.73 KiB) Viewed 3053 times
And next stable version 20200224 hits 700+.
Screenshot from 2020-06-04 11-05-49.png
Screenshot from 2020-06-04 11-05-49.png (48 KiB) Viewed 3053 times
Thanks for downloading and sorry for the pending issues still not resolved yet. :(
These users thanked the author tobetter for the post (total 9):
rooted (Thu Jun 04, 2020 1:17 pm) • mad_ady (Thu Jun 04, 2020 2:21 pm) • minoccio (Thu Jun 04, 2020 5:22 pm) • odroid (Thu Jun 04, 2020 5:52 pm) • secuflag (Thu Jun 04, 2020 6:10 pm) • istanbulls (Thu Jun 04, 2020 7:39 pm) • bright_plastik (Fri Jun 05, 2020 4:04 am) • Sav (Fri Jun 05, 2020 7:53 pm) • alphahere (Sat Jun 06, 2020 12:55 am)

mad_ady
Posts: 8582
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 578 times
Been thanked: 486 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by mad_ady »

Great job!

User avatar
istanbulls
Posts: 297
Joined: Tue May 14, 2019 10:18 pm
languages_spoken: Turkish
ODROIDs: ODROID-N2, ODROID C4
Location: Istanbul-Turkey
Has thanked: 189 times
Been thanked: 39 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by istanbulls »

Congratulations,
For my N2, PETITBOOT is a my must-have.
These users thanked the author istanbulls for the post:
rpineau (Fri Jun 05, 2020 11:53 am)

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

Hi,

I have just bought an Odroid N2 and I wanted to boot using Petitboot, I have already installed in my Odroid the version : spiboot-20200511.img .

I want to boot from SPI and then start Ubuntu from the SSD (256 GB) that is connected through USB adapter.

Can anyone provide me some guidance how to flash or generate the partitions of the SSD drive in order to work with Petitboot?

Thanks!

mad_ady
Posts: 8582
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 578 times
Been thanked: 486 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by mad_ady »

Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

nicoraf wrote:
Mon Jun 08, 2020 6:51 am
mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.
If your display is not 4K, try to change the value "display_autodetect" as "false" .

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

tobetter wrote:
Mon Jun 08, 2020 8:55 am
nicoraf wrote:
Mon Jun 08, 2020 6:51 am
mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.
If your display is not 4K, try to change the value "display_autodetect" as "false" .
Hi, Thank you very much, you were right. It was the monitor. It is interesting, I have an 2k monitor that worked with the SD cards , but it didn't work with the USB SSD disk.

So I changed "display_autodetect" as "false" and it worked. However the partition isnt working at the SSD, there are problems of configuration and even I cannot do anything when it is Ubuntu open. Do you know what else I have to change? Thanks!!!

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

nicoraf wrote:
Tue Jun 09, 2020 4:40 am
tobetter wrote:
Mon Jun 08, 2020 8:55 am
nicoraf wrote:
Mon Jun 08, 2020 6:51 am
mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.
If your display is not 4K, try to change the value "display_autodetect" as "false" .
Hi, Thank you very much, you were right. It was the monitor. It is interesting, I have an 2k monitor that worked with the SD cards , but it didn't work with the USB SSD disk.

So I changed "display_autodetect" as "false" and it worked. However the partition isnt working at the SSD, there are problems of configuration and even I cannot do anything when it is Ubuntu open. Do you know what else I have to change? Thanks!!!
I changed from boot.ini : "root=/dev/sda2 " and it worked:

# Boot Args
setenv bootargs "root=/dev/sda2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

I wonder if that is the most correct way . thanks

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

nicoraf wrote:
Tue Jun 09, 2020 4:57 am
nicoraf wrote:
Tue Jun 09, 2020 4:40 am
tobetter wrote:
Mon Jun 08, 2020 8:55 am
nicoraf wrote:
Mon Jun 08, 2020 6:51 am
mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.
If your display is not 4K, try to change the value "display_autodetect" as "false" .
Hi, Thank you very much, you were right. It was the monitor. It is interesting, I have an 2k monitor that worked with the SD cards , but it didn't work with the USB SSD disk.

So I changed "display_autodetect" as "false" and it worked. However the partition isnt working at the SSD, there are problems of configuration and even I cannot do anything when it is Ubuntu open. Do you know what else I have to change? Thanks!!!
I changed from boot.ini : "root=/dev/sda2 " and it worked:

# Boot Args
setenv bootargs "root=/dev/sda2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

I wonder if that is the most correct way . thanks
Your display issue is because of Linux kernel, not your SSD. Since when you boot your OS with the Petitboot, the Linux kernel runs twice and HDMI is not working properly with a certain display device that is not resolved yet. Therefore, I am helping the Petitboot users when they meet the same issue.

If you OS runs after changing root=/dev/sda2, please go ahead...it's ok. Just what I am not sure is why the Petitboot does not handle the root file system properly. I assume that the UUID for your root partition is different between one in boot.ini and actual UUID of your SSD. Can you please do run this command sudo blkid and cat /media/boot/boot.ini | grep UUID to share the output once you boot to your OS in SSD?
These users thanked the author tobetter for the post:
nicoraf (Tue Jun 09, 2020 7:35 pm)

Tassadar
Posts: 27
Joined: Sun Aug 18, 2019 7:04 pm
languages_spoken: english
ODROIDs: C2, XU4, N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Tassadar »

As of Petitboot version 20200224, where does it store its configuration? Found nothing relevant on the first partition of uSD card.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

Tassadar wrote:
Wed Jun 10, 2020 12:42 am
As of Petitboot version 20200224, where does it store its configuration? Found nothing relevant on the first partition of uSD card.
It's been stored in the SPI flash memory itself.
These users thanked the author tobetter for the post:
Tassadar (Wed Jun 10, 2020 3:22 am)

User avatar
CoolGames
Posts: 108
Joined: Sun Nov 24, 2019 3:07 am
languages_spoken: english
ODROIDs: Dec 25 N2
Has thanked: 18 times
Been thanked: 14 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by CoolGames »

Odroid N2 is usable as Ubuntu set top TV box system
Where is BOOT.INI to set FALSE display_autodetect ?

I have used pb-event for installing and don't see a boot.ini in /boot so as to change display_autodetect to false.
I still have to constantly flip HDMI1 on HDTV for BBY Insignia 22 inch 1080p 60hz to display output of N2.
This log also shows trying to sync by unplugging HDMI and re-plugging.
Also using with Turtle Beach USB wireless headphones because 3.5mm not usable.
Xorg.0.log
Xorg.0.log from Odroid N2 unable to sustain sync for BBY Insignia 1080p HDTV.
(72.3 KiB) Downloaded 20 times
Keyboard and mouse is OTG 2.0 with 2.4ghz dongle Insignia NS-PNC6011.
It is the only thing I am unable to eliminate for comfortable Ubuntu 20.04 5.7.1-202006082232 Mate desktop system.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

CoolGames wrote:
Wed Jun 10, 2020 3:22 am
Odroid N2 is usable as Ubuntu set top TV box system
Where is BOOT.INI to set FALSE display_autodetect ?

I have used pb-event for installing and don't see a boot.ini in /boot so as to change display_autodetect to false.
I still have to constantly flip HDMI1 on HDTV for BBY Insignia 22 inch 1080p 60hz to display output of N2.
This log also shows trying to sync by unplugging HDMI and re-plugging.
Also using with Turtle Beach USB wireless headphones because 3.5mm not usable.
Xorg.0.log

Keyboard and mouse is OTG 2.0 with 2.4ghz dongle Insignia NS-PNC6011.
It is the only thing I am unable to eliminate for comfortable Ubuntu 20.04 5.7.1-202006082232 Mate desktop system.
display_autodetect is the kernel options supported only with 4.9 kernel, not for 5.x kernel. From the log attached, I think you are not using mali-bifrost-wayland driver but use native fbdev driver, no GPU accelerated. Do you have to use 5.x kernel or 4.9 kernel is fine?

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

tobetter wrote:
Wed Jun 10, 2020 2:49 am
Tassadar wrote:
Wed Jun 10, 2020 12:42 am
As of Petitboot version 20200224, where does it store its configuration? Found nothing relevant on the first partition of uSD card.
It's been stored in the SPI flash memory itself.
for me the option configuration save isn't working, or at least I did't make it work. I have Petitboot dev. 20200511 , if I turn of the Odroid N2 , it takes a long time to detect the USB SSD attached, but then I go to System Configuration and change , Boot Order, to only boot to the disk , and timeout to 3 seconds. When I press ok and go back to system configuration it appears with the previous options.

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

tobetter wrote:
Tue Jun 09, 2020 2:11 pm
nicoraf wrote:
Tue Jun 09, 2020 4:57 am
nicoraf wrote:
Tue Jun 09, 2020 4:40 am
tobetter wrote:
Mon Jun 08, 2020 8:55 am
nicoraf wrote:
Mon Jun 08, 2020 6:51 am
mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.
If your display is not 4K, try to change the value "display_autodetect" as "false" .
Hi, Thank you very much, you were right. It was the monitor. It is interesting, I have an 2k monitor that worked with the SD cards , but it didn't work with the USB SSD disk.

So I changed "display_autodetect" as "false" and it worked. However the partition isnt working at the SSD, there are problems of configuration and even I cannot do anything when it is Ubuntu open. Do you know what else I have to change? Thanks!!!
I changed from boot.ini : "root=/dev/sda2 " and it worked:

# Boot Args
setenv bootargs "root=/dev/sda2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

I wonder if that is the most correct way . thanks
Your display issue is because of Linux kernel, not your SSD. Since when you boot your OS with the Petitboot, the Linux kernel runs twice and HDMI is not working properly with a certain display device that is not resolved yet. Therefore, I am helping the Petitboot users when they meet the same issue.

If you OS runs after changing root=/dev/sda2, please go ahead...it's ok. Just what I am not sure is why the Petitboot does not handle the root file system properly. I assume that the UUID for your root partition is different between one in boot.ini and actual UUID of your SSD. Can you please do run this command sudo blkid and cat /media/boot/boot.ini | grep UUID to share the output once you boot to your OS in SSD?
I send you the outputs.

Code: Select all

odroid@odroid:~$ sudo blkid

/dev/sda1: SEC_TYPE="msdos" LABEL="BOOT" UUID="F702-39CB" TYPE="vfat" PARTUUID="03823826-01"
/dev/sda2: LABEL="rootfs" UUID="e139ce78-9841-40fe-8823-96a304a09859" TYPE="ext4" PARTUUID="03823826-02"

Code: Select all

odroid@odroid:~$ sudo cat /media/boot/boot.ini  
ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyS0,115200n8"   # on both

# Auto Detection of Monitor settings based on your Screen information
setenv display_autodetect "false"

# HDMI Mode
# Resolution Configuration
#    Symbol             | Resolution
# ----------------------+-------------
#    "480x272p60hz"     | 480x272 Progressive 60Hz
#    "480x320p60hz"     | 480x320 Progressive 60Hz
#    "480p60hz"         | 720x480 Progressive 60Hz
#    "576p50hz"         | 720x576 Progressive 50Hz
#    "720p60hz"         | 1280x720 Progressive 60Hz
#    "720p50hz"         | 1280x720 Progressive 50Hz
#    "1080p60hz"        | 1920x1080 Progressive 60Hz
#    "1080p50hz"        | 1920x1080 Progressive 50Hz
#    "1080p30hz"        | 1920x1080 Progressive 30Hz
#    "1080p24hz"        | 1920x1080 Progressive 24Hz
#    "1080i60hz"        | 1920x1080 Interlaced 60Hz
#    "1080i50hz"        | 1920x1080 Interlaced 50Hz
#    "2160p60hz"        | 3840x2160 Progressive 60Hz
#    "2160p50hz"        | 3840x2160 Progressive 50Hz
#    "2160p30hz"        | 3840x2160 Progressive 30Hz
#    "2160p25hz"        | 3840x2160 Progressive 25Hz
#    "2160p24hz"        | 3840x2160 Progressive 24Hz
#    "smpte24hz"        | 3840x2160 Progressive 24Hz SMPTE
#    "2160p60hz420"     | 3840x2160 Progressive 60Hz YCbCr 4:2:0
#    "2160p50hz420"     | 3840x2160 Progressive 50Hz YCbCr 4:2:0
#    "640x480p60hz"     | 640x480 Progressive 60Hz
#    "800x480p60hz"     | 800x480 Progressive 60Hz
#    "800x600p60hz"     | 800x600 Progressive 60Hz
#    "1024x600p60hz"    | 1024x600 Progressive 60Hz
#    "1024x768p60hz"    | 1024x768 Progressive 60Hz
#    "1280x800p60hz"    | 1280x800 Progressive 60Hz
#    "1280x1024p60hz"   | 1280x1024 Progressive 60Hz
#    "1360x768p60hz"    | 1360x768 Progressive 60Hz
#    "1440x900p60hz"    | 1440x900 Progressive 60Hz
#    "1600x900p60hz"    | 1600x900 Progressive 60Hz
#    "1600x1200p60hz"   | 1600x1200 Progressive 60Hz
#    "1680x1050p60hz"   | 1680x1050 Progressive 60Hz
#    "1920x1200p60hz"   | 1920x1200 Progressive 60Hz
#    "2560x1080p60hz"   | 2560x1080 Progressive 60Hz
#    "2560x1440p60hz"   | 2560x1440 Progressive 60Hz
#    "2560x1600p60hz"   | 2560x1600 Progressive 60Hz
#    "3440x1440p60hz"   | 3440x1440 Progressive 60Hz
setenv hdmimode "1080p60hz"

# Monitor output
# Controls if HDMI PHY should output anything to the monitor
setenv monitor_onoff "false" # true or false

# Overscan percentage
# This value scales down the actual screen size by the percentage below
# valid range is 80 to 100
setenv overscan "100"

### voutmode : hdmi or dvi
setenv voutmode "hdmi"
# setenv voutmode "dvi"

# HPD enable/disable option
setenv disablehpd "false"

# Enable/Disable CEC
setenv cec "true"

# Hardkernel ODROID-VU7 support
# By default VU7 support is disabled
setenv disable_vu7 "true"
# setenv disable_vu7 "false"

# max cpu frequency for big core, A73 in MHz unit
# setenv max_freq_a73 "2004"  # 2.004 GHz
# setenv max_freq_a73 "1992"  # 1.992 GHz
# setenv max_freq_a73 "1908"  # 1.908 GHz
setenv max_freq_a73 "1800"  # 1.8 GHz, default value
# setenv max_freq_a73 "1704"  # 1.704 GHz
 
# max cpu frequency for little core, A53 in MHz unit
# setenv max_freq_a53 "1992"  # 1.992 GHz
setenv max_freq_a53 "1896"  # 1.896 GHz, default value
# setenv max_freq_a53 "1704"  # 1.704 GHz


# max cpu-cores
# Note:
# CPU's 0 and 1 are the A53 (small cores)
# CPU's 2 to 5 are the A73 (big cores)
# Lowering this value disables only the bigger cores (the last cores).
# setenv maxcpus "4"
# setenv maxcpus "5"
setenv maxcpus "6"

### Normal HDMI Monitors
if test "${display_autodetect}" = "true"; then hdmitx edid; fi
if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi
if test "${cec}" = "true"; then setenv cec_enable "hdmitx=cec3f"; fi

# VU7 Settings
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi

# Boot Args
setenv bootargs "root=/dev/sda2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

# Set load addresses
setenv dtb_loadaddr "0x1000000"
setenv k_addr "0x1100000"
setenv loadaddr "0x1B00000"
setenv initrd_loadaddr "0x3700000"

# Load kernel, dtb and initrd
fatload mmc ${devno}:1 ${k_addr} Image.gz
fatload mmc ${devno}:1 ${dtb_loadaddr} meson64_odroidn2.dtb
fatload mmc ${devno}:1 ${initrd_loadaddr} uInitrd
fdt addr ${dtb_loadaddr}
# unzip the kernel
unzip ${k_addr} ${loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
I have one question if in my boot.ini I have : "root=/dev/sda2" , I have noted that if I connect the USB SSD drive to another USB 3 Port (of the 4 that the Odroid N2 has ) it doesnt boot anymore. Is that explained because of that configuration ? Thanks

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

Hi , where is the github branch corresponding to the image spiboot-20200511.img ? Thanks!

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

nicoraf wrote:
Wed Jun 10, 2020 5:50 am
tobetter wrote:
Tue Jun 09, 2020 2:11 pm
nicoraf wrote:
Tue Jun 09, 2020 4:57 am
nicoraf wrote:
Tue Jun 09, 2020 4:40 am
tobetter wrote:
Mon Jun 08, 2020 8:55 am
nicoraf wrote:
Mon Jun 08, 2020 6:51 am
mad_ady wrote:
Mon Jun 08, 2020 1:18 am
Just flash the ubuntu image to the ssd with etcher and resize the second partition manually.
I did that (without resizing the second partition) , and if I start odroid n2 with SPI enabled. The disk appears at Petitboot but when I start the boot, it never appears nothing , only a black screen. To clarify it is not related with the "HDMI autoselect resolution" issue because the monitor I have works fine with SD memories without any changes.
If your display is not 4K, try to change the value "display_autodetect" as "false" .
Hi, Thank you very much, you were right. It was the monitor. It is interesting, I have an 2k monitor that worked with the SD cards , but it didn't work with the USB SSD disk.

So I changed "display_autodetect" as "false" and it worked. However the partition isnt working at the SSD, there are problems of configuration and even I cannot do anything when it is Ubuntu open. Do you know what else I have to change? Thanks!!!
I changed from boot.ini : "root=/dev/sda2 " and it worked:

# Boot Args
setenv bootargs "root=/dev/sda2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

I wonder if that is the most correct way . thanks
Your display issue is because of Linux kernel, not your SSD. Since when you boot your OS with the Petitboot, the Linux kernel runs twice and HDMI is not working properly with a certain display device that is not resolved yet. Therefore, I am helping the Petitboot users when they meet the same issue.

If you OS runs after changing root=/dev/sda2, please go ahead...it's ok. Just what I am not sure is why the Petitboot does not handle the root file system properly. I assume that the UUID for your root partition is different between one in boot.ini and actual UUID of your SSD. Can you please do run this command sudo blkid and cat /media/boot/boot.ini | grep UUID to share the output once you boot to your OS in SSD?
I send you the outputs.

Code: Select all

odroid@odroid:~$ sudo blkid

/dev/sda1: SEC_TYPE="msdos" LABEL="BOOT" UUID="F702-39CB" TYPE="vfat" PARTUUID="03823826-01"
/dev/sda2: LABEL="rootfs" UUID="e139ce78-9841-40fe-8823-96a304a09859" TYPE="ext4" PARTUUID="03823826-02"

Code: Select all

odroid@odroid:~$ sudo cat /media/boot/boot.ini  
ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyS0,115200n8"   # on both

# Auto Detection of Monitor settings based on your Screen information
setenv display_autodetect "false"

# HDMI Mode
# Resolution Configuration
#    Symbol             | Resolution
# ----------------------+-------------
#    "480x272p60hz"     | 480x272 Progressive 60Hz
#    "480x320p60hz"     | 480x320 Progressive 60Hz
#    "480p60hz"         | 720x480 Progressive 60Hz
#    "576p50hz"         | 720x576 Progressive 50Hz
#    "720p60hz"         | 1280x720 Progressive 60Hz
#    "720p50hz"         | 1280x720 Progressive 50Hz
#    "1080p60hz"        | 1920x1080 Progressive 60Hz
#    "1080p50hz"        | 1920x1080 Progressive 50Hz
#    "1080p30hz"        | 1920x1080 Progressive 30Hz
#    "1080p24hz"        | 1920x1080 Progressive 24Hz
#    "1080i60hz"        | 1920x1080 Interlaced 60Hz
#    "1080i50hz"        | 1920x1080 Interlaced 50Hz
#    "2160p60hz"        | 3840x2160 Progressive 60Hz
#    "2160p50hz"        | 3840x2160 Progressive 50Hz
#    "2160p30hz"        | 3840x2160 Progressive 30Hz
#    "2160p25hz"        | 3840x2160 Progressive 25Hz
#    "2160p24hz"        | 3840x2160 Progressive 24Hz
#    "smpte24hz"        | 3840x2160 Progressive 24Hz SMPTE
#    "2160p60hz420"     | 3840x2160 Progressive 60Hz YCbCr 4:2:0
#    "2160p50hz420"     | 3840x2160 Progressive 50Hz YCbCr 4:2:0
#    "640x480p60hz"     | 640x480 Progressive 60Hz
#    "800x480p60hz"     | 800x480 Progressive 60Hz
#    "800x600p60hz"     | 800x600 Progressive 60Hz
#    "1024x600p60hz"    | 1024x600 Progressive 60Hz
#    "1024x768p60hz"    | 1024x768 Progressive 60Hz
#    "1280x800p60hz"    | 1280x800 Progressive 60Hz
#    "1280x1024p60hz"   | 1280x1024 Progressive 60Hz
#    "1360x768p60hz"    | 1360x768 Progressive 60Hz
#    "1440x900p60hz"    | 1440x900 Progressive 60Hz
#    "1600x900p60hz"    | 1600x900 Progressive 60Hz
#    "1600x1200p60hz"   | 1600x1200 Progressive 60Hz
#    "1680x1050p60hz"   | 1680x1050 Progressive 60Hz
#    "1920x1200p60hz"   | 1920x1200 Progressive 60Hz
#    "2560x1080p60hz"   | 2560x1080 Progressive 60Hz
#    "2560x1440p60hz"   | 2560x1440 Progressive 60Hz
#    "2560x1600p60hz"   | 2560x1600 Progressive 60Hz
#    "3440x1440p60hz"   | 3440x1440 Progressive 60Hz
setenv hdmimode "1080p60hz"

# Monitor output
# Controls if HDMI PHY should output anything to the monitor
setenv monitor_onoff "false" # true or false

# Overscan percentage
# This value scales down the actual screen size by the percentage below
# valid range is 80 to 100
setenv overscan "100"

### voutmode : hdmi or dvi
setenv voutmode "hdmi"
# setenv voutmode "dvi"

# HPD enable/disable option
setenv disablehpd "false"

# Enable/Disable CEC
setenv cec "true"

# Hardkernel ODROID-VU7 support
# By default VU7 support is disabled
setenv disable_vu7 "true"
# setenv disable_vu7 "false"

# max cpu frequency for big core, A73 in MHz unit
# setenv max_freq_a73 "2004"  # 2.004 GHz
# setenv max_freq_a73 "1992"  # 1.992 GHz
# setenv max_freq_a73 "1908"  # 1.908 GHz
setenv max_freq_a73 "1800"  # 1.8 GHz, default value
# setenv max_freq_a73 "1704"  # 1.704 GHz
 
# max cpu frequency for little core, A53 in MHz unit
# setenv max_freq_a53 "1992"  # 1.992 GHz
setenv max_freq_a53 "1896"  # 1.896 GHz, default value
# setenv max_freq_a53 "1704"  # 1.704 GHz


# max cpu-cores
# Note:
# CPU's 0 and 1 are the A53 (small cores)
# CPU's 2 to 5 are the A73 (big cores)
# Lowering this value disables only the bigger cores (the last cores).
# setenv maxcpus "4"
# setenv maxcpus "5"
setenv maxcpus "6"

### Normal HDMI Monitors
if test "${display_autodetect}" = "true"; then hdmitx edid; fi
if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi
if test "${cec}" = "true"; then setenv cec_enable "hdmitx=cec3f"; fi

# VU7 Settings
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi

# Boot Args
setenv bootargs "root=/dev/sda2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

# Set load addresses
setenv dtb_loadaddr "0x1000000"
setenv k_addr "0x1100000"
setenv loadaddr "0x1B00000"
setenv initrd_loadaddr "0x3700000"

# Load kernel, dtb and initrd
fatload mmc ${devno}:1 ${k_addr} Image.gz
fatload mmc ${devno}:1 ${dtb_loadaddr} meson64_odroidn2.dtb
fatload mmc ${devno}:1 ${initrd_loadaddr} uInitrd
fdt addr ${dtb_loadaddr}
# unzip the kernel
unzip ${k_addr} ${loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
I have one question if in my boot.ini I have : "root=/dev/sda2" , I have noted that if I connect the USB SSD drive to another USB 3 Port (of the 4 that the Odroid N2 has ) it doesnt boot anymore. Is that explained because of that configuration ? Thanks
I think you must change root=/dev/sda2 to root=UUID=e139ce78-9841-40fe-8823-96a304a09859 in your boot.ini, but I doubt you already had the value root=UUID=...? Giving the physical device node to root=* causes the boot failure you had experienced, therefore you must use UUID=... or PARTID=.... Also, you must check if you have the same UUID in the different memory cards.
These users thanked the author tobetter for the post:
nicoraf (Thu Jun 11, 2020 8:52 am)

Tassadar
Posts: 27
Joined: Sun Aug 18, 2019 7:04 pm
languages_spoken: english
ODROIDs: C2, XU4, N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Tassadar »

It turned out that Petitboot version 20200224 mounts all filesystems read-only. I can unmount them, but cannot mount again, because "the device is busy". It complicates things, because I used Petitboot to edit system files to fix a broken configuration.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

Tassadar wrote:
Wed Jun 10, 2020 11:47 pm
It turned out that Petitboot version 20200224 mounts all filesystems read-only. I can unmount them, but cannot mount again, because "the device is busy". It complicates things, because I used Petitboot to edit system files to fix a broken configuration.
What kind of configuration are you trying to fix if required?
I guess you can use ums that will turn a given device as a USB Mass Storage and connect with USB cable. Try to connect your ODROID-N2 with a USB cable (Type A-to-Type Micro B), and run ums /dev/mmcblk0p1 in order to attach the first partition of eMMC to your PC, for example.

mad_ady
Posts: 8582
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 578 times
Been thanked: 486 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by mad_ady »

Doesn't mount -o remount,rw /dev/sda1 work?
These users thanked the author mad_ady for the post:
Tassadar (Thu Jun 11, 2020 2:22 am)

Tassadar
Posts: 27
Joined: Sun Aug 18, 2019 7:04 pm
languages_spoken: english
ODROIDs: C2, XU4, N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Tassadar »

tobetter wrote:
Thu Jun 11, 2020 12:33 am
Tassadar wrote:
Wed Jun 10, 2020 11:47 pm
It turned out that Petitboot version 20200224 mounts all filesystems read-only. I can unmount them, but cannot mount again, because "the device is busy". It complicates things, because I used Petitboot to edit system files to fix a broken configuration.
What kind of configuration are you trying to fix if required?
I guess you can use ums that will turn a given device as a USB Mass Storage and connect with USB cable. Try to connect your ODROID-N2 with a USB cable (Type A-to-Type Micro B), and run ums /dev/mmcblk0p1 in order to attach the first partition of eMMC to your PC, for example.
The idea is to fix the system configuration without additional devices such as PC. I might as well insert the uSD card into the PC card reader and fix it there.

Tassadar
Posts: 27
Joined: Sun Aug 18, 2019 7:04 pm
languages_spoken: english
ODROIDs: C2, XU4, N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Tassadar »

Aha, the entries in the /dev/mapper/ directory must be used, i.e. for the first partition of the uSD card: /dev/mapper/pb-mmcblk1p1, not /dev/mmcblk1p1. The remount command works too, thanks mad_ady!
Last edited by Tassadar on Thu Jun 11, 2020 2:47 am, edited 1 time in total.

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

Tassadar wrote:
Thu Jun 11, 2020 2:09 am
tobetter wrote:
Thu Jun 11, 2020 12:33 am
Tassadar wrote:
Wed Jun 10, 2020 11:47 pm
It turned out that Petitboot version 20200224 mounts all filesystems read-only. I can unmount them, but cannot mount again, because "the device is busy". It complicates things, because I used Petitboot to edit system files to fix a broken configuration.
What kind of configuration are you trying to fix if required?
I guess you can use ums that will turn a given device as a USB Mass Storage and connect with USB cable. Try to connect your ODROID-N2 with a USB cable (Type A-to-Type Micro B), and run ums /dev/mmcblk0p1 in order to attach the first partition of eMMC to your PC, for example.
The idea is to fix the system configuration without additional devices such as PC. I might as well insert the uSD card into the PC card reader and fix it there.
Understand, that makes sense. The reason why I suggest using a USB cable is that the Petitboot does not have many tools to manage the file system. :)

mad_ady
Posts: 8582
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 578 times
Been thanked: 486 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by mad_ady »

Well, you can fsck it, and if you need more stuff you can chroot into the regular system

Tassadar
Posts: 27
Joined: Sun Aug 18, 2019 7:04 pm
languages_spoken: english
ODROIDs: C2, XU4, N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Tassadar »

Tassadar wrote:
Thu Jun 11, 2020 2:21 am
Aha, the entries in the /dev/mapper/ directory must be used, i.e. for the first partition of the uSD card: /dev/mapper/pb-mmcblk1p1, not /dev/mmcblk1p1. The remount command works too, thanks mad_ady!
Another surprise: /dev/mapper/pb-mmcblk1p1 is a copy, not a real device. You can write to it, but all changes are silently discarded. Mounted /dev/mapper/pb-mmcblk1p1-origin for writing and it has worked, at last.

nicoraf
Posts: 12
Joined: Tue Dec 30, 2014 5:58 am
languages_spoken: english
ODROIDs: Odroid U3
Odroid N2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by nicoraf »

Hi, sorry I may ask again, are the sources of the latest image public ? I appreciate if you can share the link.

Thanks

Sholander
Posts: 155
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by Sholander »

@tobetter I have one peculiarity concerning my Petitboot (20200511):
On 3 SanDisk uSD card I have 3 working operating systems, CE 9.2.3, Android Pie (20200618_64) and AOSP Android 9.0 Android-TV (PIE-R.11). Along that I have CE9.2.3 installed on eMMC.

Peculiarity: Only uSD card with Android Pie (20200618_64) is not recognized by Petitboot, but normal boot works OK if eMMC is removed.
Other 2 uSD cards are recognized and work via Petitboot.

Is there anything I can try to fix this, so I don't have to pull out eMMC to work with this Android version?

EDIT: trying to manually add missing uSD card, selecting "Rescan devices" I get this error:
device-mapper: create ioctl on pb-mmcblk1p1-base failed: Device or resource busy

User avatar
tobetter
Posts: 6117
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 282 times
Been thanked: 791 times
Contact:

Re: Petitboot, yet another bootloader based on KEXEC

Post by tobetter »

Sholander wrote:
Sat Jun 27, 2020 10:50 pm
@tobetter I have one peculiarity concerning my Petitboot (20200511):
On 3 SanDisk uSD card I have 3 working operating systems, CE 9.2.3, Android Pie (20200618_64) and AOSP Android 9.0 Android-TV (PIE-R.11). Along that I have CE9.2.3 installed on eMMC.

Peculiarity: Only uSD card with Android Pie (20200618_64) is not recognized by Petitboot, but normal boot works OK if eMMC is removed.
Other 2 uSD cards are recognized and work via Petitboot.

Is there anything I can try to fix this, so I don't have to pull out eMMC to work with this Android version?

EDIT: trying to manually add missing uSD card, selecting "Rescan devices" I get this error:
device-mapper: create ioctl on pb-mmcblk1p1-base failed: Device or resource busy
I guess I missed the some changes on the new Android, I will look into it and let you know ASAP.

Post Reply

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 1 guest